To complain politely in English, describe the checkable problem, explain its real impact, ask for the next action, and name a reasonable remedy. Keep blame out of the opening. If the first person cannot solve it, repeat the facts, ask who can review the issue, and move to a written process without threats.

You can be completely right and still make your complaint weirdly difficult to solve.

“This is ridiculous. Your company has ruined everything. Do something.”

The anger may be real. The action is missing. What exactly happened? What did it affect? What should the listener do now? What outcome would close the issue?

When you need to make a complaint, maximum fury is not a strategy. It is a short route from problem to repair. This guide gives you that route—and the English to use on both sides of the exchange.

P — Problem

State what happened in terms another person can check.

I — Impact

Name the real cost, delay, confusion, risk, or blocked task.

R — Request

Ask for the next useful action: check, explain, contact, confirm, or review.

R — Remedy

Say what fair outcome would resolve the matter.

Problem-impact-request-remedy

The PIRR method turns a complaint into four jobs: identify the problem, show why it matters, ask for action, and define a workable remedy.

Build one complaint that the listener can investigate and answer
Part Question it answers Wrong-bill example Common failure
Problem What observable thing went wrong? “The bill includes two coffees we did not order.” Replacing facts with “Your service is terrible.”
Impact What did the problem change or prevent? “That adds eight pounds to the total.” Using only emotion: “I’m furious.”
Request What should happen next? “Could you check the order record?” Demanding an outcome before anyone can verify the issue.
Remedy What result would close the complaint? “A corrected bill would solve it.” Saying “Make it right” without defining right.

Hear the whole exchange

Customer: “Excuse me, the bill includes two coffees we did not order. That adds eight pounds to the total. Could you check the order record? A corrected bill would solve it.”

Server: “I’m sorry about that. I can see the extra items. I’ll remove them and bring the corrected bill now.”

Customer: “Thank you.”

Notice how little drama the exchange needs. The customer does not try to prove they are the better person. The server does not write a memoir about the till. They identify the mismatch, fix it, and return to their lives.

Request and remedy are not the same thing

The request is the next action. The remedy is the result you want.

  • Request: “Could you review the tracking history?”
  • Remedy: “I’d like a confirmed delivery date, or a refund if the order cannot be delivered this week.”

This distinction keeps your complaint flexible. The first employee may be able to investigate but not authorise a refund. Ask them to do the part they own, then identify who owns the remedy.

Official complaint-writing guidance follows a similar practical shape: focus on the important facts, say what went wrong, and state what you want to happen now.1 For a short email, putting the problem first, adding only useful detail, and ending with the hoped-for action also keeps the message clear.2

Start neutral and specific

Start with evidence, not a verdict. Your opening should make the problem easier to verify, not force the listener to defend their personality, team, company, bloodline, and entire industry.

Use the Camera Test

Ask: What would a camera, receipt, timestamp, message, contract, or neutral witness show?

Blame-heavy

“You people are always trying to overcharge customers.”

Fact-based

“The receipt shows the same item twice, but I received one.”

The second version is not weak. It is stronger because it gives the listener something checkable.

Move from character judgments to observable problems
Situation Blame-heavy opening Fact-based opening Useful receiver reply
Wrong bill “You’re cheating me.” “This item appears twice on the bill, but we ordered it once.” “Let me compare the bill with the order record.”
Delay “Your delivery team is useless.” “The order was due Tuesday, and the tracking has not changed since Monday.” “I’ll check the latest scan and whether the carrier has opened an exception.”
Noisy apartment “You have no respect for anyone.” “The bass has been coming through the bedroom wall after eleven for the last three nights.” “I didn’t realise it was carrying that far. We’ll move the speaker and lower it.”
Missed handoff “You never do your job properly.” “The client file was due to the support team at ten, and it has not arrived.” “You’re right—the handoff was missed. I’ll send the file now and confirm the owner for the follow-up.”

Neutral openers that still sound human

  • “I’m calling about a problem with order 1842.”
  • “I think there may be an error on this bill.”
  • “I need to raise an issue with yesterday’s handoff.”
  • “The delivery date has passed, and I have not received an update.”
  • “There’s been loud music after eleven, and the sound is reaching our bedroom.”

I think there may be is useful when you are not yet certain. Once the evidence is clear, plain statements are fine: “The same charge appears twice.” You do not need to turn clear evidence into a vague maybe.

