Sunshine Conversations, now rebranded as Messaging, operates as the foundational infrastructure layer powering Zendesk's Resolution Platform—a role so embedded that most administrators never consciously interact with it. Acquired from Smooch in 2018, this abstraction layer handles the technical complexity of multi-channel routing, conversation state management, and identity resolution across disparate platforms like WhatsApp, Instagram, web widgets, and AI Agents. Rather than forcing teams to maintain separate integrations for each channel, Messaging translates channel-specific quirks into a unified API, allowing admins to configure routing rules once and deploy them across new channels without rework. The switchboard—Messaging's routing engine—determines which responder (AI Agent, human agent, or third-party bot) handles each conversation, then orchestrates handovers whilst maintaining full conversation context and metadata. This architectural choice has profound implications: teams already running multi-channel operations gain significant operational leverage, but those still managing channels through legacy point-to-point integrations face technical debt that becomes increasingly costly as channel portfolios expand.
The introduction of AI Agent tickets represents a critical shift in how Zendesk unifies AI and human workflows. Previously, conversations handled entirely by AI Agents existed outside Agent Workspace, creating blind spots for analytics, quality assurance, and Admin Copilot recommendations. Now every interaction—whether resolved by an AI Agent or escalated to a human—generates a single ticket tracked from initiation through resolution. This eliminates the fragmented visibility that plagued earlier implementations and forces a fundamental question for CX leaders: how should capacity planning, SLA management, and performance metrics evolve when AI-handled conversations are no longer invisible to your reporting infrastructure? The platform's trajectory suggests Zendesk is systematically collapsing the technical seams between Messaging and core Zendesk—moving switchboard configuration from API calls to UI-driven channel management, syncing conversation metadata bidirectionally with ticket fields, and authenticating users across both systems. For administrators, this means the barrier to sophisticated multi-channel orchestration continues lowering, but it also signals that teams investing heavily in custom Messaging API integrations may find their work superseded by native UI features within quarters.
The metadata and context layer deserves particular attention for support teams managing complex resolution workflows. Conversation Extensions—custom web views embedded within conversations—enable rich interactions like flight rebookings or refund processing without bouncing customers to external systems, whilst maintaining access to conversation metadata and SunCo context. However, the guidance to treat Extensions as exceptions rather than defaults reflects a broader principle: the platform's strength lies in its ability to resolve most cases through knowledge articles and agentic procedures, reserving richer interfaces for genuinely high-value interactions. For teams evaluating their current tooling against Zendesk's capabilities, the question becomes whether your existing CX stack can match this level of seamless context propagation across channels, or whether fragmented customer profiles and siloed conversation histories remain a persistent operational drag.
Most admins and agents using Zendesk never think about Sunshine Conversations. And that is rather the point.It sits underneath the entire conversational experience in Zendesk. It does not show up as a tab in Agent Workspace. It is not a single feature you'll find in Admin Center.