When to use a flow
- Routing — send VIP customers to a senior teammate immediately.
- Escalation — if the AI can’t resolve in 2 turns, hand off.
- Auto-tagging — tag anything mentioning “refund” with
returns. - Auto-replies — send a templated greeting when a conversation opens on a specific channel.
- After-hours — politely acknowledge messages outside business hours.
Node types
Trigger
The start. Fires on message received, conversation opened, contact created.
Condition
Branch on channel, tag, AI intent, language, or a custom field.
Message
Send a message to the customer (with optional delay).
Action
Tag, set priority, assign, collect an email.
Handoff
Route to a teammate, team, or round-robin within a specialty.
Resolve
Close the conversation, optionally send CSAT.
Plan availability
Flows are available from the Growth plan upwards. Caps:| Plan | Flows |
|---|---|
| Starter | — |
| Growth | 3 |
| Business | 10 |
| Scale | Unlimited |
Typical flow shapes
Triage flow:Next
Build a flow
Step-by-step for your first flow.
Triggers
Every event you can start a flow on.
Conditions
Fields, operators, and combining logic.
Publish & test
Safely ship a flow to production.