Zendesk Is Removing Five SDKs by October 2027 — and Your Customers' History Doesn't Move With Them

On 15 October 2026 Zendesk announced that it will remove five SDKs: the Support SDK (Classic), the Talk SDK, the Smooch (Sunshine Conversations) Mobile SDK, Smooch Web Messenger and the Unity SDK (Classic). Standard support ends on 19 October 2027, and the products are removed the same day.

Zendesk's stated successor is its Messaging SDK for mobile and the messaging Web Widget for the web, which it describes as the platform on which it "will continue to invest in new capabilities". So this is not Zendesk leaving mobile support. It is a migration, with a year's notice. But it is a different kind of migration from a settings change, and one sentence in the announcement deserves more attention than the date.

What is being removed, and what replaces it

• Support SDK (Classic), Smooch (Sunshine Conversations) Mobile SDK, Unity SDK (Classic) — replace with the Zendesk Messaging SDK in your mobile app.
• Smooch Web Messenger — migrate to the messaging Web Widget.
• Talk SDK — remove it and choose a supported voice path if you still need voice.

One clarification, because the names are easy to blur: Smooch Web Messenger is not Zendesk Chat. Zendesk Chat has its own, separate retirement schedule. This announcement is about the five products above.

For mobile apps, this one ends with an app-store release

Most vendor migrations end with someone in support ops changing a setting. For the mobile SDKs, this one does not; for Smooch Web Messenger it is an embed change on your website. In Zendesk's own words, moving off the Support SDK "requires code changes, testing, a new app build, and release through the relevant app store."

That puts it on a different calendar. The work belongs to whoever builds your app, it has to fit into their release cycle, and it has to pass app-store review before customers get it. Zendesk itself advises planning for app-store review and a phased release. Nineteen October 2027 sounds far away; for a team that ships its app a few times a year, it is a handful of release windows.

The line that matters more than the date

Here is the sentence from the announcement that support leads should read twice:

"Support SDK conversations and ticket history do not transfer into the new Messaging experience. End users will not see previous interactions in Messaging; agents may still be able to view old tickets in Agent Workspace where applicable."

Your team may keep the history. Your customers lose sight of theirs. A customer who has been talking to you inside your app for years opens the new version and finds an empty conversation. If they come back to follow up on an open issue, they cannot scroll up to show you what was said.

Two more gaps are spelled out:

• Ticket lists and status. "Conversation extensions do not provide equivalent Support SDK ticket lists or ticket-status views, so arrange another approved solution for those workflows." If your app lets customers check the status of their requests, that screen needs a new home.
• Voice inside the app. For the Talk SDK, Zendesk points to Zendesk Voice as a separate phone channel or an existing SIP integration, and says plainly: "Neither option is a like-for-like replacement for embedded Talk calling."

What to do this quarter

1. Find out which of the five you actually use. Check every app and every website, including older app versions still in customers' hands.
2. Book the work with your app team now. It is a build-and-release job, not a support-ops change. Get it into a release plan with room for app-store review.
3. Decide what customers will see on day one. If history will not carry over, tell them before it disappears, and make sure open issues have somewhere to continue.
4. Replace the ticket-status workflow. If customers check request status in your app, decide where that lives afterwards.
5. Decide on voice separately. If in-app calling matters to you, that decision is not covered by the messaging migration.

A wider lesson: where does your customers' history live?

The useful question this raises is not about Zendesk in particular. It is: when the piece of software in front of your customers changes, does their history go with it?

For what it is worth, here is how DeskLeap answers that today. DeskLeap does not offer a native mobile SDK; customers reach you through a web chat widget and a hosted customer portal, and your team's replies also go to them by email. The widget is loaded from our servers, so an update reaches your website without you shipping a new app build. And the customer portal is where customers sign in with a code sent to their email and see their own ticket history, kept on the DeskLeap side rather than inside a particular client. The platform is 100% free with unlimited human agents; an optional AI Agent add-on is $29/mo each.

Whatever you use, ask the same question of every vendor: if this client goes away, what do my customers still see?

Source

Zendesk, Announcing the removal of Support SDK Classic, Talk SDK, Smooch SDK, Smooch Web Messenger, and Unity SDK Classic (announced 15 October 2026; read 16 October 2026). Quotations are verbatim from that page.