An acknowledgement is a promise about process, not a view on the complaint. The agent recognises the complaint, reads it back to the customer, opens the case, and sends an approved acknowledgement inside your deadline: reference, owner, next step and timescale. It never admits fault, offers redress or predicts the outcome.
What is a complaint acknowledgement, and who owns it?
Most regulated firms must tell a customer, soon after a complaint arrives, that it has been received and how it will be handled. A good acknowledgement does four things. It shows the firm understood what the customer is unhappy about. It gives a reference and names who is dealing with it. It says what happens next and by when. And it tells the customer how to add information or ask for support.
The head of complaints owns the acknowledgement standard and its templates. Compliance approves the wording and the deadline rules. Handlers own the case once it is open. The agent can carry the acknowledgement end to end because it is routine, rule-bound and the same every time, which is the kind of work our guide to the AI support agent that knows when to say no describes as safe to execute.
What are the steps, and at what depth?
- Agent, depth 1: recognises the complaint. In chat, email, voice or messaging, any expression of dissatisfaction that seeks a remedy or an answer, whether or not the word "complaint" is used.
- Agent, depth 3: confirms the complaint with the customer. "You are unhappy that the fee was charged after you cancelled, and you want it refunded. Is that right?" The customer's correction is recorded.
- Agent, depth 1: checks for support needs. Signs of vulnerability, accessibility requests or a preferred contact method. Anything found goes on the case for the handler.
- Agent, depth 3: opens the case with the date the complaint first reached the firm, the confirmed summary and the category.
- Agent, depth 3: sends the acknowledgement from the approved template, filling only the defined fields: reference, summary, team, next step, timescale, how to add information, where to get help.
- Agent, depth 1: routes the case. Complaints about the agent itself, complaints alleging fraud or data loss, and complaints from customers in difficulty go to named queues.
- Person, handler: accepts the case and takes over all substantive contact.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Recognise | Spots dissatisfaction in any channel | 1 | Disputed cases |
| Confirm | Reads the complaint back | 3 | Nothing |
| Support | Notes vulnerability and access needs | 1 | Acting on them |
| Open | Creates case with receipt date | 3 | Nothing |
| Acknowledge | Sends approved template | 3 | Template wording |
| Route | Sends to the right queue | 1 | Nothing |
| Handle | Nothing | none | Investigation and response |
Which controls matter, and what evidence does each leave?
Fixed template, fixed fields. The agent fills fields; it does not write prose into the acknowledgement. Evidence: template version and field values on each message.
No admissions, offers or predictions. "We will refund you", "this should not have happened" and "you will hear good news" are outside scope. Certification tests for these phrases in many forms. Evidence: scope-gate results and sampled acknowledgements.
Summary confirmed by the customer. The handler starts from what the customer agreed they meant. Evidence: the confirmed summary and any correction.
Receipt date from the first contact. Evidence: the source timestamp for each case's start date.
Complaints about the agent leave the agent. A customer complaining about an AI decision should not have the same agent run their case; see can an AI agent handle complaints about itself? Evidence: routing records.
What should you measure?
- Time from receipt to acknowledgement, against the deadline, by channel.
- Summaries corrected by the customer, as a sign of how well the agent listens.
- Cases reclassified by handlers, showing where recognition or categorisation failed.
- Acknowledgements sent outside the template or with empty fields. The target is none.
- Complaints about the agent, counted separately. As complaints about the agent are the most useful complaints argues, they tell you where its bounds are wrong.
Where does it usually go wrong?
Fast but wrong. An acknowledgement that misstates the complaint is worse than a slower one that gets it right. Do not skip the confirmation step to save time.
The acknowledgement sounds like a reply. Customers read "we are sorry for the inconvenience" as an answer. Keep the language about process.
Timescales are promised that the team cannot meet. The template should state the deadline your rules set, not an optimistic target. The deeper point is in complaints handling with agents: deadlines are the easy part.
Representatives are ignored. A complaint made by a family member, a claims firm or a solicitor on the customer's behalf needs the representative's authority checked before details are shared. The agent should acknowledge to the person who wrote and route the authority check to the handler.
Customers who started elsewhere get a second acknowledgement. Check for an open case before opening a new one.
The agent keeps talking. After acknowledging, customers often add detail or ask for a view. The agent records the detail on the case and says the handler will respond, rather than starting the investigation.
Where Pryme fits
In Pryme, acknowledgements run at depth 3 only after Attest has replayed the agent against your own past complaints and it has cleared the scope and refusal gates. Each acknowledgement is filed with its template version, and any attempt to stray into redress is refused and recorded.
Questions people ask
Can the agent resolve simple complaints instead of acknowledging them?
Some firms resolve uncomplicated complaints on first contact, which is covered in can an AI agent handle customer complaints? Resolution involves judgement and often redress, so it needs its own certification and usually a person's approval.
What if the customer does not want to make a formal complaint?
Record their choice and what they were unhappy about. Under many rules, dissatisfaction can still count as a complaint, so the case may still need handling; the handler decides.
Should acknowledgements say an AI sent them?
Yes. Customers should know they are dealing with an AI system, and the acknowledgement should name the team of people who will handle the complaint.