# Routing calibration referral brief template | SourceX

Canonical: https://refer.sourcex.si/resources/exception-routing-calibration-referral-brief-template
Last updated: 2026-11-04

A good introduction about exception routing calibration is a single page a quality operations head could forward unedited: headcount, how many queues compete for the same cases, which tools hold the cases and the review history, how far back each goes, how often reviewers met and how much they looked at, who answers for each tool, any dated change, and the CEO, who can approve a licensing talk. It carries counts and roles only. Below: a blank to copy, notes on tricky fields and one finished Illustrative brief.

The template is one of the pages under the [exception routing calibration guide](/guides/workflow-exception-routing-calibration). Reach for it only after the quality operations head says yes to a general description going to SourceX.

## Before you write it

The brief closes a conversation; it does not open one. Check three things first:

- The quality operations head has agreed to sponsor an internal discussion and to have the records described.
- You know the CEO above them, who can approve a licensing conversation, is ready to read it. The [who can say yes decision tree](/questions/who-can-license-exception-routing-calibration-records) explains the other roles.
- You can answer most fields from what owners told you. Where a field would need you to open the QA tool or router, ask the owner and record their answer.

## The blank routing calibration brief

Copy the table and complete the right-hand column. Keep each entry short: a count, a range, a category or a role.

| Field | What to write |
|---|---|
| Company size | Full-time employees at peak, contractors excluded; sites or service centers |
| Business task | The routing decision in one line, such as cases that fit two queues with different response targets |
| Queues | Number of queues and their first-response targets, described |
| Systems | Category and start year: case manager, routing tool, review tool or shared sheet, change tickets |
| Years of history | Earliest usable year per system, and any break at a past migration |
| Review cadence | How often reviewers met, for how long, and roughly how many cases each time |
| Disagreement detail | Whether each reviewer's own call survives, or only the agreed answer |
| Rule edits | Whether past rule wording is kept with dates and reasons, and whether each case shows the rule that moved it |
| Record owner | The role that owns each source |
| Records event | Any dated change the company confirmed, such as a new routing product or a tool contract ending |
| Rights note | Whose content is in the cases: the company's customers, or a client's customers under a services contract |
| Open question | The one thing nobody could answer yet |
| Authorized contact | The CEO, who can approve a licensing discussion, plus the sponsor as working contact |

There is deliberately no field for case text, labels or rule content.

## Field notes for the parts people get wrong

**Review cadence.** Ask where the review meetings left their trace. Some tools hold it natively: Zendesk QA, for example, has reviewers rate the same conversations and lets a session mark a baseline review. "Monthly sessions in the QA tool since 2022" is a concrete entry; so is "a shared sheet per month, case IDs on every row".

**Disagreement detail.** This field decides much of the value. When each reviewer's own call survives, a reader can see which cases were genuinely hard; an agreed answer alone hides that. Write what survives, year by year.

**Rule edits.** Past rule wording explains why a case went where it did, and so does the order of SLA policies in force at the time. Ask whether anyone kept the old policy order, or only today's.

**Case-side history.** Usually the easy line. Zendesk ticket audits, for instance, keep each update with the field's previous and new values. Write something like "queue and priority edits kept for all cases".

**Records event.** Only dated events the company confirmed. Real urgency is a documented replacement or retention date, never an invented deadline.

## A completed brief (Illustrative)

Fictional company, invented for this page; not a real case or a completed deal. A 380-person equipment service provider routes customer cases into five lanes, including Safety hazard and Warranty claim. It recalibrates monthly.

| Field | Completed entry (Illustrative) |
|---|---|
| Company size | 380 full-time at peak, contractors excluded; two service centers |
| Business task | Routing about 2,000 cases a week where some fit two lanes with different response targets |
| Queues | Five lanes; first-response targets from 4 hours (Safety hazard) to 2 business days (Warranty claim) |
| Systems | Case manager since 2018, routing tool since 2021, calibration spreadsheet 2021 to 2022, QA tool since 2023 |
| Years of history | Cases from 2018; rule versions and calibration from 2021 |
| Review cadence | Monthly since 2021, about 60 cases per sample, by the quality operations head's estimate |
| Disagreement detail | Individual labels since 2023; agreed answer only in the spreadsheet years |
| Rule edits | Rule versions with change comments since 2021; router logs the rule per case, kept 12 months |
| Record owner | Quality operations head for review records; workflow engineering lead for rules; support operations manager for cases |
| Records event | Routing tool replaced next quarter; old logs retained 90 days after cutover, confirmed by the company |
| Rights note | Case text written by the company's own customers; rule sets and review decisions are company work product; counsel to confirm |
| Open question | Whether decisions from the spreadsheet years can be linked to the rule versions they changed |
| Authorized contact | CEO; quality operations head as working contact |

Read it as SourceX would. Calibration runs for about five years, the most detailed records start in 2023, the router log has a dated end, and the open question is narrow. Nothing identifies a customer or reviewer. The [worked hard case](/guides/exception-routing-calibration-exception-examples) shows the kind of sequence these records preserve.

## What the brief leaves to SourceX

The brief settles which records exist, where, who owns them and who can authorize a licensing discussion. It does not settle whether they can be licensed, how customer text and reviewer identities would be de-identified, SourceX's current data needs or any offer. Those wait for SourceX's review.

The 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. Sign the Channel Partner Agreement before submitting; attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, with one partner per company.

Wrap the brief in a short note modeled on the [warm introduction brief](/resources/a-warm-introduction-brief-for-a-business-owner), or draft it with the [client opportunity brief generator](/tools/client-opportunity-brief-generator). Background for the conversation is on [exception handling records for AI agents](/guides/exception-handling-ai-agents-data) and the [customer support workflows page](/data-types/customer-support-workflows).

## 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.

When the quality operations head and the authorized contact have approved the completed brief, [register as a partner](/register), confirm the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) before you send it.

## Sources

- https://refer.sourcex.si/terms
- https://support.zendesk.com/hc/en-us/articles/7043724530842-Setting-up-calibration-in-Zendesk-QA
- https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_audits/
