Safely manage your Zendesk from the AI assistant you already use, via the Deltastring MCP. Beacon configuration platform →
← Back to news

Platform Updates: New Conditions, AI Models, and Permission Controls Announced

Zendesk

Zendesk's October 2026 product announcements reveal a platform consolidating around workflow sophistication and AI-native operations. The core update—AND/OR condition grouping in Action Builder—addresses a fundamental friction point: admins previously required multiple branches or duplicate workflows to express complex routing logic. By enabling nested conditions up to two levels deep, Zendesk eliminates unnecessary workflow bloat and reduces maintenance overhead. Simultaneously, the platform expanded AI model flexibility by making OpenAI, Gemini, and Claude connector selections dynamic, allowing teams to adopt latest models automatically through their connected accounts. These changes work in concert to reduce operational complexity whilst increasing capability depth—a strategic positioning that matters as teams increasingly rely on workflow automation to handle volume and routing decisions that once required manual intervention.

The secondary wave of announcements signals Zendesk's commitment to knowledge consolidation and permission granularity. Four new external content sources—Front, KnowledgeOwl, Kustomer, and Stoplight—now integrate as knowledge sources, enabling AI agents and Copilot to surface existing organisational content without forcing teams to migrate or duplicate information. This addresses a persistent CX challenge: knowledge fragmentation across legacy systems. Concurrently, the new "Manage end user configuration" permission allows admins to delegate security-sensitive settings without granting full administrative access, whilst suggested assignees in Copilot uses historical ticket data to route escalations to appropriate experts. For teams already running Agentforce or comparable agentic systems, these updates raise a critical question: does Zendesk's incremental approach to AI-assisted routing and knowledge access keep pace with competitors offering more autonomous decision-making, or does the emphasis on admin control and explainability represent a deliberate differentiation strategy?

The announcement of SDK deprecations—Support SDK Classic, Talk SDK, Smooch SDK, and Unity SDK Classic retiring by October 2027—signals Zendesk's decisive shift toward its Messaging SDK as the unified mobile and web surface. This is not a minor technical refresh; it requires code-level changes, app store resubmission, and loss of conversation history migration. Teams must begin planning immediately to avoid service disruption. The removal of embedded Talk calling functionality forces a choice between Zendesk Voice as a separate channel or retaining legacy SIP-IN integrations—neither offering feature parity. For support teams reliant on in-app voice or legacy ticket workflows, this represents genuine operational friction that will demand resource allocation and customer communication planning over the next twelve months.