Customer Success vs Customer Support: Two Jobs, One Confused Org Chart

Customer success and customer support are not the same function wearing different name badges. Support is reactive: a customer has a problem, you solve it. Success is proactive: you work to ensure the customer never reaches the point where a problem threatens their relationship with you. Conflating the two is one of the more expensive organisational mistakes a subscription or services business can make.

The confusion is understandable. Both functions touch customers. Both require product knowledge. Both show up in the same post-sale period. But their commercial logic is entirely different, their success metrics are different, and the skills you hire for are different. Running them as one blended team is like asking your demand generation manager to also handle customer complaints. The activities overlap in theory and collide in practice.

If you want a broader grounding in how retention strategy fits together commercially, the customer retention hub covers the full landscape, from loyalty mechanics to post-sale revenue strategy.

What Does Customer Support Actually Do?

Support is the function that handles inbound problems. A customer cannot log in. A feature is not working as expected. An invoice looks wrong. A delivery has not arrived. The job of support is to resolve these issues accurately and quickly. It is, at its core, a service quality function.

Done well, support protects the relationship. Done badly, it accelerates churn. But it is not, by design, a growth function. A support team that resolves 95% of tickets within four hours is doing its job. It is not, however, ensuring that the customer is getting value from the product, expanding their usage, or renewing at a higher tier. That is a different job entirely.

I have seen this confusion play out at agency level too. When I was running client services at a mid-sized performance agency, we had account managers who were brilliant at firefighting. They kept clients calm, resolved billing disputes, handled platform outages with grace. What they were not doing, because the role did not require it, was proactively identifying where a client’s strategy was underperforming and bringing a commercial recommendation to the table. Those are two different skill sets. We eventually split the function, and the revenue impact was measurable within two quarters.

Support metrics tend to be operational: ticket volume, resolution time, first contact resolution rate, customer satisfaction score on the back of a closed ticket. These are legitimate measures of service quality. They are not measures of commercial health.

What Does Customer Success Actually Do?

Success is the function responsible for ensuring the customer achieves the outcome they bought the product to reach. That framing matters. It shifts the question from “did we resolve their problem?” to “are they getting what they paid for?” Those are very different questions with very different implications for how you structure the role.

A customer success manager in a SaaS business might be tracking product adoption data, identifying accounts where usage has dropped, scheduling business reviews to realign on objectives, and flagging at-risk customers to the commercial team before renewal conversations begin. None of that work is triggered by a support ticket. It is proactive, commercially oriented, and focused on the customer’s outcome rather than their immediate complaint.

Understanding what actually drives customer loyalty is foundational here. The research is consistent: loyalty is not primarily driven by having problems resolved. It is driven by customers consistently achieving the outcome they came for. Support can protect loyalty by not destroying it. Success builds it.

This is why the commercial logic of success is tied to renewal rate, net revenue retention, and expansion revenue. A well-run success function does not just retain customers, it grows them. Forrester’s work on renewal rates makes clear that proactive engagement and demonstrated value are the primary drivers of renewal decisions, not reactive service quality. You cannot support your way to strong net revenue retention. You have to succeed your way there.

Where Organisations Get This Wrong

The most common mistake is not failing to separate the functions. It is separating them on paper while keeping them blended in practice. You rename your support team “customer success” and give everyone new job titles. Nothing changes operationally. The team still spends 80% of its time on inbound tickets. The metrics are still operational. The commercial accountability never materialises.

I have judged enough marketing effectiveness work at the Effies to recognise this pattern. An organisation claims to have built a customer success capability, but when you look at what the function actually does and how it is measured, it is a support team with better branding. The tell is always the metrics. If your “customer success” team cannot tell you the renewal rate or net revenue retention for their book of business, they are not running a success function. They are running support under a different name.

