Complaint Response Drafting Agent · Use case
How can we use an AI agent to draft the response to a customer complaint on our own infrastructure?
A complaint response drafting agent takes one complaint, sets out what happened in date order from the contact history, checks each point the customer raises against your complaints procedure, and drafts the response in your format with the source of each statement. The complaints handler decides the outcome and any redress, edits the draft and sends the response. The agent upholds and rejects nothing, proposes no amount, closes no complaint and sends nothing to the customer.
The complaint is one page.
The history behind it is forty.
- ✗ 01A complaint arrives as one letter, and what the company said and did sits in tickets, call notes and emails that the handler reads one by one before writing a word.
- ✗ 02The response is the company's own statement to a customer who is already in dispute, and a deadline set by the procedure or by a regulator is running.
Where it stops for a person
Always. The complaints handler decides the outcome and any redress, and sends the response.Always. It sets out and drafts, it does not decide: whether the complaint is upheld, what redress is offered and what the company admits are the complaints handler's decisions. The draft leaves the outcome blank. Where the history and the complaint differ it sets both out and does not say which is right. It reads no mood from how the customer writes. A complaint that mentions a legal claim, an ombudsman or a regulator is marked for the complaints manager first.
It sets out what happened and drafts.
The complaints handler decides and sends.
Step · 01
The complaints handler opens the complaint and uploads the customer's letter or names the ticket.
Step · 02
The agent reads that customer's contact history through your own APIs, read only, and sets out what was asked, said and done, in date order, with the record behind each line.
Step · 03
It lists each point the complaint raises and, beside it, what the history shows and the clause of the complaints procedure that applies.
Step · 04
It drafts the response in your format, leaves the outcome and any redress as blanks for the handler, and lists what it could not find.
Step · 05
The complaints handler decides the outcome and any redress, edits the draft, and sends the response.
Reads from · connectors
Your own APIs
The complaint, as an uploaded file or a ticket; that customer's tickets, call notes and emails, read through your own APIs with the operations that change something left out; and the complaints procedure and your response templates, indexed as a knowledge source. It runs with the handler's permissions and reads one customer's history for one complaint.
Acts through · MCP servers
Nothing. It writes a timeline and a draft. It has no tool that sends a response, logs or closes a complaint, or raises a refund or a credit.
What you set up
- Index the complaints procedure and your response templates as a knowledge source, and remove the versions no longer in force.
- Import the description of the API that holds tickets and contact history, and keep only the operations that read.
- Build the agent in Katonic Studio and test it on invented complaints, with a handler checking each timeline against the records.
- Publish it to the complaints team only.
Where it runs
The agent, its knowledge store and the model run on infrastructure you own or control. You choose the model and serve it yourself, so questions, documents and answers are not sent to a public AI service. Complaints and the contact history behind them stay inside the company until the complaints handler sends the response.
How you get it today
This page is labelled Use case: the agent is built in Katonic Studio. You describe the job, connect what is named above, add test questions and release the agent once it passes them. When the Catalog holds a tested template for this job, this page will carry the Template label and show how to take it.
Does it decide whether a complaint is upheld?
No. It sets out what happened and drafts the response with the outcome left blank. The complaints handler decides the outcome and any redress.
Does it send the response or close the complaint?
No. It has no tool that sends anything or changes the complaint record. The complaints handler sends the response.
How does the handler check the draft?
Each line of the timeline and each statement in the draft gives the record or the clause behind it, so the handler can read it against the source.