Zendesk has redesigned how AI-generated message disclosures appear across mobile SDKs and social channels, moving from a repetitive line-item label to an integrated indicator within the bot's display name (e.g., "Zara · AI"). The change rolls out June 11, 2026, and addresses a practical friction point: the previous design created visual clutter in longer conversations, consumed unnecessary characters in SMS and WhatsApp—directly inflating messaging costs—and felt redundant across multiple AI-generated responses. Critically, Zendesk's framing acknowledges that regulations like the EU AI Act mandate transparency about AI interactions without requiring disclosure on every individual message, giving teams flexibility to meet compliance obligations without degrading the conversation experience.
The shift carries meaningful implications for CX teams already managing multi-channel deployments. Teams can now disable the AI label per channel via API (the showAIDisclaimer parameter), but this introduces a compliance responsibility: disabling the label places the burden on your organisation to ensure regional regulatory adherence. For teams operating across jurisdictions with varying AI transparency requirements, this flexibility is valuable—but it also means audit trails and documentation become more critical. The question for many teams will be whether the UX improvement justifies the added compliance governance overhead, particularly for those without dedicated legal or regulatory review processes embedded in their Zendesk administration workflows.
The redesign reflects a broader industry tension: as agentic AI becomes more prevalent in customer interactions, the blunt-force approach of labelling every AI message becomes unsustainable at scale. Zendesk's solution is pragmatic rather than transformative, but it signals that vendors are moving away from one-size-fits-all disclosure models toward channel-specific and region-specific controls. For support leaders evaluating AI-powered tooling, this update suggests that transparency requirements and user experience are no longer binary trade-offs—but only if your team has the operational maturity to manage the compliance complexity that flexibility introduces.
Announced on Rollout starts Rollout ends June 11, 2026 June 11, 2026 June 11, 2026 We are excited to announce updates to the AI label across Social Messaging channels and Mobile SDKs, along with the ability to disable the label per channel via API. This is a follow up to the similar improvement in W
Announced on Rollout starts Rollout ends June 11, 2026 June 11, 2026 June 11, 2026 We are excited to announce updates to the AI label across social messaging channels and Mobile SDKs, along with the ability to disable the label per channel via API. This is a follow up to a similar improvement in Web