Is hiring customer support the right move if half the tickets are repetitive?

Half of your support tickets are basically the same question wearing different clothes.

"Where is my order?"
"I haven't received my order."
"Has my order been shipped yet?"

When you see that pattern day after day, the obvious reading is that you have a volume problem. And maybe you do. Maybe you need another person on the support desk. Maybe you need automated replies that catch these questions before a human ever sees them. Maybe you need a better tracking page so customers can find the answer themselves.

Any of those could be the right call. But the pattern hides something important. Seeing the same question over and over only tells you that something needs attention. It does not tell you what that something actually is.

So before you decide how to fix it, it pays to read the tickets a little more closely. Because three customers can send what looks like the same message for three completely different reasons.

Take the first one. "Where is my order?" Sometimes the answer is simple: the order is late. That is not really a support problem at all, it is a fulfilment problem. You can add support people to reply faster and more kindly, and that does help the customer feel heard, but none of it changes the fact that the order never went out on time.

Now the second customer. "I haven't received my order." The order might be completely on schedule. The customer simply expected it sooner than you ever promised. The gap is not in your warehouse, it is in the timing they had in their head. That is an expectation problem, and it landed in your inbox because somewhere along the way the customer understood the delivery window differently from how you meant it.

Then the third. "Has my order been shipped yet?" Here the order has already shipped. Everything is fine. The customer just cannot see that anything is happening, so they ask. That is a visibility problem, and the fix is usually a clearer update at the right moment, one that answers the question before the customer ever thinks to send it.

Same words on the screen, three times over. Three different causes underneath, and three different fixes.

And those are not even the full list. The repeated ticket could be coming from a confusing confirmation email, a courier dropping the ball, a stock issue you have not spotted yet, or simply a long silent stretch after someone pays when nothing arrives to reassure them.

⚡ A repetitive ticket tells you where the pressure is showing up. It does not tell you what is causing it.

That is why the answer is not automatically "hire someone", and it is not automatically "automate it" either. Hiring another support person genuinely makes sense when the volume is real and your team is buried. Automation earns its place when the answer is simple, reliable, and easy for a customer to check for themselves. But when the ticket is being created further upstream, by a late shipment or a vague email or a delivery promise that never matched reality, then more replies only help you handle the symptom faster. The thing generating the question is still sitting there, untouched.

So before you choose the fix, decode the repetition. Sit with a handful of those tickets and work out what actually happened in each one. Once you know that, the decision tends to make itself, whether what you really need is more support, better automation, clearer communication, or a change somewhere further back in how an order travels from "bought" to "in their hands".

🚀 What to do next

If this feels familiar, start here:

👉 Run the Second Look Decision Diagnostic to see what’s missing before you decide
👉See related business decision

👉 📖 Read more on Second Look blog

You can continue with making the decision afterwwards.