The second mistake is treating success as a cost centre rather than a revenue function. Support is legitimately a cost centre: you want to resolve tickets efficiently and keep the cost per resolution low. Success should be measured and funded differently. A customer success manager who manages a book of business worth £2 million in annual recurring revenue is a commercial asset. Funding that role like a support agent is a false economy.

Building a strategic customer success function requires a deliberate decision about what the role is accountable for and how it is resourced. That decision does not happen by default. It requires someone at the leadership level to make an explicit call about the commercial purpose of the function.

The third mistake is timing. Separating success and support too early, before you have the customer volume or ARR to justify two distinct functions, creates overhead without return. I have seen early-stage SaaS businesses hire a head of customer success when they have 40 customers and a support queue that one person could handle. The role becomes undefined, the person becomes frustrated, and the business has spent money on a structure it is not ready for. The separation makes sense at a certain scale. Forcing it before that scale exists is an organisational vanity project.

How the Two Functions Should Work Together

Separating success and support does not mean they operate in isolation. The handoff between them matters enormously. A support ticket is a data point. If a customer has raised five tickets in three months about the same feature, that pattern is a signal that the success manager needs to act on. The support function should be surfacing that signal. The success function should be acting on it.

This is where the operational infrastructure between the two functions becomes important. A shared CRM, clear escalation paths, and defined ownership of the customer relationship at each stage of the post-sale lifecycle are not nice-to-haves. They are the mechanics that make the separation work in practice rather than just on paper.

A well-structured customer success plan should include explicit criteria for when a support interaction triggers a success intervention. Not every ticket warrants one. But a pattern of tickets, a drop in product usage, or a missed milestone in the customer’s onboarding experience should all have defined escalation paths to the success team.

The relationship also works in reverse. A success manager who is spending their time on issues that should be handled by support is not doing their job. If a CSM is fielding basic “how do I reset my password” queries, something has broken in the handoff. The success manager’s time has a commercial value. Spending it on L1 support is a waste of that value, and it usually means the customer has not been given a clear enough understanding of how to access support.

The Metrics That Distinguish the Two Functions

If you want to know whether your organisation has genuinely separated these functions or just relabelled them, look at the metrics each team is held to.

Support metrics should include: first contact resolution rate, average resolution time, ticket volume by category, customer satisfaction score at ticket close, and cost per resolution. These are operational measures of service quality. They tell you whether the function is running efficiently and whether customers are leaving support interactions satisfied.

Success metrics should include: net revenue retention, gross revenue retention, renewal rate, expansion revenue, time to value for new customers, and product adoption rate within defined cohorts. These are commercial measures of customer health. They tell you whether the function is delivering its core purpose: keeping customers and growing them.

Some metrics sit in both camps. Customer satisfaction scores are relevant to both functions, but they mean different things in each context. A high CSAT on a support ticket tells you the ticket was handled well. A high CSAT in a quarterly business review tells you the customer feels the relationship is working. Both matter. Neither is a substitute for the other.

There is also a category of metrics that sounds meaningful but is not. Number of customer calls made per week. Number of QBRs completed per quarter. Number of health score updates logged. These are activity metrics, not outcome metrics. They tell you the team is busy. They do not tell you the team is effective. I have seen success teams hit every activity target while the renewal rate quietly deteriorated. Activity without commercial outcome is not success. It is theatre.

Retention Mechanics That Both Functions Influence

Both support and success influence retention, but through different mechanisms. Support influences retention by preventing the kind of negative experiences that trigger cancellation decisions. Success influences retention by building the kind of positive outcomes that make cancellation feel irrational.

This distinction matters for how you invest in each function. If your churn is driven by product problems, billing confusion, or poor onboarding, fixing support quality will move the needle. If your churn is driven by customers not achieving their desired outcomes, improving support quality will not help. You need a stronger success function.

Retention programmes that sit outside both functions, such as wallet-based loyalty programmes, can complement both but replace neither. A loyalty mechanic that rewards tenure or spend is a retention tool. It is not a substitute for a customer who is achieving value from your product. The mechanic works better when the underlying relationship is healthy. When it is not, the mechanic is papering over a structural problem.

