Automated flows quietly send more email than most campaigns, and they're the hardest thing to see. They live inside your email platform's builder, nobody outside the email team can open them, and after a year nobody remembers why the second email waits three days.
A board for each journey
- The real emails: add each email from its preview link or from your Library, shown as a thumbnail you can open.
- The logic: add waits, splits (bought or not, opened or not, any rule you write), goals and notes, and join them with labelled arrows.
- The conversation: comment on any step, so the team can question a timing or suggest a new branch in the same place.
Why map flows outside the ESP
- Stakeholders can see and comment on a flow without a login to your email platform.
- You can plan a new flow, or a change to an old one, before anyone builds it.
- Every journey is kept in one place, with the real emails, so a new starter can understand the programme in an afternoon.
Plan, mock up, sign off
Mock up a new email for a journey in Studio, send it for sign-off, and once it's approved it's in your Library, ready to add to the map.
Keep live journeys on the register
Once a journey is running, turn it into an automation: one page with its status, owner, sign-offs, landing page checks, results per step and a reminder when it's due a review.
Pricing
Journeys is included on every plan, including Free. See the pricing page.
Questions
Does Mailfois send the journey?
No. Your email platform (Klaviyo, Braze, Salesforce, HubSpot, Mailchimp or another) runs the automation. Mailfois is where you map it, review it and keep it documented.
Can I import a flow from my ESP?
Not automatically yet. Add each email by its preview link or from your Library, then lay out the steps.
Who can see a journey?
Everyone in your workspace. Outside people can comment on the emails in it through sign-off.
What kinds of journeys can I map?
Any: welcome and onboarding series, abandoned basket or browse, post-purchase, replenishment, winback, birthday, renewal and lifecycle programmes.