Zendesk AI setup
Configure Zendesk for AI before you ask AI to fix Zendesk.
Intelligent Triage, AI Agents, and agent copilot depend on the same operational foundations your support team already uses: content, forms, fields, tags, macros, SLAs, and routing. This is the setup checklist to review before rollout.
The goal is not more configuration. It is cleaner signal.
Zendesk AI performs best when your setup gives it clean patterns: articles that answer real questions, forms that capture intent, macros that represent approved replies, SLAs that describe urgency, and routing rules that tell Zendesk where work should go. The audit checks whether those signals are ready.
Help Centre and knowledge base
AI Agents and article suggestions need trusted, public, current content.
- Publish articles for the top recurring request types
- Archive duplicate or obsolete articles
- Keep article titles close to the language requesters use
- Review stale articles at least every six months
Ticket data quality
Intelligent Triage needs clean historical tickets and useful requester detail.
- Reduce vague ticket subjects from email intake
- Use forms for high-volume requests instead of open text
- Capture priority, product, service, location, or department where relevant
- Coach agents to tidy subjects and request context during triage
Forms, fields, and tags
Categorisation should be controlled, consistent, and useful for routing.
- Remove duplicate tags that mean the same thing
- Retire fields that are no longer used in reporting or routing
- Keep dropdown options short enough for agents to use consistently
- Map forms to real support journeys rather than internal team structure only
Macros
Agent copilot and productivity flows work better with governed response patterns.
- Create shared macros for the top recurring requests
- Move useful personal macros into the shared library
- Archive macros that reference retired tools, teams, or processes
- Use a consistent tone, escalation path, and close-out format
SLA policies
Zendesk AI needs clear urgency and priority context.
- Avoid relying on one catch-all SLA policy
- Cover the priority levels your team actually uses
- Add escalation rules for critical breach risk
- Align SLA targets to customer or employee impact
Self-service setup
Users must be routed through the Help Centre and the right request path.
- Make forms visible and easy to find from the Help Centre
- Guide email-heavy teams toward structured request channels
- Use request forms to capture the fields AI needs
- Test common user searches against your article library
Routing and automation
AI outputs need clean triggers, automations, groups, and assignment ownership.
- Document which triggers own routing, assignment, and escalation
- Remove overlapping trigger logic
- Map AI triage categories to groups or escalation paths
- Review routing changes whenever teams or services change
Turn the checklist into a score
The free Zendesk audit checks these seven areas automatically and shows which setup issue is most likely to block AI ROI.
Related Zendesk guides
Related Zendesk AI guides
More on getting Zendesk AI to actually deliver.
Zendesk AI Readiness Audit
Score your Zendesk instance across 7 AI-readiness dimensions in 2 minutes.
Zendesk AI Not Working? Fixes
Why Zendesk AI and Intelligent Triage underperform — and how to fix each.
Zendesk Answer Bot Deflection
Get the bot deflecting real tickets instead of giving generic non-answers.
Freshservice vs Zendesk AI
How the two platforms compare on AI readiness.
AI Readiness Checklist
Every check the audit runs, as a manual list you can self-assess.
Run your free AI readiness audit
Works with Zendesk and Freshservice — get your score in under 2 minutes.