Email Opening Lines: Patterns and Examples That Keep People Reading
A good email opening line does one job: it earns the second sentence. It is not a summary, not a greeting, and not a warm-up. The strongest email opening lines name something specific the reader recognizes — a date, an action, a detail from their own account — and create just enough forward pull that stopping feels like a loss. Below are eight opening-line patterns with worked examples, the reusable templates behind them, and the generic openers worth deleting on sight.
What Makes an Opening Line Work
Three levers do most of the work.
Specificity. A number, a name, a date, or a detail only this reader would recognize. "You looked at the annual plan twice this week" is specific. "We have great plans" is not. Specificity is what separates an opening line from a subject line restated.
Relevance. The line has to connect to something the reader actually did or signed up for. If the trigger is a download, the opener should reference the download. If it is a trial ending, reference the trial. Relevance is why behavior-triggered emails tend to feel more personal than batch-and-blast sends.
Momentum. A small open loop. A question the reader wants answered, a claim that needs support, a deadline that implies action. Momentum is the difference between "here is some information" and "here is the one thing you need before Thursday."
One structural note that gets missed: your opening line is read in the preview pane, right next to the subject line and preview text. If all three say the same thing, you have wasted two of them. The subject line makes the promise, the preview text adds a second hook, and the opening line should move the reader into the body — not repeat the pitch.
If you are drafting with AI, this is worth knowing: Mailerflow's AI email builder generates the design, subject lines, and preview text together from a description. That makes it easier to write the opening line as a complement to those two elements rather than a duplicate of them.
Email Opening Lines: Examples and Why Each Works
These are original, illustrative examples. Swap in your own specifics; the structure is what transfers.
Behavior-triggered
You looked at the annual plan twice this week, so here is the one question people usually ask before switching.
Why it works: names the observed action (specificity) and promises a single answer (momentum). It also pre-empts the objection instead of pitching around it.
Post-signup
Your trial ends Thursday. Here is what to do first if you only have ten minutes.
Why it works: a real deadline plus a bounded ask. The reader knows exactly how much time this costs them, which lowers the barrier to starting.
Re-engagement
You have not opened since March, so this is the last one unless you want to stay.
Why it works: it gives the reader permission to leave, which can prompt a reply from people who want to stay. It also protects your sender reputation, because unengaged contacts who opt out are better than contacts who keep ignoring you.
Content follow-up
You downloaded the pricing checklist. The second item is the one that trips most teams up.
Why it works: it references a specific asset and points at one item, not the whole list. The reader has a reason to open the file again.
Product update
The import screen now catches duplicate rows before they hit your list.
Why it works: it describes the change in terms of the reader's outcome, not the feature. No "we are excited to announce."
Founder note
I am writing this one myself because we changed something that affects your billing date.
Why it works: the human voice signals that the content is unusual enough to deserve attention, and the billing detail makes it relevant to everyone on the list.
Event follow-up
You asked about deliverability at the booth. Short answer: start with DMARC.
Why it works: it recalls a real conversation and answers the question immediately. The reader gets value in the first two lines.
Cart or browse abandonment
The size you picked is back in stock, and it usually goes within a day.
Why it works: it names the exact variant and adds a light scarcity signal grounded in something observable, not manufactured urgency. Treat the scarcity line as an example to adapt to your own restock data — only include it when the claim is true, and test whether it helps in your list before making it a default.
Behavior-based examples like these depend on having the data. Mailerflow's website-behavior tracking and dynamic segments are one way to get it, but the pattern works with any trigger source you already have — form submissions, order events, support tickets, or a field in your CRM.
Patterns You Can Reuse
The pattern gets you a decent line; the specific detail is what makes it land.
| Pattern | Template | Use when | Data needed | Caution |
|---|---|---|---|---|
| Specific Observation | "You [did X] on [date]." | You have a real behavioral trigger | Event or page-view data | Do not fake the observation |
| Deadline With a First Step | "[Thing] ends [when]. Start with [one action]." | Trial expiry, sale end, enrollment close | A real date | Only use deadlines that are true |
| Permission to Leave | "If [condition], ignore this; otherwise [value]." | Re-engagement, list cleaning | Engagement history | Expect unsubscribes; that is the point |
| One-Question Hook | "Most people ask [question] before [decision]. Here is the answer." | Considered purchases, onboarding | A known common objection | Answer it in the next line |
| Correction | "We got [thing] wrong. Here is what changed." | Bug fixes, policy changes, pricing errors | The actual change | Be specific about what changed |
| Named Detail | "The [specific item] you [action] is [status]." | Abandonment, restock, shipping | Item-level data | Keep the item name exact |
Two cautions that apply across all six. First, patterns become templates fast — if every email opens with "You looked at X," readers stop noticing. Rotate. Second, the pattern should never outrun the truth. A permission-to-leave line sent to an engaged segment reads as manipulative.
How to Build Your Own Opening Line
1. Write the second sentence first
Decide what the reader needs to know, then work backwards. If your second sentence is "the fix takes about four minutes," your opening line should set up why four minutes matters.
2. List the one true, specific thing you know
For this segment, what is the single most concrete fact? A trigger event, a date, a field value, a past action, a support ticket. If you cannot name one, the email is probably not ready to send.
3. Pick the pattern that fits the fact
A deadline fact maps to the Deadline pattern. A behavioral fact maps to Specific Observation. Do not force a pattern onto data you do not have.
4. Cut the first five words
Most first drafts start with throat-clearing. Delete the first five words and read it again. If it still makes sense, keep the cut version.
5. Read it next to the subject line and preview text
If all three say the same thing, rewrite one. Usually the opening line is the right one to change, because the subject line and preview text already did their job in the inbox.
6. Test one variable at a time
Change the opening line only, keep everything else identical, and compare. Mailerflow's A/B testing for campaigns handles the split, and dynamic segments let you isolate a behavior group so you are comparing like with like. If you want to see how those pieces fit together, the feature overview covers segmentation, automation triggers, and testing in one place.
Generic Intros to Cut
These openers delay the value and signal that the email is a template. Each one has a fix.
- "Hope you are doing well." → Cut it. Start with the reason you are writing.
- "I wanted to reach out." → "Your trial ends Thursday."
- "In today's fast-paced world." → Delete the entire sentence. It has never added information.
- "Just following up." → "You asked about X. Here is the answer."
- "We are excited to announce." → "The import screen now catches duplicate rows."
- "As you may know." → If they know, skip it. If they do not, state it plainly.
- "Quick question" (when it is not one) → Ask the actual question in the first line.
Readers often decide in the first line whether to keep going, so anything before the value costs you attention. These phrases show up often in AI-generated drafts, so if you are drafting with a model, review the first line specifically rather than accepting it as-is.
FAQ
How long should an opening line be?
One sentence, usually under twenty words. If it needs a comma splice and a subordinate clause to work, the idea is not clear enough yet. Short lines are also easier to scan in mobile preview panes.
Should the opening line repeat the subject line?
No. The subject line and preview text already made the promise in the inbox. The opening line should advance the argument, not restate it. If you cannot tell them apart, rewrite the opening line first.
Do opening lines matter for transactional emails?
Less, but not zero. A password reset should lead with the action, not a greeting. Where transactional emails carry a secondary message — a shipping delay, a plan change — the opening line is where you explain it before the details.
How do I write opening lines for a cold list versus an opted-in list?
For opted-in contacts, lean on what they did: a download, a trial, a past purchase. For cold lists, you usually have no behavior to reference, so lead with a specific, verifiable claim or a named problem. Be careful with cold outreach: relevance is doing all the work, and generic openers are more likely to be ignored or marked as spam.
If you want to skip the blank-page problem, describe the email you need and let the AI draft the design, subject lines, and preview text — then rewrite the opening line yourself using the patterns above. Generate a complete, on-brand email from a short description with Mailerflow's AI email builder — free plan available.
