Support is the first instance of the meter, so this is a support audit. Move the window, peek at what the vendor reports, and open any row down to the matched pairs beneath it. Nothing here is aggregated away from its evidence.
| Contact reason | Tier | Tickets | AI returns | Human returns | Gap | {{ excessHead }} |
|---|---|---|---|---|---|---|
| {{ q.contact_reason }} {{ q.pull_back }} |
{{ q.tier }} | {{ q.tickets }} | {{ q.ai }} | {{ q.human }} | {{ q.gap }} | {{ q.excess }} |
| Weighted across 183,000 tickets | {{ totAi }} | {{ totHuman }} | {{ totGap }} | {{ totExcess }} | ||
{{ e.rationale }}
Queue mix, vendor configuration, and how your own people close work all move the durable rate by more than the vendor's marketing does. The same meter runs on any claim/truth data — a read-only Zendesk token, or an export from whatever system you keep the work in.
This is not your number. It applies the gap measured in our calibrated sample — a durable rate {{ estRatioPct }} of the claimed rate, and a vendor fee of {{ estFeeLabel }} on every resolution billed — to the volume you entered. Your queue mix moves it by more than your vendor's marketing does. The only way to get your figure is to measure it.
| Repo area | PRs | AI survival | Human survival | Gap | Rework est. |
|---|---|---|---|---|---|
| {{ a.repo_area }} {{ a.note }} |
{{ a.pr_count }} | {{ a.ai }} | {{ a.human }} | {{ a.gap }} | {{ a.excess }} |
{{ e.rationale }}
Read-only access to your git host and issue tracker. No agent changes, no vendor cooperation, no involvement in how you deploy. You get the same envelope as the support audit: headline pair, evidence rows, named limitations.