Handling Customer Complaints on the Phone: A 5-Step Framework

A complaint call is rarely about the thing the customer says first. The late parcel, the wrong invoice or the broken feature is the trigger. What the customer wants to know is whether someone will take it seriously and do something about it. The way you handle the first minute of the call usually decides whether the rest is a conversation or a fight.

This guide gives you a five-step framework you can learn, say out loud and rehearse before the next difficult call. It is written for customer service, support and account teams. It is not legal advice, and your own company policy always comes first.

Complaint or angry caller?

The two overlap, but they need different tools. An angry caller needs the temperature brought down before anything else works. A complaint caller may be perfectly calm and still have a serious problem. Someone can write a polite, precise complaint and be more dissatisfied than a person who shouts. This article is about the structure of the whole call, from "hello" to "is there anything else". If the caller is already shouting, start with the de-escalation phrases and come back to this structure once the volume drops.

The five steps

Step 1: Let them finish

The most common mistake is jumping in with a solution while the customer is still explaining. It feels efficient, but the customer hears "you are not listening". Let them get to the end of their account. Stay quiet, and use short sounds that show you are there ("I see", "mm-hm").

While they talk, take notes on three things: what happened, when, and what they have already tried. You will need these later, and the customer will notice that you are writing.

Step 2: Acknowledge before you explain

Acknowledging is not agreeing that your company is at fault, and it is not an apology for something you cannot yet confirm. It is a sentence that shows you understood the impact.

• "That sounds really frustrating, especially after you already called once."
• "I can see why you are annoyed. You were told one thing and got another."
• "Thank you for explaining that clearly. Let me make sure I have it right."

Keep it to one or two sentences. Long apologies sound scripted. If a mistake is clearly on your side, say so plainly: "That should not have happened, and I am sorry."

Step 3: Clarify with open questions

Now ask the questions that fill the gaps. Use open questions first, then close with a precise one.

• "Can you walk me through what happened when you placed the order?"
• "What would a good result look like for you?"
• "Just to confirm, the order number ends in 4471, and it arrived on Tuesday?"

The second question matters most. Asking what the customer expects stops you from solving the wrong problem, and often the expectation is smaller than you feared. Sometimes it is larger, and then it is better to know now.

Step 4: Offer a fix, or a clear next step

Give the customer something concrete. Where possible, offer a choice of two, because a choice returns a little control to someone who feels they had none.

• "I can send a replacement today, or refund the item. Which would you prefer?"
• "I cannot approve that refund myself, but I can escalate it to my team lead today and you will hear back by Thursday noon."

If you cannot offer what the customer asks for, say what you can do instead, and say it before you say what you cannot. "What I can do is..." is a stronger opening than "Unfortunately we can't...". Only promise what you control. A promised call-back that does not happen turns one complaint into two.

Step 5: Confirm and close

Repeat the agreement in one sentence, name who does what and by when, and check whether anything else is open.

• "So I will send the replacement today, you will get a tracking email within two hours, and I will call you on Friday if it has not arrived. Is that right?"
• "Is there anything else I can help with while we are on the call?"

Then write the case notes while it is fresh. The next person who talks to this customer should not have to start from zero.

Phrases that make complaint calls worse

Some phrases reliably raise the temperature. They are worth replacing before you are on a live call.

• "Calm down." Replace with: "I want to get this sorted for you."
• "That's our policy." Replace with: "Here is what the policy allows, and here is what I can do within it."
• "You should have..." Replace with: "Let's see what we can do from here."
• "I understand." on its own. Replace with a sentence that shows what you understood.
• "As I said before..." Replace with the answer, said again, kindly.

Common mistakes in the framework

Skipping step 1. The solution may be right and still land badly because the customer has not been heard yet.

Rushing from step 2 to step 4. Without clarifying, you can fix the wrong thing quickly. Take the extra thirty seconds to ask.

Over-promising in step 4. A realistic "by Friday" is better than an optimistic "today" that you cannot guarantee.

Forgetting step 5. Without a recap, both sides leave with different memories of what was agreed.

Practising the framework

Reading a framework is not the same as using it. Under pressure, people drop the steps that feel unnatural, usually step 2 and step 5. A few ways to practise:

1. Write your own acknowledgement lines. Prepare five short sentences you would be comfortable saying, in your own words. Say them aloud.
2. Pair up with a colleague and role-play three scenarios: a late delivery, a billing mistake and a broken promise. Rotate the roles and give each other one specific piece of feedback.
3. Rehearse alone with an AI customer. In DIRI AI you hold a voice call with an AI customer who plays the complaining caller, in a prepared situation, and afterwards you read a report on specific moments. You can see what these reports contain on the how we score page, and the sample dialogues show what a call looks like. Practice is private and repeatable, so you can try the same call three times with a different acknowledgement each time.

If you lead a team, the customer service phone training guide shows how to plan regular practice across agents, and AI training for call center agents covers what to look for in a tool.

A short checklist to keep next to the phone

• Did I let the customer finish?
• Did I say one sentence that shows I understood?
• Did I ask what a good result looks like?
• Did I offer a fix or a specific next step, with a time?
• Did I recap and ask if anything else is open?

Related: How to Handle a Refund Request Call (With Script), How to Handle an Angry Caller on the Phone, Phone Etiquette for Customer Service Teams, The LAER objection handling framework.

Related situation: Complaints by phone

FAQ

How long should a complaint call take?

There is no fixed length. A clear complaint with a simple fix can take a few minutes. The aim is to finish with the issue resolved or with a dated next step, not to hit a time target.

Should I always apologise?

Apologise when your side made a mistake or when the customer had a poor experience, and keep it short and sincere. Avoid apologising for things you cannot yet confirm.

What if I cannot give the customer what they ask for?

Say what you can do first, explain the reason in one sentence, and offer the best alternative or an escalation with a date. Never promise something outside your authority.

How can I get better at complaint calls without practising on real customers?

Rehearse the five steps out loud, role-play with a colleague, or hold voice calls with an AI customer in private.

Ready to rehearse your next complaint call? DIRI AI has a Free plan with 3 voice calls a month of up to five minutes each, no card needed. Start free and choose a complaint scenario.