In B2B contexts, the dynamics are more complex. B2B customer loyalty is rarely driven by a single relationship or a single outcome. Multiple stakeholders, shifting priorities, and procurement cycles all affect renewal decisions in ways that neither support nor success can fully control. But a strong success function that has built relationships across the customer’s organisation, documented the value delivered, and aligned with the customer’s evolving objectives is in a far stronger position at renewal than one that has simply resolved tickets efficiently.

Customer lifetime value is the commercial output that both functions are in the end contributing to. Support protects it by preventing premature churn. Success grows it by driving renewal and expansion. Neither function should lose sight of that commercial north star, regardless of which operational metrics they are measured on day to day.

When to Outsource and When to Keep It In-House

Support is the more natural candidate for outsourcing. The work is often high volume, process-driven, and can be documented into playbooks and scripts. Many businesses outsource L1 support successfully, keeping L2 and L3 in-house where product knowledge and escalation judgment are required.

Success is harder to outsource well, but it is not impossible. The challenge is that success work requires deep contextual knowledge of the customer’s business, their objectives, and their internal politics. That knowledge is hard to transfer to an external provider and easy to lose when account managers rotate. That said, there are scenarios where customer success outsourcing makes commercial sense, particularly for businesses that need to scale coverage quickly without building the internal infrastructure from scratch.

The decision should be made on commercial grounds, not operational convenience. If outsourcing support frees up internal resource to build a stronger success capability, that is a sensible trade. If outsourcing success saves cost in the short term but degrades the quality of customer relationships, the long-term renewal impact will cost you more than you saved.

I spent years watching agencies make this mistake in reverse. They would keep expensive internal resource on low-value operational work and outsource the strategic client relationship management to junior account managers at offshore partners. The cost saving was visible on a spreadsheet. The damage to client retention was not visible until it was too late to reverse.

The Expansion Revenue Question

One of the clearest ways to distinguish the commercial purpose of success versus support is the question of expansion revenue. Support does not own expansion. It is not structured to identify it, pursue it, or close it. Success, when functioning correctly, does.

A customer success manager who understands the customer’s business objectives, tracks their usage patterns, and has visibility into where the product is delivering value is well-positioned to identify upsell and cross-sell opportunities. Forrester’s analysis of cross-selling and upselling consistently points to the same conclusion: the most effective expansion conversations happen when the customer already trusts the provider and can see demonstrated value. That trust is built by success, not support.

This does not mean success managers should be running around closing deals. In most organisations, the commercial close sits with account management or sales. But the identification of the opportunity, the nurturing of the relationship, and the timing of the conversation are success functions. The mechanics of cross-sell versus upsell are different, and a good success manager understands which motion is appropriate for which customer at which point in their lifecycle.

Retention and expansion are two sides of the same commercial equation. You cannot build strong net revenue retention without both. A business that retains 90% of its customers but never grows them is leaving significant revenue on the table. A business that grows customers aggressively but loses 25% annually is running on a treadmill. The success function, when properly structured and measured, is the mechanism that drives both.

There is more on the full retention picture, including how loyalty, expansion, and post-sale strategy connect commercially, in the customer retention hub. If you are building or restructuring a post-sale function, it is worth reading alongside this.

The bottom line is this: customer success and customer support are both necessary. Neither is optional in a subscription or services business. But treating them as the same function, measuring them with the same metrics, or funding them from the same commercial logic will cost you more than the organisational clarity of separating them ever would. The distinction is not semantic. It is structural, commercial, and consequential.

About the Author

Keith Lacy is a marketing strategist and former agency CEO with 20+ years of experience across agency leadership, performance marketing, and commercial strategy. He writes The Marketing Juice to cut through the noise and share what works.

Frequently Asked Questions