Blueprint
Action Flows: what replaces the ZIS detour today
Loops, conditions, Custom Code, and connectors with a UI: Action Flows turn data processing in the bot context into a product, with clear limits and a migration question.
Knowledge
Organised by topic, to read and to rebuild. The widget you can click through lives under Demos, numbers and lessons from production under From the engine room. Use the sidebar to jump straight into a topic.
Blueprint
Loops, conditions, Custom Code, and connectors with a UI: Action Flows turn data processing in the bot context into a product, with clear limits and a migration question.
Blueprint
Zendesk now gives you four ways to automate with AI Agents, but the docs won't tell you which one holds up when. A decision guide from production, with a rule of thumb that covers almost everything.
Blueprint
Flow Builder can fetch API responses but can't reshape them. How an inbound webhook into Zendesk Integration Services got past that limit, and what the detour cost in production.
Blueprint
Bubble or building block: when the Zendesk widget should stay floating, when Embedded Mode wins, and the three rules that go wrong when you mix and render.
Blueprint
Logged-in customers don't have to introduce themselves again in the chat: loginUser with signed JWTs. The architecture, the flow, token renewal, and the security rules behind it. And how the same identity also logs you into the Help Center.
Blueprint
Where does the request come from, what is it about, what belongs in routing? With conversationTags and conversationFields, the widget hands the context over up front: one line per thing worth knowing.
Blueprint
Embed the Zendesk snippet cleanly: control auto-render, catch load failures and adblockers, show a designed fallback — and understand the zE queue.
Basics
Zendesk's Admin Copilot looks at your instance and puts recommendations on the table: from dead triggers to routing. What it can do, what it can't, and who decides.
Basics
Agent Copilot is not a bot that talks to customers, but the AI layer beside the human agent in the Agent Workspace. Every reply needs his approval.
Basics
One workspace instead of one tool per channel. What the Agent Workspace pulls together: the conversation view, context panel, apps and side conversations, explained for beginners.
Basics
How Zendesk distributes tickets from email, messaging and calls by availability and capacity, and why that's a different thing from trigger-based assignment.
Blueprint
You can only recolor the widget from the outside. With the Help Center you get the code itself: templates, CSS, JavaScript. What a Guide theme is, how you build one, and why it's the canvas for everything else.
Blueprint
The default «My requests» page is a dead list. The Requests API turns it into a status tracker: secure replies and attachment uploads over TLS instead of email.
Basics
An AI answer is never better than the knowledge behind it. How a Help Center has to be built so AI Agents can answer from it reliably. The fundamentals.
Basics
Explore delivers hundreds of metrics. The skill is knowing the few that say something, and ignoring the many that only look good.
Basics
Triggers, automations, webhooks, custom fields and custom objects: five building blocks, one per job. What each one does and when to reach for which.
Basics
Roles, 2FA, SSO, audit log, deletion plans, hosting location: the basics laid out cleanly, with an eye on revDSG and GDPR. Orientation, not legal advice.
Basics
The same Zendesk engine, turned inward: what the Employee Service Suite brings to HR and IT teams, and where it differs from customer service.