If you work in support, you know the feeling of opening a new ticket and thinking, wait, haven’t I answered this one before? Same question, same fix, different person. Closing it takes two minutes, so it never feels worth stopping to do anything about. Let’s talk about why that little repeat is more expensive than it looks, and how choosing one repeating issue a month and fixing it at the source can quietly lighten the load for everyone.
Start with an everyday picture
Imagine a shop with a door that sticks. Every customer who comes in pushes, shoves, then gives the shop assistant a puzzled look. The assistant gets very good at saying, "Just lift the handle first." That is a perfectly friendly workaround, and it works, and for a long time it feels like good service.
But the real fix is ten minutes with a screwdriver. Once the door is fixed nobody needs to be told anything. Support work has plenty of sticking doors: the password reset email that lands in spam, the dashboard that needs a refresh after a deployment, the form that rejects a perfectly valid date.
Why repeat tickets cost more than their minutes
Each repeat ticket has a visible cost, which is the few minutes someone spends answering. It also has hidden costs. The person asking is mildly frustrated and wonders whether the service is reliable. The person answering gets a little more tired, because repetition is draining even when the task is easy. And the answers drift: one person says "try this," another says "try that," and soon the customer is hearing two stories.
There is one more cost that is easy to miss. When the same thing keeps coming back, it hides the new problems. A team busy with the usual suspects can overlook the unusual one sitting in the queue.
What "fix it at the source" means here
Fixing at the source means changing the thing that creates the question rather than writing a better answer. If people keep asking how to find a setting, the answer might be a clearer label. If a reminder email keeps getting lost, the fix is how it is sent. Sometimes the source sits outside the support team, in the product or in a process, and the fix is a short, well-evidenced request to the people who own it. A good request says what keeps happening, roughly how often, what it costs and what you suggest.
Occasionally the source cannot be changed at all. In that case the best fix is a better message shown at the right moment, so the person gets the answer before they need to ask.
How to choose the month’s one thing
You do not need fancy analysis. A decent method is to look through the last month’s closed tickets and tag each one with a rough cause. Then count. One or two causes will usually stand out. From those, choose the one that is most repeated and most fixable. Skip anything that needs a huge change; save it for a proper project. You are hunting for the sticky door, not the building’s foundations.
Here are a few questions to help decide:
- Does it come up every week, or only in odd bursts?
- Do we know the cause, or would we need to investigate first?
- Who can actually change it, and have we asked them?
- Will we notice if it is fixed, for instance because those tickets stop?
Looking at how the wider craft frames this
The habit lines up with ideas you will find in most writing about good delivery. The piece on principles for effective software delivery talks about feedback and continuous improvement, and a repeat ticket is nothing more than feedback arriving again and again. It also helps to know who to talk to; this overview of common DevOps role titles and what they usually cover can help you work out whether a recurring problem belongs to an operations engineer, a platform team or somebody else entirely.
A small, friendly diversion
Support teams sometimes browse other sites to see how a product listing or help center can be laid out. A website called BestToolsX shows one approach: a front-of-house look at a catalog covering software and technology, carrying a notice that its entries are samples, and its sections steer visitors to a listing by what it is and which problem it tackles. That is a layout idea and no more. The fix for your sticky door will come from your own tickets.
Doing the fix
Once you have your target, it helps to follow a short routine.
- Collect examples. Gather five or six real tickets so you are fixing what actually happens.
- Find the trigger. What happened just before each person wrote in?
- Change the trigger. Edit the wording, adjust the setting, correct the message or raise a change request.
- Retire the old answer. Update any saved replies so nobody keeps sending an outdated explanation.
- Watch the queue. Over the next few weeks, check whether those tickets fade away.
When the fix does not stick
Now and then the repeats continue. Do not take it personally. Usually it means the real trigger was a step earlier than you thought, or that two different causes were mixed together under one label. Go back to the examples, split them and fix the larger half first. A repeat after a fix is information, and it beats not knowing.
A word on tone
When you tell a customer that something has been fixed, keep the message short and warm. Say what went wrong, say that it should not happen again and thank them for flagging it, since their ticket is usually what revealed the pattern. Customers remember being listened to far longer than they remember the wording of a saved reply. If you also tell your own team in the same breath, the habit spreads: colleagues start noticing their own repeats and bringing them along, and the sticky-door list gets a little longer in the best possible way.
Keep it kind and keep it small
The best part of this habit is how gentle it is. Nobody has to give a big presentation. You pick one thing, fix it and tell the team. Over a year you will have a dozen sticky doors repaired, and customers will have noticed something they cannot quite name: the service simply feels smoother. That is a nice thing to be able to say about your team’s work, and it all started with spotting one ticket you had answered one time too many.