Email Copywriting: 7 Frameworks Beyond AIDA and BAB

AIDA and BAB are the two structures everyone learns first, and they're enough for a standard promo email. The problem shows up once you're writing thirty campaigns a quarter plus a dozen flows: the same four blocks keep coming back, the promise repeats itself, and the team ends up writing by feel because the structure no longer says anything new.

A copywriting framework isn't a technical standard. No vendor, no authority, publishes an official ranking of these methods or data comparing their performance. They're composition grids: they help decide in what order to lay out ideas, and give a shared starting point when several people write on the same account. Treat them as workshop templates, not as laws.

What is fully documented, on the other hand, is the frame your text will land in: what the inbox actually displays, what Gmail and Yahoo forbid, and what the CNIL requires. That's where most frameworks fall apart, and that's where we start.

Before the framework: the three constraints that decide the text

The inbox cuts off much earlier than you write

A framework structures the body of the email. But the recipient's first decision plays out on three elements: sender name, subject line, preview text. And the preview text gets truncated very early on mobile: 34 characters on Gmail iOS, well below most other email clients, according to Klaviyo's documentation on preview text.

In other words, your mobile hook is the length of a very short text message. A framework that plans two sentences of context before the benefit does not survive that display.

The first paragraph becomes the hook, whether you wanted it to or not

A critical point, systematically missed in audits: if no preview text is set, Klaviyo automatically displays the first line of body text in the inbox (Klaviyo source).

Direct consequence for the topic at hand: the first block of your writing framework becomes the visible hook. If your structure opens with a scene-setter ("You know that moment when..."), that's the 34-character fragment Gmail mobile will show. The framework doesn't apply to the body alone: it starts in the inbox.

What Gmail and Yahoo will never accept, whatever the framework

Several copywriting structures rely on curiosity or tension. Google's red line is explicit: subject lines, headers and display names must accurately represent the sender's identity and the message's content, without being misleading (Gmail sender requirements). Google specifically bans subject lines starting with Re: or Fwd: when the message is neither a genuine reply nor a genuine forward.

Yahoo holds the same line: no false or misleading headers, no deceptive subject lines (Yahoo best practices). Neither Google nor Yahoo impose a subject line length or format: the constraint is about truthfulness, not character count.

And the penalty is measurable. Google asks senders to keep their spam rate under 0.10% in Postmaster Tools and to never reach 0.30%. That 0.30% threshold has applied to all senders to Gmail accounts since February 1, 2024; beyond 5,000 messages a day, the sender must also authenticate their domain with DMARC and offer one-click unsubscribe. Yahoo asks senders to stay under 0.3% complaints and to honor unsubscribes within 2 days. A framework that wins you opens by overpromising costs you complaints, and complaints cost far more than opens are worth. Tracking happens in Postmaster Tools and Yahoo Sender Hub.

The CNIL framework, upstream of the text

No framework fixes a missing legal basis. In France, email prospecting to individuals requires free, specific, informed and unambiguous prior consent, evidenced by a dedicated, non-pre-ticked checkbox (CNIL, electronic prospecting). The existing-customer exception only applies if the person is already a customer and the prospecting concerns products or services similar to those already provided by the same company: simply creating an account is not enough.

Every message must state the identity of the person on whose behalf it is sent and offer an accessible unsubscribe option (CNIL golden rules). In B2B, the CNIL accepts legitimate interest when the subject of the solicitation relates to the professional role of the person being contacted.

The 7 frameworks, and when each one is the right choice

Here are the seven structures we rotate through on DTC accounts. None is endorsed by a vendor: they're working grids, and their merit is measured by your own tests, not by reputation.

1. PAS: problem, agitation, solution

Three blocks. Name a problem the reader recognizes, show what it costs if it persists, present the product as the way out.

When to use it: products that solve a concrete, identifiable pain point (discomfort, wasted time, upkeep, breakage). Excellent for a cart abandonment flow where the friction is a practical doubt.

Risk: agitation quickly slides into commercial anxiety. If the subject line promises a problem the body doesn't address, you fall into the misleading-subject-line territory banned by Google and Yahoo.

Preview text adaptation: never put the agitation phase in the first line. State the problem plainly from the first visible fragment.

2. PASTOR: problem, amplification, story, transformation, offer, response

The long-form extension of PAS, with a testimonial or story in the middle and an explicit call to action at the end.

When to use it: long, low-frequency emails. Product launches, founder emails, engagement campaigns to a warm list. The story block feeds naturally on customer reviews, and Klaviyo Reviews lets you inject those reviews into flows.

Risk: too long for a standard promo campaign. During BFCM, nobody reads six blocks.

3. FAB: features, advantages, benefits

Each product feature is translated into an advantage, then into a lived benefit. A mental-table structure, very mechanical, very fast to produce at scale.

When to use it: technical catalogs, spec-driven products (materials, composition, compatibility), range emails. It's also the best framework when several writers work on the same account, because it leaves little room for interpretation.

Risk: flat if you stop at features. The benefit has to be written out, not implied.

4. 4P: picture, promise, prove, push

Project a scene, state the promise, prove it (reviews, guarantee, verifiable product figure), push for action.

When to use it: products with a strong usage or mood dimension. Home, food, beauty, sport. The "prove" block is what keeps the promise from becoming misleading.

Risk: the "picture" is nice and eats up the entire mobile attention budget. Keep it in the body, never in the first fragment.

5. ACCA: awareness, comprehension, conviction, action

Establish the situation first, explain the mechanism, build conviction, ask for action.

When to use it: products that need explaining before purchase, subscriptions, offers with an unusual mechanic, secondhand, refurbished. Also useful in a welcome flow where the subscriber doesn't yet know the brand.

