Chat routing· Support operations
Chat Routing — Who Gets the Next Chat
Quick answer: Chat routing makes two decisions for every new chat. First, which team or queue it belongs to, usually from rules about the page, the visitor's country or a topic picked in a pre-chat form. Second, which person in that team takes it, using an assignment method such as round robin, "least busy agent" or skills matching, limited by how many chats each agent can hold at once. When nobody qualifies, the chat waits in a queue or stays unassigned.
The two decisions: which team, then which person
| Decision | Typical inputs | Example from vendor docs |
|---|---|---|
| Which team or queue | Page URL, domain, visitor country, pre-chat topic, channel, language, customer tier | LiveChat routing rules send chats to a group by URL, domain or, on its Business and Enterprise plans, the customer's location |
| Which agent | Status (online, away), current number of chats, skills, who was assigned least recently | Zendesk's default picks the eligible agent with the highest spare capacity |
| What if nobody fits | Queue, fallback group, unassigned inbox | LiveChat's fallback group catches chats no rule matched; HubSpot leaves the chat unassigned for the team to triage |
Keeping the two decisions separate makes problems easier to find. A chat in the wrong team is a rule problem; a chat stuck with an overloaded agent is an assignment or capacity problem.
Common assignment methods
| Method | How it picks the agent | Watch out for |
|---|---|---|
| Round robin | Takes turns in a fixed order among active agents | Intercom's version does not look at how many conversations each person already has |
| Least busy / spare capacity | Agent with the fewest open chats, or the most room under their limit | Needs a sensible per-agent limit to work |
| Skills-based | Only agents with the required skill (language, product, tier) are eligible | A rare skill can leave chats waiting; Zendesk offers a timeout that relaxes the skill after a set wait |
| Manual pick from a queue | Agents choose chats themselves | Slower to start; chats can sit unpicked |
| Sticky / returning customer | Sends a returning visitor to the agent they spoke to before | Only works if that agent is available |
Intercom's round robin article recommends round robin for sales teams, so new leads are spread evenly, and recommends balanced assignment, which respects each teammate's limit, for support teams.
What the vendor pages document
- LiveChat. Automatic assignment is the default and gives each accepting agent one chat in turn before anyone gets a second, until every agent's concurrent chat limit is reached. The other mode puts chats in a queue for agents to pick. Returning customers go to the agent they chatted with before, if that agent is accepting chats. If an assigned agent does not respond within the inactivity timeout, the chat moves to another agent; the timeout is fixed at 3 minutes on Starter and adjustable on Team and Business. Routing rules are checked top to bottom, and a fallback group catches the rest.
- Intercom. Round robin rotates through active teammates per team inbox, skips teammates set to Away by default, and assigns only once, when the conversation arrives. Balanced assignment, which Intercom documents for its Expert plan, gives the next conversation to the eligible teammate with the fewest open conversations, breaks ties by who has waited longest for an assignment, and respects teammate, channel and inbox limits. See our Intercom review.
- Zendesk. Omnichannel routing assigns email, messaging and call tickets using agent status, availability and capacity. Its default method is highest spare capacity; round robin is the alternative. Skills, priority and custom queues are listed for Professional and above. Zendesk notes that omnichannel routing cannot run on live chat alone; messaging must be activated.
- HubSpot. A chatflow can assign chats to chosen users or teams. With several users, chats go to the least busy available user, then to whoever was assigned least recently. If no one is available, the chat stays unassigned for the team to triage.
None of these pages publishes data on how much a routing method changes wait times or satisfaction.
Where chatbots fit
A chatbot often does the first half of routing: it asks what the visitor needs, detects the language or intent, answers what it can and passes the rest to the right team. The routing rules then pick the person. If the bot passes the topic and a short summary along with the chat, the agent does not have to ask again; see human handoff and chatbot handoff rules. Language-based routing depends on how the language is detected, covered in chatbot language detection.
How to tell if routing is working
Three things show routing problems quickly: how long chats wait before an agent accepts them (see chatbot first response time), how many chats are transferred to another team after they start, and how often chats end with no agent at all. A high transfer count points at rules; long waits with idle agents point at limits or status settings.
FAQ
What is chat routing? The logic that decides which team and which agent receives each new chat, based on rules, agent availability and how many chats each agent already has.
What is the difference between round robin and skills-based routing? Round robin takes turns among available agents. Skills-based routing first narrows the pool to agents with a required skill, such as a language or product, and then assigns among them.
Is round robin good for a small support team? It is simple and fair in turns, but Intercom's version ignores how many chats each person already has. Intercom recommends a capacity-aware method for support and round robin for spreading sales leads.
How do you route chats by language? Create a team or skill per language and send chats there, using the visitor's answer in a pre-chat form, a chatbot question or detected language. Check how your platform detects language before relying on it.
What happens to a chat when every agent is busy? It depends on the platform: it can wait in a queue, go to a fallback group, or stay unassigned. LiveChat stops auto-assigning once all agents reach their chat limit; HubSpot leaves chats unassigned when nobody is available. What a waiting visitor sees is covered in chat queue.
Can a chatbot route chats? Yes. A bot can ask the topic, answer simple questions and hand the rest to the right team, which then assigns an agent.
Related terms
- Live chat — the channel routing usually serves.
- Pre-chat form — a common source of routing data.
- Human handoff — the bot-to-person step that routing follows.
- Unified inbox — where routed conversations from several channels land.
- Warm transfer — moving a chat to another agent with context.
- Chatbot language detection — an input for language-based routing.
- Chatbot first response time — a metric routing directly affects.
- Conversation tagging — labels that rules can add and routing can act on.
Sources
- LiveChat, Understanding chat routing — livechat.com/help/understanding-chat-routing/, read 11 November 2026. Source of automatic and manual modes, round-based distribution, concurrent chat limits, returning-customer routing, the inactivity timeout and its plan differences.
- LiveChat, Setting up routing rules — livechat.com/help/setting-up-routing-rules/, read 11 November 2026. Source of URL, domain and location conditions, rule order and the fallback group.
- Intercom, Assign conversations evenly using round robin — intercom.com/help/en/articles/6512504-assign-conversations-evenly-using-round-robin, read 11 November 2026. Source of the rotation behavior, Away handling, the note that limits are ignored and the sales-versus-support recommendation.
- Intercom, Balanced assignment deep dive — intercom.com/help/en/articles/6553774-balanced-assignment-deep-dive, read 11 November 2026. Source of eligibility, fewest-open-conversations logic, limits and the Expert plan note.
- Zendesk, About omnichannel routing — support.zendesk.com/hc/en-us/articles/4409149119514-About-omnichannel-routing, read 11 November 2026. Source of the highest-spare-capacity default, round robin option, skills timeout, plan tiers and the messaging requirement.
- HubSpot, Set your conversations routing rules — knowledge.hubspot.com/inbox/set-your-conversations-routing-rules, read 11 November 2026. Source of chatflow assignment to users or teams, least-busy logic and unassigned chats.
- Chatbotscape evaluation methodology. /methodology (continuously updated).