Handling Customer Complaints: A Phone Script, Log and 10-Call Check

Every complaint call has to end with four things said out loud: the fix or next step, the name of the person who owns it, the clock time it will be done, and the customer's agreement. Without all four, the customer cannot hold you to the promise and you cannot check it.

A promise with no time cannot be late, so nobody catches it. A promise with no owner belongs to nobody.

As of November 2026, the Consumer Protection (E-Commerce) Rules, 2020 require an e-commerce entity's grievance officer to acknowledge a consumer complaint within 48 hours and redress it within one month from receipt (rule 4(5)). The rules cover marketplace sellers as well (Department of Consumer Affairs, Government of India).

Write down every promise made to the customer, be clear about what will happen at each stage and how long each stage should take, and contact the customer again within the agreed timeframe. Australian and UK public bodies give the same guidance, including acknowledging a complaint within two working days (Legal Ombudsman for England and Wales, as of November 2026; NSW Government).

A complaint call has five steps: let the customer finish, repeat the problem back, own the next step, offer one action with a clock time, and confirm before you close. Teach them in this order, because each step produces something the log needs.

Tone, greeting and hold rules are general call standards and are not repeated here.

Each of the four common complaints needs a line that holds an action, a time and an owner. Use these as starting wording and change the details to match your business.

Avoid these lines:

• "Calm down."
• "It is not our fault."
• "I will look into it." (no time)
• "Someone will call you." (no owner, no time)
• "Soon" or "today" with no clock time.

Promise a refund or replacement date only after you have checked you can meet it. A kept small promise does more than a missed large one.

Escalate when the fix needs a decision above the agent's limit, when the same customer is calling a second time about the same problem, when safety is involved, or when the caller is abusive. Use a warm transfer, where the agent stays on the line until the senior colleague has the details.

While the customer waits, tell them three things: who they are being passed to, that the colleague already has the order number and what happened, and what happens if the line drops. For example: "I am passing you to Meera, who can approve this. She has your order number and the problem, so you will not repeat it. If we are cut off, she will call you back by [time], within ten minutes of the line dropping." Our guide to warm transfer vs cold transfer covers the mechanics.

Log the escalation as a promise too, with the senior colleague as the owner.

A complaint log needs ten fixed columns, filled on the day the complaint arrives: date and time, caller, reference, issue, type, promise, due time, owner, status and customer confirmation. One row holds one promise; two promises means two rows.

The example row is illustrative.

Three rules keep it honest:

• The Due column holds a clock time, never "today".
• A row is not closed until the last column says Yes.
• A callback promised on a complaint is a task with a due time. The missed call callback workflow shows how to create one.

Records are what let you see patterns. The Small Business Development Corporation of Western Australia advises: "Keep records of all complaints in one central place or register. This will help you identify any trends or issues" (SBDC). The UK Financial Conduct Authority's review of non-deposit-taking mortgage lenders and mortgage third-party administrators (updated 29 August 2025) found that "weaknesses and failures in recording complaints may result in poor customer experiences and outcomes" (FCA).

Take the ten most recent logged complaint calls and score each Yes or No on seven checks: four from the recording, three from the log and call history. Count the Yes answers per check and fix the lowest check first.

A scorecard that only listens to the call can show what was said. It cannot show whether the promise was kept, which is why checks five to seven use the log and call history. This scorecard is our own template, not an official standard.

Did the customer finish before the agent spoke?

Pass: in the recording, the agent's first words come after the customer has described the problem. Fail: the agent cuts in before the problem is stated.

Did the agent repeat the problem back?

Pass: the agent restates the issue with at least one specific detail (order, date or item) and hears a yes. Fail: the agent goes straight to a fix.

Did the agent promise one action, a clock time and an owner?

Pass: all three are heard, such as "I will call you by 4 pm". Fail: any one is missing. "Soon", "today" and "someone will call" are fails.

Did the agent ask the customer to confirm?

Pass: the customer says yes or okay to the plan before the call ends. Fail: the call ends without it.

Is the promise in the log with the same due time?

Pass: a row dated the same day matches the recording on action, owner and due time. Fail: no row, or a different time.

Was the promise kept by the due time?

Pass: call history shows the outbound call, or the log shows the action Done, at or before the due time. Fail: it is late, or there is no record.

Did the customer hear that it was done?

Pass: the customer was contacted after the fix, was asked whether it is resolved, and the last column says Yes. Fail: the row is closed with no customer contact.

How do you read the tally?

Suppose the Yes counts out of 10 calls for checks one to seven are 9, 8, 6, 7, 5, 4 and 3 (invented numbers, to show the method). The agents listen and name the problem well, but only 3 customers heard that the fix was done. The next training is a callback and closing habit, not tone of voice.

Recordings, call history and call summaries are the evidence for checks one to seven. On our platform, every paid plan (Pro and Enterprise) includes call recording and call history, and the team shares one history for the business number.

Here is how we run the review:

Treat a summary as an index to the recording, not a verdict. AI Call Insights analyses recordings for objections, intent, competitor mentions, pricing, follow-ups and compliance flags. That gives you a second view over the same calls.

Tell callers the call is recorded. The wording and a test are in our call recording announcement guide.

As of November 2026, TalkEasy Pro is ₹999 + GST (Goods and Services Tax) a month with three hours of talktime a day, and extra talktime costs ₹49 + GST an hour. Enterprise is quote-only. Our Android app is on Google Play and needs Android 7.0 or later.

Four numbers from the complaint log are enough: complaints logged, repeat callers, on-time callbacks and promises with no clock time. Add nothing else until these are steady.

• Complaints logged: count the rows dated this week.
• Repeat callers: count the numbers that appear in two or more rows about the same issue within seven days. This is the mirror image of first call resolution.
• On-time callbacks (%): promises marked Done at or before their due time, divided by promises whose due time fell this week, times 100. Example with invented numbers: 12 promises due, 9 done on time, 9 ÷ 12 × 100 = 75%.
• Promises with no clock time: rows where Due is blank or says "today" or "soon". The target is zero.

If repeat callers rise while on-time callbacks fall, the missed promises are what is driving the repeat calls.