Outcome. A visitor who qualifies through the chatbot gets an owner and an immediate notification, instead of sitting in the Conversations inbox until someone happens to check it.
flowchart TD
A[Chatbot qualifies visitor] --> B{Owner already known?}
B -->|Yes| C[Notify existing owner]
B -->|No| D[Rotate to on-duty pool]
D --> E[Set routed date, notify owner, optional Slack]
C --> F[Create follow-up call task]
E --> F
D -->|pool empty| G[Notify sales ops, add to Needs manual routing]

When to use it, when not to
- UseUse it when a chatflow already asks qualifying questions (budget, use case, company size) and ends with a clear yes/no signal.
- UseUse it when the on-duty reps for live chat are a smaller, dedicated pool separate from the general round-robin (chat expects a faster reply than a form fill).
- SkipDo not use it for chatbots that only route to a knowledge base or ticket queue with no sales qualification step. See tickets-sla for that flow.
- SkipDo not use it if nobody staffs live chat outside business hours; route after-hours chats to a form or ticket instead of a dead-end rotation.
or the lead routing pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.





