Welcome Email for Nonprofits

A nonprofit welcome fires on the donor's first action: their first gift, a membership signup, or a petition signature. Send it within five minutes. The thank-you is the most opened message in a nonprofit program, often 50 to 70 percent open rates, because the donor just made a decision and is watching their inbox.

Lead with one impact number tied to the gift, not a mission paragraph. "Every $1 restores 4 sq ft of riverbank" beats "we protect local waterways." Generic mission copy reads like a brochure and gets skimmed. The donor wants to know what their specific gift just bought.

Write gratitude before the ask, in the mission voice. Name the place. The Coldwater. The east trail. The heron rookery. Donor-as-partner language ("you joined 3,400 members who...") outperforms donor-as-customer language ("unlock your member benefits") by a wide margin in nonprofit A/B tests. Corporate voice kills the warmth that made them give in the first place.

Push one next step. The best-performing nonprofit welcome converts a one-time giver into a monthly sustainer, because recurring revenue funds the operating budget. Sustainers are worth roughly five to eight times a one-time donor over two years. Secondary options are volunteering or sharing. Never stack three buttons; the click splits and the donor stalls.

Real copy from this template:

Subject: You're in. Here's what your gift just did. Preheader: Welcome to Riverbend Land Trust, {{ first_name|default:'friend' }}. Impact line: Every $1 you give restores 4 sq ft of riverbank. Sustainer ask: $8 a month buys a water test kit that lasts a full season. Trust line: 94 cents of every dollar goes to programs, not overhead.

Email is not a web page. It runs through four or five different rendering engines before it lands, each with its own quirks. This template is built to survive all of them.

Nested HTML tables, not divs or flexbox. Outlook, older Gmail, and several webmail clients only lay out tables reliably. Flex and CSS grid collapse or stack wrong.

Inline CSS on every element. Gmail strips the <style> block from the head for some accounts. Styles written inline on the tag survive that strip.

Bulletproof VML button for Outlook. Outlook 2007 through 365 on Windows render with the Word engine, which ignores CSS background colors and padding on <a> tags. A VML rounded rectangle forces the button to render in the right color and stay clickable. Without it, Outlook donors see a flat blue text link where the green button should be.

Live text instead of images. Every word is real selectable text, so screen readers, dark mode, and translation work, and the message lands when images are blocked by default (which they are in many clients).

Dark-mode color-scheme meta. The <meta name="color-scheme" content="light dark"> tag tells Apple Mail and Outlook to recolor the cream and dark backgrounds instead of leaving a bright white slab in a dark inbox.

One mobile media query. A single max-width:480px block bumps the headline to a readable size and drops side padding. More than one media query gets stripped by Gmail's CSS sanitizer.

Web-font fallbacks. The headline declares a web font with a full stack ('Source Sans 3', 'Helvetica Neue', Arial, sans-serif). Web fonts load in Apple Mail and a few others. Everyone else falls back to Helvetica silently, with no layout shift.

1. Export the HTML. Open the MJML below in the MJML web app or run it through the MJML CLI. Copy the rendered HTML.

2. Paste it in. Klaviyo: open your campaign or flow email, drag an HTML block into the canvas, and paste. For a full custom layout, go to Content, Templates, Create Template, and import the HTML. Mailchimp: Campaigns, Create, Email, then choose "Code your own" and "Paste in code."

3. Swap the brand. Replace "Riverbend Land Trust" with your org name. Change the four hex values: header and CTA green (#1f4d3a), cream body (#f7f3ec), dark footer (#23311f), and the muted footer text. Point every link at your own domain.

4. Wire the merge tags. These pull donor data from your ESP. Klaviyo: {{ first_name|default:'friend' }} for the name, {{ organization.Name }} for the org, and in a donation flow {{ event.Donation_Amount }} and {{ event.Donation_Date }}. Mailchimp: *|FNAME|* for the name, *|ORGNAME|* for the org, and for a connected donation integration *|AMOUNT|* or *|DONATION_AMOUNT|* (the field depends on your integration; confirm under Audience, Settings, Merge fields).

5. Test before you send. Send a live test to Gmail (web and the Android app), Apple Mail on an iPhone in dark mode, and Outlook 365 on Windows. If you have Litmus or Email on Acid, run a full render test. At minimum, check the button color in Outlook and the footer legibility in dark mode.