Key takeaway
An email example is a real send: a trigger, an audience, a message, and a next step. A screenshot carries one of those four, which is why a gallery is inspiring and hard to act on. Restate any example as the four facts and you can build it. The part nobody photographs is the floor all of them clear: an opt-out that works on the first click, actioned before the next send. I'd copy the trigger before the layout.
We also keep a library of 12,711 real emails collected from two ordinary inboxes, filterable by type, industry, design style and layout.
What an email example actually is
An email example is a real send someone can point at: the message a brand put in an inbox, at a moment it chose, to a group it picked. A screenshot isn't that. It's a photograph of the last step, and the send behind it is four things: the trigger, the audience, the message, and what happens next, of which exactly one survives the picture. I get asked for these most weeks, nearly always in the form "send me one that looks like this", and the work that follows is never the design. It's rebuilding everything the picture dropped.
Almost every page ranking for this phrase is built the same way. Brand name, screenshot, then fifty to a hundred and fifty words on why it works. That's a good thing to read when you're deciding what an email should feel like, and it's close to useless at the moment you sit down to build one, because the facts you have to type into a platform aren't in the frame.
Most of the examples in circulation come from senders with six-figure lists and years of behavioural data behind the segment. The same handful of very large consumer brands turns up on nearly all of those pages. The email is copyable. The conditions that produced it usually aren't, and list size is the thing that decides which of the two you're looking at.
The four parts of a reproducible example
Restating an example as something you could build takes four facts, and they fit in a sentence each. They're the same four any platform asks you for, in roughly the same order, and they're also the whole of what an agent needs to be told. Four facts is a send you can issue as one command; anything less is a screen you have to sit in front of.
- Trigger: the event or the date that fires the send, from a signup to an abandoned cart to a Tuesday morning.
- Audience: the segment the trigger is scoped to, which is what keeps the send off people it would annoy.
- Message: the subject line, the one thing you're asking for, and the single call to action that asks for it.
- Next step: what runs if the reader does nothing, and what stops the sequence the moment they act.
Miss one and the example stops being reproducible, because the same message on the wrong trigger is noise and on the wrong audience it's a complaint.
Six examples, written as specs
These six cover the lifecycle from signup to lapse, and between them they account for most of what any email programme runs. Each is written as the four parts rather than described as a picture. The delays are the ones in common use, and they're the first thing to change once you've seen your own numbers.
| Example | Trigger | Audience | Message | Next step |
|---|---|---|---|---|
| Welcome | Confirmed signup, within a minute or two | Everyone who just opted in, no segment yet | What they'll get, how often, one action | Second message two to three days later introduces the product |
| Abandoned cart | Cart with no order, after a set delay, commonly an hour | Excludes buyers and anyone in another sequence | Names the item, links back to the cart | Second around four hours, third around 24, stops on order |
| Order confirmation | The order itself | One person, no segment | Order number, what was bought, ship date, one secondary item | None, it's transactional |
| Re-engagement | No open, click, or order in ninety days | Everyone the condition catches, minus unseen-channel buyers | One question, one way to answer | Sequence ends in removal |
| Product launch | A date, not an event | Bought the adjacent product, browsed the category, asked to be told | Leads with what changed, one link | Second send days later to non-openers, new subject line |
| Newsletter | A schedule, weekly or monthly | Needs regular pruning of off-topic signups | One call to action at the end | None, it recurs on schedule |
Welcome
Fires on a confirmed signup and lands within a minute or two, while the person is still on the site. The audience is everyone who just opted in, so there's no segment to get wrong yet, which is why it's the one to build first. The message does a single job: say what they'll get, how often, and the one action worth taking now. A second message two or three days later is where the product goes. A welcome that arrives an hour late has lost most of what made it work.
Abandoned cart
Fires on a cart with no order behind it after a set delay, commonly an hour. The audience is where these go wrong: exclude anyone who already bought, anyone who bought something else since, and anyone sitting in another sequence. The message names the item and links straight back to the cart. A second goes around four hours later, a third around 24, and the sequence stops the moment an order lands. That cadence isn't arbitrary: testing on real cart-recovery mail found conversions drop off sharply past the first day, which is the case against stretching a third send to 48. No cart event reaching the platform means no cart email, whatever the builder looks like.
Order confirmation
The order itself is the trigger, it goes to one person, and it needs no segment. It's the highest-attention message most brands ever send and routinely the one nobody edits, going out as whatever receipt the platform shipped with. It owes the reader an order number, what was bought, and when it ships, and it can carry one secondary thing under that. This is transactional email, and stapling a promotion to it changes what the message is, which changes the rules it's sent under.
Re-engagement
Absence is the trigger rather than an action, which is what makes it harder to build than the rest: no open, no click, and no order in ninety days, and the platform has to be able to ask that of its own data. The audience is everyone the condition catches, minus anyone who bought through a channel it can't see. The message asks one question and offers one way to answer. The sequence ends in removal, and if you don't remove them, you haven't run it.
Product launch
Fires on a date rather than on an event, which sounds like the easy case and isn't, because the whole thing rests on the audience. Segment on who bought the adjacent product, who browsed the category, and who asked to be told. The message leads with what changed and carries one link. A second send goes a few days later to whoever didn't open the first, same offer, new subject line. A launch mailed to the whole list is an announcement, not a campaign.
Newsletter
A schedule is the trigger, weekly or monthly, which makes it the easy part; the audience is the hard one. A newsletter list quietly accumulates people who signed up for something else, and mailing all of them is how a complaint rate climbs. The message is the thing you actually wrote, with one call to action at the end rather than five scattered through it. The schedule tells you when to send and nothing at all about what belongs in it.
The other two things people mean by this
A second population searching this phrase wants a one-to-one professional email: an apology, a follow-up after a meeting, an introduction between two people, or a request for someone's time. Those are written by a person to one other person, and they're judged on tone and timing rather than on segmentation. None of the four parts above helps you write an apology. There's no trigger and no audience, just a sentence you have to get right.
A third group wants email address formats, which is a naming convention for the mailboxes a business publishes rather than a message anyone sends. Both halves of the phrase are ordinary English words, which is why one page has to serve three questions. If you're building sends, the four parts above are the only part of this page that's yours.
What a "why it works" caption can't tell you
Read enough of these captions and they resolve into the same three claims: strong subject line, one clear call to action, and on-brand design. All three are usually true. None of the three is measurable from a picture, and the number the captions lean on to prove them is the open rate.
The open stopped being a clean signal when Apple shipped Mail Privacy Protection. Apple's own documentation is plain about what it does: Mail hides the reader's IP address from senders, and it downloads remote content in the background when the message is received rather than when someone reads it. The remote content in question is the tracking pixel every open rate is built on. A caption quoting an open rate is therefore describing a mixed population of people and prefetchers, in a ratio that depends on what that brand's readers happen to use.
What survives better is the click, the reply, and the order, because a person has to do those. Security filters do fetch links ahead of a reader (Microsoft's Safe Links scans the URLs in a message before it is delivered), so a click figure carries some machine traffic too, but a reply and an order need a human hand, and a click is much closer to one than an open is. If you're going to lift one number off an example, lift the click, and treat any caption whose only evidence is an open as an opinion about the design.
Clicks are only measurable if the send is instrumented, and instrumentation is the part nobody copies. Tagged links, a campaign name that survives into the analytics, and something at the other end that records the order are what make an example answerable, and not one of them is visible in the frame.
The floor every one of these examples already clears
Every email on every one of those pages shipped with four things the screenshot can't show, and none of them is optional. All four are what the mailbox providers require for getting delivered at all, so copying the layout and skipping these means you've copied the visible half. Working through them takes an afternoon once, and then they apply to everything you send afterwards.
- A working unsubscribe: one click, no confirmation page, no login, and nothing asked for beyond the click itself. Yahoo asks bulk senders to action it within two days.
- One-click unsubscribe in the headers: an HTTPS
List-UnsubscribeURL alongsideList-Unsubscribe-Post: List-Unsubscribe=One-Click, the pair RFC 8058 defines, required of marketing and subscribed mail once you are sending in bulk. - Authentication and a spam-rate ceiling: SPF and DKIM on the sending domain, with DMARC alongside them once you are sending 5,000 or more messages a day to Gmail, and the spam rate Google Postmaster Tools reports kept below 0.10%, never reaching 0.30%, per Google's sender guidelines.
- An honest header and a real sender: accurate From and Reply-To fields, a subject line that describes what's inside, and a company somebody can place from the footer.
None of that is design work, and all of it is the difference between an example that lands and one that gets filed. the floor decides whether a send is accepted, not whether it was worth making. Clear all four and mail the wrong segment and you're delivered to people who complain, which walks you straight back to the spam rate you just capped.
Turning an example into something that runs
Four parts written down is a specification, and a specification is something you can hand over. That's the practical difference between the two ways of describing an email. A picture has to be interpreted by whoever rebuilds it, which is why the version that ships never quite matches the one that was admired. Trigger, audience, message, and next step can be read once and built the same way twice.
More examples die in the gap between seeing one and having it live than anywhere else, and I find the gap is almost always the builder rather than the idea. Nitrosend is MCP-first: every capability is an API endpoint and an MCP tool before it's a screen, so the spec you just wrote is close to the instruction you'd issue. An agent added to a dashboard afterwards is a different thing, because it can only reach the buttons somebody already drew a screen for, and the sends it can build are the ones that screen anticipated. Nitrosend specialises in email, so that surface covers all six of the sends above.
The spec still needs data under it. A cart trigger needs the cart event to reach the platform, a re-engagement trigger needs a real last-open date, and no amount of automation invents either one.
If you've spent an afternoon looking at emails you can see and can't build, take one of the six above and put it in front of a real list this week. The free tier runs to 8,000 emails to start and 500 a month after that, with unlimited contacts and the MCP, API, and CLI switched on without a card. Build the welcome first, watch it for a week, and let what you learn decide the second one.
Go deeper
Sources
- Google, Email sender guidelines: SPF, DKIM, and DMARC on the sending domain, one-click unsubscribe for marketing and subscribed mail, and the spam-rate thresholds in Postmaster Tools, 0.10% and a 0.30% ceiling.
- RFC 8058: Signaling One-Click Functionality for List Email Headers, the standard behind the HTTPS List-Unsubscribe URL and the List-Unsubscribe-Post header pair.
- Apple, Use Mail Privacy Protection on Mac: Mail hides the reader's IP address from senders and downloads remote content in the background when a message is received rather than when it's viewed.
- Microsoft, Safe Links in Defender for Office 365: URLs in a message are scanned before the message is delivered, and links without a valid reputation are detonated in the background, so a recorded click can be machine traffic.
Common questions
One you can rebuild. That means it arrives with four facts: the trigger that fired it, the audience the trigger was scoped to, the message and its single call to action, and what runs next if the reader does nothing. A screenshot gives you the message and hides the other three, so the useful examples are the ones written out as a specification rather than photographed.
Welcome and order confirmation, in that order. Both fire on a single event, neither needs a segment, and between them they're the first two emails most of your list will ever get from you. Abandoned cart is the natural third if you sell anything, because it's the one with money attached. Newsletters and launches are harder than they look, because the work in both is the audience.
Public galleries archive them. Really Good Emails, MailCharts, and Milled all hold large searchable collections of real sends, and Milled indexes them straight out of inboxes. They're genuinely useful for design and subject lines. What none of them records is the trigger behind a send or the segment it went to, so treat a gallery as a mood board and write the spec yourself.
Copy the structure, not the artwork or the words. Layout patterns, the position of a single call to action, and the order the information appears in are all fair to reuse. The copy, the photography, and the illustrations are somebody's work and often somebody's trademark. The better reason to rewrite is practical anyway: their subject line was written for their list, and yours isn't their list.
Accurate From, Reply-To and routing information. A subject line that describes what's inside. A sender the reader can identify and reach. A one-click unsubscribe that works on the first click, with no confirmation page and no login. And suppression that takes effect before the next send rather than at the next export.
Not on their own. Apple's Mail Privacy Protection downloads remote content in the background when a message is received rather than when it's read, and that remote content is the pixel an open rate counts. A reported open is now a mix of people and prefetchers, in a ratio nobody outside that sender can work out. Clicks, replies, and orders still mean what they always did.
Two to three each is the common shape. A welcome goes immediately, and a second message follows two or three days later once there's something to say about the product. Cart recovery runs at roughly an hour, 24 hours, and 48 hours, and stops the instant an order lands. A fourth rarely earns the complaints it costs, and the exclusions matter more than the count.
Both, and the results mix them. Most people typing it want campaign examples: welcome emails, cart recovery, launches, and newsletters. A second group wants a one-to-one professional email, an apology or a follow-up after a meeting. A third wants address formats like sales@ or firstname.lastname@, which is a naming convention rather than a message. Work out which of the three you're after first.