Key Takeaways
The ticket came in on a Tuesday. The customer's admin reported that their integration had failed again, the third time that month. The support agent fixed it and closed the ticket. On Thursday the CSM heard about it from the customer's VP, who wanted to know why nobody had flagged a recurring outage. The CSM opened the help desk, found three closed tickets and no note connecting them. Then the CSM asked support what had happened. Support asked the customer. The customer explained it for the fourth time.
Nobody in that story did their job badly. Support resolved each ticket. The CSM responded as soon as they knew. The failure sat in the gap between them, where context was supposed to move from one team to the other and didn't. This post covers why the customer success and support handoff breaks, why most advice about it misses the point, and what to change instead.
What the handoff costs the customer
The best evidence on handoffs comes from customer effort research. A 2010 HBR study surveyed “more than 75,000 B2C and B2B customers about their recent service interactions.” The obstacles they found were common: “56% report having to re-explain an issue … 59% report being transferred 62% report having to repeatedly contact the company to resolve an issue.”
The authors named these as core drivers of effort. Customers resent “having to contact the company repeatedly (or be transferred) to get an issue resolved, having to repeat information, and having to switch from one service channel to another.” Our guide to customer effort score covers how to measure that effort directly.
More recent data points the same way. Salesforce's 2023 survey found “56% often have to repeat or re-explain information to different representatives.” About three-quarters of that sample were consumers, so treat it as a general signal, not a B2B benchmark. The same survey found 66% of customers say good service depends on being matched with the right agent. That's another way of saying the context lives in people, not in the system.
Why the handoff is the problem, not the form
Most advice about the customer success and support handoff focuses on the transfer itself. Write a better handoff form. Add an AI summary. Name a directly responsible individual. Those all assume the handoff should exist and just needs to carry more.
Support's own methodology bodies disagree. The Consortium for Service Innovation, which maintains Knowledge-Centered Service, says the tiered model “creates organizational silos and handoffs/escalations that inhibit the exchange of information and knowledge, and thus inhibits learning.” It describes what customers experience as cases “bouncing” between teams.
The reason is simple. KCS says “the only way we have found to effectively capture context is in the moment of use; context cannot be recreated after the fact.” A handoff form is written after the fact, by someone summarising a conversation they've already finished. Whatever they leave out is gone.
There's a second cost that's easy to miss. HBR found “22% of repeat calls involve downstream issues related to the problem that prompted the original call, even if that problem itself was adequately addressed the first time around.” That's the integration story above. Each ticket was fixed. The pattern across them was the real issue, and no single agent saw it.
The handoff loss ledger
Customer operations teams run at least four boundaries where context changes hands. Here's what each costs the customer, what the evidence says, and who should own it. The last two columns are our recommendations, based on the sources cited.
| Boundary | What the customer has to redo | What the evidence says | Recommended owner | What must already be on the record |
|---|
| Tier 1 to tier 2 escalation | Re-explain the issue | Tiered models make cases “bounce” and block knowledge flow | The first owner keeps the case and pulls in help | The conversation and steps already tried |
| Support to CS, account risk | Explain the pattern to someone new | TSIA places escalation ownership in support | Support owns; CSM works alongside | Linked tickets for the account, with the pattern named |
| CSM change on an account | Re-teach needs and priorities | B2B customers can be more tied to the contact than the vendor | Outgoing and incoming CSM together | Goals, stakeholders and open issues on the account |
| Self-service or AI to agent | Repeat what they already searched | KCS calls passing that trail on “no dead-ends” | The receiving agent | Search terms, articles viewed and the AI conversation |
Sources: Consortium for Service Innovation, Intelligent Swarming; TSIA, The Support Services-Customer Success Handshake; Journal of Marketing, 2002; KCS v6 Practices Guide.
Keep one owner per issue
The Intelligent Swarming model offers a simple rule: “the owner of the issue retain ownership until the issue is resolved - even if they need help in resolving it.” The guide calls it playing catch, not ping pong. Help comes to the case. The case doesn't move to the helper.
HBR's study described the same idea in banking. “South Africa's Nedbank, for instance, instituted an 'AskOnce' promise, which guarantees that the rep who picks up the phone will own the customer's issue from start to finish.”
For the support-to-CS boundary, TSIA's research suggests who that owner should be. Its summary says “clear ownership of the escalation process is necessary for efficient communication and resolution, ideally housed within the support services team.” The CSM joins the case, adds account context and talks to the executive sponsor. Support keeps the case.
That runs against a common instinct, which is to hand escalations to the CSM because they own the relationship. The CSM's role is also changing. Gainsight's 2023 index notes “the percentage of CSMs responsible for Customer Support is going down.” As CS moves toward a commercial charter, handing it technical escalations makes the boundary wider, not narrower.
Make the record carry the history, not the person
One owner per issue helps with the handoffs you can remove. Some handoffs can't be removed: CSMs change, and agents go on leave. For those, the account's history has to live somewhere other than a person's memory.
Research on B2B relationships shows why. A 2002 Journal of Marketing study found “a customer's relationship with an employee who is closest to them, a key contact employee, may be stronger than the customer's relationship with the vendor firm.” One B2B customer in that study described what happens when that person leaves: “it would take me a long time to get them to understand my needs and my priorities.”
Most stacks split that history across tools. TSIA's 2026 report lists it: “Support owns the ticketing platform. Customer success owns success plans and engagement history.” HubSpot's 2024 survey of CX leaders found only 35% of CRM leaders say their customer data is fully integrated with their service tools. That's a vendor survey of self-reported integration, but it matches what most support and CS teams describe. Our post on customer operations vs customer success covers the tooling choices.
Measure repeat contacts, not handoff quality
Handoff quality is hard to measure directly. Repeat contacts aren't. HBR's authors recommend a simple alternative to first-contact resolution: “Tracking repeat calls within a specified period (we recommend seven to 14 days) is not only easier than measuring FCR but also casts a wider net.”
For a B2B team, count repeat contacts per account, not per ticket. The integration customer above had three tickets, each closed on first contact. Per ticket, that looks fine. Per account, over 14 days, it's a pattern that should have reached the CSM on the second ticket.
Four changes to make this quarter
- Name the owner for account-level escalations. Write it down. Our recommendation, following TSIA, is support owns the case and the CSM joins it.
- Link every ticket to the account. A ticket that only knows the requester can't show a pattern.
- Capture context in the conversation. Notes, steps tried and the customer's own words go on the record while the case is open, not in a summary afterwards.
- Report repeat contacts per account over 14 days. Send the list to the account's CSM weekly.
None of these needs a new handoff form. Each one removes a reason to hand off at all.
One record both teams work from
The four changes are hard when support works in a help desk and CS works in a CS platform. Each team sees its own half of the account.
MatrixFlows puts both halves on one foundation. Customer requests, accounts, success plans and knowledge articles are linked tables in Matrix. Conversations in the Inbox stay attached to the account, so a CSM can see every ticket and the steps already taken. When a customer moves from the help center or an AI assistant to an agent, the conversation comes with them. An Automation can alert the CSM when an account passes a repeat-contact threshold you set.
Back to the integration customer. On one record, the second ticket would have shown the first one. The CSM would have heard about the outage from support, not from the VP. And the customer would have explained it once.
Create a Free Workspace → and put support tickets and CS notes on the same account record this week.
.svg)
.svg)
.svg)
