Approve manual routing exceptions without undermining fairness
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
Consider a hypothetical comparison: one manager redirects a promising lead to a preferred representative; another redirects a lead because the customer explicitly requested a previous contact. Both changes appear as manual reassignments, but only one has a defensible reason. An ownership history alone cannot explain the difference.
A useful manual lead assignment exception policy requires three decisions before ownership changes: why a valid routing result should be overridden, who may approve that deviation, and how it affects subsequent allocation. Record the rule-selected owner alongside the approved owner so the decision remains reconstructable.
The recommended operating design below covers authorised departures from routing rules, not access-control configuration or compensation disputes. Its filled register and reconciliation are fictional worked examples, not customer results or evidence of product capabilities.
1. Separate exceptions from corrections
Classify the event before seeking approval:
- Ordinary routing: the current rule selects an eligible owner and no departure is needed.
- Data correction: an incorrect territory, language, or account field caused the wrong route. Correct the input and record the corrected decision.
- Manual exception: the inputs and rule are valid, and the selected owner remains eligible, but documented circumstances justify another owner.
- Rule defect: recurring legitimate exceptions suggest that the rule needs prospective revision.
If a newly discovered requirement makes the original owner ineligible, treat the reassignment as a routing correction, not an exception. Preserve the initial result for traceability, but use corrected eligibility for allocation accounting. An erroneous route should not automatically create a claim to a replacement lead.
Keep assistance separate from ownership. A specialist joining one call may solve the problem without changing the accountable owner. A genuine specialist ownership exception arises when the general owner remains eligible under the current rule, yet a documented operational benefit justifies transferring responsibility.
2. Make permitted reasons testable
Reason codes should point to evidence another reviewer can inspect. “Business need” and “management decision” are too broad to distinguish necessity from preference.
- Customer-requested owner: retain the customer's explicit request and confirm the named person is eligible and available. A representative's prediction of customer preference is insufficient.
- Specialist ownership need: identify the specialist benefit, confirm the ordinary owner remains eligible, and explain why consultation without transfer would not adequately serve the engagement.
- Continuity dependency: link active related work and explain why changing the accountable contact would disrupt it. Prior acquaintance alone is insufficient.
- Unexpected unavailability: document an availability change after valid assignment and explain why the normal fallback does not resolve it. If availability data were simply wrong when routing occurred, classify the event as a correction.
Exclude unsupported preferences, informal promises of better opportunities, and general assertions that someone is more likely to close. If performance should influence routing, propose a prospective rule with defined criteria rather than selecting individual opportunities privately.
A permitted reason does not automatically justify every requested recipient or settle the balance treatment. Approval must address both.
3. Name the decision-makers before requests arrive
The requester supplies evidence and a proposed owner. A routing approver accepts or rejects the reason. An allocation steward records execution and reconciles balances. In a small team, one person may perform the latter two roles, provided they are not the requester or recipient.
- Routine exceptions: the designated approver may authorise a specific transfer once evidence and accounting treatment are complete.
- Conflicted requests: use a named alternate if the approver requested the change, would receive the lead, or directly benefits.
- Cross-pool transfers and offset waivers: require an independent second review because they change who bears the allocation cost.
- Unsupported reasons: reject them; seniority does not convert preference into evidence.
Approval identifies the lead, recipient, reason, and accounting decision. It is not standing permission to redirect similar leads.
For urgent needs, define temporary cover authorised by a named duty manager. Prefer assistance without ownership transfer while review is pending. If a provisional transfer is necessary, record it immediately and assign a review point. Retrospective review must remain able to reject it and repair the accounting; never backdate approval.
4. Keep actual counts, baseline counts, and balances separate
For the hypothetical count-based policy used here, maintain three distinct records:
- Actual counts: assignments each representative actually receives under the team's normal counting convention. Each assignment counts once.
- Baseline counts: assignments produced by the ordinary rotation before exception-balance intervention. Retain the selected owner at each decision.
- Exception ledger: unresolved differences attributable to exceptions and their later settlement. Positive means an extra assignment relative to baseline; negative means a missed assignment.
The ledger must never add a second assignment to the recipient's actual count. It explains a difference, not another unit of work. In this simple example, where all differences arise from these events, the ledger equals actual counts minus baseline counts.
Worked reconciliation within one pool
All figures in this reconciliation are hypothetical. Nisha and Leo begin with actual and baseline counts of four each, with zero ledger balances. The ordinary rotation selects Nisha for the next lead, but an approved customer request transfers it to Leo.
- Before transfer: Nisha actual 4, baseline 4, ledger 0; Leo actual 4, baseline 4, ledger 0.
- After transfer: Nisha actual 4, baseline 5, ledger −1; Leo actual 5, baseline 4, ledger +1.
- Later settlement: the ordinary rotation next selects Leo. Both remain eligible, so the balancing rule assigns that lead to Nisha instead.
- After settlement: Nisha actual 5, baseline 5, ledger 0; Leo actual 5, baseline 5, ledger 0.
The settlement closes both ledger entries. Preserve their history, but retire them from active balancing. Do not also give Nisha another replacement or subtract an assignment from Leo's actual count.
The proposed settlement rule is specific: when ordinary routing selects a representative with a positive balance, an eligible, available representative with a negative balance may receive that assignment instead. Choose the oldest open deficit first; use the existing rotation order to break ties. If no eligible pairing exists, leave the balance open. Eligibility always comes before settlement.
Cross-pool treatment needs a separate decision
Do not translate a general-pool deficit into specialist work without an agreed conversion rule. For the specialist example below, independent reviewers exclude the transfer from general-rotation accounting, leave that rotation position unchanged, and count the assignment once in the specialist pool. They record the unoffset benefit explicitly. This is an approved accounting exception, not proof of equal opportunity.
Do not invent value weights because a lead looks attractive. Count equality and opportunity quality are different questions.
5. Reuse this filled hypothetical exception register
All names, organisations, identifiers, evidence descriptions, and decisions below are fictional. Each entry uses the same reusable fields: request, baseline, eligibility, evidence, authority, accounting, execution, and closure.
EX-A: Customer-requested owner — approved with settlement
- Request: coordinator Mara requests that enquiry H-101, Cedar Studio, move to Leo before ownership changes.
- Baseline and eligibility: general rotation selects Nisha. Both Nisha and Leo are eligible and available.
- Evidence: the customer explicitly requests Leo following an earlier discussion; the enquiry containing that request is referenced in the record.
- Authority: Priya approves; she is neither requester nor recipient. Owen is allocation steward.
- Accounting: use the reconciliation above. Actual assignment: Leo, once. Baseline assignment: Nisha. Open ledger: Nisha −1, Leo +1. No extra assignment is posted from the ledger.
- Execution: Owen confirms the authorised transfer and Leo's acceptance of responsibility.
- Closure: the later eligible assignment to Nisha settles both balances. Owen links that assignment and marks the ledger entries retired.
EX-B: Specialist ownership need — approved with explicit cross-pool treatment
- Request: Mara requests that enquiry H-102, Alder Works, move from the general rotation to specialist Dev.
- Baseline and eligibility: the valid current rule selects Nisha. All routing inputs are correct. Nisha remains qualified and eligible to own the enquiry, including coordinating specialist support.
- Evidence: the discovery note describes several linked technical workshops. Dev already owns their related specialist workstream. One accountable workshop owner would avoid repeated ownership handoffs; occasional consultation would still leave scheduling and follow-up split. This supports a discretionary transfer, not a finding that Nisha is ineligible.
- Authority: Priya approves the ownership deviation. Independent reviewer Sal separately approves its cross-pool accounting treatment.
- Accounting: record Nisha as the pre-exception rule-selected owner. Exclude this event from general-rotation counts and leave Nisha's turn unchanged. Count the assignment once for Dev in the specialist pool; create no general-pool settlement pair. Record the unoffset specialist benefit for review.
- Execution: Owen confirms Dev accepted responsibility and records the general rotation position before and after.
- Closure: ownership transfer is complete; the accounting waiver remains reviewable. Repeated cases trigger review of pool design rather than indefinite manual waivers.
EX-B is accounted for separately because the chosen policy has no conversion between general and specialist assignments. The ownership reason and the accounting waiver require separate approval; neither silently justifies the other.
EX-C: Unsupported preference — rejected
- Request: manager Ellis requests that enquiry H-103, Birch Services, move to Leo.
- Baseline and eligibility: Nisha is the eligible general-rotation owner.
- Evidence: Ellis says Leo deserves a stronger opportunity. No permitted reason is supported.
- Authority: alternate approver Sal rejects the request. Ellis cannot approve their own request.
- Accounting: no transfer or exception adjustment. The ordinary assignment counts for Nisha in actual and baseline records.
- Execution and closure: Owen confirms ownership remained unchanged and records the rejection. Broader allocation concerns go to prospective rule review.
Retain rejected requests. Recording approvals alone hides attempted preferential allocation.
6. Repair failed changes without duplicate adjustments
Keep request, approval, execution, and balance posting as separate statuses. Approval does not prove ownership changed; a proposed recipient is not an actual assignment.
If an approved transfer never occurs, do not post its planned ledger entries. If entries were already posted, reverse them with a linked correction rather than deleting history. If ownership moves again, reconcile the final actual recipient against the recorded baseline and existing adjustments before posting anything further.
For unauthorised transfers, preserve the event, confirm who owns the next customer action, and obtain an independent decision on restoration or retention. Retaining the current owner to avoid customer disruption does not validate the original action.
Link duplicate requests before posting balances. Apply the team's established cancellation convention consistently rather than improvising an exception-only treatment.
7. Review unresolved balances and concentrated benefits
Review by requester, approver, recipient, reason, and pool. Look for missing evidence, repeated cross-pool waivers, and transfers without execution confirmation. Check whether deficits remain open because eligible settlement opportunities never occur.
Concentrated customer requests may be genuine; they still deserve examination. Likewise, a zero count balance cannot establish equal opportunity quality. Treat these patterns as diagnostic signals, not proof of misconduct or fairness.
If a deficit cannot reasonably settle under current eligibility, escalate it for an explicit policy decision. Do not quietly erase it or assign an unsuitable lead to clear the ledger.
8. Test whether another reviewer can reconstruct the result
Before using the register, name the approver, alternate, and steward. Agree the counting convention, settlement rule, cross-pool treatment, and evidence location.
For a hypothetical trial covering ten requests, check every decision for a recorded baseline, eligibility finding, evidence, authority, and accounting treatment. For approvals, verify execution separately.
Ask an uninvolved reviewer to reconstruct one transfer, one settlement, and one rejection. The observable outcome is not merely fewer manual changes: it is a history explaining who received each lead, why the rule was overridden, and whether any allocation difference remains unresolved.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications