Adding an AI Agent to Zendesk, Freshdesk or Gorgias
A team that already works in Zendesk, Freshdesk or Gorgias does not have to leave it to get an AI agent that checks orders and drafts replies. There are three places to attach the agent, and they differ in how much the team's daily routine changes. Our production system uses the first and the third. This page describes all three so you can choose.
Option 1: attach at the mailbox
Every helpdesk receives email from a support address. The agent can read the same mailbox over IMAP, before or alongside the helpdesk. It distils each email, checks the order and the knowledge base, and prepares a draft and a proposed solution.
This is how our deployment receives mail: five mailboxes, 36,789 customer emails in the 30 days to 19 November 2026. It needs nothing from the helpdesk vendor, and it works with a helpdesk that has no API at all. The details are in AI for a shared support inbox.
Option 2: attach through the ticket API
Zendesk, Freshdesk and Gorgias each have an API that reads tickets and writes to them, and each supports internal notes that customers do not see. With this option the helpdesk stays the team's only screen:
- A new ticket or a new customer message triggers the agent.
- The agent reads the ticket and its history through the API, and the order through the store's API.
- It writes its output back to the ticket as an internal note: the facts it established with their sources, the proposed solution, and the reply text.
- The human agent reads the note, sends the reply as it is or edits it, and decides on any action.
What the helpdesk does not provide is the part after the decision. A refund or a reshipment that an agent approves still has to reach the person who carries it out, with an owner and a record. In this option that step is built on tags, ticket fields and the helpdesk's own automation rules.
Option 3: a workbench built for approvals
Our production system has its own ticket workbench, built around the fact that most of an agent's work is now reviewing. What it shows for each ticket:
- The customer's request for this round, separated from quoted text and old messages.
- A summary of the earlier exchange as dated facts: what was promised, what was done, what is still open.
- The verified order and shipping status.
- The AI's proposed solution and the draft reply. Replies in other languages are shown with a translation, so one team reviews every market.
- Two buttons: send and keep open, or send and close. Closing asks whether someone has to act; if so, the task goes to the execution list and the team's group chat at once.
Around the ticket sit the queues a helpdesk does not have: an "AI review" queue for solutions the AI handled on its own, an execution list split by the action a person must take, and a complaint record that archives every reply. One line per decision is written to a shared ledger, using the version a person finally approved.
How to choose
- You want drafts in front of agents with no change to their tools: option 2.
- Your helpdesk plan has no API access, or you use a shared mailbox: option 1.
- Most of your tickets end in an action, such as a part to ship or a refund to pay: option 3, because the cost sits in what happens after the reply.
The options combine. A team can keep its helpdesk for phone and social channels and run email through the workbench.
What stays the same in all three
- Reading before the model. The thread is distilled into structured facts first. A raw thread of 25 messages produced a reply that contradicted an earlier promise; structured facts fixed it and cut the input from 37,604 tokens to 4,722.
- Four lookup results. Found, confirmed none, partial, could not check.
- The approval line. Anything that moves money or goods is decided by a person.
- Counting. Sent by the AI, sent unchanged, edited before sending. In the 30 days to 19 November 2026 those were 3,331, 3,781 and 19,339.
Checking a helpdesk's built-in AI
Helpdesks sell AI features of their own. Check four things before relying on one for after-sales work: whether it looks up a specific order and its carrier status, what it says when that lookup fails, whether it keeps earlier promises consistent across a long thread, and what you are billed for. The nine checks in our chatbot checklist apply to helpdesk AI as written.
What we need from you to start
- For option 1: IMAP and SMTP access to the support mailboxes.
- For option 2: an API token for the helpdesk with permission to read tickets and add internal notes.
- For all: read-only access to orders, as listed for Shopify and for WooCommerce, Magento and custom stores.
Tell us which helpdesk you use and the free plan states which option fits, within two working days.