Troubleshooting guide

Zendesk AI not working? Start with the setup underneath it.

Intelligent Triage, AI Agents, and agent copilot can be switched on quickly. Getting useful ROI from them is slower, because the AI reflects the quality of your Help Centre, ticket data, macros, SLAs, forms, and routing.

Want the quick diagnosis?

Run a read-only Zendesk audit and get a scored breakdown across the seven AI readiness foundations.

Run free audit

1. Help Centre content is thin, stale, or not available

AI Agents and agent-facing suggestions need useful Help Centre articles to draw from. If Guide is not enabled, articles are hidden, or the content does not match your top contact reasons, Zendesk AI has very little to work with.

Symptoms

  • AI Agents fail to answer common questions
  • Suggested articles are irrelevant
  • Users still create tickets for repeat issues

Fix

Publish clear articles for your top request types, remove duplicates, and put stale articles into a review queue before expanding AI usage.

2. Ticket data is too vague for Intelligent Triage

Intelligent Triage depends on patterns in ticket subjects, descriptions, forms, and historical outcomes. Generic email tickets, empty descriptions, and inconsistent requester detail all reduce the signal available to the model.

Symptoms

  • Intent predictions are low-confidence
  • Similar tickets are triaged differently
  • Agents still rewrite or reassign many tickets manually

Fix

Tighten high-volume forms, add required fields where needed, and coach agents to clean up vague subjects during triage.

3. Tags, fields, and forms are messy

Zendesk AI performs better when ticket fields and tags describe the request cleanly. Duplicate tags, unused fields, and forms with too many overlapping options create weak categorisation signals.

Symptoms

  • Many tags mean the same thing
  • Forms do not map cleanly to teams or request types
  • Reporting looks noisy or contradictory

Fix

Retire unused tags, standardise form options, and keep a small controlled set of fields that actually drive routing and reporting.

4. Macros are duplicated, personal, or stale

Agent copilot and productivity workflows rely on response patterns. If useful macros live as personal macros, if global macros are outdated, or if duplicates compete with each other, agents stop trusting suggestions.

Symptoms

  • Agents ignore suggested responses
  • Multiple macros say almost the same thing
  • Macros reference old teams, tools, or processes

Fix

Create shared macros for the top recurring tickets, archive stale ones, and move useful personal macros into a governed shared library.

5. SLA policies do not create useful urgency signals

A single catch-all SLA, missing priority coverage, or no access to SLA policy data leaves Zendesk AI with poor urgency context. That makes prioritisation and escalation feel inconsistent.

Symptoms

  • Urgent tickets are not surfaced quickly
  • Escalations rely on manual chasing
  • Priority does not map to customer impact

Fix

Use service- or segment-specific SLA policies, cover all priorities that matter, and make escalation rules explicit.

6. Self-service paths are bypassed

If users mostly email support directly, never see Help Centre suggestions, or cannot find the right request form, AI deflection stays low even when the underlying AI feature is active.

Symptoms

  • Email remains the dominant contact channel
  • Help Centre search volume is low
  • Users submit free-text tickets instead of structured requests

Fix

Put Help Centre and request forms in the natural request path, promote the right forms, and use forms to capture the fields AI needs.

7. Triggers, automations, and groups conflict

Zendesk AI can suggest or classify, but the workflow still depends on triggers, automations, groups, and assignment rules. Overlapping rules and manual routing make AI outcomes hard to trust.

Symptoms

  • Tickets bounce between groups
  • Triggers overwrite each other
  • Manual assignment remains the default operating model

Fix

Document routing ownership, simplify overlapping triggers, and align automations with the AI triage categories you want to rely on.

What to read next

Zendesk is a trademark of Zendesk, Inc. Service Desk Builder is not affiliated with or endorsed by Zendesk.