Skip to content

What workflows do

How workflows greet, ask, route and tag conversations automatically, and how they choose which one runs.

2 min read

A workflow is a set of steps that runs by itself when something happens: a message arrives, a visitor opens a page, a call comes in. It can greet the customer, ask questions, hand over to an AI agent or a team, add tags, or call your own systems.

Before you start

Every planNeeds: Workflows: Read

Every channel has a default workflow, named such as “Default — WhatsApp”. It answers the first message on that channel: an after-hours reply when you’re closed, then your AI agent if one is live, then your team. On phone, it’s the default call flow.

You can open a default workflow and change its steps on every plan. You can’t pause or delete it, because it’s the channel’s catch-all: it runs whenever no other workflow does.

On plans with the workflow editor, you can create your own: from scratch, from a template, or by copying one. See Create a workflow.

Each workflow belongs to one channel, or to Any channel for rules that only tag, prioritise, route or alert.

TriggerWhen it runsChannels
Message receivedA customer sends a message, or only their first one.All chat
Page visitA visitor opens a page matching an address you set.Web
Scroll depthA visitor scrolls down a page by 25–100%.Web
Exit intentA visitor moves to leave the page.Web
Returning visitorA visitor comes back after earlier visits.Web
Attribute changedA value saved on the contact changes.Web
Custom eventYour website sends an event you name.Web
Tag addedA tag is added to the conversation.All
Conversation idleA conversation has been quiet for a time you set.All
Business hours changeYour office opens or closes.Any channel
When a call comes inSomeone calls one of your numbers.Phone

When several workflows match, the one highest on the list runs. Click Reorder on a channel’s tab to change the order. The default always comes last.

A conversation runs one customer-facing workflow at a time. A workflow set to run in the background never messages the customer, so it can run alongside.

To see what ran on a conversation, and why others didn’t, see Check why a workflow did or didn’t run.