A welcome email flow is the set of automated emails a store sends after someone joins its list.
Every guide opens with a version of that sentence. Then they stop agreeing.
Four choices sit inside the flow, and the published guides split on every one of them: what fires it, how many emails it holds, how fast the first one goes out, and what the numbers everyone quotes are actually counting.
The welcome flow, as published on 2026-08-31. The recommended length runs from one email to fourteen. The only shipped default in the set is three. The first email should go out “immediately” — which the sources implement anywhere from sixty seconds to twenty-four hours after signup. A first purchase either belongs in the flow or is deliberately routed away from it, depending on whose guide you read. And two platform benchmarks put the welcome open rate at 51.26% and 35.53%, with a second page from one of those publishers giving a third figure for the same year.
What is a welcome email flow?
It is an automated sequence, triggered by a new subscriber, that runs on its own after setup.
Klaviyo puts it plainly: “A welcome email series is a sequence of automated emails sent to new subscribers after they sign up to join your list.” Braze adds the purpose: “an automated sequence sent after signup to introduce the brand, build trust, collect preferences, and guide the subscriber to a first meaningful action.”
That much is settled. Everything below is where it stops being settled.
Is a flow different from a series or a sequence?
No. The words are used interchangeably.
One page titles it a series and then asks about a sequence in its own FAQ. Two others call it a flow in the middle of a page about the series. Nothing here depends on telling them apart, and no source draws a line between them.
Is a welcome flow the same as a welcome email?
No, and one source says a single email is still a legitimate choice.
Privy puts the floor at one: “A single welcome email is good. A series of two or three is better.” InboxArmy argues the other way from the same starting point: “One email can confirm a signup. It can’t build trust, showcase products, and make an offer without overloading the reader all at once.”
Both treat one email as the bottom of a range. They disagree about whether you should stay there.
What actually triggers a welcome flow?
Joining the list, in the narrow reading. Rather more than that, in the wide one.
Klaviyo’s definition names one event — signing up for the list. Braze names four: “Signup (email capture, account creation, lead form) · First app open (for app-first brands) · First browse or first product view (high intent, even before signup in some systems) · First purchase (post-purchase welcome differs from pre-purchase onboarding)”.
The last one is where the definitions come apart.
Does a first purchase belong in the welcome flow?
Two sources say yes. One says explicitly no.
InboxArmy’s definition covers a subscriber “after they sign up, create an account, or place a first order.” The Braze list includes a first purchase and flags in the same line that it is a different program. Omnisend sends those people somewhere else entirely: “Purchasers should enter a separate flow to avoid inbox overload”.
So the same store’s welcome flow contains its first-time buyers under one reading and excludes them under the other, with nothing else in the definition changing. Two stores following different guides are not reporting over the same population.
Is the confirmation email part of the flow?
The two answers are structural opposites: one publisher makes the confirmation the flow’s first email, the other makes confirming the event that lets the flow start at all.
Bloomreach makes it email one. Its first step is headed “The Immediate Confirmation Email”, and the instruction is “This should just be a signup confirmation, with a brief note on what to expect and one clear next step”.
Braze makes confirming the gate instead. In its double opt-in template, “the user must confirm their email address and opt in to messaging before this message can be sent”.
What does double opt-in do to the start line?
It moves the clock onto the subscriber.
The instruction to send immediately is measured from the signup. Under a double opt-in gate, the first welcome email cannot send until the subscriber comes back and clicks. The delay stops being a setting and becomes someone else’s behaviour.
Two flows can both be configured to send instantly and still reach the subscriber at different times, because they are timing from different events.
How many emails should be in a welcome flow?
The published answers run from one to fourteen.
Privy suggests two or three. Braze says “2-4 emails is a good starting point”. Bloomreach says “The most effective welcome series will contain 3–6 emails”, and puts the observed spread wider still: “The average length across industries is around 6 emails, though this ranges from 2 to 14 depending on business model and sales cycle.” InboxArmy reports its own builds at “3 to 6 emails across 7 to 20 days”.
The ranges overlap at three. They agree nowhere else.
Is there a standard number?
There is no standard. There is one shipped default.
Klaviyo declines the question outright and answers with a method instead: “The number of emails in your welcome email sequence depends on the length of your average purchase cycle.”
The nearest thing to a default is what a store gets if it changes nothing — a pre-built flow “with three emails sent after one minute, one day, and four days”.
When do you stop adding emails?
Both sources with a stopping rule tie it to engagement rather than a target count.
Bloomreach: “Start with 3–4 and expand based on engagement metrics.” InboxArmy sets the ceiling from experience: “The series has already crept past six or seven emails. Past that point, I’ve watched series lose subscribers faster than they gain engagement.”
Same rule, different exit point.
When should the first email go out?
Immediately — which three publishers say, and none of them defines.
Klaviyo: “Your first email should go out immediately after someone signs up for your list.” Braze: sent “immediately after signup or account creation so expectations and value land while intent is high.” Bloomreach: “Send your first email immediately after subscription, when you’re still fresh in the subscriber’s mind.”
None of those three attaches a unit.
How fast is “immediately”, in practice?
Between sixty seconds and a day, depending on the source.
The shipped default fires at one minute. The same publisher’s written guidance is slower and conditional: “Your welcome email should arrive within five minutes of customers signing up if you’re offering an incentive”, and “If there isn’t an incentive, within 30 minutes is typical”. InboxArmy’s worked client example lands at “Sent 2 minutes after sign-up” — while its written rule allows far longer: “The first email should go out immediately, or within 24 hours at the latest, after a subscriber shows interest.”
That is the same word covering one minute and one day. Nobody in this source set tests which end performs better.
How long does the whole flow run?
Four days at the short end, twenty at the long one.
The three-email default finishes on day four. InboxArmy reports its own builds at “3 to 6 emails across 7 to 20 days”. Both of those are described as a welcome flow.
One practitioner quoted by Klaviyo argues the window is fixed by the buyer rather than the calendar: “We’ve found that most people make a purchase within 10 days of subscribing to a mailing list.” That is one person’s observation, not a study, and it is the only number here that tries to set the flow’s length from outside.
What does each email in the flow do?
One job each. Both a platform and an agency say so, and both name the same failure.
Braze: “Each email should have one job, or you risk giving your customers decision paralysis.” InboxArmy: “Most welcome email sequences fail because they try to answer three or four questions at once instead.”
A flow is not one email split across days. It is several decisions about which question gets answered when.
What has to be decided before anything is written?
More than the copy, which is where the work actually goes.
Braze is direct about the cost. Welcome emails have “traditionally required manual steps to build, integrate with relevant customer data, and personalize to every user’s satisfaction”. Each email needs its own job, its own design, and its own personalisation inputs before a single subject line exists.
And the personalisation that moves anything is not the name field. Braze again: “Personalize with context, not a first name.” InboxArmy agrees: “Personalizing beyond a first name moves open rates more reliably than a name token alone”.
What do you turn off while the flow runs?
Every promotional send scheduled to land while the flow is still running.
Braze: “Pause overlapping promos while the welcome series runs.” InboxArmy: “Suppress anyone currently in a welcome series from broadcast sends.”
Both instructions are about the sends that are not part of the flow, which is what makes this a decision that lives outside it.
What is a good welcome email open rate?
The published figures are not on one scale.
Klaviyo puts it at “51.26% across all industries, in addition to an average placed order rate of 1.97%.” The benchmark study built on “more than 20 billion campaign emails and 470 million automated email sends across 27,000+ brands” reports “$6.16 per email with a 35.53% open rate.” Privy publishes a range whose top is far above either: “Most fall in the 50 to 70 percent range, which is massive.”
Agency case studies go higher again — one client account at “an average open rate of 88.75%”. That is one store, not a benchmark.
Why don’t the open rates agree?
Because nobody publishes what sits under the number, and one publisher does not agree with itself.
The 35.53% above is Omnisend’s 2025 benchmark figure. A second Omnisend page, describing the same year, says welcome emails’ “open rates only reached 33.79% in 2025, behind cross-sells, back-in-stock alerts, and abandoned cart reminders”. Neither page states a difference in scope that would separate the two.
If one publisher’s two pages differ on its own data, the gap between two different publishers tells you very little about anyone’s customers.
What are the revenue figures measuring?
Two different divisors, going by the words on the pages.
Klaviyo reports that “The business impact of a welcome email is, on average, $2.35 in RPR.” RPR, in Braze’s glossary of the same metric, is “Qualified revenue ÷ unique recipients.” The $6.16 is stated per email sent.
Those coincide only when every recipient gets exactly one email — a one-email flow. Once a subscriber can receive a second message, revenue per recipient and revenue per email are different quantities, and neither publisher states how many emails its flow contained.
The years differ too. The $6.16 is a 2025 figure; the same publisher’s “second-highest revenue per email in 2026 at $6.30 per email” is a 2026 one.
Should you use open rate at all?
Not on its own. The study that publishes the 35.53% figure warns about the metric on the same page it publishes it.
Omnisend’s benchmark study notes that “since 2021, Apple Mail’s Mail Privacy Protection has been able to preload tracking pixels, which can make some emails appear opened before a subscriber reads them”.
Two sources say the same thing about what to watch instead. Braze: “Track outcomes like activation, conversion, unsubscribes, and retention, not just opens.” InboxArmy: “Open rate and click-through rate answer a narrow question: did anyone notice? Neither tells you whether the series makes money, which is the actual point of building one.”
What does the flow cost?
Unsubscribes, at a rate near the top of the table.
In the one dataset here that compares automations against each other, “Welcome emails reached 0.87%” on unsubscribe rate. Only cross-sell, at 0.89%, is higher; every transactional type sits at 0.45% or below.
The revenue figure gets quoted constantly. This one, published beside it, rarely does.
What should you write down beside your own number?
Four things, and they take one line:
- The trigger. List signup only, or signup plus first purchase. Those are different populations reporting under the same name.
- The length. How many emails, and over how many days. Three emails over four days and six over twenty are not two views of one thing.
- The delay. In minutes, and from which event — the signup, or the double opt-in confirmation.
- The divisor. Per recipient or per email sent, and whether the figure covers the first email or all of them.
A welcome-flow number with those four beside it can be compared to last quarter’s. Without them it cannot be compared to anything, including itself.
What does this change about reading a welcome-flow benchmark?
Treat a published figure as a number plus four hidden settings, and assume they differ from yours.
When your flow underperforms a benchmark, check the trigger, the length, and the divisor before you conclude anything about your customers. And when your own number moves, check whether anything in the flow moved with it — a new email added, a delay changed, purchasers routed in or out.
The only comparison guaranteed to hold the method constant is your own flow against itself, with the settings written down and left alone.