Use GOVENANT and an AI support agent + your help desk together — govern the AI customer-service agents, not the framework. “Ticket closed” is a claim. “Problem resolved” is a record.
An e-commerce brand lets an AI support agent auto-resolve tier-1 tickets; it closes 8,000 a week and reports a 90% deflection rate.
A closed ticket isn’t a solved problem. Nobody is measuring how many “deflected” customers reopened or churned — the deflection number and the trust number are drifting apart, and only one is on the dashboard.
With resolution verified against the record and reopens logged independently, verified resolution is 68% and a reopen spike traces to a broken returns flow the agent kept “resolving.” The brand can now show customers a delivery record with the misses in it — the one thing a competitor can’t fake.
The substrate: The ticket and conversation record: resolutions, reopens, escalations, CSAT — outcome rows a support agent’s “handled” is checked against.
The path — Native substrate: The platform already produces records that map to the standard — the sweep reads what it already keeps.
| GOVENANT shape | an AI support agent + your help desk source |
|---|---|
| Duty-run | One per ticket/conversation from your help desk (Zendesk/ServiceNow/Intercom) |
| Verified outcome | Resolved AND not reopened within N days — deflection is not resolution |
| Independent watchdog | Reopens and escalations, logged separately from the agent’s own resolution flag |
| Miss | Reopened tickets, silent escalations, abandoned chats |
The substrate shapes and acceptance tests are open (CC BY 4.0): developer integration · the portable schema.
Wear the Built-on badge with a real integration; publish self-assessed levels to the registry with probe logs, open to challenge, never “certified.” A support org that can show verified resolution — misses and all — has a trust asset its competitors can only assert.
It will never say “supported” or “certified” before a working example lands and its record is public — progress lives in the GitHub issue. Holding our own examples to the standard’s claims discipline is the product.
All sample projects · Govern AI customer-service agents · All integrations · Run the audit