A customer complaint is not only a message to answer. It is also a signal about expectations, policy, product quality, staff handoff, or unclear website copy. ChatGPT can help you slow the situation down before you reply.
The goal is not to make ChatGPT decide whether the customer is right. The goal is to organize the facts, draft a calm response, and create an internal fix list so the same complaint is less likely to happen again.
Best use cases
- A customer sends an angry email or chat message.
- You receive a public review and need a short professional response.
- A refund request is emotional, unclear, or tied to a policy dispute.
- Several customers are complaining about the same issue.
- You need to brief a manager or teammate before replying.
What to prepare
- The customer's message or review.
- Order, appointment, or account details you can safely share.
- Your refund, cancellation, delivery, or service policy.
- What has already happened, including dates and promises made.
- What outcome you are willing to offer.
The workflow
- Remove private customer details before pasting the complaint.
- Ask ChatGPT to separate facts, emotions, unclear claims, and policy questions.
- Ask for a customer reply and an internal action plan separately.
- Review every promise, refund, deadline, and policy statement before sending.
- Save repeated complaint themes for a weekly operations review.
Copy this prompt
Turn this customer complaint into a response plan.
Business type:
[business type]
Customer channel:
[email, chat, phone summary, Google review, Yelp review, support ticket]
Customer complaint:
[paste complaint with private details removed]
Known facts:
[dates, order status, service details, prior messages, what your team already did]
Relevant policy:
[refund, cancellation, delivery, warranty, or service policy]
What we can offer:
[refund, replacement, correction, apology, call, store credit, no refund, investigation]
Return:
1. Complaint summary in one sentence
2. Facts we know
3. Claims that need verification
4. Customer emotion or expectation
5. Risk level: low, medium, or high
6. Recommended next action
7. A calm customer reply
8. Internal fix list to prevent repeat complaints
Do not invent policy, dates, refunds, or promises. If something is missing, write "needs confirmation."
Input example
Business type: local appliance repair company
Customer channel: Google review
Customer complaint:
They said the technician arrived late, did not have the part, charged a diagnostic fee, and told them the repair would take another week. They wrote: "This company wasted my day and charged me for nothing."
Known facts:
Appointment window was 12-3pm. Technician arrived at 3:20pm. The part was not stocked because the model number was not provided during booking. Diagnostic fee is disclosed on the booking page. Technician offered to apply the diagnostic fee to the repair if the customer approves the quote.
Relevant policy:
Diagnostic fee is charged for inspection and can be credited toward approved repair. Arrival windows are estimates, but customers should be notified if the technician is running late.
What we can offer:
Apologize for the late arrival, explain the diagnostic fee briefly, offer a scheduling priority for the return visit, and review why the delay notification did not happen.
Expected output
A useful answer should not argue with the customer. It should identify the real service failure, the policy issue, and the prevention step. In the example above, the late arrival and lack of delay notification are the strongest apology points. The diagnostic fee can be explained, but it should not become a long public debate.
The internal fix list should include clearer booking questions for model numbers, a late-arrival notification rule, and a short staff note about how to explain diagnostic fees before the visit.
Public review reply prompt
Write a public reply to this review.
Review:
[paste review]
Facts we can safely mention publicly:
[facts]
What we should not mention:
[private details, account details, health/legal/financial details, internal staff notes]
Tone:
Professional, brief, non-defensive.
Return one reply under 90 words.
Rules:
- Acknowledge the concern.
- Do not argue line by line.
- Do not reveal private customer information.
- Invite the customer to contact us directly.
- Do not promise a refund unless I explicitly included that option.
Internal fix-list prompt
Turn this complaint into an internal improvement checklist.
Complaint summary:
[summary]
What happened:
[known facts]
Current policy or process:
[policy/process]
Return:
1. Likely root cause
2. What we should verify before deciding
3. One immediate customer action
4. One staff coaching note
5. One website or policy wording update
6. One process change to prevent repeat complaints
7. How to track whether this issue happens again
Common failures and fixes
- Failure: The reply sounds defensive. Fix: ask ChatGPT to remove explanations that do not help the customer feel heard.
- Failure: ChatGPT offers a refund you did not approve. Fix: list exactly what outcomes are allowed and say not to invent offers.
- Failure: The response is too long for a public review. Fix: set a word limit under 90 words and ask for only one next step.
- Failure: The tool treats a repeated complaint as a one-time message. Fix: ask for an internal fix list and a repeat-complaint tracker.
- Failure: Private customer details leak into the reply. Fix: include a "what we should not mention" section before drafting.
Stronger prompt
Act as a customer support manager. Analyze this complaint before drafting any reply.
Complaint:
[paste complaint]
Business facts:
[facts]
Policy:
[policy]
Allowed outcomes:
[allowed outcomes]
Return in this order:
1. What the customer is upset about
2. What we did right
3. What we may have done wrong
4. What is unknown and must be checked
5. Whether this is mainly a communication issue, policy issue, product/service issue, or expectation issue
6. Customer reply under 120 words
7. Public review reply under 90 words
8. Internal action list with owner, deadline, and prevention step
Rules:
- Keep the customer replies calm and human.
- Do not blame the customer.
- Do not admit fault beyond the facts provided.
- Do not invent refunds, discounts, deadlines, or policy exceptions.
- Mark missing information as "needs confirmation."
Related guides