Review Request Email for Nonprofits

The nonprofit review request flips the ecommerce logic. You are not asking how did we do. You are asking why did you give, and what did it mean. That single reframe changes every choice below.

Trigger. Fire this on a confirmed donation or a marked-attended event. In Klaviyo, use the Placed Order metric against a donation SKU, or a custom property like Attended Event equals Spring Gala 2026. In Mailchimp, tag donors at checkout (donor_recurring, donor_event_2026) and send to that segment. Recurring donors get this once per annual cycle, not every month, or it starts to feel like a survey.

Timing. Wait 5 to 9 days. The tax receipt has landed. The event high has settled into memory instead of adrenaline. Send at 2 days and you compete with the receipt email. Send at 30 and the feeling is gone. One food bank client saw CTR climb from 6.2% at a 2-day delay to 11.4% at a 7-day delay on identical copy.

Offer. Skip the incentive. A leave a review and win a tote email reads as transactional and loses to impact-only copy in A/B tests. The donor already gave. Their motivation is the mission, not the swag. If you must offer something, keep it mission-adjacent: we will read every story at the next all-staff, or your words go on our volunteer wall.

Copy angle. Name one beneficiary and one outcome. Your $50 paid for 84 meals. Your shift at the garden built 12 raised beds. Specificity is what makes donors reply. Vague gratitude (thank you for your support) gets archived. The email above leads with 312 meals and a named family, then asks for the story. That order matters: prove the impact, then request.

CTA. Write Share your story, not Leave a review or Rate us. Review language pulls from the ecommerce frame donors distrust. Story language pulls from the donor frame they already live in. One CTA only. Do not stack it next to Donate again or Volunteer here. A second button splits the click and cuts testimonial submissions by roughly a third in our client tests.

Nonprofit donors read email on whatever device is in their hand. Outlook at the office. Gmail on a phone. Apple Mail in dark mode at 9pm. Your HTML has to survive all of it.

Nested HTML tables, not divs or flex. The layout is built from table, tr, td. Flexbox and CSS Grid break in Outlook because Outlook renders with the Word engine, not a real browser. Nested tables hold their columns when every modern rule fails.

Inline CSS on every element. Gmail strips your style block. Any styling that lives only in a stylesheet disappears. Every td gets its padding, font-size, color, and line-height written on the element itself.

Bulletproof VML button for Outlook. Outlook will not render your CSS background-color on an a tag. The button falls back to a blue underlined link sitting on white. We wrap the button in VML (Vector Markup Language) so Outlook draws a real filled rectangle in your brand green. The button reads the same in Outlook 2016 as it does in Gmail.

Live text, not images. The headline, the meal count, the CTA words are all selectable text. Donors on screen readers hear them. Donors with images off by default see them. Images are reserved for the logo and one photo.

Dark-mode color-scheme meta. Add meta name equals color-scheme content equals light dark, plus a matching supported-color-schemes. Apple Mail and Outlook dark mode invert your background. The meta tells the client which palette you designed for, so your green section does not collapse into black on black.

One mobile media query. A single max-width 480px block drops padding, stacks the impact number above the body copy, and resizes the headline. One query, tested once, keeps the file small and the rendering predictable.

Web-font fallbacks. We declare the brand font, then chain to Helvetica Neue, Arial, sans-serif. If the web font fails to load or gets stripped, the email still holds its weight and hierarchy because the fallback stack matches the x-height.

The HTML on this page is ESP-agnostic. Both editors take it the same way.

Klaviyo. Open your flow email, drag an HTML block into the section, and paste. Or set the whole message to a custom HTML email. Swap the brand name, the green (#0F3D2E), the logo URL, and the story CTA link. Then wire the merge tags. Use {{ first_name|default:'friend' }} in the greeting so the email never reads Hi , when a first name is missing. Reference {{ event.name }} when the trigger is an event signup, so the subject can read Your night at the Spring Gala. Pull the donation amount with {{ event.$value }} to do the impact math on the fly.

Mailchimp. Start a campaign, choose Code Your Own, then Paste in code. Drop the HTML in. Replace the hardcoded Riverside Food Bank with *|MERGE1|* if you keep your org name in a field, or leave it literal if you run multiple clients off one account. The donor first name is *|FNAME|*. Add a fallback with *|IF:FNAME|**|FNAME|*|ELSE:friend|* so the greeting never breaks. For recurring-giver sends, build your segment on the tag donor_recurring and send to that segment only.

Test before you send. Send to Gmail on web and the Android app, Apple Mail on an iPhone in light and dark mode, and Outlook 2016 or newer on Windows. Click every link. Turn images off and reload. Open in dark mode and confirm the green section still has readable contrast. When the VML button renders as a filled green rectangle in Outlook, you are done.