A complaint is useful information about a gap between what a customer expected and what happened. Responding well means more than posting an apology: the business needs to understand the issue, offer an appropriate remedy, and prevent a repeat. A public response may be appropriate for a public complaint, but private account details and the actual resolution belong in a secure support channel.
Acknowledge and make the next step clear
Tell the customer you have received the complaint and who owns it. Give a realistic next-update time rather than a promise you cannot keep. If safety, fraud, discrimination, or a potentially widespread defect is involved, escalate it immediately through the relevant internal process.
A public reply can be brief: 'We're sorry this happened. We are checking the order and will update you by [time]. Please contact [secure channel] with your reference number.' Do not ask someone to publish a phone number, address, payment detail, or medical information in a comment thread.
Investigate before prescribing a fix
Listen without arguing about the customer's tone. An explanation may help later, but opening with a defense can sound like refusal to help. If the company is responsible, say what it will correct. If the facts are still uncertain, do not pretend the investigation is finished.
- Record the customer's account in their own words and check order or service records.
- Ask only for information needed to resolve the problem.
- Distinguish a one-off mistake from a recurring process failure.
- Give the team member handling the case authority or a clear escalation route.
- Document what was offered, accepted, and completed.
Resolve and follow up
Possible remedies include a repair, replacement, refund, service correction, or a clear explanation, depending on the situation and applicable terms or law. Do not offer a discount as a substitute for fixing a safety or compliance issue. Explain the remedy, the expected timing, and how the customer can follow up if it fails.
Close the loop after the promised action occurs. A case marked 'answered' is not necessarily a case the customer considers resolved. Review repeated issues by product, channel, location, and root cause rather than treating each complaint as an isolated PR problem.
Use feedback without manipulating it
Keep a simple complaint register with issue category, date, owner, action, outcome, and prevention step. Look at patterns and whether the fix reduced repeat complaints. ISO 10002 provides a broader complaints-handling framework for organizations of different sizes.
Do not suppress honest negative reviews or pressure a customer to remove one in exchange for help. The FTC says review practices should show a true and accurate picture. A credible response demonstrates what the company did, not merely how it wants to appear.