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

Zendesk announces Real-Time Voice Translation capability

Zendesk

Zendesk's native Real-Time Voice Translation capability represents a meaningful shift in how translation integrates into contact center workflows, moving from overlay solutions to embedded platform functionality. Unlike point providers Krisp and Sanas, which typically require separate desktop applications, vendor agreements, or custom SDK implementations, Zendesk has productized translation directly into its agent interface without additional configuration overhead. The feature enables bidirectional translation across 13 languages during the October early access programme, with general availability planned for Q1 2027, allowing agents and customers to speak and hear in their preferred languages without channel switching or human interpreters. Critically, translation context flows through the entire interaction—routing decisions, call summaries, and recording preferences—meaning administrators gain governance at the queue level rather than managing separate third-party integrations.

The operational implications are substantial for teams already managing multilingual operations. Real-time translation eliminates the staffing economics that have historically justified dedicated language queues, allowing organisations to route by expertise and issue type instead. This fundamentally changes how you staff for language diversity, particularly for low-volume languages where dedicated agents become economically inefficient. However, the EAP version carries notable constraints: no support for transferred calls, multiparty conversations, supervisor monitoring, or video interactions. For teams relying on these workflows—particularly those using barge-in for quality assurance or handling complex escalations—the current roadmap leaves gaps that may necessitate hybrid approaches through 2027.

The pricing model remains undefined, with Zendesk committing only to usage-based billing after the EAP concludes. This creates a strategic question for administrators: should you pilot aggressively during the free early access period to establish baseline usage patterns and build internal business cases, or wait for pricing transparency before committing resources? The absence of viewable usage reporting in the EAP version compounds this uncertainty, making it difficult to forecast costs at scale. For organisations already invested in Zendesk's voice platform, native integration removes friction; for those evaluating alternatives or running hybrid CCaaS environments, the decision hinges on whether Zendesk's embedded approach justifies platform consolidation against the flexibility of point solutions.