Zendesk Chat Is Retiring in 2028. Your Live Chat Doesn't Have To.

On 4 August 2026, Zendesk announced that Zendesk Chat is being removed. It retires on 31 January 2028, and full access to the Chat dashboard ends on 28 July 2028. Customers move to Zendesk messaging, with an 18-month window and self-serve migration tooling.

That is a reasonable amount of notice, and the migration tooling is real. This post is not about the timeline being unfair. It is about one sentence in the announcement that every helpdesk buyer should read carefully — because it describes a risk that has nothing to do with Zendesk specifically.

The sentence

"Chat is a legacy product that hasn't received feature enhancements since 2020 and does not support modern AI features."

That is Zendesk's own description, in their own announcement. We are quoting it verbatim rather than paraphrasing, because a paraphrase would sound like a competitor's attack and the original is simply a statement of fact from the vendor.

Sit with the arithmetic for a moment. If you have been paying for Zendesk Chat since 2021, you have been paying for software that received no feature work for the entire period you were a customer — and the first formal notice of that fact arrived in the same document that gave you a date to leave by.

Why this happens, and why it will happen again

Zendesk Chat came from the acquisition of Zopim in 2014. Zendesk messaging was built later, in-house. For years both shipped in the same product line, and from the buyer's side they looked like two features of one platform. They were never that. They were two codebases with different ages, different architectures, and — as it turns out — very different amounts of engineering attention.

This is the normal outcome of growth by acquisition, not a scandal. A large platform buys a product, runs it alongside the native equivalent, and eventually has to choose which one gets the AI work. The acquired product becomes "legacy" long before it is announced as legacy. The announcement is not when maintenance stopped; it is when the vendor got around to telling you it stopped in 2020.

Which means the useful question when you evaluate any helpdesk is not "does it have live chat." Nearly all of them do. The question is: is the live chat the same product as the ticketing system, or is it a company they bought? The answer predicts which half gets the next five years of investment.

What to do if you are on Zendesk Chat

You have until January 2028, and that is genuinely a long runway. Our practical advice, in order:

• Do not start here. Zendesk's API token deprecation has a hard cutoff of 30 April 2027 and involves far more engineering — every custom integration you own has to move to OAuth. If you only have capacity for one migration this year, it is that one, not this. We laid out all of it in the full calendar of Zendesk's six migrations through 2028.
• Inventory your Chat logic now, migrate later. Triggers, shortcuts, departments, routing rules — this is the material that has to be rebuilt in messaging, and it is much easier to write down while the system is still running normally than during a cutover.
• Find the owner of your widget embed. If the chat widget is installed through custom code on a marketing site, the person who can change it is usually not on the support team. Discovering that in month 17 is a bad time to discover it.
• Use the window to re-evaluate, not just to comply. A forced migration is the one moment when the switching cost of staying and the switching cost of leaving are closest together. If you were ever going to look at alternatives, this is the cheapest time to do it.

Where DeskLeap fits

We build a helpdesk, so read this section knowing we have a stake in your answer.

Our live chat is not an acquired product running beside the ticketing system. It is part of the same platform, built by the same team, sharing the same visitor records, the same knowledge base and the same agent inbox as tickets. That is the structural reason it does not have a retirement date to plan around — not because we are more virtuous, but because there is no second chat product for it to lose an internal argument to.

Some specifics, so this is checkable rather than atmospheric:

• Live chat, ticketing and the knowledge base are one product. A chat that cannot be resolved becomes a ticket with the transcript attached, and the visitor gets an email reply on the same thread.
• When nobody on your team is available, the widget offers the visitor a message form instead of leaving them watching a spinner — and you can set business hours per site so it does that immediately outside your opening times rather than after a wait.
• The platform is free, and human agents are included at no cost. The only paid component is the AI Agent add-on at $29 per month per agent, which you can add or remove whenever you like.

What we will not claim is that switching is effortless. Moving a helpdesk means moving history, retraining a team and re-embedding a widget, and any vendor who tells you otherwise is selling. If Zendesk messaging fits your team, migrating within Zendesk is the shorter path and you should take it.

The narrower case for looking elsewhere is this: if you are already going to spend engineering time on the API migration, and you are already going to rebuild your chat logic somewhere, it is worth spending an afternoon asking whether you want to do the next round of this on the same platform.

Sources

• Announcing the removal of Zendesk Chat for messaging-eligible customers
• About the removal of Zendesk Chat and migration to messaging
• Announcing the removal of API tokens as an authentication method for API requests

Verified against Zendesk's documentation on 12 August 2026. Dates change — check the sources before planning a quarter around them.