Zendesk Chat
Zendesk Chat is live chat software scheduled for removal on 31 January 2028, with Chat dashboard access ending 28 July 2028. It is sold only inside Zendesk Suite, and Zendesk's own migration path to messaging does not carry the chat archive across.
Zendesk Chat is a customer support platform known for deep integration with zendesk support platform. Live chat software Zendesk is removing on 31 January 2028. It's best suited for existing zendesk suite teams migrating to zendesk messaging.
Below you'll find a detailed breakdown of Zendesk Chat's features, pricing, strengths, and weaknesses to help you make an informed comparison with alternative platforms.
Zendesk Chat Key Features
Zendesk Chat Strengths & Limitations
Strengths
- Strong brand recognition
- Comprehensive support suite
- Real-time visitor monitoring for proactive chat
- Deep ticketing integration
Limitations
- Zendesk removes Chat on 31 January 2028
- Chat history cannot be transferred into Zendesk messaging
- Triggers, routing and widget settings have no export at all
- Per-agent pricing on an annual-only rate card
Zendesk Chat Pricing
At $115/agent/month, a 5-agent team pays $575/month. Converge offers flat $49/month for up to 15 team members.
Converge Platform Data
How Converge compares to Zendesk Chat — first-party numbers, not vendor benchmarks
| Team Size | Zendesk Chat | Converge | Annual Savings |
|---|---|---|---|
| 5 agents | $575/mo | $49/mo | $6312/yr |
| 10 agents | $1150/mo | $49/mo | $13212/yr |
| 15 agents | $1725/mo | $49/mo | $20112/yr |
Ready to try Converge?
$49/month flat. Up to 15 agents. 7-day free trial, no credit card required.
Start Free TrialZendesk Chat vs Other Platforms
Frequently Asked Questions
Zendesk Chat's Suite Professional plan costs $115/agent/month. That is the annual rate, and Zendesk publishes no monthly figure anywhere on its pricing page. Zendesk Chat itself is removed on 31 January 2028, so a new subscription buys Zendesk messaging rather than Chat. For comparison, Converge costs $49/month flat for up to 15 team members.
Zendesk Chat is best suited for existing zendesk suite teams migrating to zendesk messaging. Its standout feature is deep integration with zendesk support platform.
There are 49+ platforms you can compare with Zendesk Chat in the customer support platform category. Each comparison above shows detailed feature and pricing differences to help you choose.
Zendesk announced the end of life of Zendesk Chat on 4 August 2026. The product is removed on 31 January 2028 and access to the Chat dashboard ends on 28 July 2028, giving an 18-month transition window. That announcement covers messaging-eligible accounts, meaning Chat + Support and Zendesk Suite. Customers on the legacy Chat-only plan are told a separate removal will be announced, so they have no published date to plan an export against — a worse position than the accounts with a deadline, not a better one. Zendesk's stated reason is that Chat is “a legacy product that hasn’t received feature enhancements since 2020 and does not support modern AI features” (Zendesk removal announcement, edited 5 August 2026).
No, and it does not transfer if you stay inside Zendesk either. Zendesk's documentation team has confirmed there is no option to move live chat history into Zendesk messaging: chat history already attached to a ticket stays readable on that ticket, but the Chat History archive does not travel (Zendesk migration documentation, edited 29 April 2026). The practical consequence is that the export job is identical whether your destination is Zendesk messaging or a different vendor, and it has to be finished while the Chat dashboard is still live. Transcripts come out of the History page as .TXT files, chat metadata comes out separately as CSV, and anything older than 90 days has to come out of the Chat API.
Everything that encodes behaviour rather than content. Chat triggers and their visitor-behaviour conditions, routing logic, banned visitor lists, widget customisation (brand colours, pre-chat form fields, operating-hours display, custom CSS) and the Chat dashboard's historical analytics have no export route of any kind — screenshot each trigger's conditions and copy the CSS before you cancel. Four things people assume are stuck do come out through the API: shortcuts, visitor profiles, agent profiles and your department structure. Budget the rebuild, not the export: pulling transcripts is an afternoon, and retyping a dozen triggers and a pre-chat form into a new widget is the part that actually holds up a cutover.