Onboarding
Part of Customer success for B2B products
Customer success versus customer support
Understand the different jobs of customer success and support, and how to hand off a problem without losing sight of the customer's goal.
Customer support helps a customer resolve a specific problem or request. Customer success helps the customer achieve the outcome it intended from the product over time. Both may speak to the same people and work on the same obstacle; the useful distinction is the decision each team owns.
| Question | Customer support | Customer success |
|---|---|---|
| What is the immediate job? | Investigate a reported fault or service request and help resolve it. | Check progress toward an agreed customer outcome and coordinate action when it stalls. |
| What starts the work? | A case, incident or request, although support may also alert customers proactively. | A goal, milestone or concerning signal, although a customer may also ask for help first. |
| What shows progress? | A response, workaround or resolution checked against the reported issue. | Evidence that the intended workflow and outcome are improving, or that a remaining obstacle has an owner. |
These are suggested operating distinctions, not universal job descriptions. A support team can prevent problems before a ticket arrives. A success manager can respond to an urgent concern. Timing alone does not settle ownership.
Customer success versus customer support: key differences
- Immediate jobInvestigate a reported fault or service request and help resolve it.
- Immediate jobCheck progress toward an agreed customer outcome and coordinate action when it stalls.
- What starts the work?A case, incident or request, although support may also alert customers proactively.
- What starts the work?A goal, milestone or concerning signal, although a customer may also ask for help first.
- What shows progress?A response, workaround or resolution checked against the reported issue.
- What shows progress?Evidence that the intended workflow and outcome are improving, or that a remaining obstacle has an owner.
Route a problem by the work required
Suppose users of a hypothetical B2B approvals product cannot submit a request. The investigating team needs the error, affected users, steps to reproduce it and customer impact. Customer success should record how the fault affects the agreed approvals goal, coordinate any customer-side change and check whether the workflow works after the technical response.
The account needs a clear route to report the problem and a clear owner for updates. Where the technical owner and relationship owner differ, share the case reference, impact, next update and any dependency between them.
Routing a problem by the work required
- Support team gathers error details, affected users, steps to reproduce, and impact
- Customer success records impact on the agreed approvals goal
- Customer success coordinates any necessary customer-side change
- After technical fix, confirm the workflow functions as intended
- Ensure clear ownership and communication between technical and relationship owners
Close the account-level concern
A closed ticket does not always mean the customer can complete its task. After a material fault, ask the affected user or process owner whether the workaround or fix restored the workflow. If not, reopen the technical question or document the remaining obstacle.
A success manager should avoid promising a fix date, custom feature or service concession on behalf of another team. The manager can explain the customer's goal and urgency, secure the right internal owner and communicate the next confirmed step. Technical findings and commitments should come from whoever is authorised to make them.
For an ongoing account, agree a short handoff rule: what belongs in a support case, when customer success is notified, who updates the customer and what evidence closes the account-level concern.
Handoff process for account-level concerns
- Confirm the technical fix or workaround is applied
- Verify the workflow resumes as intended
- If the workflow is still disrupted, reopen the technical case or document the obstacle
- Success manager communicates the next confirmed stepnot promises of fixes or concessions
- Agree on a handoff rulewhat goes in a support case, when success is notified, who updates the customer
