Two welcome flows on one list

The deliverability assignment gave this finding one section. It deserves the whole procedure, because the welcome flow is the one every brand has and almost none has tested from the outside. At a kidney-health supplement and education brand, the one from the flat-revenue case, four days into a deliverability rebuild, I audited the welcome flows. Both welcome email flows, one live and one in draft, started when someone joined the same list, and that list was the master email list of 143,520 profiles. A new subscriber with no orders qualified for both, so the day the second flow launched as built, new people would get two sequences at once. The SMS welcome was already sending wrong: it fired when anyone joined any list, with no filter. Of the last 100 list joins, 88 were the master list and 8 were back-in-stock lists, so someone asking to be told when a product was back got a welcome text for a program they had not joined. Existing customers qualified, people could re-enter on every list join, and quiet hours were off for an audience mostly over 60.

No report showed any of it. Flow reports show what each flow sent; they do not show that two flows point at the same person. It appeared only when I opened each trigger and looked up the name behind the list ID.

Why welcome flows break quietly

A welcome flow is built once, on the day the platform is set up, and then forms get added. A popup for the newsletter, a footer form, a restock alert, a quiz, a checkout opt-in, a landing page for a creator. Each one joins a list or fires an event, and each one was built by whoever needed it that week. The welcome flow still triggers on what it was pointed at in year one. The forms have moved on.

So the failures come in two kinds. Too many: two flows share a trigger, or a second flow was cloned from the first and both were left live. Too few: a form joins a list no flow listens to. At a hand-dyed yarn brand, from the acquisition case, the birthday gift was running as an ad to new people, and its signup page used the wrong form, so people who signed up joined no list and never got a welcome email. The brand was paying for traffic to a page that led nowhere.

The audit is a signup

The audit has two halves and costs nothing. The first half is inside the platform: list every live welcome flow, email and SMS, with its trigger, and look up the name behind every list ID, because a list in a build spec can turn out to be your master list. The second half is from the outside, and it is the one almost nobody does. Sign up with a new address from every form on the site: the popup, the footer, the restock alert, the checkout box, the quiz if there is one, each landing page. Use a different address per form, or a plus-address, so you can tell them apart. Then watch the inbox and the phone for seven days and write down what arrives, from which flow, at what hour.

Three things come out of it that no dashboard gives you:

• The map. Which form joins which list and fires which flow. At most brands this has never been written down, and the person who could draw it has left.
• The collisions. Two welcomes on one day, a welcome text to someone who asked for a restock alert, a discount in one flow and a different discount in the other.
• The silences. A form that joins nothing, or a flow whose trigger no form fires any more, which is the one with nobody in it.

What I recommended at the brand

At the kidney-health brand, the fix was filters, not new flows, in a set order. The SMS welcome first, the same day, since it was the one sending wrong. Then an exclusion on the email welcome before the second flow launched, tested on a seed profile first, because a "does not equal" filter on a property most people do not have can behave unexpectedly, and this one sat in front of 143,520 people. The skip-if-recently-sent setting was off on every send I checked; I would still fix the filters first, because that setting skips rather than delays, and a lost send makes no noise. Longer term, give each signup point its own small list and add people to the master list at the end of the flow, so a new welcome does not mean editing every existing flow. The rest of that work is in the segment-decision assignment.

The habit that stays is the one from the migration assignment: trigger each event yourself and confirm it arrives with the fields the flow reads. The first sign of a broken trigger is a flow with nobody in it, and the first sign of a doubled trigger is a person with two welcomes, and only one of those shows up in a report.

Do this Monday

1. List every form on the site: popup, footer, restock, checkout opt-in, quiz, landing pages, the account page. Note which list each joins and which event it fires.
2. Sign up to each one with a distinct address, on the same day.
3. For seven days, log what arrives: the flow, the message, the day and hour, email or text.
4. Mark the collisions: any address that got two welcome sequences, or a text it did not ask for.
5. Mark the silences: any address that got nothing, and any welcome flow that nothing on the site can fire.
6. Fix with filters first: the flow that is sending wrong today, then an exclusion that keeps a person in one welcome, tested on a seed profile before it goes in front of the list. Then rebuild only what the map says is missing, and give each new signup point its own small list.

In one line: open every welcome trigger and name its list, then sign up to your own site from every form and watch what arrives for a week, because no report shows two welcomes pointed at one person, or none.