# Who can license routing calibration records? | SourceX

Canonical: https://refer.sourcex.si/questions/who-can-license-exception-routing-calibration-records
Last updated: 2026-11-04

Introduce the CEO, who can authorize the discussion and sign, with general counsel reading the customer terms, and ask the quality operations head to convene. That person ran the review meetings and knows what survived, but seldom has the standing to approve a licensing talk alone. Whoever administers the routing product can pull files; that is access, not authority. An outside vendor or integrator may keep copies from a project, yet the material belongs to the company that ran the queues.

This decision tree belongs to the [exception routing calibration guide](/guides/workflow-exception-routing-calibration). It answers one question for workflow automation advisors: inside a service operation, who can say yes to a conversation about its calibration history?

## Why the quality operations head comes first

Few people outside the quality team know these records exist. Every agent sees cases; engineers see rules. The review meetings, the split votes and the agreed answers usually sit in a tool or a folder only the quality operations head looks after. In Zendesk QA, for example, those results stay on a separate calibration dashboard and leave internal quality scores untouched, so even peers in operations may never have seen them.

That makes the quality operations head the one person who can describe the material honestly: how often reviewers met, how many cases they looked at, whether each reviewer's own call survives, and whether agreed answers led to recorded edits. Knowing the records is not owning the company's rights in them. Start with this person; do not finish with them.

## The decision tree, step by step

Each answer moves you along the tree or tells you to stop. The graphic shows the same path from left to right.

1. **Who ran calibration?** If your contact is a router administrator, team lead or reviewer, ask who owns the sampling and the rulings. The answer is the quality operations head or head of service quality.
2. **Will they convene?** Ask whether they would sponsor an internal conversation about the company's review history. If no, stop.
3. **Is anyone outside the company holding records?** A routing vendor, implementation partner or outsourced QA provider may hold copies. Note them, but do not approach them. They are not the source of authority.
4. **Whose content is in the cases?** Separate the company's own work product (rule sets, rule versions, sampling method, rulings) from case text written by customers or tied to a client's customers. Customer content goes to the counsel branch.
5. **Are people identifiable?** Reviewer labels carry reviewer names or IDs; case histories carry agent and customer identifiers. These go to counsel and the privacy owner.
6. **Who approves new uses of company information?** The CEO, advised by general counsel. In an outsourcing provider, add the account executive for any client whose contract counsel flags.

The introduction is ready when you have a named convener and a named approver.

## Access, knowledge and authority: a role table

| Role | What they have | Can they authorize a licensing discussion? |
|---|---|---|
| Reviewer or team lead | Their own labels and comments | No; a participant in the reviews |
| Routing tool administrator | Rule exports, execution logs, retention settings | No; technical access is not authority |
| Platform administrator for the case manager | Case histories and field change audits | No; describes what exists |
| Routing vendor or implementation partner | Copies of configurations from the project | No; the records belong to the operating company |
| Quality operations head | Sessions, labels, rulings, completeness | Rarely alone; the right convener |
| General counsel | Customer and client contract terms, privacy duties | Advises; the gate for customer content and identities |
| CEO | Company agreements and commitments | Yes, advised by counsel |

Case-side history is often the easiest to describe because platforms record it in detail: Zendesk ticket audits, for instance, record each update with change events naming the field and its previous and new values. Detail in the system says nothing about who may license it.

## Records that send the conversation to counsel

- **Customer case text.** Messages written by customers, or about a client's customers, are governed by customer terms and, for outsourcing providers, client contracts. The guide on [whether an outsourcing vendor can share client data](/questions/can-an-outsourcing-vendor-share-client-data) explains the usual limits.
- **Reviewer and agent identities.** Where EU law applies, personal data includes information that identifies a person by name or an identification number. Labels tied to named reviewers fall in that group, so the privacy owner joins counsel to plan de-identification.
- **Records held by a former vendor.** If reviews ran in a tool whose contract has ended, check what the exit terms say before anyone describes those records as available.

Rule sets and rulings written by the company's own staff usually raise fewer questions, but counsel still confirms.

## Two false starts to avoid

**Starting with the router administrator.** They answer quickly and often offer an export. Decline: partners never handle raw client records, and an export does not carry authority. Ask the administrator who owns the review program instead.

**Starting with the vendor.** The routing vendor knows the configuration better than anyone, and may even suggest the conversation. But the vendor cannot license the company's records, and going around the company damages trust. Every introduction goes through the operating company's own convener and approver.

## What stays unknown until SourceX's rights review

The tree tells you who can authorize a conversation. It does not settle whether the records are licensable, how customer content would be de-identified, whether there is SourceX's current data needs for review histories, or any offer. [Why data rights matter](/proof/why-data-rights-matter) explains why that review comes first. For context on the value of these records, see [why operations data is valuable](/proof/why-operations-data-is-valuable) and [exception handling records for AI agents](/guides/exception-handling-ai-agents-data); the [system map](/guides/exception-routing-calibration-records-across-systems) helps the convener describe what exists.

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. 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, and one partner is credited per company. Put the named approver in the [referral brief template](/resources/exception-routing-calibration-referral-brief-template).

## 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 has agreed to convene and named the executive who can approve, [register as a partner](/register), check the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) before you make the introduction.

## 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/
- https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng
