Automation
Automation you can read a month later
Trigger, condition and action flows for WhatsApp: auto-replies, business hours, escalation and handover, with a run history that says what happened and why.
Flows built from triggers, conditions and actions
A new conversation, a keyword, a campaign reply, a schedule or an API call starts a flow. Conditions branch on contact attributes, message content or time of day.
Business hours are a first-class thing
Per team, with holidays, in the organisation time zone. An out-of-hours reply that fires at noon because a server is in another country is the classic version of this bug.
Handover to a human, deliberately
A flow can assign, tag, escalate or stop and hand the conversation to a team. Automation that cannot get out of the way is a complaint generator.
A run history per execution
Every run records which branch it took, what it sent, and what failed. When a customer says "your bot told me", you can look it up.
An entitlement on some plans and not others. The pricing table says which.
The rest of the product
Shared inbox
Assignment, teams, routing and SLA timers, with every agent in the same queue.
Campaigns
Template approval, segments, scheduling and delivery reporting that goes down to the message.
AI
Draft replies, summaries and extraction — with the allowance printed and no overage.
Security
SSO, SCIM, IP allowlisting, retention, export controls, audit export, data residency.
Try it on your own number
Create an organisation, connect a number through Meta, and use the whole product for the length of the trial.