Support has the case. The customer wrote down what is wrong in their own words. It sits open. Support tries a few things. None of them cut it. The customer gets frustrated.
At a software company that is when the CSM gets it.
Not because anyone decided the CSM should have it. Because the customer got loud enough to reach the CSM.
The CSM opens the case. Reads the customer’s words. Goes to find out where it stands.
It is already in Jira. Engineering has it. Nobody said no to it. It is sitting under other work. Nobody told the CSM that. Nobody told support either. The case is in the queue, and the queue is the answer.
So the CSM pings the engineering manager. Or product. Whoever answers faster.
I’ve seen this play out over my entire career. I was the one getting pinged. Here is what moved a case once it reached me.
Not the customer’s words. How loud the customer was. How big the account was. If it was a big enough deal, sales got on the thread, and then it moved for sure.
That is the whole mechanism. The case moves by weight. A loud customer weighs more than a quiet one. A big account weighs more than a small one. A sales rep on the thread weighs more than a CSM alone.
Nobody decided the case needed a root cause. Nobody decided it didn’t. Nobody decided anything. The case got heavy enough and it moved.
Here is what happens when it moves.
It gets prioritized. It gets fixed. The customer gets a response. The account calms down. The case closes.
Nobody asked why it happened. That question never came up. The fix was the decision, and the fix was made by weight.
Think about who had the context.
Support had the customer’s words from the first day. The CSM has been on the account for two years and knows this is the third time something like this has landed there. That is the frontline: support and CX at a software company, or the IT team at a business that runs on software. They see it first. They know the most. They have no vote on whether it gets a root cause.
Engineering has the vote and not the context. They have a ticket in a queue. The customer’s words are three handoffs back.
The cases that never get heavy enough stay in the queue. Same symptom, smaller account, quieter customer. They close later as fixed, or they close as won’t fix. The why was never on the table for those either.
That is where the investigation cost sits. Not in the loud cases. Those get fixed. In the quiet ones that were the same thing, fixed one at a time, by weight, whenever the next customer got loud enough.
The customer wrote down what was wrong on the first day. Somebody read it. Then everyone waited to see how loud they would get.
Teams where a case moves because of who is on the thread, not because anyone decided it should, are exactly who we’re thinking about.
If that’s your team, we offer a complimentary Investigation Cost Audit. Forty-five minutes. Structured diagnostic across five dimensions. You leave with a scorecard that puts numbers on what your team carried last quarter: in time, in repeat cases, and in the fixes that shipped before anyone asked why.