A hook is the first 40–60 characters of your email — subject line plus preheader — that give a reader a specific reason to open right now. It works when it names a concrete outcome, a deadline, or a question the reader already has. It fails when it describes the email instead of earning the click.
Why This Matters
The inbox is a cost-benefit decision made in under two seconds. Your reader scans sender name, subject line, and the grey preheader text next to it. If those three elements don't promise something specific, the email becomes unread archive.
Email marketing returns around $36 for every $1 spent, according to widely cited Litmus and DMA benchmarks — confirm current figures before you quote them in a deck. That number is real, but it's an average, and averages hide the split. A list with a strong hook culture opens at 30%+; a list sending "Newsletter #47" opens at 12%.
Consider a founder running a 4,000-person list. She rewrites one subject line from "Quick update" to "Your invoice template is inside" and open rate moves 9 points in a week. Nothing else changed. Same send time, same list, same offer.
What Makes an Email Hook Actually Work?
A working hook does three jobs in one line: it names a specific person or situation, it promises a concrete payoff, and it creates mild time pressure. Miss any one and the reader defaults to skip. The strongest hooks pair a real number or named entity with a plain-spoken verb.
Specificity beats cleverness every time. "Cut your onboarding time" is vague. "Onboarding in 3 emails instead of 9" is a hook. The second version tells the reader exactly what changes and how much.
Length matters more than people admit. Mobile clients truncate subject lines around 35–45 characters on iPhone, and Gmail clips the preheader at roughly 100 characters. Front-load the payoff. If your best phrase sits at character 60, most readers never see it.
A useful pattern: [specific noun] + [unexpected verb] + [concrete outcome]. "Your welcome email is scaring people off" fits. So does "The subject line that beat our control by 2x."
Which Subject Line Formulas Actually Get Opened?
Four formulas carry most of the load: the curiosity gap, the named outcome, the direct question, and the pattern interrupt. Each fits a different send type. Match the formula to the email's job — announcements reward clarity, re-engagement rewards curiosity.
| Formula | Best for | Example shape | Watch out |
|---|---|---|---|
| Curiosity gap | Re-engagement | "We changed one thing" | Feels clickbait if body doesn't deliver |
| Named outcome | Promotions, launches | "Your Q3 report is ready" | Generic if the outcome is soft |
| Direct question | Surveys, replies | "Still using spreadsheets?" | Weak if the answer is obviously no |
| Pattern interrupt | Cold or dormant lists | "Ignore this if you're set" | Backfires without real relevance |
Test one variable at a time. If you change subject line and send time together, you learn nothing. Tools like Klaviyo and Mailchimp let you run A/B tests on subject line alone, and the winner usually reveals which formula your list responds to. Keep a running log of winners — after 20 sends you'll see a pattern no blog post can give you.
How Do You Write a Preheader That Doesn't Waste the Hook?
The preheader is the second half of your hook, not a summary. Most senders let it auto-fill from the first line of body copy, which usually produces "View this email in your browser" or a repeated subject line. Write it manually. It should extend the subject line's promise, not restate it.
If your subject is "Your invoice template is inside," the preheader should add the reason: "Free, editable, works in Google Sheets." That combination answers what and why in one glance.
Gmail and Apple Mail both pull the first ~100 characters of preheader text, so the payoff has to sit up front. A common failure: writing a beautiful subject line and then letting the preheader say "Hi [First Name], hope you're well." That greeting eats the entire preview.
Set the preheader as a hidden field in your ESP — Klaviyo, ConvertKit, and HubSpot all support a dedicated preheader slot. If you skip it, the client grabs your first body line. Fill the slot every time.
What Do Most People Get Wrong About Email Hooks?
The biggest mistake is optimizing the subject line while ignoring the sender name and the first body line. All three are read as one unit. A brilliant subject line from "noreply@company" lands worse than a plain subject from a name the reader recognizes.
The second mistake is writing the hook before the email. If you don't know the single action you want, the subject line has nothing specific to promise. Write the CTA first, then reverse-engineer a hook that makes that CTA feel inevitable.
The third mistake is treating personalization as a first-name merge tag. "Hi Sarah" doesn't create relevance; referencing Sarah's last purchase does. Behavioral hooks — "Your trial ends Thursday" — outperform name tokens because they carry information the reader didn't have to supply.
This misconception persists because merge tags are easy and behavioral data is hard. One requires a field; the other requires your ESP to talk to your product. That's why the lazy version wins by default, and why the teams that do the work see open rates other lists can't reach.
Key Takeaways
- A hook is subject line plus preheader working together — never write one without the other.
- Front-load the payoff: mobile truncates around 35–45 characters on the subject line.
- Match the formula to the email's job; curiosity gaps fail on transactional sends.
- Sender name and first body line are part of the hook, not separate from it.
- Test one variable at a time and keep a log — patterns emerge after about 20 sends.
Frequently Asked Questions
How long should an email subject line be?
Aim for 35–45 characters so it survives iPhone truncation. Gmail desktop shows more, but mobile is the constraint. Put the specific payoff in the first 30 characters and treat anything past 45 as bonus for desktop readers.
Should I use emojis in subject lines?
Only when the emoji carries meaning. A calendar emoji before a date works. A random fire emoji next to "Newsletter" reads as noise. Test on a segment first — emoji performance varies wildly by audience and industry.
What's the difference between a hook and a subject line?
The subject line is one component. The hook is the full first impression: sender name, subject line, preheader, and the first visible line of body copy. Optimizing only the subject line leaves three-quarters of the hook unmanaged.
Can a great hook fix a bad email?
No. A hook that overpromises trains readers to distrust your sender name. If the body doesn't deliver what the subject promised, the next send opens worse. Fix the email first, then sharpen the hook.
How often should I test subject lines?
Every send is a test opportunity, but only run one variable at a time. If your list is under 1,000 subscribers, batch tests across weeks instead of splitting a single send — small samples produce noise, not signal.
Your Next Step
Open your last sent campaign and read the subject line, preheader, and sender name as if you were a stranger. If you can't name the specific payoff in three seconds, rewrite the preheader tonight using the hidden field in your ESP. One edit, one send, and you'll have your first real data point on what your list actually opens for.