Customer Success vs. Customer Support: What is the difference?

Short answer

What is the difference between Customer Success and Customer Support?

Customer Support is responsible for making sure the customer's enquiries are resolved. Customer Success is responsible for making sure the customer's goals are reached. Both can be proactive, and both can handle urgent cases – the difference lies in mission, goals and responsibility, not in who answers the phone.

Customer Support and Customer Success are often confused. That is not surprising. Both functions talk to customers, both solve problems, and in many companies they sit in the same team – sometimes in the same person.

Even so, they are built for different things. The simplest difference is this: Customer Support is responsible for making sure the customer's enquiries are resolved. Customer Success is responsible for making sure the customer's goals are reached.

That difference has consequences for how the functions work, what they are measured on, and how they should be organised. But it is not absolute, and it is easy to make it simpler than it is.

Two different missions#

The mission of Customer Support is to help customers who have a question, a problem or an error. The starting point is an enquiry, and the work is done when the enquiry has been resolved well. Good Customer Support is fast, precise and friendly, and lets the customer get on with what they were doing.

The mission of Customer Success is to make sure the customer achieves what they bought the product to achieve.¹ The starting point is the customer's goal, and the work is never quite done as long as the relationship lasts. Customer Success does not just ask “is the problem solved?”, but “is the customer on the way to where they want to be?”.

This means the two functions often see the same customer from different angles. Customer Support sees individual cases. Customer Success sees patterns and direction.

Two missions, the same customer

Customer Support

1. The customer gets in touch
2. The case is logged
3. The problem is solved
4. The case is closed

Done when the case is resolved.

↕ Enquiries are signals for Customer Success – and context about the customer makes Customer Support's answers better.

Customer Success

1. The customer's goal
2. Onboarding
3. Use and value
4. Renewal and expansion

Not done as long as the relationship lasts.

Reactive and proactive – with caveats#

It is common to say that Customer Support is reactive and Customer Success is proactive. As a rough description, that is correct: Customer Support starts when the customer gets in touch, Customer Success tries to act before the customer needs to.

But the line is not that sharp.

Customer Support can be proactive. A good Customer Support team notifies customers of known errors before they notice them, publishes answers to common questions, and passes insight from enquiries on to product development. Some of the most effective measures for reducing enquiries come from Customer Support itself.

Customer Success can be reactive. When an important customer is unhappy, a renewal is at risk, or a critical error hits a customer, it is often Customer Success that has to handle the situation. A good Customer Success Manager answers questions too.

The difference therefore lies less in the activity and more in the responsibility. Customer Support is responsible for the quality of the answers. Customer Success is responsible for how the customer relationship develops.

Different goals and measures#

Because the missions differ, the functions are also measured differently. This is where the difference becomes most concrete.

Simplified comparison. Many companies mix the roles, and the table describes centres of gravity, not fixed boundaries.

Some of the terms in the table may need explaining:

• CSAT (Customer Satisfaction Score) measures how satisfied the customer is with a specific interaction, typically through a short question after the case is resolved.
• First contact resolution shows the share of enquiries resolved without the customer having to get in touch again.
• NRR (Net Revenue Retention) shows how much of the revenue from existing customers has been retained over a period, including expansion and net of downgrades and losses.
• Time to value is the time from when the customer starts until they achieve the first concrete value from the product.

These measures are explained in more detail in How do you measure the value of Customer Success?

Different areas of responsibility#

Who is responsible for what varies a great deal. Even so, it is useful to distinguish between responsibilities that typically sit with one of the functions, and responsibilities that have to be shared.

Typically Customer Support:

• Answering enquiries in all channels
• Troubleshooting and solving technical problems
• Escalating errors to product and development
• Maintaining the help centre and answers to common questions

Typically Customer Success:

• Onboarding and handover from sales
• Following up the customer's usage and progress
• Identifying customers at risk
• Renewals and, in some companies, expansion
• Customer meetings, reviews and business dialogue

Shared responsibility:

• Insight into customers' friction and needs for product and management
• The customer experience at the handovers between teams
• Knowledge content and self-service

The shared responsibility is often what falls between two stools. Nobody owns the whole customer experience if both functions only look after their own part.

How the functions should work together#

Customer Support and Customer Success are most valuable when they use each other's information.

Enquiries are signals. A customer who suddenly contacts Customer Support much more often than before, or who stops getting in touch altogether, may be changing their relationship with the product. Customer Support sees this first. Customer Success needs to know.

Context makes Customer Support better. A Customer Support agent who knows that the customer is in the middle of onboarding, has a renewal in three weeks or has just had a bad experience can give a better answer than one who only sees the case.

Patterns in enquiries show where the friction is. When many customers ask about the same thing, it is rarely a Customer Support problem. It is a product, onboarding or communication problem. Customer Success is often well placed to drive the work of removing the cause.

When many customers ask about the same thing, it is rarely a Customer Support problem.

In practice, this means the functions should share data, have a common understanding of the customer segments, and have clear handover routines. It also means management should avoid measuring Customer Support only on how quickly cases are closed. A Customer Support team rewarded for speed has little incentive to spend time finding the cause of the problems.

Organisational variants#

There are many ways to organise the two functions. None is right for everyone.

Separate functions. Customer Support and Customer Success are two teams, each with its own leader. That gives clear responsibility and specialisation, but requires deliberate collaboration so that the customer does not experience two separate worlds.

Customer Support as part of Customer Success. Both functions sit under one leader, often with the title Head of Customer Success or VP Customer Experience. That makes it easier to see the whole, but can lead to the reactive work eating up capacity for the proactive work.

One function, several roles. In smaller companies it is common for the same team to do both. That can work well, as long as time is deliberately set aside for proactive work and the queue is not allowed to decide everything.

Segment-based. Large customers get a dedicated Customer Success Manager who also handles many of their enquiries. Smaller customers are served through Customer Support and digital customer journeys.

The choice depends on the number of customers, the value per customer, the complexity of the product and how mature the company is. The most important thing is that responsibility is clear – not which box on the organisation chart it sits in.

Why job titles can mislead#

It is common for positions with Customer Success in the title to be Customer Support in practice, and vice versa. Some companies have chosen the title because it sounds more strategic, or because it makes recruiting easier. Others have gradually extended Customer Support's responsibility to include onboarding and follow-up, without changing the title.

This creates three concrete problems:

1. Salary comparison becomes difficult. Two people with the same title can have completely different tasks, mandates and responsibilities. That makes it hard for both employers and employees to judge what the right pay is.
2. Expectations become unclear. A new leader who hires a “Customer Success Manager” may expect proactive, commercial work – and get someone used to answering enquiries, or the other way round.
3. Measurement becomes misleading. If a function that is really doing Customer Support is measured on retention, the results will look either unfairly poor or randomly good.

When trying to understand a role, it is therefore more useful to ask about the responsibility than the title: what is the person responsible for achieving? What decisions can they make? What are they measured on?

Summary#

Customer Support and Customer Success are not opposites. They are two parts of the same customer relationship, with different missions:

• Customer Support makes sure the customer gets help when something is not working.
• Customer Success makes sure the customer gets where they want to go.

Both can be proactive, both can handle urgent situations, and both depend on each other. The difference lies in what they are responsible for – and it is that responsibility that should determine how they are organised, led and measured.