Routing can make a support team faster, or it can create a mess that is harder to see. A rule may look fair while sending the hardest conversations to the same person. An SLA policy may create noise if every small question is urgent. Auto-reassign may save a waiting customer, but it can also steal ownership from someone already working on the case. Roll it out slowly.
First make the queue visible
Before changing rules, look at the current queue. How many conversations are unassigned? How long is first response time? Which operators are overloaded? Which departments miss targets? Convor exposes queue depth, workload, first response, SLA, and operator analytics because routing without measurement is mostly guesswork.
Separate department from priority
Department answers who should handle the topic. Priority answers how quickly it should move. Mixing them makes rules brittle. Billing can have routine invoice questions and urgent account issues. Technical support can have simple setup questions and real incidents. In Convor, department, tags, priority, and SLA can be handled separately.
Pick a rule people can explain
Round-robin is easy to understand. Least-busy is better when workload changes during the day. Skills-based routing helps when only part of the team can handle a topic or language. Weighted rules help when senior people should leave room for escalations. The best first rule is usually the least surprising one.
Use auto-reassign as a safety net
Auto-reassign should handle clear failures: the owner is offline, first response was missed, the conversation has waited too long, or priority changed. It should not keep optimizing ownership in the background every few minutes. When conversations jump between people, nobody feels responsible and the visitor repeats context.
Keep manual takeover
Support work needs judgment. Someone may know the customer. A senior operator may keep a hard case. A sales person may take a technical question because they already own the account. The system should make the default path efficient, not block intentional overrides. Assignment history makes those overrides visible.
Get new posts in your inbox
No spam. Unsubscribe anytime.
