Auto-Reply to Tickets Using Knowledge Base Articles

A knowledge base auto-reply closes that loop automatically. When a ticket arrives, an AI agent reads it, searches your knowledge base for the most relevant article, extracts the steps that actually answer the question, and posts a clear, written reply — then updates the ticket status. The repetitive questions get handled the moment they land, and your agents spend their day on the tickets that genuinely need a person.

This guide walks through how that works with Macha. One thing to be clear about up front: Macha is not a helpdesk and it isn't trying to replace Zendesk, Freshdesk, Gorgias, or Front. It's an AI agent layer that sits on top of the helpdesk you already run, reads from the knowledge sources you already maintain, and writes back into the same ticket your team is looking at.

What "auto-reply from a knowledge base" actually means

It's worth separating two ideas that get bundled together:

• Article suggestion / search. The customer types a question into a Help Center widget and gets a list of articles to read themselves. This is classic self-service deflection — useful, but it still asks the customer to do the reading and the interpreting.
• A written answer in the ticket. The AI reads the specific ticket, finds the matching article, and replies in the customer's words with the actual steps — "Here's how to reset your password: 1, 2, 3…" — then closes or pends the ticket. The customer gets an answer, not a reading assignment.

This use case is the second kind. The distinction matters because the second is what actually lightens the queue: a real answer resolves the ticket; a link often just produces a follow-up.

Here's the worked example we'll use throughout, drawn from a real Macha workflow:

Customer: "How do I reset my password? I've tried the login page but can't find the option." Macha (searches the Help Center, finds "How to Reset Your Password" — 95% match): "Here's how to reset your password: 1. Go to the login page and click Forgot Password 2. Enter your email address 3. Check your inbox for the reset link (check spam too) 4. Click the link and set your new password The link expires in 24 hours. Let me know if you run into any issues!" Macha then sets the ticket status → Solved and tags it kb-auto-resolved.

No agent touched it. The answer is grounded in a real article, written in plain language, and the ticket is closed and tagged so you can measure exactly how much volume this handled.

How the workflow is wired

Under the hood this is four tool calls against your helpdesk, orchestrated by an agent and kicked off by a trigger.

Three building blocks make this run, and each maps to a part of the Macha dashboard.

1. Connect your knowledge sources

The reply is only as good as what the agent is allowed to read. Macha's knowledge layer can pull from your Zendesk Help Center directly, and it can crawl a website, ingest uploaded documents, or connect live sources like Google Docs, Notion, and Confluence — so a policy that lives in your internal wiki can ground an answer just as well as a published article. (See the Data Sources docs for the full list.)

If your answers live in Zendesk Guide, that's the most direct setup: the agent reads from the same articles your customers already see.

2. Build the agent that writes the reply

The agent is where you set the rules: which model it uses, which knowledge sources it can search, and how it should behave — tone, when to answer, and crucially, when not to. You write instructions like "Only reply when you find an article that clearly answers the question with high confidence. Otherwise, leave the ticket for a human and add an internal note." That guardrail is what keeps auto-reply honest.

3. Set the trigger

Finally, you tell Macha when to run. For this workflow the trigger is Ticket Created on your Zendesk account, optionally narrowed with a condition so the agent only fires on tickets that look like common questions (for example, by group, tag, or channel). Triggers can also be Slack messages, webhooks, or schedules — but ticket-created is the natural fit here. (Triggers docs.)

Grounding: why it doesn't make things up

The reason this is safe to put in front of customers is that the agent isn't free-associating. It's doing retrieval first, then writing — it searches your indexed knowledge, retrieves the closest article, and is instructed to answer from that article. If nothing matches well, the right behavior is to stay quiet and escalate, not to guess.

This is the same principle the major helpdesks apply to their own generative replies. Zendesk's documentation for AI Agents Advanced is explicit: when a knowledge reply is triggered, the agent searches the available knowledge sources, and "if no relevant knowledge is found, the AI agent informs the customer that it can't answer their question" (Zendesk help). Freshdesk's Email AI Agent and Freshservice's Freddy work the same way — generating replies grounded in knowledge base articles and past resolutions. Macha's advantage is that the same agent can read across multiple sources (Help Center plus your Notion wiki, say) and take real actions on the ticket afterward, not just paste an answer.

A good knowledge-grounded reply, then, has three properties:

1. It's sourced. Every answer traces back to a specific article. If the article is wrong, you fix the article and every future reply improves.
2. It knows its limits. No confident match, no auto-reply. The ticket goes to a human untouched.
3. It's measurable. The kb-auto-resolved tag turns "how much did this deflect?" into a Zendesk view you can actually count.

Suggest vs. send: choose your level of autonomy

Going from zero to fully automated replies overnight makes a lot of teams nervous, and reasonably so. You don't have to.

