Where is your bottleneck?

A founder once told me their CX team was slow and unresponsive. Customers were complaining. Support tickets were piling up. The team looked unmotivated.

I asked how long it took the team to resolve a refund request. She said three days. I asked why. She said the ops lead had to approve it, then finance had to sign off, then she had to review anything above a certain amount.

The support team had been hired to help customers. But they could not actually help anyone. They could only escalate and wait.

What founders call a CX problem is often not a CX problem at all. It is a decision-making chain that the customer experiences as bad support.

Here is what I usually find when I look behind the support team: the founder is still the approval layer for things that should have been delegated months ago. So every ticket that needs a real answer sits in a queue, waiting for someone who is too busy to clear it.

The team is not the bottleneck. The system behind them is.

You can retrain the support team. Rewrite the scripts. Add empathy training. But if the system behind them stays the same, the same pain will show up again. In a smaller businesses, that pain is expensive. Every customer conversation matters more.

CX problems do not begin in the CX team. They end there.

If your support team feels slow, the first question worth asking isn't "how do we train them better?" It's "what are we making them wait for?"

That's usually where the real work is. It's a meaningful conversation to have.