Customer Success vs Customer Support: When You Need Both

Why the Distinction Actually Matters

The terms get used interchangeably, and that confusion has real cost. Companies hire a "customer success manager" expecting expansion revenue, then quietly turn the role into ticket triage. They hire "support" expecting reactive ticket work, then add proactive account management responsibilities that the team has no time or training for. The result is unclear ownership, missed expansion revenue, and burnout in roles that try to do both jobs.

This guide separates the two functions cleanly. What each one does, what each owns, when to hire which, and how the two coordinate without stepping on each other. It pairs with our customer support tier 1/2/3 operation and broader customer retention strategies.

Customer Success vs Customer Support at a Glance

Dimension	Customer Support	Customer Success
Mode	Reactive	Proactive
Trigger	Customer-initiated ticket or chat	Internal account health signal or milestone
Goal	Resolve the immediate issue	Drive long-term customer outcome
KPI focus	Response time, resolution time, CSAT	NRR, expansion revenue, retention, NPS
Time horizon	Per-ticket (minutes to hours)	Per-quarter to per-year
Account ownership	Anonymous queue, ticket-by-ticket	Named accounts, ongoing relationship
Compensation	Usually salary	Salary + variable on retention / expansion
Best skills	Patience, product knowledge, communication	Strategic, consultative, business acumen
Best-fit company stage	From customer #1	From ACV $5K+ or customer count 100+
Typical seniority	Mixed; entry-level common	Mid-senior; rare entry-level
Reports into	Support ops, often part of CX or engineering	CS, often part of sales or revenue ops

What Customer Support Actually Does

Customer Support handles the inbound stream of customer-initiated requests. The work is reactive by design — a customer hits an issue, opens a ticket, and Support resolves it.

Core Support Responsibilities

Responding to inbound tickets (email, chat, in-app)
Resolving billing questions and account changes
Troubleshooting bugs and product issues
Escalating technical issues to tier 2 / engineering
Maintaining the knowledge base
Handling refund and cancellation requests
Coordinating with engineering on systemic issues

What Support Doesn't Own

