To handle customer complaints well, work through seven steps in order, from acknowledging the issue to logging its root cause. The exact words an agent uses at each step decide whether a frustrated customer calms down or escalates, so each step below includes ready-to-use phrasing for every channel. Those steps also work as a QA scorecard for the whole team.
Why the words matter as much as the process
A complaint process works only when agents have the right words ready before the conversation starts. According to Zendesk’s retention guide, 85% of CX leaders say customers will leave after a single unresolved issue, so a structured process is one of the most direct ways to improve CSAT. Improvising under pressure tends to produce vague promises and scripted-sounding empathy, which is where the steps below help.
Support teams that work in English as a second language need the phrasing as much as the process. In Talaera’s coaching-session analysis, customer communication was the top focus for 63% of the 679 support learners included, a directional figure. Talaera teaches a three-part shorthand for difficult customer conversations (Acknowledge, Act, Confirm), and the seven steps below cover the same ground before adding follow-up and root-cause logging.
Step 1: Restate the issue before you try to fix anything
Acknowledging a complaint means restating what the customer told you before you try to fix it. The customer should finish speaking (or finish their message) before the agent paraphrases the specific issue and names the emotion they hear. Active listening, which means restating what you heard so the customer knows it landed, shows that you absorbed the problem instead of waiting for your turn to talk.
| Avoid | Say instead | Why it works |
|---|---|---|
| “I understand.” | “Thank you for letting us know about this. I can see how [specific issue] would be frustrating.” | Naming the specific issue keeps the reply from sounding scripted or dismissive. |
| “Calm down.” | “I hear you. The [specific problem] isn’t the experience you should be having, and I want to make sure we get this right.” | Validating the reaction lowers the temperature, while “Calm down” can escalate it. |
A paraphrase has two jobs. It proves the agent listened, and it gives the customer a chance to correct a misunderstanding before the team solves the wrong problem.
A paraphrase can be as direct as “So what happened is [paraphrase their issue]. I’d be frustrated too.” One support agent in the Philippines said they can now “effectively make sounds that show I am listening,” which is the audible side of active listening. For a deeper bank of phrases, see Talaera’s list of empathy statements.
Step 2: Ask open questions to get the full picture
Asking open questions before proposing a fix prevents the team from solving the wrong problem. Open-ended questions give the customer room to share context that a yes-or-no question would miss, and they save the follow-up contacts that missing information creates.
| Ask | What it uncovers |
|---|---|
| “Could you walk me through what happened after [X]?” | The sequence of events |
| “What were you expecting to see at that point?” | Expectation versus reality |
| “So I can look into this properly, could you share your order or account number?” | The identifiers needed for a lookup |
| “When did you first notice the issue?” | The timeline |
Together these questions build a complete picture without making the customer repeat themselves. Blaming phrasing does the opposite, because a line like “You should have contacted us sooner” shifts fault onto the customer and undoes the trust built in Step 1. Agents who practice empathic listening keep the focus on understanding instead of judging.
Step 3: Apologize for the experience and own what happens next
A genuine apology names the specific impact on the customer rather than the abstract situation. Owning the experience means accepting accountability for making it right, even while the root cause is still under investigation, and it doesn’t require admitting legal fault. The weight of the apology should match the severity of the issue, and these phrases give agents a starting point to adapt.
- Minor inconvenience: “I’m sorry for the confusion with your invoice. That shouldn’t have happened.”
- Moderate disruption: “I apologize for the delay in processing your order. I understand this affected your timeline, and I take full responsibility for getting this resolved.”
- Significant failure: “I sincerely apologize for the service outage and the impact it’s had on your operations. You have every right to expect better, and I’m personally going to see this through.”
Two phrases can undo an apology. “I’m sorry you feel that way” puts the problem back on the customer’s emotions, and “That’s not our department” signals blame-shifting and forces the customer to restart the complaint elsewhere. Apology norms also differ across cultures, so global teams should review guidance on apologizing across cultures before standardizing scripts.
Step 4: Offer a specific fix with a time attached
Vague promises such as “we’ll look into it” leave the customer guessing and generate contacts that could have been avoided. A good proposal names a specific action and a time, then checks that the customer accepts it.
| Say | What it does |
|---|---|
| “Here’s what I can do for you right now. I’m going to [specific action], and you’ll see that reflected by [day/time].” | Names the action and the deadline together. |
| “I want to make sure we get this right, so I’m going to [action] and follow up with you by [time].” | Commits the agent to a second touchpoint. |
| “I have two options I can offer. [Option A] or [Option B]. Which works better for you?” | Gives the customer a choice, which builds agreement. |
Phrases such as “We’ll get back to you as soon as we can” and “Someone will be in touch” do the opposite, because they give the customer nothing to hold the team to. A realistic deadline builds trust, since a customer told “by Thursday” who hears back on Wednesday remembers the early finish, while one promised “today” who hears nothing remembers the miss. One customer support agent in the Philippines said they now focus on “being clear and timely, since I’ve learned that American clients value transparency and quick resolutions.”
When an issue falls outside an agent’s authority, escalation language matters both externally and internally. Externally, the agent can say, “Let me bring in [name or role] who can authorize this for you. I’ll stay on this until it’s resolved.” Internally, the receiving colleague needs a factual summary of the issue and what has been tried, plus exactly what the customer has been told so far, which spares the customer from repeating themselves. For hostile interactions, agents can use Talaera’s guide to handling difficult customers for de-escalation phrasing.
Step 5: Confirm the customer agrees the issue is resolved
Before marking a complaint resolved, the agent asks the customer directly whether the outcome meets their needs. Silence doesn’t equal satisfaction, and skipping this check is one way resolved complaints quietly become repeat complaints or churn risks.
| Say | What it does |
|---|---|
| “Does that fully resolve this for you, or is there anything else I can help with?” | Asks for an explicit yes or no. |
| “I want to make sure this works on your end. Can you confirm the issue is resolved?” | Checks the result from the customer’s side. |
| “Before I close this out, is there anything we’ve missed?” | Gives the customer a last chance to flag a gap. |
Resolved versus closed: A closed ticket means the team has finished its work. A resolved complaint means the customer agrees the problem is fixed.
Each phrase puts the decision in the customer’s hands and gives them an explicit opening to flag gaps the team would otherwise never hear about.
Step 6: Follow up within 24 to 48 hours
A short follow-up message 24 to 48 hours after resolution shows the customer that your team cares how the issue ended. It is easy to skip this step because the problem feels done, which leaves the one proactive touchpoint unused. Sending it on the channel the customer used keeps the message where they already expect it.
The template below works as a starting point for email, and the same wording shortens well for chat.
Subject line: Checking in on your [product/service] experience
Hi [Name],
I wanted to follow up on the [brief issue description] we resolved on [date]. Everything should be working as expected now. If anything still feels off, or if you have more feedback, I’m happy to help. Thank you for your patience while we worked through this.
Best regards,
[Agent name]
A message this short also gives any customer with a lingering doubt an easy way to reopen the conversation, which is the point of sending it.
Step 7: Log the root cause so the same complaint doesn’t return
Logging the root cause turns each resolved complaint into data that can prevent future complaints, but only if the team captures it the same way every time. Tagging complaints by category turns individual tickets into a pattern map for product and ops teams. Reviewing the log monthly shows which categories are growing and where an upstream fix would cut complaint volume.
A four-category taxonomy keeps tagging fast enough for agents to do in real time.
- Process: Workflow or policy gaps, such as a customer who received no shipping confirmation or was transferred between three departments.
- Product: Defects or missing features, such as a broken integration or a report that won’t export.
- People: Agent errors or training gaps, such as incorrect information given on a previous call.
- Policy: Terms the customer finds unfair, such as a refund window they consider too short or an SLA exclusion they weren’t aware of.
Pairing each category with the same seven log fields keeps the data consistent across agents and channels.
| Log field | What to record |
|---|---|
| Date | When the complaint was received |
| Channel | Which channel the customer used |
| Root-cause category | Process, Product, People or Policy |
| Sub-category | The specifics, such as “no shipping confirmation” |
| Resolution applied | What the agent did to fix it |
| Time to resolve | Hours or days from first contact to confirmation |
| Customer sentiment at close | A rating on a three-point scale |
Root-cause logging is a training tool as well as a reporting function. Complaints that cluster under People point to a coaching gap, and complaints that cluster under Process point to an ops fix.
How the steps change on phone, email and chat
The seven steps work on every channel. Wording and pacing change with the medium. Phone calls allow warmer, more conversational language. Email demands structure and completeness in a single send, while chat favors short sentences and faster turns.
| Moment | Phone | Chat | |
|---|---|---|---|
| Acknowledgment | “Thank you for calling about this. I can hear this has been frustrating, and I want to help.” | “Thank you for reaching out. I understand this issue has affected your workflow, and I’m looking into it now.” | “Got it, thanks for flagging this. I’m on it.” |
| Apology | “I’m sorry you’ve had to deal with this. That’s not the experience we want for you.” | “I apologize for the inconvenience this has caused your team. This falls short of what you should expect from us.” | “Sorry about that. Let me fix this for you.” |
| Proposal | “Here’s what I’d like to do. I’ll [action] and have it resolved by [time]. Does that work for you?” | “To resolve this, I will [action]. You can expect [outcome] by [date]. Please let me know if you’d prefer a different approach.” | “I can [action] right now. Should take about [time]. Sound good?” |
| Follow-up | Call back within 24 to 48 hours to confirm. | Send a short check-in 24 to 48 hours after resolution. | Send a short chat message or email 24 to 48 hours later. |
Agents can keep this table open during live interactions as a channel reference, and the phone column serves as a starter phrasebook they can adapt to their own voice.
The seven steps double as a QA scorecard and role-play kit
The seven-step lifecycle works as a ready-made QA scorecard, because each step becomes an observable scoring criterion in call and ticket reviews. Scoring against concrete behaviors can make coaching conversations faster and fairer across the team.
| Step | What the reviewer checks |
|---|---|
| 1. Restate the issue | The agent paraphrased the customer’s specific issue and named the emotion. |
| 2. Ask open questions | The agent asked at least one open question and collected the identifiers needed for a lookup. |
| 3. Apologize and own it | The apology named the specific impact, and the agent said what happens next. |
| 4. Offer a fix with a time | The agent stated a specific action and a time, and the customer agreed. |
| 5. Confirm the resolution | The agent asked the customer to confirm the issue was resolved before closing. |
| 6. Follow up | A follow-up message went out within 24 to 48 hours. |
| 7. Log the root cause | The ticket carries a root-cause category and all seven log fields. |
The scripts in each step also work as role-play material during onboarding. A new agent and a tenured teammate can take one step each, with one playing the customer and the other practicing the recommended phrasing. Swapping to the phrases to avoid lets both hear the contrast.
Structured practice of this kind is what Talaera’s scenario-based programs build on. In the Dialpad case study, 149 support agents in the Philippines, India and Argentina trained with Talaera, and Dialpad’s own figures show soft-skill CSAT up 2.7% and manager escalations down 1.2%. One Dialpad agent said, “Even small changes in wording made a big impact on customer perception.”
A documented process makes complaint handling consistent
A documented, trainable process with the right language at every step turns complaint handling from individual talent into a team habit. Consistency becomes the default across channels and language backgrounds, because every agent has the same words ready.
How much of the script to adopt depends on the team’s channels and products, and no team needs perfection on day one. A shared framework that agents can practice and QA can measure is enough to start, and the complaint log will show over time which problems to fix upstream.
Want to help your customer-support team handle complaints well in English? Contact Talaera.
Frequently asked questions
What should you say to handle a customer complaint professionally?
A professional response names what the customer experienced and pairs it with a clear next step. For example, “I can see this caused a delay on your side, and I’m sorry about that.” Vague phrases such as “I understand your frustration” can feel dismissive without a paraphrase of the specific issue. In emotionally charged situations, agents can keep a list of de-escalation phrases within reach.
How do you follow up after resolving a customer complaint?
One short message 24 to 48 hours after resolution is enough. A good template opens with confirmation, such as “I wanted to check that the replacement order arrived and is working as expected,” and closes with an invitation to reopen the conversation if anything is still unresolved. That single touchpoint signals ownership and gives the customer an easy way back.
How do you log the root cause of a customer complaint?
Each complaint gets one of four root-cause categories, and the team records the same seven fields every time. Consistent tagging matters more than lengthy narratives, because it lets the team spot patterns across products and channels. ISO 10002 also recommends analyzing and evaluating complaints to improve quality.
Can English training help my team handle complaints more effectively?
Yes, particularly at the steps where language gets in the way. Talaera’s customer service English training gives non-native English speakers scenario-based practice in the phrasing and tone each step needs, along with cultural awareness for global customers.
