Rules
Part of Email copywriting for people who want the details
Email copywriting best practices: a pattern for offers
Email copywriting best practices as a fill-in pattern for an offer email: what each bracket needs, the proof to attach, and when to hold the send.
What to take away
- Draft an offer email from a placeholder pattern, and replace every bracket with verified information before sending.
- A bracket that cannot be filled is a reason to hold the send or cut the line, never to write around it.
- Keep claims, proof, material terms and the call to action close enough to be judged together.
- Include a valid physical postal address and a working opt-out, and honor opt-out requests.
The pattern, line by line
Use this placeholder-based offer email as a drafting pattern. Each line has one job, and each bracket marks a fact that someone has to supply and check.
- Subject:Your [product] offer, with full terms
- Preview:See what's included, the price, and renewal details.
- Opening:You're receiving this because [accurate reason tied to signup or purchase].
- Body:[Product] includes [verified feature]. It costs [price and currency]; [renewal, fees, eligibility, deadline, and cancellation terms].
- Proof:[Name the review source, testimonial, or study and state exactly what it supports.]
- CTA:Review the offer and terms.
- Help:Questions? Reply to [monitored address].
Fill the brief before the brackets
A bracket can only be filled from facts, so the writer needs verified facts before the first draft. State the audience, situation, message type, sender, market, useful decision, responsible non-action, constraints, guardrails and mature outcome.
Define the decision first
- Audience and situation
- Message type and sender
- Market and useful decision
- Responsible non-action
- Constraints and guardrails
- Mature outcome
Give the writer a complete offer as well. Broader guidance on voice and structure sits in the email copywriting guide, while the pattern here only covers the offer email.
What each bracket needs
| Bracket | Fill with | Evidence to attach | If it is missing |
|---|---|---|---|
| [product] and [verified feature] | The actual product and a documented feature | Product facts | Cut the line |
| [price and currency] | The verified price | Price source, date | Hold the send |
| [renewal, fees, eligibility, deadline, cancellation] | Every material term | Approved terms | Hold the send |
| [accurate reason] | The real signup or purchase link | Signup or purchase record | Change the reason |
| [review source, testimonial, or study] | The named source and what it supports | Source, scope, disclosure | Remove the proof line |
| [monitored address] | A reply-to someone reads | Named owner | Fix before sending |
Keep terms beside the promise
Show price, currency, dates, availability, renewal, eligibility, exclusions, required purchase, delivery, cancellation and material fees where the reader needs them. A qualification should clarify the offer, not contradict it.
For example: "Today: [price and currency]. Renews at [amount and frequency] unless canceled; [fees and exclusions]. Offer ends [date and time]." Replace every bracket with verified terms before sending, and let the terms sit in the same block as the price they qualify.
Let the journey stage shape the opening
The opening line depends on where the subscriber is. A welcome email can explain why the subscriber is hearing from you, and a post-purchase email can clarify next steps. A renewal or win-back email can make current terms and choices clear.
Keep the sender recognizable across the From name, sending address, monitored reply-to, subject, preview, opening, body and destination. Avoid fake replies, official-looking disguises, invented relationships and subjects that do not reflect the message.
Attach proof that says only what it can
Useful proof can include a named review source, a testimonial with its source and any relevant disclosure, or a study citation that identifies its method and population. State only what the evidence supports, and do not turn a possible outcome into a personal guarantee.
For testimonials, the FTC says it investigates and brings cases involving endorsements made on behalf of an advertiser under Section 5 of the FTC Act, which generally prohibits deceptive advertising. Keep the evidence and any necessary disclosures close to the claim they support.
Opt-out, address and authentication
Include a valid physical postal address and a clear, working opt-out, and honor opt-out requests. The FTC's CAN-SPAM guide states that your message must include your valid physical postal address. The CAN-SPAM duties apply to commercial messages sent to US recipients.
A preference center can let subscribers choose message types. SPF, DKIM and DMARC support email authentication, and BIMI can display a brand logo where supported, but none of these verifies an offer claim. Personal data in the copy should follow the California privacy rules where those subscribers are in scope.
Test the filled template
Test the copy in the real template, client, data state, device, language and destination before release. Check rendering in Gmail, Outlook and Apple Mail. Tools such as Litmus and Email on Acid can support previews, but they do not replace assistive-technology checks.
Use WCAG 2.2 as an accessibility reference, and review subject, preview, body, links, expired offers, mobile layout, blocked images, zoom and keyboard access. Layout and accessibility problems often show up only after the brackets are filled with real, longer text.
Preserve the brief, sources, claim evidence, writer, reviewers, approved copy, audience, version, destination, exposure, result, expiry and rollback. Refresh the message when product facts, price, evidence, rules, customer state or automation changes, so the filled pattern never outlives its facts.
Common questions
Can a bracket stay in the sent email?
No. Every bracket is replaced with verified information, and an empty one means the send waits or the line is removed.
Should benefits appear before features?
Use the order the reader needs. State the relevant outcome, then provide the feature, evidence, term or limitation required to evaluate it.
Can the pattern replace user testing?
No. It organizes the work. Representative readers and production-like systems still need to test comprehension, accessibility, rendering, action and outcome.
