An AI customer service agent is software that works through your open help desk tickets, finds the answer in your own documentation and writes a reply for you to check. The safe version drafts and flags, and a person decides what the customer actually sees. This guide shows how that works in practice, using Support Replier from Dialogo as the example.
What an AI customer service agent does in one run
A run is one pass over your queue. Support Replier works through your open help desk tickets every 2 hours on weekdays, so a ticket that arrives in the morning has a draft waiting before lunch.
For each new ticket it does three things:
- Reads the customer's message.
- Searches your help docs for the page that answers it, then your public help centre.
- Saves the answer on the ticket as an internal note that only your team sees, or tags the ticket for a person when your docs do not cover it.
If you connect Slack, urgent or angry tickets go to your Slack channel, so you do not need to refresh the queue to find them. Cancellations and security problems are treated as urgent too, and at setup you can name the words, customers or plans that are urgent for you.
The point is not to remove people from support. It is to remove the first part of each ticket, the hunt through the docs and the blank page, while a person still owns the answer.
What it drafts and what waits for your approval
The agent writes from your docs, and nothing more. Each internal note starts with "READY TO SEND" and names the pages the answer came from, so your team can check the source in a few seconds.
Here is how the work splits:
| Step | Who does it |
|---|---|
| Find the answer in your docs | The agent |
| Write the answer as an internal note, or tag the ticket for a person | The agent |
| Flag angry, urgent, cancellation and security tickets in Slack, if connected | The agent |
| Read the note and answer the customer | Your team |
| Send the answer as a public reply | The agent, only if you allowed it at setup, after your OK in Dialogo |
You choose at setup whether the agent may reply to customers. Unless you clearly say yes, it never emails or replies to a customer: your team reads the note and answers in the help desk as usual. If you say yes, it sends each answer as a reply, and every reply waits for your OK in Dialogo unless you turn approvals off.
If a topic is on your never-answer list, the agent leaves it to your team.
What if your docs do not cover the question?
The agent tags the ticket for a person and adds a note on what is missing, instead of guessing. That is deliberate: a plausible but invented answer is worse than no answer. The agent answers only from pages it finds in your docs and help centre, and the question goes onto a list you can use later (see below).
Which help docs and tools it reads
The core setup needs two apps:
- A help desk: Zendesk, Freshdesk (Freshdesk needs your API key) or Gmail.
- A docs app: Notion, Google Docs, Confluence or Google Drive, where your help articles live.
Composio Search reads your public help centre. It needs no sign-in, so it connects by itself.
A few optional apps add context or alerts:
Dialogo AI
See this in action. Your real tools, your real workflows.
Free to try: set up 1 agent and run 3 free rehearsals, then pay when you go live.
| Optional app | What it adds |
|---|---|
| HubSpot | The customer's deals and history next to every draft |
| Outlook | Earlier emails with the customer as context for the reply |
| Jira or Linear | One issue for each bug a customer reports |
| Slack | One alert with the urgent tickets |
Dialogo connects to 3,000+ apps in total, but you do not need to think about that for support. Setup for this agent takes about 15 minutes, and most of that is signing in to your help desk and docs.
The weekly "questions your docs cannot answer" list
This is the part that keeps your docs improving. Every Friday the agent saves a list of the questions your docs could not answer as a page in your docs app.
That list is a to-do list for your documentation. If five customers asked about the same delivery rule and no page covers it, writing that page does two jobs: it fixes the gap, and the agent can answer the next ticket from it.
A simple routine works well:
- Open the weekly page on Monday.
- Pick the two or three questions that came up most.
- Write or update the matching help page.
- Let the next run use it.
Over a few weeks the tickets routed for a missing answer get rarer, because you wrote the pages they pointed to.
What to measure in the first two weeks
You do not need a dashboard. Keep a simple tally for ten working days:
- Drafts you used as written. A draft sent unchanged is a clear win.
- Drafts you edited. Note why. If you keep fixing the same thing, a docs page needs a rewrite.
- Tickets routed to a person. The notes on what is missing show where your docs have gaps.
- Urgent flags you agreed with. If the Slack alerts feel noisy or miss something, change what counts as urgent in the agent's setup answers.
- Time to first reply. Compare against your own numbers from before, not against a benchmark from somewhere else.
For example, a small team could count drafts in a spreadsheet for two weeks and then decide whether to keep the agent on its schedule. The numbers are yours, so the decision is too.
For the bigger picture, see the autonomous customer support use case.
Questions people ask
Can an AI customer service agent reply to customers by itself?
Only if you allow it. Unless you said yes at setup, it adds internal notes (or Gmail drafts) that only your team sees, and your team sends the reply. If you allowed replies, each one still waits for your OK in Dialogo unless you turn approvals off.
Can it make up an answer?
It answers only from your docs and help centre and names the pages it used. When they do not cover a question, it tags the ticket for a person with a note on what is missing, and the question goes on the weekly list.
What do I need to connect?
Zendesk, Freshdesk or Gmail, and Notion, Google Docs, Confluence or Google Drive for your help docs. Composio Search reads your public help centre with no sign-in. HubSpot, Outlook, Jira, Linear and Slack are optional.
Can I see it work before I pay?
Yes. After you connect your apps and confirm the setup answers, the free rehearsal takes your oldest open ticket through the whole job and shows the answer or the routing note, the tag and the alert it would make. It adds and sends nothing.
Try it on your own data
Set up one agent and run up to 3 free rehearsals on your real tickets before you decide to go live. Try Support Replier free. Nothing is sent without your approval.