Exception routing calibration: what to inventory before a routing engine replacement

Short answer

Before replacing a routing engine, inventory the calibration history: the sampled cases reviewers re-checked, the routing labels they assigned, the reviewer decisions and baseline rulings, each version of the routing rules, and the SLA policy each case received. Record the years covered, which system holds each record, who owns it, and when the old engine or its logs go dark. Keep it at metadata level, then introduce the quality operations head to start the conversation.

Visual briefFull-size diagram
An annotated stack of five calibration record types (rule versions, execution logs, SLA policy order, calibration sessions and reviewer labels), each tagged with the question to answer before the old routing engine is switched off.
Illustrative inventory questions. The note that calibration results sit apart from quality scores reflects Zendesk QA's documented behavior.

Exception routing calibration is the periodic check that cases land in the right queue: a sample of routed cases is re-labeled by reviewers, disagreements are settled, and the rules are adjusted. Over years, that loop builds a record of how a service operation decided what each kind of case really was. A routing engine replacement moves the rules forward and often leaves the loop behind.

What should be inventoried before a routing engine replacement affects exception routing calibration history?

A short list, filled in with the client's operations lead, before the cutover plan is final:

  • Rule versions. How many versions of the routing rules exist, how far back, and whether the old engine can export them with dates and change comments.
  • Execution logs. Whether the engine logged which rule fired per case, and its retention period.
  • SLA policy history. The list order and conditions over time, not only today's.
  • Calibration samples. How many cycles, how many cases per cycle, and where the case IDs live.
  • Reviewer labels and rulings. Which tool or spreadsheet, whether individual reviewer labels survive or only the consensus, and who wrote the baseline rulings.
  • Owners. The named owner of each source, and which contracts govern customer content inside the cases.
  • The real deadline. The date the old engine's license, logs or admin access ends.

Nothing on this list should be copied or retained without the company's authority; the list exists so the decision is made knowingly.

Why do calibration records rarely move with the routing rules?

Because they live in different places and answer different questions. A migration project asks what the new engine must do on day one, so it carries the current rules and queues. The calibration history explains why the rules look the way they do, and it is spread across tools that are not part of the cutover.

Three documented behaviors show the gap:

RecordDocumented behaviorWhy it matters before cutover
Calibration sessionsIn Zendesk QA, reviewers rate the same conversations, a session can mark a baseline review, and results appear only in the calibration dashboard, not in quality scoresA migration that moves quality scores may not move calibration history
SLA policy orderZendesk compares SLA policies from the top of the list and applies the first match; a ticket has one SLA policy at a timeToday's order says nothing about the order a past case was judged against
Ticket field changesZendesk ticket audits record each update, including the field changed with its previous and new valuesRe-routing events may survive in the helpdesk even if the engine's own logs do not

Salesforce Omni-Channel works on a related idea: routing priority sets the order in which work items from queues reach service reps, lower numbers first, with ties routed oldest first. Whatever the platform, the inventory question is the same: is the history of these settings kept anywhere, or only their current values?

What does a finished inventory look like?

The example is Illustrative, for a fictional 400-person business process outsourcing provider replacing its routing engine at the end of a contract.

SourceYearsOwnerWhat survives todayAccess ends
Routing rule versions4Workflow engineering leadExported quarterly with change commentsEngine license end date
Rule execution logs1Platform administratorLast 12 months onlyEngine license end date
SLA policy history4Support operations managerCurrent order only; past orders in change ticketsNot affected
Calibration sessions and baselines3Quality operations headCalibration dashboard and monthly spreadsheetsQA tool contract renewal
Individual reviewer labels3Quality operations headConsensus only before year twoQA tool contract renewal

The partner's version of this table contains no cases, labels or rules: just counts, names and dates. It tells SourceX and the company where to look later.

Does the company qualify?

The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

For an outsourcing provider, the cases usually belong to its clients' customers, so client contracts decide much of what can be licensed; that is for the rights review, not the partner. Partners sign the Channel Partner Agreement before submitting, and the first valid introduction within the 90-day window is credited when the company submits a verified application. As an Illustrative figure, not a forecast: an Actual Supplier Payout of $400,000 for a qualifying completed handoff would mean a default reward of $70,000. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details. For related reading, see exception handling records for AI agents, procurement approval exceptions, logistics exceptions, the freight audit and payment page, the Zendesk system page and the industries hub.

Go deeper on exception routing calibration

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a client's routing engine cutover is scheduled and its calibration history lives only in the old system, register as a partner, check the company against who qualifies, and keep the program terms open while you draft the handoff.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Is a routing rule set worth anything without the cases?

Much less. A rule set says what the engine was told to do. The sampled cases, the labels reviewers gave them and the decision that changed the rules show what went wrong and how it was judged, which is the part a rule export cannot carry.

Does a workflow automation advisor need admin access to describe these records?

No. Describe them at metadata level: which systems, how many calibration cycles, how far back, who owns them. Having admin access for a project does not give you, or the client's admins, authority to license the records.

What if calibration was done in spreadsheets?

That is common and still useful, provided each row can be tied back to a case ID and a date. Note the file location and owner on the inventory. SourceX's review decides whether the material is usable.

Sources

  1. refer.sourcex.si/terms
  2. support.zendesk.com/hc/en-us/articles/5600997516058-About-SLA-po…
  3. developer.zendesk.com/api-reference/ticketing/tickets/ticket_audits
  4. help.salesforce.com/s/articleView
  5. support.zendesk.com/hc/en-us/articles/7043724530842-Setting-up-c…

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment