
Customer Complaint Response: Example and AI Prompt
A useful response to a customer complaint acknowledges the specific concern, explains what you will check, and gives the customer a next update you can deliver. AI can help draft the message from the facts you supply. A person still needs to verify the wording, authorize any remedy, and own the follow-through.
If you're a woman running a service business with a team, a complaint can feel personal. I would give yourself enough space to understand the issue before composing a reply. Your customer needs attention to the problem, and your team needs clear responsibility for handling it.
Understand the concern before drafting
Read the customer's message alongside the relevant agreement and delivery record. Separate what the customer reports from what your business has confirmed. Both belong in the review.
A customer may say an agreed update never arrived. Your system may show a message was sent. That still leaves questions about the destination, access, and what the message contained. Avoid deciding the customer is wrong simply because one activity was logged.
The Australian Government's complaint-handling guide recommends listening, keeping records of promises and agreements, asking for relevant documents, and following up. The approach below applies those service practices to a reviewed written response.
Give your team a short complaint record
Keep the record where the responsible team can access it. Include only the information needed to understand and handle the matter.
Customer concern: What happened according to the customer's account? Preserve useful specifics.
Confirmed facts: What does the agreement, message history, or delivery record establish?
Unanswered questions: What needs checking, and who can check it?
Requested outcome: What has the customer asked for? Record “not stated” when needed.
Authorized next action: What can the person handling the complaint actually commit to?
Owner and update time: Who will follow through, and when can the customer expect an update?
Confirm the owner and update time internally before putting them in a message. A promise made to sound reassuring becomes another problem if nobody can keep it.
Acknowledge the issue in plain language
Consider a fictional example. Priya owns a consulting business. A client says the project checklist link is inaccessible and that this has delayed her team's preparation. Priya's team has confirmed that access needs correcting. It can send a working link that afternoon, but it hasn't checked whether the preparation delay changes the project schedule.
A response could read:
I'm sorry the checklist link wasn't accessible when your team needed it. We've confirmed the access problem. I'll send the corrected link this afternoon and ask you to confirm it opens. I'll also check with the project lead whether the delay affects the preparation schedule, then update you tomorrow by noon.
Those commitments fit this fictional situation only because the team has checked it can meet them. The response acknowledges the confirmed error and the customer's reported impact. It doesn't promise that the schedule is unaffected before the project lead has reviewed it.
When you haven't confirmed what happened, acknowledge the concern and explain the next check. Don't invent an apology for an event you can't yet describe, or use vague sympathy to avoid addressing an error you have confirmed.
Ask AI for a draft that stays within the record
Use the business-approved tool and remove unnecessary identifying or confidential details. Supply your complaint record and the relevant approved response guidance.
Draft a concise reply to this customer complaint using only the supplied record. Acknowledge the specific concern in plain language. Distinguish confirmed facts from information still being checked. Include only the next actions and update times explicitly authorized in the record. Do not invent causes, promises, refunds, policy terms, or a resolution. Do not infer the customer's motives. If an owner, action, or update time is missing, list it in a separate internal review note rather than filling it in. Produce a draft for human review.
Read the draft against the original message. Check the ordinary sentences as closely as the obvious commitments. “This won't happen again” is a promise. “We've fixed it” is a factual claim. Neither belongs in the reply without support.
Any decision about a refund, contractual responsibility, or another remedy should go through the person authorized to assess it using the applicable terms and obligations. A writing tool shouldn't make that decision for your business.
Finish the action behind the message
Sending the response doesn't close the complaint. Record the action, the person responsible, and the agreed update time in the team's work system. Keep a record of the message and what happened next.
In Priya's example, correcting the link and checking the schedule are separate actions. Confirming the link opens also matters. Don't mark everything complete because the first email went out.
After addressing the issue, ask whether the customer still needs anything clarified. Then review what your team can improve. Repeated access problems may call for a check before sending materials. An isolated issue may need a smaller correction. Use the evidence to choose.
For a clear structure around the next message, see the follow-up email example and adapt it to the action actually agreed.
Want help building a customer-response workflow that your team can use with AI? Contact AI with Dani to discuss the process you want to improve.
