A welcome email flow is the sequence that sends after somebody subscribes. It’s usually the highest-earning flow in an account, because it’s reaching people at the only moment they’ve ever actively asked to hear from you.
Here’s the problem it has to solve. A new subscriber has no purchase history, no browse data and no engagement record. You don’t know anything about them yet. So most welcome flows send everyone the same thing, which is the one decision that caps what the flow can earn.
The fix is to ask one question at signup and branch the sequence on the answer. That’s the whole idea, and the rest of this is how to build it.
See what your Klaviyo account is leaving on the table.
Request a free Klaviyo auditWhat should a welcome email flow actually do?
Earn the first order, and do it while you’ve still got their attention. Signup is the moment of peak intent and it decays fast.
The common failure is treating it as an introduction. Brand story, founder letter, a tour of the range. All of that’s about you, and none of it’s what they came for. They came because something on your site looked like it might solve a problem they’ve got.
The second failure is sending everyone the same six emails. Two people who signed up in the same minute did it for completely different reasons, and a sequence written for the average of them is written for neither.
What is the one question worth asking at signup?
Something about the customer’s problem, not about your product range. “What brought you here?” works. “Which category are you shopping?” doesn’t, because that’s asking them to navigate your catalog instead of telling you what they want.
The reason this is worth doing is specific to the welcome flow. Everywhere else in a lifecycle program you can segment on behavior, because there is some. At signup there isn’t any. The answer to one question is the only high-value thing you can collect at the only moment they are definitely paying attention.
The friction objection, and why it is mostly wrong
Everyone’s first reaction is that a second step will cost signups. It does cost some. What it misses is that the address on its own isn’t worth much until somebody buys, and the answer is what gets them there faster.
Run it as a test rather than taking anyone’s word for it, including this one. Measure signup rate and first-order rate together. A form that converts slightly worse into a list that converts considerably better is a trade worth making, and if it isn’t, your own numbers will say so inside a month.
The build detail that quietly kills this
In a multi-step Klaviyo form, the button that moves somebody from the question step onward has to be set to Submit form. If it’s set to go to the next step instead, the answer never gets written to the profile, the property stays empty, and every branch you built downstream collapses into the default path.
It fails silently. The signups still arrive, the flow still sends on time, and the only symptom is that everybody lands in the same branch. Check it on a real submission before you build anything on top of it, and check the property actually appears on the profile.
How do you branch a welcome flow on the answer?
The answer from the form gets stored as a profile property, and that’s all the machinery you need. Inside the flow you use a conditional split on that property, with one branch per answer and a default branch for people who skipped the question.
| Element | What it does |
|---|---|
| Signup form | Asks the question and writes the answer to a profile property |
| Trigger | Subscribed to list, as normal |
| Conditional split on the property | One branch per answer, plus a default |
| Branch content | The first two or three emails speak to that answer and nothing else |
| Rejoin | Later emails can be shared again once the specific case is made |
Four to six branches is the usual range. Fewer than four and you might as well not have asked. More than six and you’re writing sequences nobody reads, because the branches get too thin to keep up.
Keep the tagging separate from the sending
A pattern worth copying from well-built accounts: don’t do the property-writing inside the sending flow. Keep a small separate flow whose only job is to write profile properties, and let the welcome series read them.
It sounds like extra work, and it’s the difference between a flow somebody can still edit in a year and one nobody’ll touch. In one account we run there are eleven of those tagging flows sitting in front of the sending flows, and the sending flows stay readable because of it.
What goes in each welcome email?
Six messages, one job each. The branch decides what the first three are about, and the jobs stay the same whichever branch somebody’s in.
| # | Job | What it actually says |
|---|---|---|
| 1 | Deliver what you promised | The code or the thing they signed up for, immediately, with nothing else competing |
| 2 | Answer their stated problem | This is the branch. Speak to the answer they gave, and only that |
| 3 | Prove it | Evidence that it works for people in their situation, not generic praise |
| 4 | Handle the objection they have not voiced | Every category has one predictable doubt. Name it before it stops them |
| 5 | Make it easy | Shipping, returns, guarantee. The practical reasons people stall at the last step |
| 6 | Ask, with a reason to act now | The only overtly promotional one, and it works because the five before it did their job |
Only the last one sells. If the five before it landed, it hardly has to.
One thing to keep out: don’t stack a second discount on top of the signup offer. You’ve already given them a reason to buy. A second one teaches people to wait, and they learn it fast.
How long should you wait between welcome emails?
The first one goes within minutes, because they’re still on the site. After that the gaps open up as the signup gets further away and there’s less to react to.
| Gap | Why | |
|---|---|---|
| 1 | Within 15 minutes | They are still there, and they are waiting for the code |
| 2 | 1 day | Next day, while they still remember signing up |
| 3 | 1 day | |
| 4 | 1 to 2 days | The sequence is doing its work |
| 5 | 2 days | Slowing down as urgency fades |
| 6 | 2 to 3 days | Last call before they move to the regular calendar |
That shape comes from a live account: a welcome series with fifteen delays in it, mostly one day, a few two days, and a single fifteen-minute delay at the top. There’s nothing clever about it, and nothing accidental either.
Set an exit condition, not just a cadence. Somebody who buys on email two shouldn’t be getting emails three to six as written. Put the purchase check in a profile filter, which Klaviyo re-evaluates before every email, so the sequence stops on its own.
Should a welcome flow use double opt-in?
It depends on one thing, and that’s where your list growth is coming from.
- If you have deliverability trouble, or you buy traffic that converts suspiciously well, double opt-in is worth the lost volume. It filters out the addresses that damage you.
- If your signups come from people who already know the brand, single opt-in with a sunset policy behind it usually earns more. You keep the volume and you clean up later.
What matters more than the choice is that the confirmation email isn’t a dead end on its own. If you use double opt-in, the confirmation should carry the thing they signed up for, so clicking is worth doing instead of being an administrative chore.
How many emails should a welcome flow have?
Six reach any one person. The number you build is much larger, and that’s the part nobody mentions.
In one subscription account we run, the welcome series holds 47 emails and any single subscriber receives 4 of them. Forty-seven exist so the four you get are written for your answer, not for the average of everyone’s.
So “how many emails should a welcome flow have” is the wrong unit. Count the messages one person gets, and judge the build by how specific those messages are. A flow is a library plus a router, which is covered properly in the guide to all 22 flows.
How do you know the welcome flow is working?
Attributed revenue will flatter it, and it’ll flatter it badly. The welcome flow reaches people who just raised their hand, so it takes credit for orders that were coming anyway.
Hold out a random sample. A profile-sample split inside the flow sends a small percentage nothing. The difference in first-order rate between the two groups is what the sequence actually caused. Most accounts have never run one, which is why most people quoting their welcome flow revenue can’t tell you what it’s actually worth.
The second number is the one that tells you whether the question was worth asking: compare first-order rate between branches. If every branch converts the same, either the question’s wrong or the branches aren’t different enough to matter.
Why is my welcome flow not sending?
Three causes account for nearly all of it, and the first one’s the most common by a distance.
- The signup is not reaching the list the flow triggers on. On Shopify, subscribers from forms and checkout only land in a list if you’ve selected one in the integration’s sync settings.
- The messages are not live. Klaviyo flows have no on/off switch, so a flow can be half live and half draft and still look switched on.
- You imported a list and the flow fired on everyone. This is the reverse problem, and it’s why you turn list-triggered flows off before an import, as Klaviyo warns.
The three layers to check when a flow goes quiet goes through all of it in order, including every skip reason and what each one means.
What should you read next?
- All 22 Klaviyo flows, and the grid that shows which ones you are missing. The welcome flow is one row of it.
- The post-purchase flow, which is where the second order is won or lost.
- Why a flow goes quiet, and the order to check things in.
- What Smart Sending is doing to your flows, because it skips welcome emails too.
- How lifetime value is actually built, which is what the first order is the start of.
If you’d rather somebody went through your own signup form and welcome sequence properly, our Klaviyo audit does exactly that and tells you what to fix first.
Frequently asked questions
What is a welcome email flow?
A welcome email flow is an automated sequence that sends after somebody subscribes to your list. It usually earns more per recipient than any other flow, because it reaches people at the one moment they have actively asked to hear from you.
How many emails should be in a welcome flow?
Six reaching any one person is a good target: deliver what you promised, answer their stated problem, prove it, handle the unvoiced objection, make buying easy, then ask. The number you build can be far higher if the sequence branches.
How long should a welcome email flow be?
About a week to ten days. The first email sends within 15 minutes, the next two a day apart, and the gaps widen to two or three days by the end as the signup gets further away.
What should the first welcome email say?
Whatever they signed up for, immediately and with nothing competing with it. If you promised a code, the code is the email. Brand story and product tours belong later, if at all.
Should you ask a question in the signup form?
Yes, if you will act on the answer. At signup there is no purchase history or browse data, so the answer to one question is the only high-value thing you can collect. Store it as a profile property and branch the sequence on it.
Does a two-step signup form reduce signups?
It can reduce them slightly. The question is whether the list converts better afterwards, so measure signup rate and first-order rate together rather than signup rate alone.
Should a welcome flow use double opt-in?
Use it if you have deliverability problems or unverified traffic sources. If your signups come from people who already know the brand, single opt-in with a sunset policy behind it usually earns more.
How do you measure whether a welcome flow works?
Hold out a random sample with a profile-sample split and compare first-order rate between the two groups. Attributed revenue overstates welcome flows because they reach people who just signed up and were likely to buy anyway.
Sources
- Klaviyo, Understanding flow triggers and filters
- Klaviyo, How to create a segment or list-triggered flow
- Klaviyo, Understanding form blocks and fields
Flow architecture described here is drawn from live subscription accounts we run. No client, product, category or platform is identified, and no signup question options or answer values are published.
This is part of the program we run as an ecommerce email marketing agency.
