Ready-made journeys

A ready-made journey is a complete automation with the emails, waits and checks already in place. You choose one, fill in the few things only you know — which list, which segment, who the emails come from — rewrite the emails in your own words, and set it live.

Each one is a starting point, not a fixed product. Once it is yours you can change the wording, the timing or the steps like any other journey. See Automations for how journeys work.

When you choose a journey under New automation, the panel on the right lists its steps. The ones marked in amber are yours to fill in, and it says so: You choose … before it can be published. It also tells you how often one person can go through it.

The emails come with a subject line and a short placeholder message, with the unsubscribe line already in. Rewrite the message, or pick one of your templates instead. The one thing each email needs from you is who it comes from.

Four of them start from something happening in your app, and those need your developer to tell Mailyte about it first. They are marked below.

Welcome

Welcome series — three emails to someone who joins a list: straight away, a day later, and three days after that. Each person goes through it once. You choose: the list, and who the three emails come from.

Recover a sale

Abandoned checkout — someone starts a checkout and does not finish. An hour later they get a reminder, and two days after that a last one. The moment they buy, they leave and receive nothing more. Runs every time they abandon a cart. Needs your developer: your shop must tell Mailyte when a checkout starts and when an order is completed. You choose: who the two emails come from.

Assessment reminder — for applications: someone submits an application but does not take the assessment. Reminders two days and five days later; completing the assessment takes them out. Needs your developer: your system must tell Mailyte when an application is submitted and when an assessment is completed. You choose: who the two emails come from.

After a purchase

Post-purchase — a thank-you straight after an order, a "how is it going?" a week later, and a review request two weeks after that. Needs your developer: your shop must tell Mailyte when an order is completed. The thank-you is not a receipt; your checkout already sends one. You choose: who the three emails come from.

Time to restock — 25 days after someone buys something that runs out, a nudge to buy again. Buying first takes them out. Needs your developer: your shop must tell Mailyte about completed orders, and mark the products that run out. You choose: who the email comes from. Change the 25 days to how long your product really lasts.

Win back

Win back the quiet ones — someone matches a segment of people who have gone quiet. They get a "we miss you" email. If they click something within a week they are given a tag you choose, so you know they came back; if not, they get one last offer. One person can go through it again after 90 days. You choose: the segment, who both emails come from, and the tag.

Say goodbye to silent contacts — someone matches a segment of people who have not opened or clicked in a long time. They get one "still want to hear from us?" email. A click within two weeks gives them a tag you choose, marking them as still interested; otherwise they are unsubscribed, with a note saying why. Removing people who never read your email is one of the best things you can do for whether the rest of it arrives. You choose: the segment, who the email comes from, and the tag.

Dates and milestones

Birthday or anniversary — three days before a date saved on the contact, every year, at 9am in their own time, an email with a gift. If they buy within ten days, it counts as a success. You choose: who the email comes from. Your contacts need a date detail called birthday — add it under Contacts → Custom fields, or point the start at a different date detail.

Event reminders — for a webinar or an event: someone is given a tag, then gets an email a week before, the day before, and on the day with the recording. You choose: the tag and who the three emails come from. Your contacts need a date detail called event_at holding when the event is.

Nurture

Warm up new leads — someone joins a list and gets a guide. Three days later, if they clicked it, a teammate is emailed to follow them up and the journey ends. If not, they get a customer story, and four days later an invitation to book a call. You choose: the list and who the three emails come from.

Reply hand-off — someone replies to one of your emails (out-of-office replies are ignored). They are tagged and a teammate is emailed, so a real person picks up the conversation. You choose: the tag.

1. Go to Automations and choose New automation.
2. Filter by the kind of journey you want, or search. Choose one to see its steps on the right.
3. Give it a name only you will see and press Use this recipe.
4. Click each step marked in amber and fill it in. For an email, choose who it comes from, then rewrite the placeholder message or pick a template.
5. For a journey that needs your developer, send them Sending contact events. The names these journeys expect are listed there, so nothing has to be retyped.
6. Press Preview, then Set live.

It will not set live. A step is still marked in amber. Every one of them needs a choice from you.

A journey that needs your developer never starts. Your app has not told Mailyte about that moment yet, or calls it by a different name. Open the start step: the list shows what your app has actually sent. If the name there differs from the one the journey uses, choose the one your app sends.

Birthday or event reminders send nothing. The contacts have no value in the date detail the journey reads, or the detail has a different name. Open the start or the wait step and choose the right detail.

Win back or say goodbye starts nobody. The segment is empty, or it describes people who are still active. Check its count under Contacts → Segments.

The wording is not right for you. Change it. These are starting points, and every email in them is yours to rewrite.

• Automations — how journeys work, going live, and the report
• Email templates — design the emails these journeys send
• Contacts and lists — lists, tags, segments and date details
• Start a journey