Ticket routing
Related terms
Routing
Routing is deciding which agent, team, or AI agent receives a contact, based on intent, language, skill, customer tier, and availability. Accurate routing is the cheapest available reduction in handle time, because a misrouted contact pays the cost of being read and reassigned twice.
Skills-based routing
Skills-based routing assigns each contact to the agent best matched to it, by language, product line, account tier, certification, or proficiency score, rather than the next available agent. It applies across voice, chat, email, and WhatsApp. It typically runs on top of standard routing logic inside a unified queue such as OnClarity’s omnichannel inbox. Tighter matching improves resolution quality, but it can lengthen wait times if few agents hold the required skill. Example: an Arabic-language mortgage question is routed to a licensed mortgage specialist instead of a generalist support agent.
Round robin routing
Round robin routing assigns each incoming ticket, chat, or call to the next agent in a fixed, repeating sequence, cycling back to the first agent once everyone has received one. It guarantees an even count of assignments but ignores ticket complexity, agent availability, and language or product skill. Workload can still land unevenly even when the numbers look balanced on paper. In a 12-agent queue, one agent might receive three multi-part complaints in a row purely by rotation order, while a colleague handles three quick password resets in the same stretch. Teams often layer smarter logic on top of this baseline, balancing by current workload or skill rather than relying on rotation alone. That approach sits closer to skills-based routing or load-balanced assignment than to pure round robin.
Text classification
Text classification is the task of assigning a piece of text to one or more predefined categories. In multi-class setups, each text gets exactly one label. In multi-label setups, it can carry several labels at once. Intent recognition, topic assignment, and auto-tagging are all applications of this underlying task. For example, an inbound email might be classified as both "billing dispute" and "churn risk" at the same time. That dual label determines which queue the email enters and whether it triggers an alert. Classification quality depends heavily on label definitions being clear and consistently understood across teams; a vague label like "other" tends to absorb anything that doesn't fit an obvious category. OnClarity's Voice of Customer applies this structure when sorting incoming feedback for routing and reporting.
