Key Takeaway
The quickest way to find a broken welcome email flow is to sign up as several fake subscribers yourself. Seed test contacts force every delayed branch to fire so you see what real people actually get. One candle shop found a dead branch that had been mailing nothing to a third of its new list for five weeks.
Meet the Shop That Trusted the Preview
Nadia runs a candle company with about 2,400 email subscribers. Her welcome email flow splits on a quiz answer at signup. The question is “Which scent do you want more of?” The answers are citrus and woods.
From there the flow has four real paths. Citrus buyers, woods buyers, people who click the discount link and people who never click. Each path sends a short series spread across ten days.
In the editor, everything looked right. Preview mode showed every message.
Where It Broke
The woods branch had a delay set to wait three days. Then a condition checked whether the subscriber had opened the first email.
That condition was wired to the wrong event. It listened for an open from the citrus branch. So anyone on the woods path who opened the first email got pushed into a branch that sent no further email.
No second email and no third. The flow just stopped.
Why Nobody Noticed for Five Weeks
Nadia tests her own signup now and then. She always picked citrus and found that path worked fine.
The woods path took 38 percent of new subscribers. She had never once landed in it on purpose.
Volume was too low for complaints. Welcome emails get opened by roughly half the people who receive them. A missing follow-up rarely triggers an angry reply. People simply buy somewhere else.
What a Seed Test Contact Actually Is
A seed test contact is a dummy subscriber profile you control. You give it an email address you can open. Then you feed that profile into one specific branch of the welcome email flow.
Nadia built four of them: one for citrus, one for woods, one for discount clickers and one for people who ignored the discount.
She tagged each profile with a plain label like “woods path, opened email one”. That tag told her later which condition the seed was built to trigger.
Forcing Each Branch to Fire
The setup took her under an hour. At signup she answered the quiz to steer each seed into the branch she wanted.
For the two click conditions she used her own inbox. She opened one email and left another unopened. That split the seeds across the behavior branches without writing any extra code.
The core move is simple. You make the path run.
Running the Test Without Waiting Ten Days
Most email tools let you shorten delays while testing. Nadia cut a three-day wait down to three minutes. She pushed the flow live for one hour then reset it.
All four seeds moved through in under twenty minutes.
If your platform will not speed up delays, clone the flow into a sandbox. Trim the waits to a few minutes and leave the live version off. The nodes and conditions are the same. You are only compressing the clock.
What the Seeds Revealed
Three of the four landed exactly where they should. The woods seed received only the first email.
That single result paid for the whole exercise. For Nadia it was about 15 people a week who never got the product education that drives a first purchase.
She fixed the condition node in six minutes. Finding it took far longer than the fix.
The Check That Matters Most After a Fix
Verify a fix with a real test. Send the seed contact through the updated welcome email flow at normal speed once.
A long delay can expose a send that lands on a weekend or crosses a subscriber’s time zone. Those problems only appear when real time passes.
Build Your Seed Roster Today
Write down every branch your welcome email flow can take. Count them. Then create one seed contact per branch.
- Make a folder in your inbox for seed mail.
- Label each seed with the exact branch and condition it tests.
- Shorten the delays in a sandbox copy of the flow.
- Run the real flow at full speed once before you launch.
Repeat the test after every edit. Branches drift the moment someone touches a condition node or changes a send order.
The Habit Worth Keeping
Testing a welcome email flow is an ongoing job. Treat seed contacts as a permanent part of your list.
Nadia now runs her four seeds on the first Monday of each month. The woods branch has fired correctly ever since.
Start with two seeds if four feels heavy. Cover your highest-traffic branch and your lowest-volume one.
Read the full guide: How to Test Delayed Branches in a Welcome Email Flow Before Launch