Driving customer outcomes (that's Success)
Account-level relationship management for renewal
Identifying expansion opportunities
Quarterly business reviews
Strategic product adoption planning

For the operational details of staffing tiered support, see our tier 1/2/3 support guide.

What Customer Success Actually Does

Customer Success drives customers toward the outcomes they bought your product to achieve. The work is proactive — Success identifies which accounts need attention, when, and intervenes before problems compound.

Core Success Responsibilities

Onboarding new customers to first value (often overlaps with implementation)
Account-level relationship management
Quarterly business reviews (QBRs) for mid-market and enterprise
Identifying and acting on at-risk account signals
Driving feature adoption and deeper product usage
Identifying expansion opportunities and triggering sales
Owning the renewal motion
Capturing customer outcomes and case studies

What Success Doesn't Own

Inbound ticket queue (that's Support)
Bug fixes or technical implementation
Net-new sales (that's Sales)
Day-to-day technical troubleshooting

When You Need Customer Support

You need customer support functionally from your first paying customer. The question is whether you need a dedicated person and at what stage.

Customer Count	Support Model
0–25	Founders handle all support directly
25–100	Founder + AI chat agent for tier 1
100–500	First dedicated support hire (often generalist CX role)
500–2,000	Tiered support (T1, T2), often with AI on T1
2,000+	Full multi-tier ops, dedicated leads, regional coverage

The founders-handle-it phase is critical for learning. Founders see every issue, hear every frustration, and use that to drive product improvements. Hiring support too early breaks this feedback loop.

When You Need Customer Success

Customer Success requires more conditions to justify the headcount than Support. Three criteria:

Average contract value (ACV) above $5K annually. Below that, customer success doesn't have enough revenue per account to justify a dedicated CSM. Self-serve onboarding plus great support is more cost-effective.
Customer outcomes that require active management. Some products are obvious — the customer signs up, uses the feature, gets value. Others require workflow changes, change management, integration work, or sustained discipline. The latter benefit from CS.
Expansion opportunity within accounts. If the typical customer can grow 2x+ within the account (more seats, more usage, more features, more business units), you have an expansion engine that CS amplifies.

If all three are true, hire CS. If only one or two are true, defer.

CSM Staffing Ratios

Customer Segment	Active Accounts per CSM
SMB (ACV $5–25K)	80–200 (often "pooled" model, not 1:1)
Mid-market (ACV $25–100K)	30–60
Enterprise (ACV $100K+)	10–25
Strategic (ACV $500K+)	3–10

These ratios assume active customers, not total. A CSM responsible for "150 SMB customers" is realistic; a CSM responsible for "15 enterprise accounts" is also realistic. The economics scale with ACV.

How the Two Functions Coordinate (Without Stepping on Each Other)

The cleanest division of responsibility:

Customer Event	Owned By	Coordinates With
Inbound ticket: bug, billing, how-to	Support	Engineering (for bugs), Success (escalation visibility)
Outbound: "we noticed you haven't used X feature"	Success	Marketing (for assets)
New customer onboarding	Success (or implementation)	Support (for technical questions)
Customer at risk of churn	Success	Support (signals from ticket volume / sentiment)
Expansion opportunity (new seats, upgrade)	Success	Sales (for closing)
Quarterly Business Review	Success	Account management, Product
Cancellation request	Success (saves)	Support (initial reception)
Renewal	Success	Finance, Sales
Customer-driven feature request	Support (logs)	Success (prioritizes), Product (decides)

The pattern that fails: both teams "own" account relationships interchangeably. The pattern that works: Support owns issues, Success owns outcomes. Either function can hand the customer to the other based on what's being asked.

How to Avoid the "CSM Doing Support" Anti-Pattern

The single most common failure mode in growing SaaS companies: customer success managers spending 60–80% of their time on support tickets that should be handled elsewhere. This happens predictably:

Support team is understaffed → tickets back up → customers escalate to their CSM
CSM, motivated by relationship preservation, handles the ticket
This becomes normal → CSM time is now consumed by reactive ticket work
Expansion and retention outcomes degrade because CSM isn't doing CS work
Company blames CS function for missing NRR, when the real problem is Support understaffing

The fix: enforce the function boundary. CSMs should escalate inbound issues back to Support with a tracking mechanism, not absorb them. If Support genuinely can't keep up, the answer is more Support headcount, not asking CSMs to fill the gap.

Common Customer Success / Support Mistakes

Hiring a "CSM" for Support Work

The most expensive mis-hire in early SaaS. A senior CSM (often $90–$130K base + variable) doing tier 1 ticket triage is roughly 3x the cost of the right hire for the work. If your need is reactive ticket coverage, hire Support.

Hiring Support for Account Management

The reverse problem. Asking a tier 1 support agent to drive expansion conversations, run QBRs, or own renewal motion sets the role up to fail. The skill profile is different.

Combining the Roles in a "CX Manager"

For companies under $1K ACV with mostly self-serve customers, a generalist CX role handling both works. Above that, the dual ownership creates role ambiguity. Either function suffers.

Compensating CS on Pure Headcount Metrics

CSMs paid only on base salary and overall NRR have weak incentive to drive specific expansion. CSMs paid on per-account expansion (e.g., 10–20% variable tied to net expansion from their book) align incentives correctly.

No Account Health Scoring

CS without account health signals is reactive. The CSM only knows there's a problem when the customer complains — too late. Build account health scoring (usage trends, NPS, ticket volume, late-payment signals, executive turnover) so CS works proactively.

When You Don't Need Either Function Yet (Not For You)

Skip both dedicated functions if:

You have fewer than 30 customers. Founders should handle every interaction. The learning is irreplaceable.
Your ACV is under $500 and your product is fully self-serve. A great help center, in-product guidance, and AI chat handles most needs. Hire neither role; invest in product and docs.
You're pre-PMF. Customer-facing roles solve "delivery" problems; if customers aren't yet sure they want the product, the problem isn't delivery — it's product.
You're a marketplace where each side has different needs. Build dedicated "supplier success" and "buyer support" rather than the standard SaaS framework — the dynamics are different.

Conclusion

Customer Support and Customer Success are different functions with different goals, different KPIs, and different skill profiles. Confusing them — hiring a CSM to do Support work, or a Support hire to do CS work — wastes 30–50% of the role's value.

Hire Support first, when your customer count crosses 50–100. Hire CS later, when ACV crosses $5K and accounts have meaningful expansion potential. Keep the function boundaries clean. Compensate CS on expansion outcomes, not just retention. Pair both functions with disciplined user onboarding design, strong customer feedback loops, and accurate NPS measurement — together they form the customer-facing system that turns acquired customers into expanding revenue.

Frequently Asked Questions

What is the difference between customer success and customer support?

Support is reactive — it resolves customer-initiated tickets (bugs, billing questions, how-tos). Success is proactive — it drives customers toward their desired outcomes through account management, QBRs, expansion conversations, and renewal motion. Support's KPIs are response time and CSAT; Success's KPIs are net revenue retention and expansion.

Which should I hire first — customer success or customer support?

Customer Support, almost always. Support becomes necessary when ticket volume exceeds what founders can handle (typically 50–100 customers). Customer Success requires more conditions to justify — ACV above $5K, customer outcomes that need active management, and meaningful expansion opportunity within accounts. Most companies under $1K ACV never need a dedicated CSM.

What are the 4 pillars of customer success?

Onboarding (driving customers to first value), adoption (driving sustained usage of key features), retention (preventing churn through proactive intervention), and expansion (growing account value through upsell and cross-sell). All four are CS responsibilities — the ratio shifts by company stage. Early-stage CS focuses heavily on onboarding and adoption; mature CS shifts toward retention and expansion.

Are CSM (Customer Success Manager) and CRM (Customer Relationship Management) the same?

No. CSM is a role — the person responsible for an account's success. CRM is software (Salesforce, HubSpot, Pipedrive) that tracks accounts, contacts, and activity. A CSM uses a CRM, often alongside dedicated CS platforms (Gainsight, ChurnZero, Catalyst, Vitally) that add health scoring and playbooks the CRM doesn't provide.

How many customers should one CSM handle?

Depends on ACV. SMB CSMs (ACV $5–25K) handle 80–200 accounts in pooled or one-to-many models. Mid-market CSMs ($25–100K ACV) handle 30–60 accounts. Enterprise CSMs ($100K+ ACV) handle 10–25 accounts. Strategic CSMs ($500K+ ACV) handle 3–10 accounts. The economics need to support the headcount cost — at low ACV, dedicated CSM coverage isn't financially viable.

Can one team do both customer success and customer support?

Yes, in two cases: (1) ACV below $1K with mostly self-serve customers — a generalist 'CX' role works. (2) Very early stage (under 30 customers) where founders handle everything. Above $5K ACV with meaningful expansion potential, separate the functions. The middle range ($1–5K ACV) often runs combined roles, but the function boundary should be clear even if the headcount isn't separate.

What are the 3 Cs of customer satisfaction?

Common references vary, but the most widely-used framework is Consistency (the customer's experience is predictable across touchpoints), Convenience (the customer can get what they need without friction), and Care (the customer feels the company is genuinely invested in their outcome). Customer Success and Customer Support both contribute to all three, but with different emphasis — Support drives consistency and convenience; Success drives care and outcome.