Blog
Notes on support, switching and saving.
Practical guides for teams running customer support, and the thinking behind ChaosDesk.
-
Triggers, automations and SLAs that behave the same after the move
How ChaosDesk keeps imported business rules behaving the way they did, and how we measure it instead of hoping.
-
Replacing the Zendesk Web Widget without touching your zE() calls
How to swap the Zendesk messaging widget for the ChaosDesk messenger by changing one script tag, and what to check before you do.
-
Zendesk pricing in 2026, explained
The Zendesk list prices as of November 2026, the add-ons that change the total, and a worked example for a team of 20 agents.
-
Keep your Zendesk API scripts: changing one base URL
How the Zendesk-compatible API lets internal services, SDK clients and help-centre widgets keep working after a move to ChaosDesk.
-
What comes over when you import a Zendesk account
A walk through everything the ChaosDesk importer copies from Zendesk, in what order, and how it handles the things that do not map one to one.
-
Why the AI copilot is in the plan, not an add-on
How ChaosDesk can include reply drafts, summaries, translation and triage in every paid plan, and what fair use means in practice.
-
Parallel run and cutover, one group at a time
Why moving one group at a time beats a big-bang switch, and the exact steps of a cutover with a fallback window.
-
Customer support data in the EU: what to ask your helpdesk vendor
Eight questions that tell you where your support data really lives, who can read it, and what happens when you leave.
-
Zendesk alternatives in 2026: a factual comparison
Freshdesk, Zoho Desk, Help Scout, Intercom, Gorgias and ChaosDesk compared on pricing model, AI pricing, data hosting and migration effort.
Bring your whole Zendesk history. Keep your way of working.
Import tickets, users, rules and the help centre, run both side by side, and switch when your team is ready.
Send us a line from your work address and we will add you to the early access list.