Routing, assigning and escalating
Assigning is deciding who takes a conversation.
Routing is having rules make that decision at the moment the conversation comes in. Escalating comes later, when whoever received it cannot resolve it.
Why it matters
Because manual distribution collapses exactly when it is needed most.
On high-volume days. And because a conversation that takes two hours to reach whoever can resolve it has already used up half the customer’s patience before anybody reads it.
Types of routing
They are combined.
The usual approach is to pick the team first and the person second.
- By channel or mailbox. What comes in through billing goes to billing.
- By customer attributes, such as language, plan or account.
- By topic, detected in the message with keywords or with an AI model.
- By skills, to whoever knows that product or that language.
- By workload, to whoever has the fewest open conversations.
- Round robin, taking turns among those available.
Start with the objective criteria
Language and customer plan are criteria that do not fail and that resolve from a field.
Routing by message content is more ambitious and gets it wrong more often, so it is worth leaving until the basics work.
By workload or by continuity
Assigning to whoever has least open balances the load but breaks continuity.
A returning customer ends up with somebody else and repeats their story. Routing first to whoever handled them before, and by workload only if that person is away, usually works better.
The rule that should not be there
There is nearly always an old rule nobody remembers creating that sends conversations to a dead queue.
Reviewing the rules once a quarter is half an hour that saves finding out through a complaint.
