Give ChatGPT a short timeline, the evidence you have, and the result you want. Ask for a calm complaint that explains what happened, what remains unresolved, and what the company can do next. Before sending, check every date, amount, claim, and attachment against your records. A strong letter makes the problem easy to investigate; it does not need threats or invented legal language.
What you need before you start
Use this approach for a delivery problem, a service that was not provided as agreed, a wrong bill, damaged goods, or an unresolved support request. It is also useful when frustration makes your first draft hard to follow. If you need advice about legal rights or a formal deadline, that is a separate question requiring current guidance for the relevant location and situation. This method helps you describe your facts and request a remedy.
Bring: Prepare the company name, a harmless order or account reference, dates, the agreed product or service, what happened, contact attempts, available evidence, and your preferred solution. Include only personal details needed for the company to find the case. Use placeholders in the drafting chat for addresses, account numbers, and contact details that you can add yourself before sending.
Start with these steps
- Write a dated timeline from your records. Separate what you know from what you suspect or have been told.
- Choose one main remedy, such as a replacement, corrected bill, refund request, or explanation. State any acceptable alternative clearly.
- Ask ChatGPT for a concise subject line and a letter built from the confirmed facts, with a short evidence list and a clear next action.
- Remove unsupported accusations, invented policies, legal claims, and facts that are missing from your records.
- Check references, dates, amounts, attachments, contact details, and the actual route for submitting the complaint.
- Send the checked letter through the appropriate channel, keep a copy, and record the submission date and any receipt.
A prompt you can adapt
Help me draft a complaint to [company or team]. Use simple, calm, firm language. State the problem early, present my dated facts in order, explain what remains unresolved, and request [preferred remedy]. Do not invent facts, laws, company policies, rights, quotes, or deadlines. Do not accuse anyone of intent we cannot prove. Label missing information outside the letter. Use placeholders for private details. Include a subject line, the letter, and a checklist of facts and attachments for me to confirm. My timeline: [dates and events]. Evidence: [items I really have]. Previous contact: [dates and response]. Acceptable alternative: [if any]. Requested response date: [my chosen reasonable date, or omit].
Replace every bracket with real information. Remove fields that do not affect your task.
What this looks like in practice
In this invented example, a customer ordered a desk lamp for $48 on 2 September 2026 under reference EX-204. It arrived on 6 September with a cracked base and would not stand securely. The customer emailed support on 7 September with two photographs and received an automated acknowledgment that day. They received no further reply by 14 September. They want a replacement; if a replacement is unavailable, they would accept a refund. The letter can state those facts and ask for instructions about the damaged lamp. It cannot claim the company ignored repeated calls, caused an injury, or promised a seven-day resolution, because none of that is in the example records.
A complaint built from facts and a remedy
Purchase, damage, support email, unresolved status
Order confirmation and actual photographs
Replacement requested; refund accepted if unavailable
Checked letter, submission receipt, and later reply
Make the problem easy to understand in the first few lines
Start with the order, service, or bill and the problem you want fixed. The reader should not have to work through several paragraphs of disappointment to discover that a lamp arrived damaged. A clear opening could be: 'I am writing about order EX-204, a desk lamp that arrived with a cracked base. I would like a replacement and instructions for handling the damaged item.' That sentence gives the team a case and an action.
You can be polite without making the problem sound small. 'Sorry to bother you' is unnecessary when you are asking for a purchase issue to be resolved. Equally, calling the company dishonest before explaining the evidence can move attention away from the actual fault. Say what happened, why it matters, and what you need.
ChatGPT is useful when your rough notes are full of emotion or repeated details. Give it those notes, but ask it to preserve the facts while improving the order and wording. You do not have to erase your experience. If a missed appointment caused you to take time off work, that can be relevant when accurately described. Do not let a tidy rewrite erase an important impact or add one that did not happen.
Turn your records into a dated timeline
Use receipts, messages, photographs, account records, and your own dated notes to build the timeline. Begin with the agreement or purchase, then the problem, then your attempts to resolve it. Keep the sequence short enough to follow, but include the facts needed to distinguish your case from an ordinary request.
Do not describe a date as exact if you only remember roughly when something happened. 'Around 6 September' is different from 'on 6 September.' If the exact day matters, find the delivery record. Likewise, a message saying 'we will look into this' is not the same as a promise to issue a refund. Quote only wording you can compare with the original message.
Split statements into observed, reported, and inferred. 'The base has a crack' is an observation supported by the photo. 'The delivery driver dropped it' is an inference unless you saw that happen or have evidence. A complaint can explain the damage without deciding who caused it. That leaves the company able to investigate while keeping your description accurate.
| Date | Confirmed event | Supporting record |
|---|---|---|
| 2 September 2026 | Purchased desk lamp for $48, order EX-204 | Order confirmation |
| 6 September 2026 | Lamp arrived with cracked base | Delivery record and two photographs |
| 7 September 2026 | Emailed support with photographs | Sent email and automated acknowledgment |
| 14 September 2026 | No further response received | Checked correspondence at drafting time |
Choose a remedy the company can act on
'Please sort this out' leaves the receiver guessing. A remedy is the action you want: replace the damaged lamp, correct the bill, explain an unexpected charge, arrange the missed service, or consider a refund. Pick the main outcome and state it plainly. You can ask for more than one connected action, but make the priorities clear.
In the example, the customer wants a replacement and return instructions. They accept a refund if a replacement is unavailable. That is a useful alternative because it helps the company answer without another round of messages. It does not mean a replacement or refund has already been approved. The letter is a request.
You may ask for a reply by a chosen date, but describe it honestly as your request unless a verified policy or rule supplies a deadline. For example: 'Please let me know by 21 September how you propose to resolve this.' That is different from saying the company is legally required to answer within seven days. The writing method does not establish such a rule.
If you are unsure which outcome you want, ask ChatGPT to compare your options using only your facts. A replacement may suit you if you still want the item. A refund request may suit you if the delay makes the item no longer useful. Keep policy eligibility and legal entitlement separate from personal preference.
A complete complaint letter from the sample facts
This sample uses the invented lamp case. Replace its facts with your own verified information rather than sending it unchanged. It gives the company enough detail to locate the order and understand the requested solution. Private contact details are placeholders so they can be added after the draft is checked.
The letter includes the earlier contact because it explains why this is now a complaint. It does not say support deliberately refused help. An automated acknowledgment confirms receipt of that earlier message, but does not prove a person reviewed the case.
Subject: Damaged desk lamp, order EX-204, replacement requested. Dear Customer Support, I am writing about order EX-204, a desk lamp purchased for $48 on 2 September 2026. It arrived on 6 September with a cracked base and does not stand securely. I emailed your support team on 7 September and attached two photographs showing the damage. I received an automated acknowledgment that day, but I have not received a further response as of 14 September. I would like a replacement lamp. If a replacement is unavailable, I would accept a refund. Please also tell me whether you need the damaged lamp returned and provide the relevant instructions. I have attached the order confirmation and the two photographs for reference. Please let me know by 21 September how you propose to resolve the problem. You can contact me at [email or phone]. Thank you for your help. Kind regards, [name].Repair the additions that make a letter unreliable
Imagine ChatGPT writes, 'Despite numerous calls and your repeated refusal to help, I demand compensation for the injury caused by your unsafe product.' Our sample facts do not contain calls, refusal, injury, or a compensation request. The sentence changes the story. Even if it sounds strong, it should not survive the fact check.
A focused correction is: 'Remove calls, refusal, injury, compensation, and any legal claims. The only earlier contact was the email on 7 September and an automated acknowledgment. Keep the observed cracked base, the replacement request, the refund alternative, and the request for return instructions. Do not add motives.' The corrected letter should match the sample above.
Also check smaller shifts. 'The product is unusable' may be fair in some cases, but our notes say it does not stand securely. 'Delivered late' needs a promised delivery date and the actual arrival date. 'Charged twice' needs two charges, not a pending payment and a completed one that might represent the same transaction. Accurate detail is more helpful than broad labels.
Use evidence without overwhelming the receiver
Send the evidence that shows the purchase and the fault. Name files clearly, such as order-confirmation.pdf and lamp-base-photo-1.jpg, if those are the actual files you attach. Mention the same names in your records so you can later identify what was submitted. Do not say you attached a receipt if you only pasted an order number.
A large collection of unrelated screenshots can hide the useful evidence. Select the relevant messages and retain their dates and context. If you crop a screenshot, keep enough information to show what it is. Preserve the originals in your own records. A short evidence list tells the reader why each item matters without retelling the whole complaint.
Before sharing, remove unrelated personal details from copies where appropriate. A bank statement may show other transactions and account information that the company does not need. The drafting chat may only need 'amount $48, date 2 September, reference EX-204.' The company receiving the complaint may need your actual reference, but ChatGPT usually does not need the full private record to improve the wording.
Check the channel's limits before finalizing attachments. A form may allow only a few files or a fixed amount of text. Ask for a shorter version that preserves the facts and request. Keep the full checked letter yourself, then submit the version the channel can accept.
Adjust the tone without weakening the request
The best tone depends on the problem and previous contact, but the facts should remain unchanged. For a first message, a friendly request may be enough. For a repeated unresolved issue, a firmer letter can state the prior dates, the lack of resolution, and the specific action now requested. Firm means clear and direct, not insulting.
Ask for tone changes with boundaries: 'Make this firmer by shortening the apology and stating the requested action clearly. Preserve all facts and do not add threats.' That is safer than 'make it more aggressive,' which gives little guidance about what can change.
If English is not your first language, ask for simple English that preserves names, dates, and amounts exactly. You can also compare the draft with your notes in your preferred language. Read the final version carefully for important distinctions: a requested refund, a promised refund, and a received refund describe three different states. A translation should not move your case from one to another.
Keep a record and write the next message from it
After sending, save the exact submitted wording, attachments, date, and any confirmation or case number. A saved draft is not proof of submission. If you use a web form, keep its confirmation where available. This simple record prevents confusion later about what the company received and when.
If there is no reply by your requested date, write a factual follow-up. In our example: 'I submitted a complaint on 14 September about order EX-204 and requested a response by 21 September. I have not received a response as of 22 September. Please confirm the current status and the next step.' Use this wording only if those later events actually happened. The original sample stops at drafting on 14 September.
If the company replies, compare its proposal with your request. A reply that asks for another photograph is not a replacement confirmation. A statement that a refund is being considered is not proof of payment. Ask ChatGPT to separate what has been agreed, what remains open, and what you need to do next using the actual message.
For further escalation, check the company's published complaint route and any relevant official guidance for your situation. Use your saved record to explain the unresolved point. The completed letter is useful because it leaves a clear trail of facts, requests, and responses, which makes the next step easier to choose.
Your next useful step
Keep the letter, attachments, submission receipt, and any reply together. If the problem continues, use that record to write a factual follow-up or follow the company's published complaint process.
Check the result before you use it
- Does every event in the letter have a date and match a record you hold?
- Does the letter distinguish observed damage, a reported statement, and an unproven suspicion?
- Is the requested remedy specific, with any alternative clearly marked?
- Are attachments actually present, relevant, and named correctly?
- Have private details, legal claims, and the submission channel been checked before sending?
Watch for: A formal-sounding rewrite may invent rights, deadlines, conversations, or accusations to make the complaint stronger. Those additions can weaken your real case. Firmness comes from clear evidence and a concrete request, not from words you cannot support.