Journeys

What you can automate

• Welcome and auto-reply flows — answer the first message instantly, at any hour, instead of leaving it unread until morning.
• Abandoned cart recovery — wait a set delay after a trigger fires, then follow up on WhatsApp where open rates beat email.
• Lead qualification — ask a few branching questions and route the contact to the right team before a human ever joins.
• Drip sequences — space messages out with delay nodes so onboarding or nurture arrives over days, not all at once.
• Appointment and order updates — trigger a utility message off an event from your own system via the API.
• AI steps mid-flow — hand one turn of the conversation to the AI agent, then return to the scripted path.

No code required

Journeys are built by dragging nodes onto a canvas and connecting them — triggers to start the flow, conditions to branch on contact attributes or replies, delays to control timing, and message nodes for what actually gets sent. There is nothing to deploy and no script to write.

For teams that do want to drive automation programmatically, the REST API can trigger a journey from your own systems.

FAQ

Can I build a WhatsApp chatbot without coding?

Yes. Journeys are drag-and-drop: triggers, branching conditions, delays, message nodes, and AI steps on a visual canvas, with no code to write or deploy.

Can a journey send an abandoned cart reminder?

Yes. Trigger the journey from your own system through the API, add a delay node for how long to wait, then send the follow-up message.

Do journeys work with the AI agent?

Yes. A journey can hand a turn to the AI agent as a step in the flow and then continue along the scripted path.

Do automated conversations cost anything?

Chatbot conversations count against your plan allowance — 500 per month on Free for the first six months, 6,000 on Pro. Any billable messages Meta charges for are drawn from the wallet at Meta’s rate plus the flat 10% platform fee.

Related