Welcome and abandoned-cart email flow brief

Updated 4 September 2026 · reading time about 8 minutes

The email flow that costs a store money is rarely the one with a weak subject line. It is the cart sequence still chasing someone who paid two days ago, and the welcome sequence sitting in a document because the platform was never connected. Both are briefing failures, and both are cheaper to prevent than to explain to a customer.

The decision rule

Outsource when your email platform is connected and demonstrably sending. Do it yourself when it is not.

Copy written for flows that cannot fire is inventory nobody uses. It waits in a document while you fight the integration, and by the time sending works the range has shifted, the shipping policy reads differently, and half the lines need rewriting. You paid for a draft and then rewrote it yourself.

The do-it-yourself case is stronger in this category than in most. You already hold the raw material a writer would have to ask for: the questions people send you, the reason the last person gave for not buying, the thing about delivery you keep having to explain twice. A rough first pass in your own words costs an evening, and if you later hand it to someone better, that pass becomes the brief. A writer improving your sentences works from your objections. A writer starting from an empty page works from generic ones.

Demonstrably sending means you filled in your own signup form and the email arrived in your inbox, and you abandoned a real cart on purpose and the platform recorded it. Not that the app is installed and the dashboard looks green.

Why these two flows before anything else

Both talk to people who have already done something. One group handed over an address and did not buy. The other put a product in the cart and stopped. That is a different writing job from a broadcast campaign, which has to manufacture a reason to appear at all.

Because the reader has already shown intent, the useful content is not news. It is the answer to whatever stopped them: the sizing question, the delivery worry, the comparison they were half-way through when something interrupted. An email in either sequence that answers nothing is decoration with an unsubscribe link attached.

It also means the email and the page have to argue the same case. If the email leads on how long the thing lasts and the page leads on how fast it ships, the click is wasted — the reader lands and starts the decision again. Keep the two aligned: briefing product page copy.

What the deliverable must contain

Ask for five things per email and refuse a delivery missing any of them: subject line, preview text, body copy, one action, and the delay before it sends.

The delay is the part writers leave out and owners do not notice until setup. Without it you are the person deciding timing, which is the decision you thought you had bought. The single action is the same problem in a different place: two links asking for two different things means the writer never chose which one mattered, and the reader will not choose on their behalf.

Ask for the whole thing as a table, one row per step, one column per field. You want something you can transcribe into your platform field by field without redesigning it. Flowing paragraphs look better in a document and cost you an afternoon of unpicking, plus the chance of pasting step three's subject line onto step two.

Say whether you want plain text or copy fitted to a template you already have. If you have no template, plain text is the safer order — a designed email you cannot rebuild yourself is one more thing you have to buy again the next time a link changes.

The flow map to hand the writer

Fill this in before you order. It is the difference between a writer inventing a sequence and a writer writing yours.

Flow map for the two sequences — you set the delays and exits before ordering
Step	Its single job	Trigger or delay	Exit condition	You supply
Welcome 1	Confirm the signup was worth it and say what will arrive	Signup confirmed, no delay	Unsubscribe	Your form wording, and what you actually intend to send
Welcome 2	Answer the objection that most often stops the purchase	Delay you set, in hours or days	Order placed; unsubscribe	The objection verbatim, and the page it links to
Welcome 3	Give one true reason to act now	Delay you set	Order placed; unsubscribe	A reason that is not a discount: stock, lead time, a policy
Cart 1	Show what is in the cart and make finishing trivial	Cart abandoned, then a delay you set	Order placed; cart emptied; unsubscribe	How your platform links back to a saved cart — confirm it first
Cart 2	Answer the objection that stopped them at checkout	Delay you set	Order placed; unsubscribe	Shipping and returns pages, quoted exactly as written
Cart 3	Ask plainly once, and invite a reply instead of a click	Delay you set	Order placed; unsubscribe	Where replies land, and who reads them

Two columns there are yours alone. A writer can suggest a delay and an exit, but only you can decide whether a first order should end the welcome sequence or move that person into a different conversation. Decide it, write it into the map, and every step has a defined stop rather than an assumed one.

Step counts are yours too. Three and three is a workable shape, not a rule; what matters is that each step has a job you can name in one line. If you cannot name it, delete the step rather than briefing it.

Copy only, or copy plus setup

Settle this in writing before you order, in one sentence: "copy only, delivered as a table", or "copy plus the two automations built in our platform and left switched off". Those are different jobs, and only the second one needs access to your account.

Decide the scope and the access before you order. This boundary is where this kind of order turns into a dispute, because "set up my email flows" reads to each side as their own version of the work. If setup is included: the account stays in your name, the seller gets the narrowest permission level that lets the work happen, you never share your own login, the flows are handed over switched off, and the access is removed when the job closes. Name who runs the tests, too. If nobody is named, nobody tests.