Do not exaggerate to make the complaint “stronger”

Avoid inventing dates, damage, promises, witnesses, medical effects, legal rights, or previous contacts. Do not turn “twice” into “every time,” or “late by one day” into “you completely ruined my life.” Exaggeration gives the other side a new argument and can damage your credibility.

A study of complaint responses from 50 Indonesian learners of English found examples involving insults, swearing, direct personal criticism, and threats; the researchers also found that status and social distance affected the responses.9 The study used imagined oral scenarios in one learner population, so it does not describe all learners or all real conversations. Its useful classroom lesson is narrower: learners need models for complaints that are direct about the problem without attacking the person.

Complaints in shops, services, housing, and work

The framework stays; the context changes. The PIRR order remains stable, but the evidence, relationship, risk, and realistic remedy change with the setting.

Four settings, four complete complaint-and-response exchanges
Setting Complaint using PIRR Useful reply Boundary to notice
Shop: wrong bill “This receipt charges me for three cables, but I bought two. That adds twelve euros. Could you check the transaction? I’d like the extra charge removed.” “I’m sorry about the error. I’ll check the till record and process the correction if it matches.” The employee may need evidence or manager approval before refunding.
Service: delay “The technician was booked for nine to eleven, and no one has arrived or called. I have missed a morning of work. Could you contact the dispatch team? I need a confirmed arrival time today or a new appointment I can rely on.” “I’m sorry you were left without an update. I’ll contact dispatch now and return within ten minutes with either an arrival time or rebooking options.” A real time for the next update may be more useful than another vague promise.
Housing: noisy apartment “The bass has been coming through the bedroom wall after eleven for three nights, and it is waking my child. Could you lower it after eleven and move the speaker away from this wall? That would resolve it for us.” “Sorry—we did not know it was reaching the bedroom. We’ll move the speaker and keep the volume down after eleven.” Do not confront someone who seems aggressive or unsafe. Leave and use building management, security, or another appropriate local channel.
Work: missed handoff “The client notes were due to support at ten, and the team still cannot access them. That is blocking the promised callback. Could you send the notes by eleven and confirm who owns the callback? We need the customer contacted before noon.” “I missed the handoff. I’ll upload the notes by ten forty-five and message support with the owner and callback time.” Focus first on restoring the work. A repeated work problem may need a separate manager or HR process.

Shops: bring the transaction, not your entire consumer biography

Useful details include the item, date, receipt, order number, amount, defect, and what was promised. The US Federal Trade Commission’s sample complaint guidance similarly recommends giving the essential transaction details, explaining the problem, and stating the resolution wanted while remaining polite and reasonable.3

Services: ask for ownership and an update time

When several teams are involved, “Someone will call you” is not a plan. Ask:

  • “Who is checking this?”
  • “What is the next step?”
  • “When should I expect an update?”
  • “What should I do if I have not heard by then?”

Housing: solve the behaviour without escalating the danger

Make the time, frequency, location, and impact specific. Request a practical change. But language skill is not a reason to enter an unsafe confrontation. If the person is threatening, intoxicated, violent, or already escalating, create distance and use an appropriate building, emergency, or official channel for your location.

Work: repair the operation before prosecuting the person

In an urgent handoff failure, establish the missing item, blocked task, new deadline, and owner. Later, if the pattern is repeated or serious, document it through the organisation’s process. UK workplace guidance from Acas recommends that a formal grievance (official workplace complaint) state what it concerns, include relevant evidence, and say what action the employee wants, while keeping the requested outcome specific and realistic.8 That is UK guidance, not a universal statement of workplace rights.

Ask for a solution

Name the repair. “I want a solution” is emotionally understandable and practically useless. Choose a remedy that is connected to the problem and fair for the size of the impact.

Choose the smallest remedy that would genuinely close the issue
Remedy job Useful phrase Good fit Watch out for
Check “Could you review the order record?” You suspect an error but need confirmation. Do not present uncertainty as proven misconduct.
Explain “Could you explain what this fee covers?” The charge or decision may be valid but unclear. An explanation is not automatically a correction.
Correct “I’d like the duplicate charge removed.” The record contains a clear error. Say which charge, amount, or line needs correction.
Replace or repair “Would you replace the faulty unit, or repair it by Friday?” A product or service has not met the agreed condition. Availability, policy, warranty, and local law may affect the options.
Refund “If the order cannot be delivered this week, I’d like a refund.” The promised service cannot be completed within a useful time. A refund is not always owed; rights and terms vary.
Rebook “Please offer a new appointment with a confirmed window.” A missed or delayed appointment still needs to happen. A new date without ownership or confirmation may repeat the problem.
Confirm “Could you confirm the decision and next step in writing?” The issue is complex, repeated, or moving between teams. Do not ask for a giant report when one clear confirmation will do.
Stop it happening again “Could you explain what will change before the next handoff?” The immediate problem is fixed but likely to repeat. Avoid demanding punishment when a process repair is the real goal.

