Ticket source-based routing (chat vs email vs form)
One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.
Professional
Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Service Hub Professional.
OutcomeTickets route to a pool sized and skilled for their originating channel, so a chat conversation expecting a fast reply does not sit behind a backlog of async email tickets.
Workflow maptickets-sla-011
When to use it, when not to
Use it
- Use it when different channels need different response speed or skill, for example live chat expects a near-immediate reply while email tickets can queue.
- Use it as one input among several if product or category also matters; see Variants for combining signals.
Read more on when to use itShow less
Skip it
- Do not use it as your only routing signal if it leaves a channel's pool without the skill to handle what actually came in; pair it with product or category routing where needed.
- Do not use it if every channel already feeds the same pool with the same expectations; there is nothing to differentiate.
Read more on when to skip itShow less
The rest of this spec
Not the workflow you needed?
More in Tickets and SLA
50 specs in this section
Read 12 complete specs before you pay.
One per category, same format as the paid ones. Email only, no card.
We email the link, then a short note when specs change. Nothing else.
Here it is. Download the pack now (.zip) The link is in your inbox too.
Read the free Tickets and SLA spec