Risk: the educational tone turns into a lecture. Comprehension should serve the purchase, not replace it.

6. SLAP: stop, look, act, purchase

An ultra-short structure built for mobile. A hook that stops the scroll, a visual or offer that reads in a second, an action, a purchase.

When to use it: limited-time promo campaigns, end-of-sale reminders, second-wave BFCM sends. It's the framework most compatible with the 34-character truncation, because it plans no context-setting at all.

Risk: worn out if it becomes the only register. On a tired list, a string of SLAP sends feeds unsubscribes, a topic covered in our method to reduce your unsubscribe rate.

7. QUEST: qualify, understand, educate, stimulate, transition

Qualify who the email is for first, show you understand the situation, inform, stimulate desire, transition to the action.

When to use it: segmented emails, reactivation, B2B sequences, offers reserved for a subset of the list. The "qualify" block works all the better when it rests on real segmentation: see our 6 core segments for a DTC brand.

Risk: qualification turns into poorly worded exclusion ("this email isn't for you"). In practice, it should read as recognition, not as sorting.

Quick decision table

This table is a starting grid drawn from our agency practice, not a performance ranking. No vendor source lets you claim that any of these frameworks converts better than AIDA or BAB: your own testing program decides that.

Carrying the framework down to the subject line and preview text

Treat subject line and preview text as a pair

The classic mistake is writing the subject line from the framework, then leaving the preview text blank. Klaviyo will then pull up the first line of the body, meaning the first block of the framework. On a PAS structure, that displays the raw problem in 34 characters on Gmail mobile. Sometimes it works, often it doesn't.

The method we apply:

• Write the body with the chosen framework.
• Extract the idea from the first block and turn it into an explicit preview text, calibrated to keep its meaning within the first 34 characters.
• Check that the subject line and preview text don't say the same thing twice.
• Reread the whole thing asking whether a reader who doesn't open the email still understands what it's about.

Personalization: always set a default value

A first-name-personalized subject line with no fallback value produces an incomplete text for every profile with no first name on file. The syntax documented by Klaviyo is {{ first_name|title|default:'there' }} (Klaviyo source). Pick a fallback that keeps the sentence readable. The same reflex applies to every conditional block in the body, a topic covered in our Klaviyo dynamic content guide.

Generating variants without starting from scratch

Klaviyo's subject line assistant offers 3 options per request, regenerable at will (Klaviyo documentation). Useful for getting unstuck, provided you edit the output afterward: it's a starting point, not a subject line ready to send. On what AI actually contributes to email, we detailed our position in AI and email marketing.

Testing a framework without fooling yourself

This is the point that separates a useful framework rotation from a style exercise.

To test a subject line, preview text or sender name, Klaviyo recommends open rate as the winning metric and sticking to two variations, even though the interface lets you clone more (Klaviyo A/B test documentation). Two variations, one variable changed: that's the only way to attribute a difference to something.

Three field precautions:

• Don't test "PAS versus SLAP." Two frameworks vary the subject line, preview text, length, tone and offer all at once. You'll learn nothing. Test one variable: the subject line from framework A against the subject line from framework B, identical body.
• Watch how you measure opens. Apple Mail's privacy protection distorts open rate readings, a topic covered in our article on Apple MPP and the metrics to track. Open rate remains the metric Klaviyo recommends for this kind of test, but a small gap doesn't mean much.
• Watch complaints as closely as opens. A framework that gains 2 points of open rate while pushing the spam rate toward Gmail's thresholds is a net loss. The full testing method is covered in our Klaviyo A/B test guide.

Rotation, rather than a single framework

In agency practice, the question "what's the best framework" goes nowhere. The useful question is: how many different structures run on this account over a quarter, and does each email type have its own.

A reasonable starting point for a DTC brand:

• Transactional and post-purchase flows: FAB or ACCA, because information comes first.
• Recovery flows (cart, browse): PAS, short, one objection per email.
• Promo campaigns: SLAP, with a subject line that states the offer directly.
• Editorial campaigns: 4P or PASTOR, in limited volume.
• Reactivation and segments: QUEST, backed by real segmentation.

The rest comes down to execution: an honest subject line, a hand-written preview text, a default value on every variable, and complaint monitoring. If you want a second opinion on how your content rotation holds up on a real account, that's the kind of work we do at our Klaviyo agency.

FAQ

Which email copywriting framework converts best?

No vendor or normative source publishes data comparing these frameworks' effectiveness against each other, or against AIDA or BAB. They're composition grids, not certified methods. The only valid answer for your brand comes from your own tests, one variable at a time.

How many characters should an email subject line be?

Neither Google nor Yahoo impose or recommend a subject line length: their requirements concern the truthfulness of the subject line, headers and display name. The preview text, on the other hand, is truncated to 34 characters on Gmail iOS according to Klaviyo, and the limit varies widely from one email client to another: that's the constraint that should guide your writing.

Can you use a mysterious subject line to boost opens?

Not if it doesn't accurately represent the content. Google bans misleading subject lines, including fake Re: or Fwd:, and Yahoo bans deceptive subject lines. Beyond the principle, the cost is measurable: Google asks for a spam rate under 0.10% and never above 0.30%.

Should you fill in the preview text on every send?

Yes. Without a preview text set, Klaviyo automatically displays the first line of the email body. Your first writing block then becomes the inbox hook, without anyone having decided it should be.

How do you cleanly test two frameworks in Klaviyo?

Don't pit them against each other wholesale. Klaviyo recommends sticking to two variations and treats open rate as the winning metric for a subject line, preview text or sender name test. Isolate one variable, keep everything else identical, and watch complaints as well as opens.

Want a second opinion on your email copywriting rotation? Talk to the Deliver team.