Published by
Throne of Profit EditorialReviewed by
William Hassell
Founder & Chief Editor, Throne of Profit
Every managed IT shop has them: the tickets that come back. The printer that drops off the network every Monday. The user whose Outlook profile corrupts every few weeks. The VPN that "just needs a reboot" over and over. Each one gets closed fast, so it feels handled — but it isn't fixed, it's postponed. And on a flat-rate managed agreement, every reopened ticket is time you already sold, spent again on a problem you already solved. The tickets that quietly destroy MSP margin aren't the hard ones — they're the easy ones you keep solving, because closing a symptom fast and fixing a cause permanently are two completely different acts.
The reason this hides so well is that recurring tickets look like productivity. The tech closes them quickly, the queue moves, the numbers look fine. But the same fifteen-minute fix, repeated weekly across dozens of clients, is a full technician's week vanishing into rework nobody chose to buy.
ONE UNDERLYING CAUSE, PAID FOR OVER AND OVER
root cause (never fixed)
│
├─ ticket ▇ close fast ░ → same time next week
├─ ticket ▇ close fast ░ → same time next week
└─ ticket ▇ close fast ░ → same time next week
▼
hours resold weekly, margin gone quietlyOwner symptoms
The same handful of issues, users, or devices show up in the queue week after week.
Techs close tickets fast, yet the total volume never actually drops.
Your busiest clients aren't the biggest — they're the ones with unfixed recurring problems.
Why this happens
The queue rewards closing, not fixing. A tech is measured on tickets resolved and response time, so the fastest path — reboot, clear the profile, reset the connection — always wins over the slower path of finding why it keeps breaking. Speed closes the ticket; it doesn't remove the cause. On top of that, recurring issues are scattered across weeks and techs, so no one person ever sees the pattern. The Monday printer problem and last Monday's printer problem look like two separate tickets, not one unfixed cause billed twice. Without someone stepping back to look at repeats across time, the shop treats every recurrence as brand new.
Common mistakes
Optimizing for close speed, which rewards fast symptom relief over permanent fixes.
Never grouping tickets by cause, so repeats look like unrelated one-offs.
Letting each tech handle recurrences solo, so no one sees the pattern across the week.
Treating a workaround as a resolution — a reboot script isn't a fix, it's a snooze button.
Not tracking reopens or repeats, so recurring work is invisible in every report.
Business consequences
On a fixed-fee agreement, recurring tickets are pure margin erosion — you're delivering the same labor repeatedly for a price that assumed you'd solve it once. A shop with quiet, chronic recurrence can look busy and profitable right up until capacity is gone and the team is drowning in work that should never have returned. The owner who hunts down root causes gets the opposite: falling ticket volume, freed-up technician hours, and headroom to take on more clients without hiring. Same team, same agreements — far less rework. That gap between the two shops, over a year, is enormous, and almost none of it shows up until you look at repeats.
How experienced operators think about it
They separate two jobs that look identical in the queue: close the ticket and kill the cause. Closing fast is right in the moment — the user needs to work. But the second a ticket has come back more than once, it stops being a support request and becomes an engineering problem: something in the environment is broken and needs a permanent fix, not another patch. Experienced operators watch for repetition as its own signal. A ticket that recurs is telling you exactly where a few hours of real work would erase weeks of future labor. They treat recurring tickets as a to-do list for permanent fixes, and they protect the time to actually do them.
Practical actions
Flag repeats, don't just close them. When a ticket looks familiar, mark it as a recurrence so the pattern becomes visible instead of vanishing into the queue.
Review the top recurring issues on a set cadence. Once a week or month, pull the problems and clients that keep coming back and rank them by time consumed.
Separate the fix from the close. Resolve the user's immediate issue, then open a distinct task to remove the underlying cause — and don't call it done until that's shipped.
Ask "why" until you hit something you can fix for good. The reboot works because something fails; chase that until the answer is a permanent change, not a workaround.
Protect time for root-cause work. Reserve recurring hours for permanent fixes, or the always-urgent queue will consume every minute and the repeats never die.
Questions every owner should ask
Which issues, users, or clients show up in my queue over and over — and do I actually know?
When a ticket recurs, does anyone fix the cause, or do we just close it faster each time?
How many technician hours a week are going to problems we've already "solved" before?
Frequently asked questions
How do I tell a true recurring problem from normal, unrelated tickets?
Look for the same symptom, device, user, or client returning on a rhythm — weekly, monthly, or right after a specific event like an update or reboot. One printer issue is a ticket; the same printer every Monday is a pattern. The tell is repetition over time, which is exactly what a fast-moving queue hides. You don't need anything fancy to find it — just someone periodically looking at what keeps coming back instead of treating each ticket as brand new.
Won't spending time on root-cause fixes slow down my ticket response?
Briefly, then the opposite. A permanent fix costs more than a quick close in the moment, but it removes every future recurrence of that issue — so total volume falls and your team gets faster because they're not re-solving old problems. The shops buried in tickets are usually the ones that never invest the hour to end a recurring issue. A little root-cause time now buys back a lot of queue time later.
Related articles
Running a Profitable Managed IT Services Business — the pillar.
Running Client Reviews That Actually Renew and Expand Accounts — where recurring-issue trends become a client conversation.
Setting Response-Time Expectations Clients Won't Fight You On — managing the queue clients see.
Chasing New Customers but Losing Old Ones? — the general retention problem.
Simple Ways to Bring Past Customers Back — reconnecting with clients you've lost.
Every business has more decisions than time
Whether you need help solving one problem, evaluating a major opportunity, or making a company-changing decision, Throne of Profit gives you consulting capacity on demand.
Purchase only the consulting capacity you need and use it across Weekly Focus, Strategic Focus, Financial Focus, and ThinkTank engagements.