Zendesk What's New, Followed Properly
This page deliberately lists no features. Zendesk's what's new moves too fast for that, so here's where the news lives and how to follow it without drowning.
Where Zendesk publishes what's new
They are scattered across four places, and most admins only know about one.
Plus the status page, which is incidents rather than releases, though a badly received change occasionally shows up there first.
Three kinds of change, and only one is urgent
Sort every announcement into one of these before you spend any attention on it.
Opt-in features. New capability you switch on. Interesting, never urgent. Read, note, move on, revisit when you have a reason.
Default-on changes. Arriving whether you asked or not, usually with a date. These change what your agents see and occasionally what your rules do. Worth ten minutes each.
Deprecations and removals. Something you rely on is going away, on a specific date. These are the ones that break you, they are almost always announced months ahead, and they are almost always ignored until the week they land.
If you only read one category, read the third. An API version being retired with six months of notice is a calm afternoon of work, or a weekend, depending entirely on whether anyone was following along.
Set up the subscriptions once
Ten minutes of setup replaces the habit you were never going to keep.
The fifteen-minute monthly pass
Put it in the calendar on the same day each month. Fifteen minutes, and treat it as maintenance rather than reading.
Skim the month's notes and triage each item into ignore, plan or act. For anything in plan or act, ask four questions: does it touch our triggers or automations, does it touch a marketplace app or integration we depend on, does it change what agents see, and does it change a number in a report leadership looks at.
Write the outcome in a shared log with the date. That log is worth more than it sounds, because in eight months when a report shifts inexplicably, the answer is usually a change that landed and got noticed by nobody.
Before a default-on change arrives
Test in a sandbox if your plan includes one. That's what it is for, and change control is one of the better arguments for a higher tier.
If you do not have a sandbox, do the next best thing: list the macros, triggers, apps and views that touch the affected area, check them the day the change lands, and tell your agents in advance. Support teams under pressure do not enjoy surprise interface changes, and a two-line heads-up costs you nothing.
Never let a significant change land on a Monday morning if you have any say in the timing.
One last piece of advice about early access programmes. They're genuinely useful if you have a specific problem the new thing solves, and a distraction otherwise. Joining an early access programme because it sounds interesting means you're now running a beta in production on behalf of a team that didn't ask for one. Pick the ones that answer a question you already have.
Why we are not listing features here
Deliberate omission, and worth explaining. Any list of recent Zendesk releases written today is misleading within a quarter and actively wrong within a year, and there's a whole genre of blog post that exists purely to rank for this search while describing a product that has moved on.
The durable thing isn't the feature list, it's the habit: know the four places changes get published, know which category of change can hurt you, subscribe once, and spend a quarter of an hour a month. Do that and you'll never be surprised by a deprecation. Skip it and you'll find out about the change from an agent, on the day, in the middle of a busy shift.
Frequently asked questions
Where do Zendesk product updates get announced?
In the release notes on the support site and in the community announcements. Zendesk product updates that change defaults are also emailed to admins, which is the mail worth not filtering.
Where is the Zendesk what's new page?
In Zendesk's own help centre, published on a regular cadence and split by product area, with bigger items also posted to the announcements section of the community.
Can I get Zendesk updates by email?
Yes. Follow the release notes and announcements sections in their help centre and new posts arrive by email. Route them to a shared address rather than one person.
How do I find out about API changes?
The developer changelog, which is separate from the general release notes. Anyone maintaining an integration, webhook or private app should be subscribed to it.
Do I have to accept new Zendesk features?
Some are opt-in and some arrive by default on a published date. The announcement says which, and the default-on ones are why the monthly skim is worth doing.
How much notice does Zendesk give before removing something?
Deprecations are typically announced well ahead with a dated end of life. The problem is rarely the notice period, it's that nobody was reading.
One thing that never changes in a release note
Whatever ships next quarter, 8% to 20% of your queue will still be duplicates. Ticket Merger handles that part.
Start free trial14-day free trial. No credit card required.