7 Customer Complaint Examples — and the Scripts That Actually Fix Them

Thirteen percent of dissatisfied customers tell 15 or more people about their bad experience, according to Qualtrics XM Institute research. The other 87% just leave — quietly, without a complaint, directly to a competitor. That asymmetry matters: the customers who actually complain are your best recovery opportunity. The ones who say nothing are already making up their mind to leave. You'll see it in churn data three months from now, not in your support queue today.

PwC research shows that 32% of customers stop doing business with a brand after just one bad experience. That single-strike number means the average complaint interaction isn't just a customer service moment — it's a retention decision. Teams that build systematic complaint-handling processes, with clear scripts, defined escalation paths, and enforceable resolution timelines, hold customers who would otherwise churn silently and never explain why.

What Are Customer Complaints?

Customer complaints are expressions of dissatisfaction that a customer communicates to a business — about a product, a service interaction, a billing issue, a broken process, or an unmet expectation. They arrive through every channel: live chat, phone, email, social media, reviews, and in-person. The most important insight from complaint research is that the complaint itself is rarely the terminal event. It's the response quality that determines whether the customer stays or leaves. A complaint well-handled often produces more loyalty than if the problem had never occurred — a pattern known as the service recovery paradox, documented in research from Bain & Company and Harvard Business Review.

Long Wait Times

Wait-time complaints arrive before the conversation has even started — which means the customer is already in a negative state when your agent picks up. The frustration isn't really about the time; it's about feeling like they're not a priority. Agents who open by apologizing for the wait generically ("Sorry about that!") and then immediately ask the customer to re-explain their issue in full compound the problem. The customer just spent 12 minutes waiting. They want to feel like that time meant something.

The recovery approach: acknowledge the specific wait, show urgency about resolution, and give a concrete timeline for what happens next in the first 20 seconds. Don't rush the acknowledgment to get to the resolution. The customer needs a moment to feel heard before they're ready to receive your help.

Rude or Dismissive Agents

This complaint type is almost always a symptom of two organizational problems: agent burnout and inadequate de-escalation training. Agents handling 80+ contacts per day on complex issues without coaching or support will eventually stop performing the emotional labor that good service requires. The complaint a customer files isn't wrong — but the cause is usually systemic, not individual. McKinsey research on contact center operations consistently finds that frontline agent experience and customer experience move together. When agents feel unsupported, customers feel dismissed.

When a customer complains that a previous agent was rude, the instinct of many organizations is to apologize and close the loop. The more effective move: acknowledge the experience specifically, escalate internally for coaching, and — if possible — follow up directly with the customer to show the feedback was taken seriously. Customers who make this complaint and receive genuine follow-through often become among the most vocal advocates.

Having to Repeat Information

Research from Salesforce consistently ranks "having to repeat information" as one of the top three sources of customer frustration across industries. The reason it's so damaging is the signal it sends: the company doesn't track me, doesn't connect its systems, and treats each contact as if no previous history exists. For a customer who called yesterday and sent an email Monday, being asked to "start from the beginning" on a live chat Wednesday isn't just inconvenient — it's a signal that the company isn't paying attention.

This complaint is entirely preventable. Agents with access to full conversation history — previous channels, previous contacts, what was promised, what was resolved — never have to ask a customer to repeat themselves. The investment in CRM integration and unified agent views pays for itself in CSAT recovery alone, before you count the contacts it avoids entirely.

Product Not as Described

This complaint type carries a trust breach that extends beyond the individual purchase. When a customer receives something that doesn't match what they were shown or told, the problem isn't just the product — it's the reliability of your entire sales and marketing process. According to Edelman Trust Barometer research, trust once broken requires 2–3 positive experiences to repair. That means the handling of a "product not as described" complaint needs to over-deliver on every dimension: speed, transparency, and resolution quality.

The common mistake: treating this as a returns process rather than a trust-repair conversation. The script that opens with "I can process a return for you" doesn't address why the customer is actually upset. They're upset because they were misled — and they want to know that someone acknowledges that, not just that someone can transact a refund.

Billing Errors and Unexpected Charges

Billing complaints combine two of the most sensitive complaint dimensions: financial stakes and transparency breach. A customer who sees a charge they didn't authorize isn't just frustrated — they're questioning whether they can trust your company with their payment information. Intercom's pricing model generates exactly this kind of complaint at scale: customers see escalating monthly charges as their AI resolves more queries, triggering "what is this charge?" contacts that erode trust in the platform itself.

The handling principle for billing complaints is: never make a customer justify why an unexpected charge is wrong. The burden of proof is on the company. Lead with acknowledgment and a commitment to investigate — not with a policy recitation about when charges apply.

Broken Promises and Missed Follow-Ups

This is the complaint that comes from a previous service failure compounded by a second one. A customer was promised a callback that didn't happen. They were told their refund would arrive in 5 business days — it's been 11. An agent said they'd escalate the ticket — the customer heard nothing. Broken promises are doubly damaging because they mean the customer already gave the company a chance to fix things, and the company failed twice.

The recovery from this complaint type requires more than a script. It requires immediate, visible action — not another promise. The worst thing an agent can do at this point is apologize and set another timeline. The customer won't believe it. Show them the action in real time: "I'm escalating this right now, here's the ticket number, and here's my direct contact information if you don't hear back within 24 hours."

No Path to a Human

This complaint arrives before the customer reaches a human — it's the complaint about the system itself. Chatbot dead ends. IVR loops that never offer a live agent option. Email auto-replies that close tickets without resolution. These experiences signal to customers that the company has deliberately made it difficult to get help, which is the most trust-damaging interpretation available to them. And they're often correct — companies do design friction into contact channels to reduce volume rather than to improve service.

When a customer finally reaches a human after a bot or IVR dead end, they've already invested significant effort. They're primed to escalate. The correct response isn't to re-route them. It's to absorb the frustration, acknowledge the barrier they just navigated, and demonstrate immediately that reaching a human was worth the effort.

The Universal Complaint Recovery Process

Every complaint type above, regardless of the specific issue, follows the same recovery sequence. Teams that internalize this sequence produce more consistent outcomes than teams that rely on agent intuition alone.

What Your Platform Should Be Doing for You

The scripts and processes above are only as effective as the platform supporting them. Agents handling complaints need full contact history from all previous channels before the conversation starts. They need real-time access to account data, order status, and billing records without leaving the chat window. And when AI handles the first contact, it needs to pass every piece of relevant context to the human agent before the handoff — so the customer never has to repeat themselves.

One distinction worth understanding before you evaluate platforms: Intercom Fin charges $0.99 per AI-resolved complaint. Zendesk AI charges $1.50 per resolution. That pricing model means your bill rises as your AI handles more contacts — which creates a perverse incentive to underconfigure your AI to manage monthly costs. Velaro charges by conversation volume instead, with no per-AI-resolution fee. As your AI resolution rate increases, your bill stays flat. That matters when you're trying to scale complaint deflection efficiently rather than managing it conservatively to avoid charges.

The Bottom Line

Most customer complaints aren't about the original problem. They're about how the company responded to it. Qualtrics XM Institute research shows that 83% of customers feel more loyal after a complaint is resolved well — which means every complaint that reaches an agent is a retention opportunity disguised as a problem. The seven complaint types above all have recoverable outcomes if agents follow a consistent sequence: acknowledge specifically, take ownership, set a concrete next step, follow through before closing, and capture the data. Teams that build systematic complaint handling don't just reduce churn — they build the kind of customer relationships that generate reviews, referrals, and renewals.