If you run quiz funnels, most revenue is won after the first visit: the user leaves an email, thinks it over, compares options, and comes back (or doesn't). A well-built email sequence keeps the conversation going — with the right message at the right moment.

Generate with AI helps you draft that entire sequence quickly. You describe who you're talking to and what each email should say; web2wave writes the subject lines and HTML. Everything lands as drafts so you can edit, translate, and activate when you're ready.

Email sequences are available on the Advanced plan. For how triggers, delays, and stop conditions work after activation, see Email sequences.

Where to find it

Open your project in the cabinet.
Go to Email Sequences.
Click 🪄 Generate with AI.

You can start from scratch or load one of the built-in sequence templates (see below).

How generation works (step by step)

1. Choose the project

Pick the project whose quizzes, paywalls, and branding should drive the sequence. Quiz and paywall pickers unlock after you select a project.

2. Set the visual style

Emails can match your funnel look:

Auto-detect — web2wave picks a style that fits your niche.
Preset styles — e.g. Fresh Minimal, Classic Professional, Soft Modern, Calm & Airy.
From quiz / From paywall — colors and typography are taken from a specific quiz or paywall in the project.

The generator also creates a header image for each email in your project's visual style.

3. Describe your target audience (once for the whole sequence)

Tell the AI who these emails are for. This description applies to every email unless you override it on a specific step.

You can:

Write it manually — e.g. "Women 30–45 who want to lose weight without strict diets" or "Busy professionals improving business English for promotions".
Infer from a quiz — web2wave reads your quiz and suggests an audience profile (who they are, what they want, what's holding them back).
Infer from a paywall — same idea, based on the paywall context.

The audience description is saved on the project, so next time you open the generator it is pre-filled.

4. Build the sequence (or start from a template)

Each row is one email in the chain. For every email you set:

Field	What it means
Start trigger	What event schedules this email (e.g. Lead email left, Any purchase, App installed).
Delay	How long to wait after that event (minutes, hours, or days).
Stop trigger	What cancels this email if it happens first (usually Any purchase or App installed).
What should this email say	A short brief in plain language — tone, angle, offer. The AI turns this into full copy.
Subject hint (optional)	A preferred subject line or angle; leave empty to let the AI decide.
CTA link	Where the main button goes: your paywall, a quiz, app download link, or a custom URL.

Use Add another email for more steps, or open Choose sequence… to load a ready-made chain (see the next section).

5. Generate and review

Click Generate. You can close the window — work continues in the background. When finished, all emails appear in Email Sequences as Drafts.

Before going live:

Read each email on mobile and desktop.
Check links and the main CTA.
Adjust subject lines if needed.
Switch status from Draft to Active only when you're satisfied.

Built-in sequence templates

Three templates cover the most common funnel stages. You can use them as-is or as a starting point and edit the briefs.

Push to Purchase (7 emails · Lead → Any Purchase)

For users who left an email in the quiz but haven't paid yet.

#	When	Role of the email
1	~10 minutes	Welcome — confirm their plan is being prepared; one clear CTA to the paywall.
2	~1 hour	Problem / solution — name the pain from the quiz and show how your product fixes it.
3	~6 hours	Social proof — results, testimonials, or "people like you" stories.
4	~1 day	FAQ / objections — time, price, "will it work for me?"
5	~2 days	Urgency — limited discount or bonus; reason to act now.
6	~4 days	Last chance — offer expiring soon; recap main benefits.
7	~7 days	Final — last email in the series; risk-free angle or guarantee if you offer one.

Stop trigger for all steps: Any purchase — as soon as they pay, the rest of the sequence is cancelled.

Push to Install (3 emails · Any Purchase → App Installed)

For subscribers who paid but haven't opened the app yet.

#	When	Role of the email
1	Immediately	Confirmation + install — thank them; step-by-step iOS/Android install.
2	~1 day	Getting started — first actions inside the app; quick win.
3	~3 days	Reminder + support — what they're missing; offer help if they're stuck.

Stop trigger: App installed.

Push to Upsell (3 emails · App Installed → Purchase)

For active users who might upgrade to a higher plan or add-on.

#	When	Role of the email
1	~3 days after install	Premium intro — features they don't have yet.
2	~7 days	Social proof upsell — what premium users achieve.
3	~14 days	Special offer — time-limited upgrade discount or bonus.

Stop trigger: Purchase (additional purchase / upgrade).

What a good email chain should look like

Templates give you structure; these principles help you adapt them to your product and market.

One job per email

Each message should have one main goal — open the paywall, install the app, answer one objection, or remind about an expiring offer. If you pack too much into a single email, clicks and conversions drop.

A typical lead nurture arc looks like this:

Trust → Problem awareness → Proof → Objections → Urgency → Final nudge

You don't have to use all seven emails on day one. Even 3–4 well-spaced messages often outperform a long chain of repetitive "buy now" notes.

Match timing to intent

User state	They're thinking…	Good timing
Just left email	"Is this legit? What do I get?"	First email within 15–60 minutes.
Same day, no purchase	"I'll decide later."	2–6 hours — social proof or quick FAQ.
Next 1–3 days	"Maybe, but…"	Objections, comparison, small incentive.
Day 4–7	"I forgot / not sure."	Stronger offer or last chance.

Avoid sending five sales emails in one day — it hurts deliverability and unsubscribes.

Always tie copy to the quiz

The strongest sequences reference what the user already told you in the funnel: their goal weight, language level, habit they want to build, etc. The audience description and quiz-based inference exist so every email feels personal, not generic.

Good brief example:

"Remind them their personalized plan is ready based on quiz answers. Mention that most users see first results in 2–3 weeks. CTA: paywall with intro offer."

Weak brief example:

"Promotional email about our app."

One primary CTA

Every email should have one obvious button — usually the paywall, sometimes app download or a specific quiz. Supporting text links are fine, but the main action should be unmistakable.

For lead sequences, point CTAs to the same paywall (or the paywall that matches their quiz) so tracking and discounts stay consistent.

Stop triggers are part of the strategy

Stop triggers protect user experience and your brand:

Lead sequence → stop on Any purchase — don't keep selling after they've paid.
Post-purchase install sequence → stop on App installed — don't nag once they're in the app.
Upsell sequence → stop on Purchase — stop when they upgrade.

If you add custom steps, ask: "Should this email still send if the user already did X?" If not, set the right stop trigger.

Tone across the chain

Stage	Tone
Early (welcome, problem)	Warm, helpful, curious — like a coach, not a billboard.
Middle (proof, FAQ)	Confident, specific, evidence-based.
Late (urgency, final)	Direct, honest about deadlines — avoid fake scarcity you can't enforce.

Subject lines work best when they're specific and human: "Your plan is almost ready" beats "IMPORTANT: 90% OFF!!!" for long-term inbox placement.

Length and format

Mobile-first: short paragraphs, one column, large tap target on the CTA.
Scannable: subhead, bullet list, one hero image — not a wall of text.
Legal/footer: keep unsubscribe and company identity consistent with your other project emails (see Deliverability best practices).

When to use which sequence type

Your goal	Start with
Recover quiz leads who didn't pay	Push to Purchase
Paid but low app activation	Push to Install
Free/trial users in app; grow ARPU	Push to Upsell
Mixed funnel	Run separate steps with different start triggers — don't mix "lead" and "purchase" triggers in one confused row.

You can run multiple sequences in parallel for the same project as long as each step's start/stop logic makes sense (e.g. lead nurture + post-purchase onboarding are separate chains).

Tips before you activate

Domain and From address must be configured under Email settings — otherwise nothing sends.
App download CTA requires a Web Download Link in project app links settings.
Review drafts — AI output is a strong first draft, not a final legal/compliance check.
Test yourself — send a test from the email step editor after you tweak HTML.
Start small — activate the first 2–3 emails, watch sequence analytics, then add or adjust later steps.
Translations — generate in English first, then add languages on each step if you serve multiple locales.

Related pages

Email sequences — triggers, delays, tracking, filters, analytics.
Email settings — domain, From name, SMTP.
Deliverability best practices — inbox placement and sending hygiene.