# Routing calibration records before a cutover | SourceX

Canonical: https://refer.sourcex.si/guides/workflow-exception-routing-calibration
Last updated: 2026-11-05

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.

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:

| Record | Documented behavior | Why it matters before cutover |
|---|---|---|
| Calibration sessions | In 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 scores | A migration that moves quality scores may not move calibration history |
| SLA policy order | Zendesk compares SLA policies from the top of the list and applies the first match; a ticket has one SLA policy at a time | Today's order says nothing about the order a past case was judged against |
| Ticket field changes | Zendesk ticket audits record each update, including the field changed with its previous and new values | Re-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.

| Source | Years | Owner | What survives today | Access ends |
|---|---|---|---|---|
| Routing rule versions | 4 | Workflow engineering lead | Exported quarterly with change comments | Engine license end date |
| Rule execution logs | 1 | Platform administrator | Last 12 months only | Engine license end date |
| SLA policy history | 4 | Support operations manager | Current order only; past orders in change tickets | Not affected |
| Calibration sessions and baselines | 3 | Quality operations head | Calibration dashboard and monthly spreadsheets | QA tool contract renewal |
| Individual reviewer labels | 3 | Quality operations head | Consensus only before year two | QA 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](/guides/exception-handling-ai-agents-data), [procurement approval exceptions](/guides/how-to-assess-procurement-approvals-and-exception-workflows), [logistics exceptions](/guides/how-to-identify-logistics-exceptions-and-their-documented-resolutions), the [freight audit and payment page](/industries/freight-audit-and-payment-company), the [Zendesk system page](/systems/zendesk) and the [industries hub](/industries).

## Go deeper on exception routing calibration

- [Exception routing calibration referral brief template](/resources/exception-routing-calibration-referral-brief-template): a fill-in template for the introduction note.
- [Exception routing calibration exception examples](/guides/exception-routing-calibration-exception-examples): worked cases, such as a case that fits two queues with different SLAs.
- [Exception routing calibration records across systems](/guides/exception-routing-calibration-records-across-systems): a map of the links between case manager, workflow engine and QA tool.
- [Who can license exception routing calibration records](/questions/who-can-license-exception-routing-calibration-records): a short answer on which decision-maker to introduce.

## 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](/register), check the company against [who qualifies](/who-qualifies), and keep the [program terms](/terms) open while you draft the handoff.

## Sources

- https://refer.sourcex.si/terms
- https://support.zendesk.com/hc/en-us/articles/5600997516058-About-SLA-policies-and-how-they-work
- https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_audits/
- https://help.salesforce.com/s/articleView?language=en_US&id=service.service_presence_routing_configuration_settings.htm&type=5
- https://support.zendesk.com/hc/en-us/articles/7043724530842-Setting-up-calibration-in-Zendesk-QA
