How to Set Up AI Agents That Respond Automatically to Zendesk Tickets
Autonomous AI agents run without a human in the loop. A Zendesk trigger fires — new ticket created, customer replied, status changed — and your AI agent reads the ticket, decides what to do, and acts. No queue, no waiting, no copy-paste. Here's how to set it up.
What is an autonomous agent?
An autonomous agent is an AI agent that runs without a human in the loop. It's triggered by an external event — a new Zendesk ticket, a customer reply, a status change — and executes a full workflow: read the data, make decisions, call tools, and post a response. The customer gets a reply in under 60 seconds, 24/7.
Compare this to a copilot agent (which drafts suggestions for a human to review) or a chatbot (which interacts with the customer directly in a widget). Autonomous agents work behind the scenes on your Zendesk tickets.
The three components
Every autonomous agent needs three things configured:
1. Tools — what the agent can do
Tools are the actions your agent can perform. For a Zendesk ticket agent, you'll typically enable:
- Get Ticket — read the ticket's subject, description, status, tags, and conversation history
- Get Custom Fields — read custom field values with labels (order numbers, brands, etc.)
- Add Internal Note — post a draft response that a human can review before sending
- Add Public Reply — respond directly to the customer (for fully autonomous flows)
- Search Articles — search your Help Center knowledge base for relevant answers
You can also add custom API tools (for order lookup, CRM queries, etc.) and knowledge-base sources (uploaded docs, website content).
2. Instructions — how the agent thinks
Instructions are plain-text (or rich HTML) rules that define the agent's behaviour. They tell the agent what to look for, how to classify tickets, what business rules to apply, and how to format responses. Think of them as the agent's training manual.
3. Triggers — when the agent runs
Triggers connect external events to your agent. Macha supports eight Zendesk trigger types:
- New Ticket — fires on the first customer message
- Customer Reply — fires on every customer comment
- Status Changed — fires when status changes (open → pending, etc.)
- Priority Changed, Assigned, Closed — fires on the respective event
- Messaging — fires on WhatsApp, Messenger, Instagram, LINE, Telegram messages
- Custom Webhook — you configure which tickets fire via Zendesk's trigger builder
From draft mode to production
We recommend starting in draft mode: enable only the Internal Note tool (not Public Reply). The agent reads tickets and drafts responses as internal notes. Your team reviews the drafts, gains confidence in the agent's quality, and then enables public replies when ready.
What to watch for
- Volume and credits: every autonomous run consumes credits. A busy Zendesk with 500 tickets/day means 500 agent runs. Monitor your credit usage and set up alerts at 50%, 80%, and 90% thresholds.
- Trigger scope: start narrow. Use the "Custom Webhook" trigger type with specific Zendesk conditions (tags, brands, groups) rather than "Every Customer Message" which fires on everything.
- Closed-ticket errors: Zendesk doesn't allow updates on closed tickets. If a trigger fires on a closed ticket and the agent tries to post a reply, it gets a 422 error. The agent handles this gracefully (logs it and stops) but it's wasted credits. Filter out closed tickets in your Zendesk trigger conditions.
