How the problem develops
A general service enquiry bounces between sales, operations and delivery. Each transfer asks the customer to repeat the brief. Routing by a single keyword is tempting, but a request can mention several services or quote an old conversation.
What to check first
- Group recent misroutes by missing information, outdated team ownership and genuinely ambiguous requests.
- Check whether transfers preserve the original message and its attachments or strip away the context.
A better process
- Define a short service taxonomy in language customers understand.
- Keep one maintained owner table for each service and a general review queue.
- Transfer the request with its context and ask only for the missing routing detail.
What a system can do
Route explicit service selections and well-defined message types, then prepare uncertain requests for triage.
Where people stay in control
Routing is an administrative decision. It should not commit to scope, price or eligibility.
Benefits and tradeoffs
The useful outcome
The receiving team starts with the existing context instead of another customer explanation.
The tradeoff
Too many categories make intake harder; too few hide important distinctions. Review actual misroutes before expanding the form.
Test before going live
Use single-service, multi-service, unknown-service and obsolete-service examples. None should disappear or loop between teams.