A growing software company combines customer support and customer success into a single team, reasoning that both functions ultimately serve the same broad goal of customer satisfaction — and within several months, the team's actual time allocation reveals nearly all of its capacity going toward resolving incoming support tickets, with proactive customer success activities like adoption check-ins and account health reviews consistently deferred and eventually abandoned, a specific and well-documented structural pattern that emerges when these two genuinely different functions are combined under one team.
Why support and success are genuinely different functions, despite serving a broadly related overall goal
Customer support reactively resolves specific customer issues and questions as they arise, measured primarily by response time, resolution time, and ticket volume — customer success proactively works to ensure customers are genuinely achieving value from a product over time, measured primarily by product adoption, account health, and renewal likelihood. These are meaningfully different activities requiring different skills, different daily rhythms, and different specific success metrics, despite both broadly serving a company's overall customer relationship.
Why combining them into one team specifically causes support to crowd out success work
A support ticket carries immediate, visible time pressure — a customer is actively blocked or frustrated right now, and there's a clear, measurable expectation for timely response — while proactive success activities like a quarterly account health review or adoption check-in carry no equivalent immediate deadline pressure, making it easy and rational, in the moment, for a combined team facing competing demands on limited time to consistently prioritize the urgent support work over the important but less immediately pressing proactive success work.
Why this crowding-out pattern tends to compound and worsen over time rather than self-correct
Deferred proactive success work doesn't simply wait patiently for eventual attention — customers not receiving proactive success engagement are more likely to experience the exact kind of confusion, underutilization, or dissatisfaction that eventually generates more support tickets, meaning a combined team's initial tilt toward reactive support work can create a self-reinforcing cycle where more support tickets crowd out more proactive success work, which in turn generates yet more future support tickets.
Why this specific dynamic tends to emerge gradually rather than being obvious from the start
A combined support-and-success team may function reasonably well when overall customer volume and support ticket load are still genuinely low, since there's enough available team capacity to handle both reactive and proactive work adequately — the crowding-out dynamic tends to emerge specifically once support ticket volume grows to a point where it reliably consumes the team's full available capacity, at which point the previously adequate combined structure starts systematically starving proactive success work.
How growing companies typically address this once the pattern becomes apparent
Companies experiencing this specific crowding-out pattern typically respond by separating support and success into genuinely distinct teams with separate leadership, separate metrics, and protected capacity specifically allocated to proactive success work — a structural separation that prevents the urgent, deadline-driven nature of support tickets from continuing to systematically crowd out the important but less immediately pressing proactive success activities.
What this means for structuring customer-facing teams as a company grows
- Recognize customer support and customer success as genuinely distinct functions with different metrics and different daily time pressures, even though both serve broadly related customer relationship goals
- Watch specifically for support ticket volume beginning to consistently crowd out proactive success activities in a combined team structure
- Consider separating the two functions into distinct teams once support volume grows to a point where it reliably consumes available team capacity
- Protect dedicated capacity specifically for proactive success work, since it carries no equivalent immediate deadline pressure to compete against urgent support demands
Combining customer support and customer success under one team can work reasonably well at genuinely low volume, and the specific, well-documented crowding-out pattern that emerges as volume grows is a structural consequence of urgency, not a failure of any individual team member's prioritization judgment — a distinction that points toward organizational separation, not simply better individual time management, as the actual fix.