Article overview: When companies consider outsourcing, they should also account for the cost of poor customer experience. Unresolved customer support problems can cost the business revenue, so the price of a BPO partnership should be weighed against the losses caused by those problems. Lower customer support costs mean nothing if customers keep leaving.
Customer Losses Don’t Always Look Like Support Problems
Customers don’t always cancel right after a bad support experience. Some remain customers for a while and leave later without mentioning the earlier issue. If the company doesn’t check customer support history when reviewing churn, the two events may never be connected.
If CX and operations leaders judge customer support mainly by staffing expenses or cost per contact, the operation can look efficient even when the same customer has to come back for help. Cost per contact measures each interaction separately, so three contacts about one problem can still look inexpensive on paper. The actual cost is the total time spent resolving the issue. When repeated customer support problems contribute to cancellations, the lost revenue also becomes part of the cost of poor customer experience.
Reviewing customer support history alongside cancellations and changes in spending gives CX and operations leaders a clearer view of customer experience and churn. It can show which problems tend to appear before customers pull back, giving the company a chance to fix the issue before another customer decides that staying is more trouble than it’s worth.
Bad Support Can Cost the Next Sale
A global Qualtrics XM Institute survey of nearly 24,000 consumers examined how spending changed after a very poor experience. Among the very poor experiences reported, consumers spent less with the company in 38% of cases and stopped buying from it in 15%.
Qualtrics used those responses and household consumption data from the World Bank to estimate that $3 trillion in sales was at risk across the 23 countries studied. Since those countries represented 79% of global household consumption, Qualtrics projected the worldwide figure at $3.8 trillion for 2025. That projection assumes consumers outside the study would respond to poor experiences at a similar rate, so it should be treated as an estimate rather than confirmed lost sales.
A company can run a smaller version of this analysis using its own customer support and sales data:
- Choose a set period to review. Start with customers who contacted support during a specific month or quarter. A defined period keeps the data consistent and provides enough records for a useful comparison.
- Group customers by contact reason. Separate the records according to why customers needed help. This makes it easier to see whether one problem is more closely associated with lower spending or churn than others.
- Compare what customers did afterward. Review whether each group renewed or bought again over the next few months. Compare those results with customers who had a similar profile and purchase history but didn’t contact support during the same period.
- Add resolution history. Separate customers who received an answer during the first conversation from those who had to contact support again about the same issue. This can show whether repeat contacts are followed by a larger drop in spending.
- Estimate the revenue at risk. Calculate the average spending difference between the affected customers and the comparison group. Apply that difference to the number of customers who contacted support about the same issue to estimate how much revenue may be associated with it.
Other factors can influence whether customers buy again, so this process shows a possible connection rather than proving that customer support caused every lost sale. Even with that limitation, it gives the company a more useful estimate of the cost of poor customer experience than refunds and credits alone. It also gives CX and operations leaders a clearer view of the impact of bad customer service and which problems need attention first.
Loyalty Can Look Better on Paper
Companies can think customer loyalty is stronger than customers say it is. PwC’s 2025 Customer Experience Survey found that about nine out of ten executives believed loyalty had grown in recent years, while only four out of ten consumers said the same. PwC also found that 29% of consumers had stopped using or buying from a brand because of poor customer experience. Sales can remain steady for a while, so support data can help companies spot a strained customer relationship sooner.
A repeat contact should change how the case is handled:
- Set a clear trigger. Decide when a case should be flagged, such as when a customer contacts support again about the same issue within 30 days. The timeframe can be adjusted based on the company’s typical purchase or subscription cycle.
- Give the next agent the full context. Bring the customer’s previous conversations, proposed solutions, and unresolved questions into one view. The agent can continue the work instead of asking the customer to start over.
- Put one person in charge. Assign someone to manage the case through resolution, including any follow-up the customer was promised. Ownership should remain clear even when another department needs to help.
- Define when the case moves up. Set escalation rules based on the severity of the problem and its effect on the customer. This helps urgent cases reach someone with the authority to resolve them without relying on an agent’s judgment alone.
- Track what happens next. Review whether customers with repeat contacts continue buying, downgrade, or cancel after the issue is resolved. Comparing those results over time can show how customer experience and churn are connected and whether the process is helping the company retain more customers.
Customers who come back for help are still giving the company a chance to get it right. The customer support operation should be ready to use it.
A Bad Review Can Make the Next Sale Harder
People read reviews while deciding whether to buy. When the same support complaint appears several times, prospective customers can begin treating it as a problem they might experience too.
CX teams need a consistent way to separate isolated complaints from recurring support problems:
- Use the same issue labels everywhere. Create one list of categories for the review tracker, customer support platform, and sales CRM. This prevents the same refund problem from being recorded under several different names and hiding the pattern.
- Set a threshold for investigating complaints. Choose the number or percentage of similar reviews that will trigger a review of the underlying process. Base the threshold on the company’s usual review volume and adjust it as that volume changes.
- Check the customer support data. Look for contacts filed under the same category, then review how often customers had to follow up and how long the issue took to resolve. This helps confirm whether the public complaints match a problem inside the support operation.
- Assign the fix to the right department. Send the reviews and support data to the department responsible for the process. Record the person responsible, the change being made, and the completion date in a shared tracker.
- Measure the results over equal periods. Compare the percentage of reviews and support contacts tied to the issue before and after the change. Using equal time periods and percentages prevents changes in customer or review volume from distorting the result.
Fixing recurring support problems keeps the impact of bad customer service from becoming the next customer’s reason to walk away.
New Customers Don’t Always Equal Growth
Suppose a company gains 1,000 customers and loses 700 in the same month. It finishes the month with 300 more customers than it had at the start, not 1,000. Focusing on the new customers while leaving out those who left makes growth look bigger than it was.
Companies can avoid that by reporting customers acquired, customers lost, and the net change in customer count together. Subtracting losses from new customers shows how much the customer base grew after churn was accounted for.
For a subscription business, the next step is to check whether customers stayed long enough to cover their acquisition cost. Pull a group of customers who canceled after an unresolved support case or repeated contacts about the same issue. Calculate the average gross margin contribution per customer before cancellation, then compare it with the average customer acquisition cost (CAC) for that group. If the contribution per customer is lower than the CAC, the acquisition cost wasn’t fully recovered.
This analysis does not prove that customer support caused the cancellations. Looking at customer experience and churn alongside CAC can show whether unrecovered acquisition cost is concentrated among customers who experienced the same support problem. CX and finance teams can compare that amount with the cost of addressing the problem, then track whether early churn declines after the change.
The BPO Quote Is Only Part of the Cost Comparison
A BPO proposal arrives with a clear price, while the current operation’s costs are spread across different budgets and reports. The cost of poor customer experience can be harder to spot because it appears through additional support work and lost customer revenue.
A useful comparison should account for five areas:
- The cost of running support today. Add up payroll, benefits, software, recruiting, training, and the management time dedicated to customer support. This creates a baseline for the current operation before any improvements are considered.
- The cost of existing support problems. Measure the agent time spent on repeat contacts and cases caused by unresolved issues, unclear policies, or inaccurate help content. Include overtime and lost revenue associated with customers who canceled or spent less after those problems. This captures part of the impact of bad customer service that normal operating expenses can miss.
- The price of fixing the operation internally. Estimate the additional spending and implementation time required to address the problems identified. Depending on the operation, that could involve extending coverage, hiring managers, improving training, or changing technology.
- The full scope of the BPO proposal. Confirm which responsibilities are included in the quoted price and which will remain with the client. Recruitment, training, quality management, workforce planning, reporting, and staffing adjustments should be accounted for before comparing the BPO with the internal option.
- The BPO partner’s improvement plan. Ask what will change after launch and how the results will be measured. Each proposed change should have a starting baseline, a measurable target, a named owner, and a schedule for reviewing performance. When retention is a goal, the proposal should also identify the customer retention CX metric that will be tracked.
The strongest BPO proposal makes the price clear and identifies the service results the partnership is expected to improve.
Reducing the Cost of Poor Customer Experience
Repeat contacts create costs that can disappear inside the support budget. The business pays again for work that should have been finished, while the customer spends more time chasing a resolution. When unresolved support problems contribute to churn, the lost revenue also adds to the cost of poor customer experience.
Peak Support works side by side with clients to find out why customers keep coming back for help. Our account leaders trace repeat contacts to the point where the original issue was left unresolved, then help correct the process and set a clear target for improvement. We check the results after the change goes live. If the problem continues, we review the change with the client and adjust it.
Build a customer support operation that keeps earning your customers’ business with Peak Support.