Start with the last question your team answered five times. Was the answer missing, hard to find, or different for every customer? That distinction tells you whether to write a better article, add a ticket rule, or leave the decision with a person.
You do not need to replace Zendesk or Intercom to run this experiment. Keep your inbox and pick one repetitive workflow. Use the helpdesk to handle tickets and the help center to answer questions that do not need a ticket in the first place.
1. Find one question worth removing from the queue
Sample a week or two of closed conversations. Group them by the customer's goal, such as inviting a teammate, exporting an invoice, or reconnecting an integration. Merge overlapping tags and read enough examples to tell a common question from several issues that happen to share a tag.
For each group, note how often it appears, how long it takes to resolve, and whether the answer depends on account data. Start with a frequent question that has a stable, public answer. Do not copy ticket transcripts or personal information into the help center.
2. Decide what to automate
| If the work is... | Start with... | Example |
|---|---|---|
| A predictable action on an existing ticket | A helpdesk rule | Send an unanswered ticket back to the right queue after a defined interval. |
| A common question with one public answer | A task-specific help article | Show where workspace owners can download a receipt. |
| A question that can be answered from approved articles | A source-backed AI answer with a human fallback | Explain supported export formats and link to the export guide. |
| A sensitive or account-specific decision | A human handoff | Investigate a disputed charge or review an account recovery request. |
In Zendesk, automations are time-based. Use a trigger when the action should happen on a ticket event instead, such as routing a newly created ticket. Neither is a substitute for fixing an article that keeps sending customers to the wrong menu.
3. Turn a recurring ticket into an answer customers can use
Suppose customers keep asking why they cannot download a receipt. Read a few tickets and check the real product. If only workspace owners can download receipts, say that before the steps. Include the exact menu labels, where the download appears, and what someone should do if they are not an owner. Link the article from the billing page and from the agent reply your team already uses.
If you add an AI answer, test the question as an owner, a non-owner, and someone asking about a missing charge. It should explain the permission requirement, cite the article, and hand off the missing-charge case instead of guessing. Use the AI knowledge base guide to turn these checks into a repeatable test set.
4. Measure whether the issue actually gets resolved
Compare the number of tagged contacts per 1,000 active accounts before and after the change, using comparable periods and the same tagging rules. Track repeat contacts for that issue and audit a sample of AI answers or escalations. A conversation that went quiet is not proof the customer got what they needed.
Give the article an owner. When the billing screen or permissions change, update the source and rerun the three test questions. Expand to another ticket category only once the first workflow is dependable.
Use the help center release checklist to keep the source current, and the ticket deflection scorecard to separate verified outcomes from silence.
Keep your helpdesk. Move the help center only if it helps.
If the inbox works but the public site is hard to use or maintain, you can evaluate the two separately. Start with the Zendesk help center migration guide or the Intercom help center migration guide. The Zendesk comparison shows where DocsAlot fits if you want to preview a different home for your articles.