In brief
- One scenario is enough to start. The welcome message triggered at sign-up is the easiest to set up, whatever your sector.
- Half a day of inventory before touching the tool. Knowing what data you hold on your contacts, and which of it is reliable enough to trigger a send.
- Two weeks are enough to go live. One trigger, three messages, one exit condition, a series of tests: the whole scope of the first project.
- The start-up trap is always the same. Sending a scenario written for new subscribers to the whole database, and burning your list overnight.
An online retailer calls us with 12,000 contacts in the database and an automation tool paid for over fourteen months. No active scenario. The account has been used three times, for manual sends their old tool did just as well.
It is not a tool problem. They had wanted to map all their customer journeys, segment the database into eight profiles and plug in behavioural scoring. After three meetings, the project was too big to launch.
The way out is always the same: one scenario, just one, live within two weeks. Here is how we go about it with someone who has never automated anything.
The half-day inventory: what you really know about your contacts
Before opening the tool, answer three questions: where do the contacts come from, since when, with what proof of consent. A list inherited from a 2022 trade show is not handled like last month’s sign-ups, and collecting consenting email addresses determines what you are allowed to send.
Next, measure how complete each field is. Open a CSV export and count: first name, sign-up date, source, purchase amount. A field filled in for 30% of the database can serve neither as a filter nor as a personalisation variable.
Finally, list the events your site sends to the tool: sign-up, account creation, confirmed order, form submitted, appointment confirmed. That list limits your triggers, not your imagination. If it is empty, your first project is your site’s tagging plan.
Our rule: a piece of data is usable if it covers at least 80% of the contacts concerned, if it is fed automatically and if you know who updates it. The rest is documentation, not fuel.
Which first scenario to choose for your business
The right first scenario fires on a frequent, dated event, when the contact’s interest is at its peak. It is not the most profitable on paper: it is the easiest to run unattended.
| Type of business | First scenario | Exact trigger | Exit condition |
|---|---|---|---|
| E-commerce | Welcome in 3 messages, aimed at the first order | Newsletter sign-up, or account created with no order | First order confirmed, or end of message 3 |
| B2B service | Download follow-up: context, proof, conversation | Download form submitted (study, price list) | Meeting booked, or end of message 3 |
| Appointment booking | Confirmation, preparation, reminder | Appointment created in the calendar with a future date | Appointment attended or cancelled |
Two scenarios often top the list without suiting a first start. Abandoned basket assumes reliable tracking, so tracking you can vouch for. Reactivating inactive contacts touches the contacts most fragile in deliverability terms.
The welcome scenario, set up step by step
Let us take the e-commerce case. The principle carries over to the other two rows of the table; only the content changes.
1. The trigger
Choose “contact added to the Newsletter list”, not “contact created”. The nuance matters: a contact created during an order has already bought, and welcoming them reveals a system that does not know who it is talking to.
Add a one-time entry condition: a contact never goes through this scenario twice. The option exists in every tool; tick it before anything else.
2. Message 1, sent immediately
Short, factual subject line that restates what the person has just signed up for. The body fits into three blocks: who you are in two sentences, what the contact will receive and how often, the resource or code promised. A single clickable action, repeated twice at most.
No promotion here. This message establishes a sender address the contact will recognise next time. Sign with a real first name and job title, not “The team”.
3. Message 2, after 48 hours
This message brings the proof: your three best-selling products with their reviews, a customer case with figures, or the answer to the three objections you hear most on the phone. A single action, again. The 48-hour delay is a compromise: early enough for them to remember you, late enough not to look like a machine running away with itself.
4. Message 3, five days after message 2
This is the message that asks for a commitment. In e-commerce, a welcome code expiring after seven days, with the date shown. In B2B, a twenty-minute conversation with a direct booking link.
Without a response, the contact leaves the scenario and joins your normal communication. Do not lengthen the sequence: a fourth message never makes up for the silence after the first three.
5. The exit condition
Write it before the messages. The contact leaves as soon as they have taken the expected action, and in any case at the end of message 3. Without this rule, a customer who has just ordered is invited two days later to place their first order.
What to remember A scenario comes down to four elements: a trigger, delays, content, an exit. If you cannot state all four in one sentence each, it is not ready to be built.
The six checks before activating
- The test on yourself. Sign up with a personal address through the site’s real form, not the internal test button. All three messages must arrive at the planned intervals.
- Mobile rendering. Open the messages on a phone, with images blocked. The subject line must stay clear when cut off at around forty characters, and the action button must be tappable with a thumb without zooming.
- The loop. Check that no message updates a field or list used as a trigger for the same scenario. That is how you build a send that loops all night.
- Unsubscribing. Actually click the link from your test account, then check that the contact leaves all running scenarios, not just the mailing list.
- Variables. Look at what a contact with no first name produces. “Hello ,” with its orphaned comma is the signature of a badly set-up automation.
- The audience scope. Reread who will enter the scenario. That is the next point, and the one that costs most when it goes wrong.
The mistake not to make On activation, most tools offer to include contacts who already meet the entry condition. Saying yes sends your welcome sequence to the whole database, including customers who have been loyal for five years. The result is immediate: a wave of unsubscribes, spam complaints, sender reputation damaged for several weeks. The scenario must only touch sign-ups made after it is activated.
Second trap: volume. Activate on a single sign-up source, the one with the least traffic, and watch it run for 48 hours before opening it to the other forms.
The following two weeks: what to watch and what to adjust
A scenario that has just been activated is monitored, not optimised. Change only one thing at a time. The useful comparison is not a market benchmark, it is the behaviour of your own campaigns on the same database.
| What to watch | The warning sign | The adjustment |
|---|---|---|
| Entries into the scenario | Far fewer than the site’s sign-ups | The trigger does not capture every form |
| Message 1 opens | Clearly below your usual campaigns | Subject line or deliverability problem: check the sender and domain authentication |
| Clicks on messages 2 and 3 | A sharp drop between 1 and 2 | Message 1’s promise does not hold: rewrite message 2 |
| Unsubscribes | Above your regular sends | Pace too intense or audience badly filtered: space out the delays before touching the content |
| Expected action (order, meeting) | None among contacts who have already left | Message 3’s offer is too weak or too late |
The signal that allows you to move to the next scenario comes down to three conditions: fourteen days with no manual intervention, around thirty contacts through the sequence, and an unsubscribe rate back to the level of your other sends. As long as one of the three is missing, a second scenario will only double the problem.
Once all three are met, the next steps are mapped out: abandoned basket, follow-up after first purchase, reactivation. We detail these three scenarios and how to measure the incremental revenue they actually generate.
Frequently asked questions
How long does it take to set up a first marketing automation scenario?
Two weeks are enough for a three-message welcome scenario. Allow half a day for the data inventory, a day of writing, half a day of building in the tool, then a week of testing before full opening. Most of the time goes into writing and testing, not configuration.
Which tool should you choose to start with marketing automation?
The one you already have. Most email solutions include automated scenarios in their standard plans, and a welcome sequence needs nothing more. Changing tools before you have run one complete scenario postpones the project by several months without teaching you anything.
Should you send the welcome scenario to contacts who have already signed up?
No. A welcome message sent to a contact who signed up two years ago breaks trust and triggers mass unsubscribes. Reactivating the existing database is handled by a separate scenario, with different content and pacing, once the welcome sequence is stable.
Does an automated scenario require specific consent?
The consent collected at sign-up covers the welcome sequence, provided the form states what the contact will receive. The unsubscribe link must appear in every message and work immediately. For the data used to personalise sends, GDPR obligations apply just as they do for manual sends.
What you will have gained in two weeks
An active welcome scenario means a useful message sent to every new subscriber without anyone having to think about it, and a first measure of what a sign-up is worth to you. It is also internal proof that the project is moving, which unlocks budget and attention for what comes next.
The difficulty of marketing automation is never technical. A badly set-up scenario works against you continuously, whereas a failed campaign stops by itself. That is why we start from a small, monitored scope, as described on our marketing automation page.
Unsure which first scenario to set up? We look at your sign-up sources, how complete your contact fields really are and the events your site can already produce: that is what determines where to start. Let’s talk.