A customer complaint needs an owner, a useful reply and a next step. A polished public response is only the start: someone must investigate the problem and follow through. This playbook gives a small team a repeatable way to handle ordinary service complaints without copying the same apology into every thread.
Separate the public reply from the investigation
Read the whole message before answering. Note what the customer says happened, what they want and what your team can verify. Treat an allegation as something to investigate, rather than a fact to repeat. Check whether a colleague has already replied so the customer does not receive conflicting instructions.
The public reply should acknowledge the specific concern and explain the next step. Keep order numbers, contact details and account information in your established private support channel. Do not ask someone to post those details in a public comment, and do not copy them back into your response.
Use a simple routing table
| Situation | Owner | First action |
|---|---|---|
| Late delivery or missing item | Customer service | Check the order privately and confirm the next update |
| Repeated product fault | Customer service and product lead | Record the recurring issue and investigate the affected item |
| Public disagreement about a policy | Customer service lead | Check the policy and explain the applicable process plainly |
| Threat, safety concern or suspected data exposure | Designated incident lead | Escalate promptly through the organisation’s incident process |
Adapt these roles to your team. The person watching social messages does not have to solve every case, but they do need to know who owns the handoff. Name a backup for days when the usual owner is unavailable.
Write four useful sentences
- Acknowledge the actual issue: “I’m sorry your delivery has not arrived when expected.”
- Say what can happen next: “Our support team can check the order and delivery status.”
- Give the established private contact route: “Please use the support contact on our website and include your order reference there.”
- Set a realistic update expectation, using a time your team has agreed and can meet.
Do not promise a refund, replacement or resolution before checking what you can authorise. Avoid diagnosing the cause from a single comment. “We are checking what happened” is more accurate than blaming a courier without evidence.
A worked example
Imagine a customer writes: “My workshop booking confirmation never arrived, and nobody has answered me.” A possible reply is: “I’m sorry you have been left unsure about your booking. Our support team will check the booking and confirmation message. Please contact us through the support address on our website with your booking reference, rather than sharing it here. Once we receive it, we will update you by the next working day.”
This is a hypothetical example. Use the final sentence only if the team can meet that commitment. Internally, assign the case to a person and check the booking system, delivery logs and prior replies before drawing a conclusion.
Close the loop and learn from repeats
Keep a private case log with the issue category, assigned owner, promised update, current status and resolution date. Store customer details in the support system; a separate reporting sheet usually only needs a case reference. Limit access to people who need it for the work.
At a weekly review, look for missed updates and repeated causes. If several customers cannot find delivery information, improve that information and check the next group of enquiries. Count reopened cases separately from newly reported problems: closing a ticket is not proof that the customer received a workable answer.
Check the reply before posting
Ask whether it addresses this customer’s issue, contains only verified facts, protects private details, names a practical next step and makes a promise the team can keep. An AI-assisted draft can help with wording, but the case owner still needs to check every factual statement and commitment. A thoughtful response should lead to action inside the business, not end at the comment box.