The most significant operational pattern that Zendesk administrators need to understand is the increasing frequency and severity of service incidents, particularly those related to AI-powered features and infrastructure issues.
These incidents, which include problems with AI agent tickets, messaging delays, and knowledge ticket submission issues, suggest that Zendesk's rapid expansion into AI-driven customer service is outpacing the stability of its underlying systems, requiring administrators to closely monitor performance, test new features thoroughly, and be prepared to respond quickly to mitigate the impact of service disruptions.
Nico's Commentary
The general availability of the action builder means this will be a fun week for Zendesk admins who haven't yet had a play with the latest toy. I'm not generally a fan of no-code solutions because they often come with frustrating limitations baked in, but on the other hand this could well be a gateway drug for teams who haven't yet gone beyond standard Zendesk objects in their workflows.
Like we demonstrate with our Zendesk theme engine we believe in engineering processes, testing and measuring and iterating. It's something we have been discussing a lot lately, particularly around understanding the data we can explore in Zendesk instances.
Recently we had a great morning with our friends at Geckoboard and went into detail about this and other elements of our work, which resulted in this edit: