← Back to news

Announcing the new Copilot auto assist experience EAP

Zendesk

Zendesk has released a new Auto assist experience through early access programme, introducing three core improvements designed to reduce friction in AI-assisted support workflows. The updates—streamlined onboarding with AI-generated procedures, a non-blocking composer that allows agents to work whilst suggestions generate, and a confidence mode that learns in real time—address a fundamental adoption challenge: agents rejecting suggestions because they lack contextual relevance or arrive at inconvenient moments. By removing the requirement for the 'agent_copilot_enabled' tag and filtering suggestions through confidence thresholds, Zendesk is tackling the gap between feature availability and actual usage, a critical distinction for teams measuring ROI on AI tooling.

The timing and scope of this release signal Zendesk's response to competitive pressure in agentic AI. Whilst Salesforce has moved aggressively into autonomous contact centre agents through partnerships like Ribbon, Zendesk's incremental approach focuses on agent augmentation rather than replacement—a strategic choice that reflects either confidence in the co-pilot model or caution about full autonomy. For administrators already managing Auto assist adoption, the confidence mode's real-time learning presents both opportunity and risk: suggestion quality should improve, but teams must monitor whether the system's learning patterns align with their specific workflows, particularly in verticals where consistency and compliance matter more than speed.

The broader implication hinges on whether these usability improvements translate to measurable productivity gains or merely reduce friction without shifting the underlying economics of support. CX leaders should treat this EAP as a testing ground for their own Auto assist maturity—teams struggling with low suggestion acceptance rates will benefit most, whilst those already seeing strong adoption may find the updates marginal. The question for larger deployments is whether confidence mode's learning mechanism will require ongoing tuning or if it genuinely becomes self-optimising, as this determines whether the feature reduces administrative overhead or simply redistributes it.