How to handle customer complaints before they cost you

How to reduce churn and keep customers happy with a 6-step process for resolving customer complaints

Without a system in place to handle customer complaints, they can quickly lead to lost revenue and increased churn.

This guide covers the most common types of customer complaints, a step-by-step framework for how to handle customer complaints in sales and how to use complaint data in your CRM to protect customer relationships before they break.

Key takeaways from how to deal with customer complaints

  • Every unresolved complaint carries a churn risk, but a structured response process reduces that risk before you lose a customer.

  • The most common complaint types follow predictable patterns, which helps you spot recurring issues and tackle them at the source.

  • A step-by-step framework gives customer-facing teams a clear path from first contact through to resolution and follow-up.

  • Pipedrive lets you log complaints against contact and deal records so you can assign follow-up activities and spot recurring problems.


The impact of customer complaints on your business

Customer complaints go beyond individual cases and can directly impact your business goals.

Medallia’s 2026 State of CX report found that 30% of customers experienced an issue in their most recent interaction with a company. When an issue occurs, the likelihood that a customer considers switching more than doubles.

For SMBs, that churn risk is compounded by the fact that most unhappy customers don’t raise a complaint at all. According to a 2023 Coveo report, 56% of customers rarely or never complain after a negative service experience.

When a customer complains, it gives you a valuable opportunity to resolve the issue and retain the relationship.

Complaints also flag issues that other customers haven’t raised. Resolving the root cause prevents wider retention and revenue losses.

The most common types of customer complaints

Most customer complaints fall into five categories, which makes it straightforward to identify patterns and improve the customer experience:

Complaint type

What typically drives it

Quality of the company’s products or services

The output didn’t meet the standard communicated during the sale

Wait times and delays

Response times, delivery or resolution took longer than expected

Communication breakdowns

The customer didn’t get the information they needed, or got conflicting information

Billing and pricing

Charges were unexpected, incorrect or unclear

Poor customer service

An interaction felt unhelpful or unprofessional


Once you identify the category behind a consumer complaint, you can trace it back to a specific part of the customer journey.

Say the head of customer support notices that most complaints fall into the wait-time category.

To address the cause, they might work with operations to review where delays occur or arrange regular timeline updates for sales reps so they don’t promise something the business can’t deliver.

The fix happens upstream, before the complaint ever reaches the customer service team.

Download your guide to managing teams and scaling sales

The blueprint you need to find a team of superstars and build a strong foundation for lasting sales success


How to handle customer complaints

The six steps below provide any team member with a path from first contact through follow-up, with strategies for team leaders to log issues and track patterns to reduce future complaints.


1. Acknowledge and listen to the customer

Customers want their complaints resolved, but they also want to feel heard.

Jumping straight to solutions before a customer has finished explaining the problem can make the conversation feel transactional. When that happens, the customer might escalate the issue or, conversely, disengage completely.

Instead, start by acknowledging the customer feedback. Saying something as simple as “I can see why that’s frustrating” signals that you’re paying attention to what the customer needs.

Avoid language that transfers responsibility to the customer. Phrases like “we’re sorry you feel that way” or “this isn’t usually a problem” undermine trust.

Note: On social media, where complaints are public, a prompt acknowledgment within your omnichannel support strategy matters as much for your brand reputation as it does for the individual. Other potential customers will see how you respond, which can impact their decision to consider you in the future.


2. Investigate the issue

Once the customer feels heard, gather the information you need to understand the cause of the issue.

At this point, having a customer relationship management tool (CRM) comes in handy.

A CRM allows you to keep records for each customer or contact, including past purchases, open deals, previous interactions and any notes left by colleagues. This additional context helps you piece together what went wrong.

For example, if a customer says they were charged too much, their CRM record might show that a discount recently expired, but no one told them.

Without that information, the cause is harder to identify, leading to a slower resolution and a more frustrated customer.

If you don’t have this information, use these three questions to guide your investigation:

  • What specifically happened versus what the customer expected?

  • Where in the process did the gap appear?

  • Who else was involved, and what do they know?

Getting clear answers to all three helps you get a complete picture of the problem before you propose a solution.


3. Agree on a resolution

Set a clear, realistic expectation for what will happen and when.

A good rule is to acknowledge the initial complaint within one business day and provide a resolution within two to three business days. This timeframe gives you enough time to investigate customer issues without leaving them in the dark.

If the resolution will take longer, take a phone number to update the customer directly rather than leaving them waiting for an email.

Here are some common resolution types for the different customer complaint types:

Complaint type

Common resolutions

Product or service quality

Replacement, rework or refund, depending on the severity

Long wait times and delays

An updated timeline with an explanation of the cause

Communication breakdowns

A clear account of what happened and a direct apology

Billing and pricing

Correction of the charge and a refund where applicable

Poor customer service

Acknowledgment and escalation to a manager if needed


Before closing the conversation, make sure the customer is happy with the proposed outcome. If they’re not, don’t push back on their response. Ask what outcome they’d consider fair.

In most cases, customers have a specific expectation in mind, and knowing what that is gives you something concrete to work with.

If their expectation is outside what you can offer, escalate to someone with the authority to make that call rather than leaving the customer at a dead end.


