Triggers from real events
Start from a form, booking lifecycle event, order or payment event, audience change, manual start, quiet contact, or a custom event from your own system.
Read the journey guideMarketing automation, made visual
Start with a real business event, add a wait or decision, then send the right WhatsApp or email message. Mondovo keeps the journey editable in a visual builder, with goals, webhooks, and site functions when a path needs to go further.
Use the journey editor to save and activate a live workflow. The visual below is a readable example of the steps you can connect.
Journey editor · example
Editable pathForm submitted
A new enquiry enters the journey
Wait 1 day
Choose a fixed duration or an event-provided time
Update lead score + tag
Keep the contact record useful for the next decision
If / else: audience or score
Route each contact to the path that matches
WhatsApp path
Use a template outside the 24-hour window
Email path
Continue with a tailored follow-up
Goal reached or stop
Record the outcome and finish the path
One workflow, several useful paths
The builder gives every step a place in the journey. Chain condition nodes when one decision is not enough, and keep each branch understandable to the team that will maintain it.
High-intent path
A contact with the right lead score or audience membership receives a timely WhatsApp message or email follow-up.
→ Finish at a named goal
Needs-more-context path
A different contact can wait, receive another message, or move through another condition before the team is asked to act.
→ Continue, call a webhook, or stop
Plain-language controls
Every live journey is validated before it runs, then processed in the background one step at a time.
What you can build
Start small, then add the branch or integration that makes the next customer action easier to manage.
Start from a form, booking lifecycle event, order or payment event, audience change, manual start, quiet contact, or a custom event from your own system.
Read the journey guideAdd a fixed wait, wait for a time carried by a custom event, or send during the contact’s local hours. Choose the timing that fits the conversation.
Branch on contact status, lead score, tags, audience membership, location, language, company, contact details, interactions, trigger data, or a JSONLogic rule.
Send an approved template outside the 24-hour service window, or a normal message while the person’s WhatsApp conversation is open. Use contact and event fields to personalize it.
See WhatsApp automationSend an email from the same journey, with optional translation to the contact’s language and the same clear branch logic around it.
Update tags, pipeline status or stage, lead score, and custom fields so future paths have better context.
Send a JSON payload to an external endpoint with a chosen HTTP method. You can halt the path when the endpoint returns an error.
Call one of your deployed site functions and reuse its result in a later message or decision. This gives a journey a controlled connection to your site logic.
End a successful path at a named goal for conversion reporting, or stop a path with a reason when the journey should finish.
Before you activate
The best journey is specific about what starts it, what it sends, and when a person or system takes over.
01
New journeys start switched off. Review the trigger, each branch and the message content, then activate when ready. New entrants follow the saved version; existing runs keep the version they entered.
02
Select one supported event, audience rule, manual start, or custom event contract. Your own system can send event fields that become message merge fields.
03
WhatsApp templates need Meta approval for messages outside the 24-hour service window. Inside the window, a normal message can continue the conversation.
04
Use a named goal for the conversion you want to measure, or an exit reason for a path that should stop. Webhooks and site functions can extend the workflow.
05
Email uses your verified sending domain. SMS needs its site setup and applicable usage balance. WhatsApp needs the business’s connected number, approved templates where required and Meta message charges.
Questions before you build
Yes. Add a condition split with a true and false path, then chain more condition nodes when the journey needs several branches. Conditions can use contact fields, audience membership, trigger data, and advanced JSONLogic rules.
Yes. Choose a fixed duration, wait for a time supplied by a custom event, or limit sending to local hours. A wait is a visible step in the same journey graph.
Supported starts include forms, booking and claim lifecycle events, orders, payments, abandoned carts, returns, audience changes, manual starts, quiet contacts, and custom events from your own system.
Yes. Add the channel steps you need and route contacts with conditions. WhatsApp follows Meta’s approved-template and 24-hour service-window rules; email has its own editor and delivery path.
Yes. Add a weighted A/B split with at least two variants, then connect each variant to its own next step. You can finish different variants at different goals or exits.
Yes. Add an outgoing webhook with a JSON payload, or call one of your deployed site functions. Both steps can be configured to stop the journey when an error should block the next step.
The journey builder updates contact tags, pipeline status or stage, lead score, and custom fields. It does not currently include a teammate-assignment node.
Email activity can be reported, but opens and clicks are not native journey triggers or condition fields. Use a supported event or a custom event from your own system when an external signal needs to start a path.
Create a journey around the event, timing, and channel your business already uses.
Start building