• Draft for review (training wheels). Instead of posting a public reply, the agent writes the answer as an internal note and leaves the ticket for an agent to approve, edit, and send. Your team gets the speed of a pre-written, sourced answer while keeping a human in the loop. This is the Draft ticket responses for agent review variant of the same workflow.
• Auto-send (full autonomy). Once you trust the agent on a category — order status, password resets, return-policy questions — you flip those to post publicly and close the ticket, as in the example above.

A sensible rollout is: start in draft mode on one or two well-documented categories, watch the suggested replies for a week, and promote the categories that are consistently correct to auto-send. You're never forced into all-or-nothing.

When not to use a knowledge-base auto-reply

This pattern is excellent for a specific shape of ticket and a poor fit for others. Being honest about the boundary is what keeps customers happy.

• Questions that need account data, not an article. "Where is my order?" or "Why was I charged twice?" aren't answered by a static article — they need a live lookup against Shopify or Stripe. That's a different (and very doable) Macha workflow, but it isn't this one. Don't point a KB-only agent at order-status tickets.
• Thin or stale knowledge. If the article is outdated, the reply will be confidently outdated. Auto-reply makes the quality of your knowledge base visible — which is healthy, but it means you should clean up your top articles before you switch on auto-send.
• Emotional or high-stakes tickets. Complaints, cancellations, churn risk, anything legal or safety-related. Route these to a person. A correct-but-robotic article reply to an angry customer makes things worse.
• Ambiguous questions. If the agent can't find a high-confidence match, the correct outcome is escalate, not improvise. Set that guardrail in the agent instructions and resist the temptation to lower the confidence bar to juice your deflection number.

The teams that get the most out of this treat the auto-reply rate as a quality metric, not a vanity metric: a smaller set of confidently-correct deflections beats a large set of mediocre ones.

What it does to your numbers

Vendor and agency write-ups across the category commonly cite 30–50% deflection of Level-1 tickets from knowledge-grounded replies, with first-response times dropping sharply because matched questions are answered instantly (figures from sources like eesel and CoSupport). Treat those as directional, not promises — your actual rate depends entirely on how much of your volume is genuinely repetitive and how good your articles are. The honest framing: Macha automates the action of answering; the outcome depends on your queue and your knowledge base.

What you can count on is the mechanics. Instant first response on matched tickets, every reply traceable to a source, and a clean tag on each auto-resolved ticket so you can see — in your own Zendesk reporting — exactly how much volume this took off your team's plate.

Pricing

Macha bills in credits, charged per AI action — not per deflection or per resolution. Each step the agent takes (reading the ticket, searching knowledge, writing the reply) is an action, and the credit cost depends on the model you choose: roughly 0.5–9 credits by model, with the default GPT-5.4 Mini at 1 credit. Because cost is per action and not per outcome, a tight auto-reply workflow is inexpensive to run at volume. You can try it on the 7-day free trial, no credit card required, and the full plan breakdown is on the pricing page.

How to set it up

1. Connect your helpdesk. Link Zendesk (or Freshdesk) so Macha can read tickets and post replies. See Macha on Zendesk.
2. Connect your knowledge. Add your Help Center as a source — and optionally a website crawl, uploaded docs, or a live Notion/Confluence/Google Docs source.

1. Build the agent. Give it the knowledge sources, a model, and clear instructions — including the rule to escalate when it isn't confident.
2. Start in draft mode. Have it write internal-note suggestions first. Review for a week.
3. Promote to auto-send on the categories that prove reliable, set the Ticket Created trigger, and add a tag like kb-auto-resolved so you can measure the impact.

FAQ

Does Macha replace my helpdesk? No. Macha is an AI agent layer that runs on top of Zendesk, Freshdesk, Gorgias, or Front. It reads and writes in the same tickets your team already uses — you keep your helpdesk exactly as it is.

Where does the answer come from? From your own knowledge: your Zendesk Help Center, a crawled website, uploaded documents, or live sources like Notion, Confluence, and Google Docs. The agent retrieves the best-matching article and answers from it, so replies trace back to content you control.

What happens if there's no matching article? The agent is instructed not to guess. With no confident match it leaves the ticket for a human — optionally adding an internal note flagging the gap, which is a useful signal for what to write next.

Can I review replies before they're sent? Yes. Run the agent in draft mode and it posts answers as internal notes for an agent to approve and send. Promote categories to fully automatic only when you trust them.

Can it close the ticket too? Yes. The workflow can set the status (Solved, Pending, etc.) and apply a tag like kb-auto-resolved so the deflection is measurable in your standard helpdesk reporting.

What about questions that need order or billing data? Those need a live lookup, not an article — a different Macha workflow that connects Shopify or Stripe. A knowledge-base auto-reply is for questions a published article can fully answer.

Want to see it on your own tickets? Read more about Macha on Zendesk, browse the docs, or explore other Macha use cases.