4. Log the complaint in your CRM

Record every complaint against the relevant contact so any team member who deals with the customer in the future has the full picture.

Consistent logging also creates an audit trail for customer support. If a customer reopens or disputes a complaint, there’s a clear record of what was reported, what was agreed and when.

Here’s how to use Pipedrive to log and track complaints at each stage of the process.

Adding notes to the contact or deal record

Add a note to the relevant contact or deal record as soon as the complaint is logged by going to the detail view and clicking “Notes” in the top right corner.

Customer complaints Pipedrive notes


You can use the “@” symbol to mention another team member, for example, if you need the billing team to verify a credit card charge.

You can also pin the note so that anyone going into the contact or deal record can see it straight away.

Assigning follow-up activities

Once you’ve logged the complaint, create an activity, such as a task or a follow-up call, and assign it to yourself or another team member.

Open the detail view of a deal or contact and click the activity tab to link an activity directly to that item.

Customer complaints Pipedrive activity


The activity appears in the assignee’s pipeline with a due date so that they won’t forget.

Using custom labels to categorize complaints

If your team handles complaints at volume, Pipedrive’s custom labels let you tag each complaint by type or status directly on the deal record.

Customer complaints Pipedrive custom labels


A tag like “billing dispute” or “unresolved” makes it possible to filter across the whole customer base and spot patterns. Complaints that would otherwise sit buried in individual contact records become visible at a team level.

With Pipedrive’s workflow automation, you can automatically trigger an email when you apply a label to the record.

For example, tagging a contact as “billing dispute” could send them an automatic acknowledgment while your team investigates the charge.


5. Follow up after resolution

A short call or email three to five days after you resolve the problem confirms the issue was genuinely fixed rather than just closed.

Keep your follow-up short and specific and reference the original complaint rather than sending a generic check-in. Here’s an example email response for customer complaints follow-ups:

Hi [name],

I am following up on the billing issue we resolved last week. Has everything looked correct on your end since then? Let me know if there’s anything else I can help with.


For people who nearly churned, this type of customer interaction rebuilds trust and turns them back into loyal customers. It shows that you’re genuinely interested in their customer satisfaction.

Pipedrive in action: Marmelada Market, an e-commerce platform for designers, was using a CRM that didn’t integrate with its other tools, which created delays, errors and dissatisfied customers.

After switching to Pipedrive, the team connected all their systems and automated customer support workflows, cutting admin time by 50%. According to Adielle Biton, Head of Sales, “Pipedrive’s automation has not only saved us time but has significantly helped customer service ratings and revenue.”


6. Review previous complaints for patterns

A monthly review of complaint records in Pipedrive’s Insights dashboard streamlines the process, letting you identify which complaint types appear most frequently so you can take action.

Open a dashboard and filter by your complaint-type custom label. Complaints that cluster around the same root cause indicate a process problem rather than a one-off failure.

For example, a SaaS business notices that billing complaints spike every January and traces the spike to renewal emails being sent to spam.

The team flags the deliverability issue for the marketing manager to fix. In the next renewal period, the team sees that billing complaints in that category dropped, confirming the fix worked.

Pipedrive’s reporting and analytics tools let you track custom fields over long periods.

With consistent logging, your company’s response to customer complaints becomes a standing item in your business review rather than an ad-hoc exercise when something goes wrong.

How to address customer complaints before they happen

For teams that don’t have a dedicated complaints team, every complaint that reaches support is time they could spend elsewhere.

A few simple practices reduce how often common complaints appear.

Make pricing and costs clear before the sale

Ensure your pricing page messaging clearly covers extra charges, for example, for setup fees or add-ons, not just the base price.

Train the sales team to repeat these charges during negotiations, so prospects know what to expect. It’s often the surprise more than the charge itself that prompts a customer complaint.

Set realistic timelines for delivery and response

Wait time complaints usually stem from a gap between customer expectations and what happened, rather than from the wait itself.

If a delivery typically takes five days but occasionally takes eight, mention the latter upfront rather than promising the former. The same goes for response times on support tickets or quote requests.

Keep customers updated during long processes

When customers don’t hear from you, they tend to assume something has gone wrong.

A brief check-in while a resolution is in progress keeps the customer from chasing you and gives them concrete information.

Something as simple as “we’re still looking into this and will have an answer by Thursday” can go a long way.

Brief staff on common edge cases

Complaints about poor customer service are sometimes less about attitude and more about a team member being caught off guard by a question they don’t have a good answer for.

Sharing a short list of common tricky questions, refund policy exceptions, delivery delay scripts and pricing exceptions means staff will know how to handle situations before they escalate.

Even with these habits in place, complaints will still come in.

When they do, having a clear process for how to resolve customer complaints removes guesswork and makes outcomes more consistent.


Final thoughts

The businesses that handle complaints best are those that treat each instance as an opportunity to learn.

Over time, a consistent process turns complaint data into a clear picture of where the customer experience is breaking down and what to fix first.

Pipedrive keeps complaint records tied to customer history, assigns follow-ups to specific team members and surfaces trends through reporting so that the whole team can act on complaints consistently.

Start a 14-day free trial and see how complaint tracking fits into your customer relationship workflow.


FAQs about how to respond to customer complaints