Exact remedy or remedy range?

Use an exact remedy when the correction is obvious:

“The same item was charged twice. I’d like the duplicate charge removed.”

Use a remedy range when more than one outcome would work:

“I need the equipment before Monday. A replacement by Friday would work; otherwise, I’d like a refund so I can buy it elsewhere.”

A range gives the listener room to solve the actual problem without making you repeat the entire complaint. It is flexibility, not surrender.

Make the remedy fair

A useful remedy answers three tests:

  1. Connection: Does it repair the actual problem?
  2. Scale: Is it fair for the size of the impact?
  3. Authority: Can this person approve it, or can they identify who can?

“Fire the cashier” is usually not a proportional remedy for one till error. “Remove the incorrect charge and review why it happened” is closer to the problem. The FTC likewise advises complainants to state exactly what they want done and keep the request reasonable.4

Useful solution phrases

  • “What can you do to resolve this today?”
  • “The outcome I’m looking for is…”
  • “A replacement would solve the immediate problem.”
  • “Would either a Friday delivery or a refund be possible?”
  • “Who can authorise that remedy?”
  • “If that option is not available, what can you offer instead?”

Escalate without threats

Calm escalation means changing the level, owner, or channel of the complaint—not adding more threat to your voice.

1. Restate

Repeat the problem, impact, and unresolved remedy in one short version.

2. Reassign

Ask who has the authority, information, or responsibility to review it.

3. Record

Ask for a reference number, written confirmation, next step, and response time.

4. Redirect

Use the organisation’s formal process or an appropriate external channel when necessary.

Step 1: Restate without restarting the entire saga

“The delivery was due Tuesday, and I still have no date. I need the equipment for Monday’s event. If delivery by Friday cannot be confirmed, I’m asking for a refund.”

New listener, same clean complaint. Do not punish the second person with the full director’s cut.

Step 2: Ask for the right owner

  • “I understand you cannot approve that. Who can review it?”
  • “Could you transfer me to the person responsible for billing corrections?”
  • “Is there a supervisor or complaints team that can examine the evidence?”
  • “Who owns the next update from here?”

Step 3: Turn fog into a process

  • “Could I have the complaint reference number?”
  • “Please confirm what will happen next.”
  • “When should I expect a response?”
  • “If I do not receive one by Friday, which channel should I use?”

Complaint-handling guidance from the Parliamentary and Health Service Ombudsman emphasises acknowledging the complaint, clarifying the issues, understanding the impact and desired outcome, and explaining the process and likely timescales.6 Its formal standards are for particular UK public services, but the communication principle transfers: people need to know what is being investigated, by whom, and when they will hear again.

Pressure vs process

Escalate the route, not the aggression
Threat or unsafe pressure Process-based alternative
“Refund me now or I’ll destroy your business online.” “If a refund cannot be reviewed here, please give me the formal complaint route and response time.”
“You’ll regret this.” “I’m going to document the issue and use the next available review channel.”
“I know people who can make trouble for you.” “Who is authorised to make a final decision on this complaint?”
“I’ll stand here and shout until you fix it.” “This conversation is not resolving the issue. Please give me the written process or a manager’s contact details.”

Do not threaten violence, harassment, false reviews, false reports, exposure of private information, or legal consequences you cannot honestly support. Do not pretend to hold a role, authority, or personal circumstance that is not true to gain an unfair advantage. If an interaction becomes unsafe, leave rather than trying to win the scene.

The FTC’s complaint-letter guidance specifically advises against angry, sarcastic, or threatening language and recommends a clear record, relevant document copies, a reasonable requested action, and a response period.4 The exact consumer routes and rights in that guidance are US-specific.

Respond when you receive a complaint

Answer with ownership, not defence. A good response does four jobs: acknowledge the complaint, clarify what needs checking, own the next action, and confirm the remedy or update time.

