The Workflow Library

Library / Lead routing / lead-routing-016

Chatbot/live chat qualified lead handoff to rep with notification

Lead routingContactSales Hub ProfessionalIntermediate~35 min to buildalso needs Marketing Hub ProfessionalFull spec

This spec is filed under Sales Hub Professional, and one of its steps belongs to another subscription: add to static list needs Marketing Hub Professional. Both are required to build it as written.

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.

Workflow map Enrollment, branches and actions at a glance lead-routing-016
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]
action or delay branch public on every spec, paid or not

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.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.5 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.8 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.5 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

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.