Most people starting with email automation open the tool immediately and begin building. The result is a complicated journey that stalls halfway.
This part is about the planning that happens before the tool — and it determines whether the whole journey works.
1. Define the trigger
Every journey starts with an action from the customer: signing up to the list, buying, abandoning a basket, or a month passing with no purchase.
The trigger has to be clear and specific. "When they show interest" is not a trigger; "when they submit their details in the form" is.
2. Define the goal
What do you want the customer to do at the end of the journey? Buy? Book a call? Use the product? Leave a review?
One goal per journey. A journey trying to do three things confuses the customer and fails at all three.
3. Write the messages in order
Before the tool, write on paper: how many messages, what each is about, and what step it asks for.
The order that usually works: a welcome and explanation, then value or education, then answering an objection, then a clear offer.
4. Set the timing
Timing is part of the message. The welcome immediately, the second after a day or two, and the rest at wider intervals.
The general rule: the closer the customer is to deciding, the faster the timing. An abandoned cart message after an hour; a reactivation message after months.
5. Define the exit
You have to define when the customer leaves the journey — the moment they buy, for example.
The worst experience is a customer buying and continuing to receive messages saying "complete your purchase." That step gets forgotten often and it damages trust.
Draw the whole journey
On one page: the trigger first, then the messages in order with their timings, the conditions, the exit point, and the goal.
That page is what you will then execute in the tool in half an hour. And the drawing is what prevents the complexity that stalls most journeys.
Start with the shortest journey possible
Three messages is plenty at the start. You can add more later based on the result.
A long, complex journey is hard to test and hard to fix, and most of its value sits in the first two messages anyway.
Prepare the content before you build
Write the full message texts before you open the tool. Writing inside the tool makes messages short and rushed.
And read them aloud: is this a message I would have been happy to receive? If the answer is no, fix it before you switch it on.
In short
Before any tool: define the trigger, the single goal, the messages in order, the timing, and the exit point.
Draw the journey on a page, start with three messages only, and prepare the full texts before you build.
This is part one — part two covers execution, measurement and improvement.