# Respond to customer complaints with facts, a clear action, and follow-up

> Prepare the facts, applicable policy, and available remedies, then draft a channel-appropriate response a team member can review and deliver.

**Author:** Awamer  
**Published:** 2026-11-11  
**Category:** Practical guides

---

A polite response does not resolve a complaint unless the next action is clear. Before drafting, distinguish the customer’s account, verified business records, and available remedies. An assistant can organize those inputs, while compensation and exceptions remain decisions for an authorized person.

## Separate facts from assumptions

Collect the sanitized complaint, event sequence, and checked order status. Record unresolved questions rather than asking the model to choose a convenient explanation. A conflict between records may require a focused clarification before a final response.

For a fictional sizing complaint, confirm what the customer received and which information guided the purchase. Do not assume they ignored instructions or acknowledge an unverified event. Recognizing the reported inconvenience does not require inventing its cause.

## Define the remedy and decision owner

Provide the approved policy and genuinely available options, such as clarification, inspection, exchange, or a return process. Identify actions requiring approval. Promise no amount, deadline, or operation the team cannot deliver. The [returns policy template](/en/ai-prompts/store-return-policy) helps express existing rules clearly for appropriate review.

Customer message: [sanitized text]. Verified facts: [list]. Unknowns: [questions]. Approved policy and available remedies: [details]. Channel: [channel]. Draft a response that acknowledges the problem and explains the next action and follow-up route. Add no blame or unapproved promises. If needed, suggest one clarification question. Keep customer-facing text separate from internal notes.

## Adapt to the channel

Public replies should avoid order details and personal data while providing a suitable follow-up route. Private messages can contain necessary details after appropriate checks. Email may benefit from a short summary and ordered steps. Use the [complaint response template](/en/ai-prompts/customer-complaint-response), then inspect the tone and clarity yourself.

Ask whether the customer knows what to do next and whether the response reflects the seriousness of the situation. Escalate cases outside the team’s authority rather than allowing the model to settle a dispute or create an exception.

## Verify the outcome

Sending a reply is not proof that the remedy happened. Record the actual action and follow-up status, then classify fixable causes such as product information, packaging, delivery, or unclear policy.

Use [review analysis](/en/ai-prompts/customer-review-analysis) to identify recurring patterns. Keep sanitized examples approved by the team and use them to improve the template. The [ecommerce hub](/en/ecommerce) connects the response to supporting policy and operational context.
