Write honest subject lines for announcements, onboarding, newsletters, and offers, then test them against useful outcomes rather than opens alone.
A subject line should help the reader decide whether the email matters now. It does not need to win a cleverness contest.
The easiest improvement is often specificity. "Your August usage report" gives someone more information than "Big news inside." The subject and the first screen of the email should make the same promise.
These are writing examples, not measured winners. Replace the details with facts from your own message.
| Situation | Subject | Why it fits |
|---|---|---|
| A requested report is ready | Your August report is ready | Names the deliverable and period |
| A new feature for existing users | Compare two drafts side by side | Describes the capability |
| A setup reminder | One step left to connect your store | Useful only if exactly one step remains |
| A newsletter | Three checkout emails worth studying | Sets a concrete expectation |
| An event reminder | Tomorrow: the onboarding workshop | Gives timing and context |
| A genuine offer deadline | Your workshop discount ends Friday | Appropriate only when the deadline is real |
| A feedback request | What stopped you from finishing setup? | Opens a relevant conversation |
| A product change | What changes on your next invoice | Makes an account change easy to recognize |
Avoid fake Re: and Fwd: prefixes. Do not imply that a teammate wrote personally when the message is a mass campaign. A short-term lift is not worth teaching people to distrust the sender.
Most subject lines follow one of a handful of shapes. A pattern gives you a first draft to edit. Pick the one that fits what the email actually contains. The examples are illustrations.
| Pattern | Shape | Example |
|---|---|---|
| Number | A count and a concrete topic | 5 fixes for a slow checkout page |
| How-to | A task the reader already has | How to import contacts without losing unsubscribes |
| Question | A question the reader might ask themselves | Which weekly report do you actually read? |
| Curiosity | A specific gap that the email closes | Why your welcome email lands in Promotions |
| Personal detail | A name plus something that belongs to that person | Priya, your workspace export is ready |
| Deadline | A real date or cutoff | Registration for Thursday's workshop closes tonight |
| Proof | A source or result the body can back up | What customers asked for in this release |
| Benefit first | The outcome before the feature | Send the weekly report without opening a spreadsheet |
| Announcement | A label and the new thing | New: pickup lockers at the Main Street store |
| Plain label | Exactly what the email contains | Your March invoice |
Curiosity and deadline lines carry the most risk. A curiosity line has to be answered in the first screen of the email. A deadline line is honest only when the deadline exists and applies to the person reading it.
These lines are also illustrations. Replace the details with facts from your own message, and drop any line whose claim is not true for every recipient.
The abandoned cart guide covers when a reminder helps and when it becomes pressure.
A line such as "You asked for dark mode" is fine when customers did ask. If nobody requested the feature, describe it instead.
The preview should add information. If the subject names a new report, the preview can explain what it contains or where to find it. Repeating the subject wastes the space.
Do not depend on an exact character limit. Mail clients, devices, font sizes, and sender names change how much text appears. Put the useful words near the beginning and inspect a real mobile inbox.
Personalization helps only when the underlying data is reliable and the detail matters. Test missing first names and other fields. A broken placeholder is more memorable than an ordinary subject.
Choose a hypothesis. For example, will naming the product task attract more relevant visits than announcing a generic update? Keep the audience, body, and send window comparable while testing that difference.
Define the outcome and observation window before sending. Sample size depends on the baseline rate, the smallest effect worth detecting, and the statistical power you need. There is no universal rule that 1,000 recipients makes a result significant.
Opens can be distorted by privacy features. Prefer a relevant click or downstream action when it fits the test. If the interval around the result is wide, record it as inconclusive instead of manufacturing a winner. The A/B testing guide works through this choice.
A subject that attracts the wrong reader can raise opens while lowering trust. Check replies, unsubscribes, and completion of the intended action alongside any lift.
Use the email writing guide to connect the promise to the body. For automated messages, confirm that the promised next step is still relevant when the email sends.
In the US, the FTC's CAN-SPAM compliance guide says a commercial email's subject line must accurately reflect the content of the message. Run through this list before each send.
Re: or Fwd: prefix.