What moves a quote here: the number of steps, whether setup is included, whether the writer has to match an existing template, how many revision rounds you want, turnaround, and how much research your brief leaves them to do. Quote against the finished brief below and you get a number for your job rather than for an average one.

Compliance you cannot delegate

These emails go out under your name, from your domain, to people on your list. A freelancer can draft the footer. The obligation stays with you.

Three things remain yours regardless of who writes the copy. A working unsubscribe in every email of every step, tested by actually clicking it. A sender identity that is honestly your business rather than a friendlier invented one. And a lawful basis for contacting the person at all — an address given to you through your own form or checkout, with the source and date recorded, and the wording they agreed to kept on file. Buying a list or scraping addresses is not an option here, whatever a seller offers alongside the copy.

Record the consent source as a habit, not a project: which form, when, and what it said the subscriber would receive. If you cannot say where an address came from, do not email it. That single rule is what keeps this out of trouble.

Requirements differ by market, and they change. Check the current rules for the markets you actually email rather than assuming your own country's apply everywhere, and do that before the first send rather than after a complaint.

Test it before a customer sees it

Run all of this on your own store, on your own phone, with the flows live but before anyone else is in them.

Sign up through your real form with an address you can read on your phone, and read it there first.
Abandon a real cart — add a product, start checkout, leave — then wait out the delay and see whether anything arrives.
Click every link, including the one back to the cart and the unsubscribe. A dead cart link makes the entire sequence pointless.
Place a real order part-way through the sequence, then confirm the remaining steps do not send.
Check the sender name and the reply-to, and reply to yourself. Somebody will reply.
Read the whole sequence in order, the way a person receives it. Repetition that is invisible in one email is obvious across three.

The fourth one is the failure customers notice. A cart sequence that keeps nagging someone who has already paid reads as carelessness, and it is the thing they mention to other people. Confirm the exit fires on a real order rather than trusting that a setting whose name sounds right is doing the work.

Receipts, dispatch notices, and other order emails are a separate system with their own failure modes, and they belong in the pass over the finished store: commissioning pre-launch store QA.

Ordering it

Brief

STORE
What we sell, in one sentence:
Who buys it, and what they compare it to:
The objection that most often stops the purchase, verbatim:
The product page these emails send people back to:

LIST AND CONSENT
Where signups come from (form, popup, checkout opt-in, other):
What the signup form says the subscriber will receive:
Markets these subscribers are in:

PLATFORM
Email platform in use:
Sending confirmed working: yes / no (if no, do not order yet)
Existing template to match, or plain text:

SEQUENCES
Welcome: number of steps I want:
Abandoned cart: number of steps I want:
Per step I need: subject line, preview text, body copy,
  one action, and the delay from the previous step
The one action per email is: buy / read the page / reply /
  answer a single question — one only, no second ask
Delays and exit conditions: use the flow map attached

VOICE
Tone sample: two paragraphs I have written that sound right:
Words and phrases to avoid:

NEVER PROMISE
No discount, code, or free shipping unless written here:
No delivery date, dispatch window, or arrival promise:
No guarantee or returns terms beyond my policy page:
Product claims must come from my page, not be invented:

DELIVERABLE
Format: one table, one row per step, one column per field
Platform setup included: yes / no
If yes: whose account, which login, and who runs the tests
Revisions included, and what counts as a revision:
Deadline:

Check on delivery

It arrives in the format you ordered — one row per step, every field filled, nothing left as "TBC".
Every step has exactly one action. Count the asks; a step trying to do two things goes back.
Every step has a delay and an exit condition written as something you can enter, not as "shortly after" or "until they buy".
Unsubscribe wording is present in every step, not only the first one.
No discount, code, or free shipping appears anywhere you did not authorise it. A writer trying to be helpful can hand away your margin in one line.
No delivery date, dispatch window, or arrival promise beyond what your shipping policy actually says.
Subject line and preview text are different sentences that do not repeat each other.
It reads on a phone. Open the copy at phone width and check the first line still carries the point.
Product claims match your product page rather than filling gaps with invented features.
The sequence stops on purchase — verified with a real order, not by reading the exit setting.

Where to look: email marketing listings. Related: the 7-task launch outsourcing checklist for where this sits in the launch order, and reading a listing and vetting a seller before you order.

The copy is the visible half. What decides whether these two sequences earn anything is the plumbing you specify: what fires each email, what stops the sequence, and who checks that both actually work. Write those three down and the writing has somewhere safe to live.