Acknowledge

Show that you heard the issue and impact.

Clarify

Check facts, evidence, desired outcome, and any missing detail.

Act

State what you can do now and who owns anything else.

Confirm

Give the remedy, next update, reference, or closure.

Acknowledging is not the same as accepting every allegation (claim that is not yet proven)

You can recognise the experience before you finish checking the facts:

  • “I can see why the unexplained delay is frustrating.”
  • “I understand that the missed handoff blocked the customer callback.”
  • “Thank you for showing me the duplicate charge.”
  • “I’m sorry you were left without an update.”

Then be honest about what you still need to check:

“I cannot confirm yet why the charge appeared, but I can review the transaction and update you within fifteen minutes.”

British Council guidance for written complaint responses recommends acknowledging the complaint, focusing on facts rather than excuses or blame, apologising where appropriate, explaining the action, and offering a solution or compensation when suitable.7

Agent replies for the four core cases

Answer the issue, not only the emotion
Complaint Weak reply Useful reply
Wrong bill “That’s impossible. Our system is accurate.” “Thank you for pointing it out. I’ll compare the receipt with the order and correct it if the item was duplicated.”
Delay “It should arrive soon.” “I’m sorry there has been no update. I’ll contact dispatch and return by two thirty with a confirmed date or your cancellation options.”
Noisy apartment “Calm down. It’s not that loud.” “I understand the bass is reaching the bedroom after eleven. We’ll move the speaker now and keep the volume down tonight.”
Missed handoff “I’ve been busy. It’s not only my fault.” “The handoff was missed, and support is blocked. I’ll upload the notes by ten forty-five and confirm the callback owner in the team channel.”

Do not promise what you do not control

Bad promise:

“I guarantee the refund will be in your account today.”

Honest ownership:

“I can submit the refund today. Finance normally confirms it within two business days, and I’ll send you the reference as soon as it is accepted.”

That answer separates your action from another team’s timeline. It is less impressive for three seconds and much more trustworthy tomorrow.

Broader complaint-handling guidance likewise stresses listening carefully, confirming the concern and outcome sought, managing expectations, and explaining the next step and timescale.5 The source is for UK public-service organisations, so this article uses only its communication principles—not its procedure as a worldwide rule.

Written vs spoken complaint

Choose the channel by complexity. Speak when the problem is simple and fixable now. Write when the issue is complex, repeated, based on disputed facts (facts people disagree about), evidence-heavy, or moving through a formal process.

Choose the channel that gives the problem the right amount of structure
Channel Best for Language shape Risk
Spoken A wrong bill, missing item, noise, simple delay, or fix available in real time Short PIRR line, one clarification, one remedy The details or promise may be forgotten or misunderstood.
Written A repeated failure, formal workplace complaint, facts people disagree about, attachments, money, safety, or unresolved escalation Subject/reference, dated facts, impact, evidence, requested action, remedy, response date A long emotional message can bury the actual complaint.
Speak, then confirm in writing A useful conversation produced an agreement that matters “Thank you for speaking with me. To confirm, you will…” The written note can become argumentative if you reopen settled points.

A compact written complaint

Subject: Complaint about [order, service, address, or handoff reference]

Problem: On [date/time], [observable event happened].

Impact: This caused [specific cost, delay, blocked task, risk, or inconvenience].

Evidence: I have attached [receipt, screenshot, message, photo, or record], where relevant and safe.

Request: Please [check, explain, correct, contact, investigate, or confirm].

Remedy: I am asking for [reasonable outcome].

Next step: Please confirm by [date] who is handling this and when I should expect a response.

Keep original documents unless the relevant official process requires otherwise; send copies when appropriate. Remove unrelated private information before sharing evidence. Do not secretly record a conversation or publish personal data unless you have checked the applicable rules.

Written does not mean inflated

Inflated

“I hereby wish to bring to your esteemed attention the profoundly unacceptable circumstances pertaining to the aforementioned transaction.”

Clear

“I’m writing about a duplicate charge on invoice 1842.”

Formal writing needs structure, not a powdered wig. British Council complaint-letter guidance recommends concentrating on important facts and including the reason for writing, what went wrong, and what should happen now.1

Confirm a spoken agreement

Subject: Confirmation of today’s call — order 1842

Thank you for speaking with me today. To confirm, you will remove the duplicate charge and email the corrected invoice by Thursday. If I have misunderstood any part of that agreement, please let me know.

