# Ticket Backlog A ticket backlog is the total volume of unresolved customer support requests, service incidents, and project tasks currently sitting in an MSP’s queue. It represents the gap between the demand for technical assistance and the team’s capacity to resolve those issues within a defined timeframe. A **ticket backlog** is the total volume of unresolved customer support requests, service incidents, and project tasks currently sitting in an MSP’s queue. It represents the gap between the demand for technical assistance and the team’s capacity to resolve those issues within a defined timeframe. Managing this backlog is not just a technical requirement; it is a core commercial necessity. When a backlog grows unchecked, it erodes client trust, impacts service level agreements (SLAs), and directly reduces the profitability of the service desk. ## Key Takeaways - **Backlog is a Health Metric:** An unmanaged ticket backlog is often a symptom of underlying issues in standardisation, staffing, or tool utilisation. - **Commercial Impact:** High backlog levels lead to client churn and prevent the team from focusing on high-margin project work. - **Standardisation is Key:** Reducing ticket noise starts with implementing consistent hardware and software standards across your client base. - **Velocity Matters:** It’s not just about how many tickets you close, but how quickly you can move them from "New" to "Resolved." - **Accountability:** Clear ownership of the queue ensures that aging tickets don't get lost in the shuffle. - **Strategic Reviews:** Use backlog data during client reviews to demonstrate why specific upgrades or security changes are necessary. ## The Anatomy of an MSP Ticket Backlog In the world of managed services, a backlog is inevitable. Clients will always have issues, and systems will always require maintenance. The goal isn't necessarily a "zero backlog" state—which is often unrealistic for a growing business—but rather a controlled, predictable queue. At MSP Agenda, we view the ticket backlog through a commercial lens. If your technicians are constantly underwater, they aren't looking for ways to improve the client’s environment; they are just trying to survive the day. ### Active vs. Stagnant Backlog Not all backlog items are created equal. To manage the queue effectively, you must distinguish between tickets that are moving and those that are stuck. - **Active Backlog:** Tickets currently assigned, being worked on, or awaiting a scheduled technician visit. These are healthy signs of a busy desk. - **Stagnant Backlog:** Tickets "waiting on vendor," "waiting on customer," or simply ignored for days. This is where client dissatisfaction begins. - **Ghost Backlog:** Low-priority tasks that no one intends to do but no one wants to close. These clutter your reporting and skew your metrics. ### The Economic Cost of a Growing Queue Every ticket in your backlog carries a carrying cost. There is the direct cost of technician labour, but more importantly, there is the opportunity cost. When the service desk is overwhelmed, the business loses the ability to execute on projects that drive non-recurring revenue. Furthermore, a heavy backlog leads to "technician burnout." High turnover in your technical team is expensive to manage and disrupts the long-term relationships you’ve built with your clients. As Luis Navarro often emphasised during his time building Totality Services, profitability is closely tied to how efficiently your team can move through their daily tasks. ## Common Causes of Backlog Bloat Before you can fix the backlog, you have to understand why it’s growing. In our experience sitting between technical teams and business owners, the root cause is rarely "we need more people." It is usually a failure of process or alignment. | Root Cause | Impact on Backlog | Commercial Risk | | --- | --- | --- | | Lack of Standardisation | Higher "noise" and unpredictable issues. | Low margins due to excessive support time. | | Poor Ticket Triaging | Important issues get buried under trivial ones. | SLA breaches and client frustration. | | "Waiting on Client" Limbo | Tickets stay open for weeks without progress. | Inaccurate reporting on team capacity. | | Inadequate Documentation | Technicians reinvent the wheel for every fix. | Reduced efficiency and longer resolution times. | ### The Standardisation Gap If you support ten different firewall brands and five different backup solutions across twenty clients, your ticket backlog will always be higher than an MSP that enforces a strict technology stack. Standardisation allows your team to develop deep expertise, leading to faster resolutions and fewer repeat tickets. ### The "Triage" Failure Without a dedicated dispatcher or a clear triage process, technicians often pick the "easy" tickets first. This leaves complex or politically sensitive issues to rot in the backlog. Effective triaging ensures that the most impactful tickets are addressed first, regardless of how difficult they are. ## Strategies for Backlog Reduction Reducing a ticket backlog requires a tactical approach. You cannot simply tell your team to "work harder." You need to change the mechanics of how work enters and exits the system. #### 1. The "Clean Sweep" Initiative Start by auditing every ticket older than 30 days. If a ticket has been sitting for a month without progress, it is likely no longer relevant or the client has found a workaround. Reach out to the client, explain that you are cleaning up the queue, and ask if the issue is still a priority. Many times, you can close 10-15% of your backlog just by asking. #### 2. Implement a "Ticket Kill" Hour Dedicate one hour a day where the entire team (including senior engineers) focuses exclusively on closing out simple, low-priority tickets. This clears the deck and allows the team to focus on deeper technical challenges for the remainder of the day without the visual clutter of a massive queue. #### 3. Enforce Documentation Standards A significant portion of backlog growth comes from "knowledge silos." If only one person knows how to fix a specific client's proprietary software issue, that ticket will sit until they are free. Centralised, accessible documentation is the antidote to this bottleneck. #### 4. Leverage Automation and Self-Service Look at your most common ticket types. If "password resets" or "new user setups" are clogging your backlog, these are prime candidates for automation. Redirecting these to a self-service portal or an automated workflow frees up hours of technician time every week. ## Using the Backlog to Drive Commercial Conversations One of the biggest mistakes MSPs make is hiding their backlog from their clients. At MSP Agenda, we believe in using data to drive better business outcomes. Your ticket backlog is a goldmine of evidence for your next QBR (Quarterly Business Review). If a specific client accounts for 40% of your total backlog, that is a conversation about their aging hardware, their lack of user training, or their refusal to adopt your recommended security standards. When you can show a client that their outdated server is causing 15 tickets a month, the recommendation to replace it becomes a business decision rather than a technical sales pitch. ### Connecting Backlog to Security Reviews Security and support are inextricably linked. A high ticket backlog often includes "noise" from security incidents—phishing attempts, account lockouts, or malware alerts. By conducting regular security reviews, you can identify the root causes of these tickets and implement preventative measures. Luis Navarro’s experience building Totality Services taught us that clients are much more likely to approve a project if they understand how it will reduce friction in their own workday. Reducing the ticket backlog is a benefit the client can actually feel. ## Metrics that Matter: Monitoring the Queue To keep the ticket backlog under control, you need to track the right KPIs. Don't just look at the total number of open tickets; look at the trends and the velocity. - **Net Remaining:** The number of new tickets opened minus the number of tickets closed in a day. If this number is consistently positive, your backlog is growing. - **Average Age of Open Tickets:** If this number is increasing, your team is struggling with "stuck" tickets. - **Re-open Rate:** If tickets are being closed but then reopened, your team is rushing to reduce the backlog without actually fixing the root cause. - **Backlog Ratio:** The number of open tickets per technician. This helps you identify when it’s time to hire. ### The "SLA Breach" Warning Your backlog is the leading indicator of future SLA breaches. If your backlog is growing, your response times will eventually suffer. Monitoring the backlog allows you to react before the client feels the impact and starts looking for a new provider. ## Advanced Insights: The Psychology of the Backlog Managing a technical team requires an understanding of human behaviour. A massive, insurmountable ticket backlog is demoralizing. It leads to "learned helplessness," where technicians feel that no matter how hard they work, they will never catch up. Break the backlog down into manageable chunks. Use gamification or small incentives for "Backlog Blitz" days. Most importantly, ensure that leadership is visible in the queue. When a founder or manager helps clear the deck, it sends a powerful message about accountability and shared goals. #### Managing Client Expectations Communication is the best defence against a high backlog. If you know the team is backed up due to a major project or an internal system migration, tell your clients. Most business owners are reasonable if they are kept in the loop. It is the silence that kills the relationship. ## Frequently Asked Questions ### How do I know if my ticket backlog is "too high"? A good rule of thumb is the "Tickets per Seat" metric. Most efficient MSPs aim for 0.5 to 1 ticket per user per month. If your total open backlog exceeds two days' worth of your team's total capacity, you are entering a danger zone where service quality will begin to decline. ### Should I hire more staff to clear the backlog? Not necessarily. Hiring is a permanent solution to what might be a temporary process problem. First, look at your standardisation and automation. If your team is spending time on tasks that could be automated or prevented through better client standards, hiring more people just masks the inefficiency. ### How does a ticket backlog affect MSP valuation? During an acquisition, like the eight-figure exit Luis Navarro achieved with Totality Services, buyers look at operational efficiency. A high, messy backlog suggests poor management and high future costs. A clean, well-managed queue indicates a scalable, profitable business that isn't dependent on manual firefighting. ### What is the difference between a backlog and a queue? In common MSP parlance, a "queue" is the list of active work waiting to be started, while the "backlog" is the total accumulation of all unfinished work across all statuses. A queue is tactical; a backlog is systemic. ### Can I just close old tickets that haven't been touched? Yes, but do it strategically. Use a "stale ticket" workflow that emails the client one last time, informing them that the ticket will be closed due to inactivity. This gives the client a chance to re-engage while allowing you to clear the noise from your reporting. ### Does standardisation really reduce the backlog? Absolutely. When every client uses the same firewall, your technicians don't have to spend 30 minutes researching how to make a simple configuration change. Speed of resolution is the fastest way to shrink a backlog, and standardisation is the fastest way to increase speed. ### How often should I review my backlog? Service managers should review the queue daily for urgent bottlenecks. Leadership should review backlog trends weekly to identify staffing needs or client-specific issues that need to be addressed in the next business review. Managing a **ticket backlog** is a balancing act between technical execution and commercial strategy. By focusing on standardisation, clear communication, and consistent process, you can transform your service desk from a source of stress into a driver of client value and MSP profitability. --- Source: https://mspagenda.com/glossary/ticket-backlog Last updated: 2026-08-24