This page maps those links for the exception routing calibration guide. A workflow automation advisor can use it in one meeting with the client's support, engineering and quality leads: name each system, the identifier it stores and the person who answers for it, then mark each link as intact, partial or missing.
Three systems, one calibration loop
Calibration runs in a loop. Cases get routed, a sample is pulled, reviewers label it blind, a lead settles disagreements, and an engineer edits a rule. Each turn of the loop writes to a different place, and each place uses its own identifiers.
- Case manager. The ticket itself: text, channel, timestamps, queue, priority and a trail of field edits. Many platforms keep this trail in detail; Zendesk's ticket audits, for example, log every update with change events showing a field's previous and new values. Identifier: case ID.
- Routing tool. The routing logic: ordered rules, their versions and, on good platforms, a per-case record of which rule acted. Identifier: rule ID plus version, and ideally the case ID in each log line.
- Calibration store. A QA product or a shared spreadsheet holding sessions, blind labels, comments and the agreed answer. Identifier: session ID, plus the case ID on each label row if someone thought to add it. Some products mark the agreed answer explicitly; Zendesk QA, for one, lets a session flag a baseline review.
- Change log. Often a ticketing project where engineers request and approve rule edits. Identifier: change ticket ID, which may or may not cite the session.
System, record, linking key and owner
| System | Record | Linking key | Typical owner |
|---|---|---|---|
| Case manager | Case with text, channel and timestamps | Case ID | Support operations manager |
| Case manager | Field change history: queue, group, priority | Case ID and audit timestamp | Platform administrator |
| Case manager | SLA policy and target applied to the case | Case ID and policy name | Support operations manager |
| Routing tool | Rule set and its order on a given date | Rule ID, version and effective date | Workflow engineering lead |
| Routing tool | Execution log: which rule acted on which case | Case ID and rule ID with version | Platform administrator |
| QA tool or shared sheet | Calibration session and sample | Session ID and case IDs | Quality operations head |
| QA tool or shared sheet | Individual reviewer labels and comments | Session ID, case ID and reviewer | Quality operations head |
| Change log | Rule change with comment | Change ticket ID citing the session ID | Workflow engineering lead |
Two rows carry most of the risk: the per-case execution log, because it may be kept only for a short window, and the label rows, because shared sheets rarely carry the case ID.
One fully joined case (Illustrative)
A fictional 450-person broadband provider runs its own customer service team. Two of its queues are Billing disputes (24-hour first response) and Retention (4-hour first response). A customer emails: "I was double billed again. Cancel my service." Nothing here describes a real company or a completed deal.
| Stage | System | Record | Key |
|---|---|---|---|
| Arrival | Case manager | Case 884210 created by email, priority normal | Case 884210 |
| Routing | Routing tool | Rule R-14 v6 ("billed", "charge") assigns Billing disputes | Case 884210, rule R-14 v6 |
| Clock | Case manager | Billing policy, 24-hour target; first reply at 21 hours | Case 884210, policy Billing standard |
| Outcome | Case manager | Status solved; customer canceled two days later | Case 884210 audit events |
| Sample | QA tool | Calibration session CS-2025-07, case included | Session CS-2025-07, case 884210 |
| Labels | QA tool | Reviewers: Retention, Retention, Billing | Session, case and reviewer |
| Ruling | QA tool | Baseline: stated intent to cancel overrides the billing topic | Session CS-2025-07 |
| Change | Change log | Retention rule R-09 moved above R-14; R-14 becomes v7 | Ticket citing CS-2025-07 |
Every row joins because the case ID appears in the router log and the QA session, and the change ticket cites the session. Take away the rule version in the router log and the routing step becomes a guess.
Where the joins break
| Join | Usual break | Question to ask the owner |
|---|---|---|
| Case to rule fired | The router logs the queue assigned, not the rule that assigned it | Does the log name the rule and version per case, and for how long is it kept? |
| Case to SLA policy applied | The policy order is edited in place with no history | Is there a record of the SLA policy order over time? |
| Case to reviewer label | Labels kept in a shared sheet keyed by row number or agent name | Does every label row carry the case ID and date? |
| Ruling to rule change | Rules edited with no reference to the calibration decision | Do change tickets cite the session or ruling? |
A replacement project that migrates open cases and today's configuration but not the router log or the QA history keeps the outcome and loses the reasoning. The worked hard case shows what that reasoning looks like step by step.
What the map does and does not settle
A finished map shows which records exist, which years they cover, how they join and who owns them. It does not show whether they can be licensed. Case text written by customers falls under customer terms, so counsel shapes the answer; the who can license decision tree shows who decides. Platform background is on the Zendesk system page, and why operations data is valuable explains why the joined history matters more than any single export.
The introduced company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license 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. What stays unknown until SourceX reviews it: rights in customer content, de-identification, SourceX's current data needs and any offer. 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.
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 case IDs run through its router log and review sessions, register as a partner, confirm the company on who qualifies and read the program terms before you share the map with SourceX.