The final sentence is a clarification move, not a new complaint. That is where the live clarification guide earns its keep: confirm the shared understanding before another failure is born.

Practice cases

Practise both roles. Do not memorise a giant complaint script. Build one PIRR exchange, switch roles, then repeat after the first remedy is unavailable.

Wrong bill: correct the charge without accusing the staff

Speak before revealing the model. Your restaurant bill includes two desserts, but your table ordered one. The extra charge is seven euros.

Customer: “Excuse me, the bill includes two desserts, but we ordered one. That adds seven euros. Could you check the order? I’d like the extra charge removed.”

Server: “I’m sorry about that. I’ll compare it with the order record and bring a corrected bill.”

Customer: “Thank you.”

Second round: The server cannot change the bill personally.

Server: “Only the shift manager can remove an item.”

Customer: “Understood. Could you ask the shift manager to review it?”

Delay: ask for a real update, not “soon”

Speak before revealing the model. A technician was booked for nine to eleven. It is twelve thirty, nobody arrived, and you missed work.

Customer: “The technician was booked for nine to eleven, and no one has arrived or contacted me. I have missed a morning of work. Could you check with dispatch? I need a confirmed arrival time today or a reliable new appointment.”

Agent: “I’m sorry you were left without an update. I’ll contact dispatch now and call you within ten minutes with the available options.”

Customer: “Thank you. I’ll expect the call by twelve forty.”

Second round: The agent says only, “They should be there soon.”

Customer: “I still do not have a confirmed time. Who can check the schedule and give me one?”

Noisy apartment: make the boundary specific and keep it safe

Speak before revealing the model. Bass has reached your child’s bedroom after eleven for three nights. The neighbour appears calm and it is safe to speak.

Neighbour: “Hi. The bass has been coming through the bedroom wall after eleven for the last three nights, and it is waking my child. Could you lower it after eleven and move the speaker away from this wall? That would solve it for us.”

Resident: “Sorry—we did not realise. We’ll move it and keep the music down.”

Neighbour: “Thanks, I appreciate it.”

Safety variation: The resident becomes aggressive.

Neighbour: “I’m ending this conversation now.”

Leave. Do not keep practising your English on an unsafe person. Use the appropriate building or official channel for the situation.

Missed handoff: restore the work before discussing the pattern

Speak before revealing the model. A colleague was meant to send client notes to support at ten. At ten thirty, the notes are missing and the promised callback is blocked.

Colleague: “The client notes were due to support at ten, and the team still cannot access them. That is blocking the callback. Could you upload them by eleven and confirm who owns the call? We need the customer contacted before noon.”

Receiver: “I missed the handoff. I’ll upload the notes by ten forty-five and confirm the callback owner in the team channel.”

Colleague: “Thanks. Please tag me when both are confirmed.”

Second round: This is the third missed handoff.

Colleague: “The immediate callback is now covered. Because this is the third missed handoff this month, I’d like us to review the process with our manager after today’s issue is closed.”

Receive the complaint: acknowledge, clarify, act, confirm

Speak before revealing the model. A customer says a delivery due Tuesday has not arrived and they need it for Monday.

Customer: “The order was due Tuesday, and the tracking has not moved since Monday. I need it for an event next Monday. Could you check what happened? I need delivery confirmed by Friday or a refund.”

Agent: “I’m sorry you have had no update. Let me confirm the order number and delivery postcode. I’ll contact the carrier, then return within fifteen minutes with either a Friday delivery confirmation or the refund-review process.”

Customer: “The order is 1842. Thank you.”

The Complaint Repair Score

Give yourself one point for each box. A six-point complaint is ready to use; a three-point complaint probably still contains smoke but no fire exit.

Can the listener solve or route your complaint?

Practise one complaint/remedy exchange. Open the speaking-practice chooser and select the path that best fits your blocker. Create one complaint scene, speak the PIRR line, answer as the receiver, then repeat after the first remedy is unavailable and escalate through the process—not through threats.

Practise one complaint/remedy exchange

The linked page is a general speaking-practice chooser. It does not open this complaint lesson preloaded, automatically record the exchange, verify your evidence, determine your legal rights, or score politeness, safety, escalation, or remedy quality. You create the scene and judge the second attempt with the six-point score.10

A useful complaint does not hide the problem to sound nice. It makes the problem hard to misunderstand and the next step easy to act on.