Define routing as a decision that produces one accountable owner and a clear reason. Apply service, region and capacity rules in an agreed order, and send unresolved cases to a named fallback queue. An enquiry should never disappear because no rule matched or several rules matched equally well.
Begin with the CRM’s existing assignment features. A custom router is justified only when a specific combination of rules, external availability data or exception handling remains difficult to configure.
Three rules point in different directions
Fictional enquiry E-115 requests a training programme for a customer with offices in Bristol and Boston. The service is leadership training, the buyer is an existing account managed by Sam, and the requested session is online. Sam is away for two weeks.
A territory-only rule may send it to the UK team, while a service rule sends it to a specialist and an account rule retains Sam. The business must decide precedence. The software should not make that policy choice from the customer’s wording.
| Step | Question | Outcome |
|---|---|---|
| Account relationship | Is there a responsible account owner? | Keep relationship visible |
| Service expertise | Which team handles this request? | Select qualified internal queue |
| Availability | Can the owner accept it now? | Assign approved cover if needed |
| Fallback | Is anything unresolved? | Send to intake coordinator |
Write the precedence in plain language
Agree whether existing account ownership overrides territory, whether service expertise overrides general workload balancing, and what counts as unavailable. “Capacity” needs a defined measure; the number of open records may not represent their complexity or urgency.
For E-115, a reasonable configured policy might assign an available service coordinator while keeping Sam as the account relationship owner. That is an example, not a universal recommendation. The operating team should choose and document the rule.
- Name the fields each rule uses.
- Define precedence when rules conflict.
- Separate accountable owner from people notified.
- Specify absence and cover arrangements.
- Provide a fallback with a monitored next action.
- Record reassignment reasons and history.
Require an acknowledgement where it matters
A notification can be delivered while nobody accepts the task. Where the handoff is important, record acceptance or return by the receiving owner. If a person declines because the enquiry belongs elsewhere, preserve their reason and route it deliberately.
NIST’s framework includes establishing responsibilities for AI-supported systems. Our recommendation is to make responsibility visible at the enquiry level, with an owner for unresolved routing rather than an anonymous automation queue.
Handle uncertain classification conservatively
An assistant may propose the service category from free text, but it should expose ambiguous requests. “Training support” could mean buying a course, changing a booking or asking for technical help with a platform. The wrong category can send the enquiry to a team that cannot act.
Do not use inferred personal characteristics to prioritise people. Route business requests using relevant, agreed operational fields and let staff resolve ambiguous cases. The purpose is accountable handling, not opaque ranking of customers.
Provide a simple manual reassignment action with a reason. Staff will encounter legitimate exceptions that were not anticipated in the first rule set. Those cases can inform a later policy change without requiring an emergency edit to the automation.
Test failures as well as ordinary assignments
Prepare fictional cases with missing regions, multiple services, existing owners on leave and simultaneous arrivals. Confirm that each case produces an owner or a visible exception. Test what happens when the capacity source is stale or unavailable.
Then review actual handoff behavior in an authorised pilot: acceptance, reassignment and time spent resolving errors. A CRM routing workflow should remain understandable when the normal rule fails. If the current CRM can deliver that behavior through configuration, use it before adding another service to maintain.
Sources and further reading
AI-assisted research and writing, checked against the linked sources. Worked examples are fictional. Product features can change; confirm the details in your own account.