This worked example is part of the exception routing calibration guide, which sets out what to inventory before a routing tool is replaced. Here the task is narrower: show, with one hard case, why the sequence of decisions is the evidence and the final rule set is not.
The case: a sparking unit filed as a warranty claim (Illustrative)
A fictional 380-person equipment service provider runs two queues among several. Safety hazard cases target a 4-hour first response. Warranty claims target 2 business days. A customer writes through the web form: "Warranty claim: unit sparking when switched on."
The case fits both queues. The words "warranty claim" describe what the customer wants; the word "sparking" describes a hazard. Which queue it lands in depends on rule order, and the right answer depends on a judgment the rules did not encode. That is the exception: a case that fits two service queues with different SLAs. This is not a real company or a completed deal.
Step by step: who decided and which record caught it
| Step | What happened | Who or what decided | Record that captured it |
|---|---|---|---|
| 1. Arrival | Case created from the web form; priority set to normal by a form default | Form configuration | Case record: text, channel, product, timestamp, priority |
| 2. Routing | Rule 1 matches "warranty" and assigns the warranty queue before rule 2 ("sparking", "smoke", "burning") is checked | Routing tool, by rule order | Rule execution log with rule ID and version, if the router keeps one |
| 3. SLA | The warranty queue's policy applies; first response comes after 19 hours | SLA policy order | Response-target policy on the case; policy list on that date |
| 4. Sampling | The monthly calibration sample of 60 routed cases includes this one | Quality operations team | Calibration session with case IDs |
| 5. Labels | Three reviewers label it independently: two say Safety, one says Warranty | Reviewers | Individual labels with reviewer, comment and date |
| 6. Ruling | Safety terms override product-claim terms, whatever else the case says | Quality operations head | Baseline ruling in the review meeting |
| 7. Correction | The safety rule moves above the warranty rule; a safety-first routing label is added; next month's sample is re-checked | Workflow engineering, on the ruling | New rule version with a change comment citing the meeting |
Steps 2 and 3 are not hypothetical mechanics. In Zendesk, ticket triggers are checked in order from first to last each time a ticket is created or updated, so the first matching rule can decide the queue before a later, better rule is reached. After triggers run, the ticket goes through the SLA system: policies are compared from the top of the list, the first match applies, and a ticket holds one SLA policy at a time. A blank Priority field means no SLA applies at all, which is why the form default in step 1 matters too.
Why this sequence is useful evidence
Each record answers a different question a reviewer would ask:
- Steps 1 to 3 show the problem as the system saw it: what was known, what the rules did with it, and what it cost in time.
- Steps 4 and 5 show people disagreeing about the same facts, which is the hardest part of routing to capture and the most informative.
- Step 6 shows an authorized judgment that resolves the disagreement and states a principle.
- Step 7 shows the principle turned into a rule, and the re-check shows whether it worked.
Calibration tools often keep steps 4 to 6 apart from everyday quality data. In Zendesk QA, for example, reviewers rate the same conversations and compare scores and comments, a session can mark a baseline review, and calibration results appear only in the calibration dashboard, not in internal quality scores. A report built from quality scores alone would never show the disagreement.
Together the seven records connect a business exception to an authorized action and a checked result. That is the kind of operational history described on why operations data is valuable and in exception handling records for AI agents.
The three records most often lost
Ask about these first, because they disappear quietly:
- The rule version at step 2. Engines often log the outcome (queue assigned) but not which rule produced it. Keep only today's rule set and the case looks as if it was always routed correctly.
- Individual labels at step 5. Many teams keep only the consensus. The split vote is what shows the case was genuinely hard.
- The ruling at step 6. Rulings are often written in meeting notes or chat, with no link to the rule change they caused.
Keep only the case and nobody can see why it took 19 hours. The system map shows which system usually holds each of these and the identifier that joins them.
How to recognize similar cases at a client
A workflow automation advisor can spot this pattern in a short conversation without looking at a single case. Listen for:
- Two or more queues with different response targets, and keyword or category rules that decide between them.
- A regular review or QA sampling routine, monthly or quarterly, with named reviewers.
- Rule changes that someone can tie to a review finding ("we moved the safety rule up after the March review").
- A dated records event, such as a routing tool replacement or the end of a QA tool contract.
Similar exceptions appear in other workflows: a procurement request that fits two approval paths, covered in procurement approval exceptions, or a closure call that could go to retention or cancellation, as on the call center closure recordings page.
What a partner can say, and what stays unknown
Describe the case history at metadata level: which queues, how many review cycles, how many cases per sample, whether individual labels and rulings survive, which systems hold them and who owns them. Never pull cases or labels to demonstrate the point. The referral brief template gives the fields.
The introduced company needs 50+ full-time employees at peak (contractors excluded), a 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. Unknown until SourceX reviews it: whether customer case text can be used, how it would be de-identified, SourceX's current data needs and any offer. Partners sign the Channel Partner Agreement before submitting; 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 can still replay its hard routing cases from arrival to rule change, register as a partner, check the company on who qualifies and read the program terms before you describe them to the quality operations head.