CRMsoftware.pro

Ticket backlog calculator

Find out when your support backlog will be cleared: open tickets ÷ (tickets resolved per day − new tickets per day). See the date it clears, how many extra tickets or agents a deadline needs, and how the queue moves over the next 8 weeks.

Your queue today

tickets
All unsolved tickets right now
/ day
Average of the last few weeks

Your team

/ day
Needed for the agents you'd need to add
/ day
Leave empty to use agents × tickets per agent
Empty = today. Day 1 is this date if it's a working day.
Working days

Public holidays are not excluded.

Your target (optional)

working days
tickets
0 means every ticket. A few open tickets is normal.
tickets
To see how much of the backlog is overdue

Fewer tickets in, a shorter queue

A backlog only shrinks when your team resolves more tickets than arrive. Answering the simple questions before they become tickets is the cheapest way to get there.

CRMsoftware.pro puts an AI agent on your website and in your messengers. It answers questions about prices, orders and opening hours in seconds, day and night, and hands the rest to your team with the full conversation saved in the CRM.

  • AI agent answers on your website, WhatsApp and Telegram
  • Every chat saved to the contact and the deal
  • Tasks and reminders so no ticket waits without an owner

Free plan, no credit card. Paid plans from $19/month, billed yearly.

The formula

How to calculate how long a ticket backlog takes to clear

Your backlog is the number of open tickets at a point in time. It changes every day by the tickets that arrive minus the tickets your team resolves.

Backlog tomorrow = backlog today + new tickets − resolved ticketsNet change per day = new tickets per day − resolved tickets per dayDays to clear = (backlog − backlog you keep) ÷ (resolved per day − new per day)Resolved per day needed = new per day + backlog ÷ target days

Zendesk’s Backlog Evolution report works the same way: it takes the backlog at the end of one day, adds the next day’s new tickets and subtracts the next day’s solved ones. In its example, 155 + 34 − 24 = 165.

Use averages per working day and the same working days for both numbers. If tickets also arrive at weekends, add them to the working-day average: 700 new tickets a week with a 5-day team is 140 per working day.

The backlog only shrinks when the team resolves more tickets than arrive. When both numbers are equal, it stays the same size forever, however hard everyone works.

Two ways to read the size of a backlog

MeasureFormulaWhat it tells you
Days of incoming workbacklog ÷ new tickets per dayHow many days of demand are waiting. MetricNet shows the same ratio as a percentage of daily volume.
Backlog-to-throughputbacklog ÷ resolved tickets per dayHow many working days your team needs to work through the queue once, and roughly how long a new ticket waits if tickets are handled in order.
Net change

−24 a day

‎120 − 144 = −24

Days to clear

20 days

‎480 ÷ 24 = 20

Needed for 10 days

168 a day

‎120 + 480 ÷ 10 = 168

Worked example

One support team, step by step

An illustrative team, not real data. Press Show example in the calculator to load these numbers.

On Monday, 23 November 2026 a support team has 480 open tickets. About 120 new tickets arrive every working day. Its 8 agents each resolve about 18 tickets a day, Monday to Friday. The team wants the backlog gone within 10 working days, and 90 of the open tickets are already older than its 3-day SLA.

‎1. Throughput: 8 × 18 = 144 tickets a day

‎2. Net change: 120 − 144 = −24 tickets a day, or −120 a week. The backlog shrinks

‎3. Days to clear: 480 ÷ (144 − 120) = 20 working days, which is 4 weeks

‎4. Date: day 1 is Monday, 23 November, so the 20th working day is Friday, December 18, 2026

‎5. Target of 10 days: 120 + 480 ÷ 10 = 168 tickets a day, 24 more than today. 24 ÷ 18 = 1.33, so 2 more agents (rounded up)

‎6. Size: 480 ÷ 120 = 4 days of incoming work (400% of daily volume); 480 ÷ 144 = 3.33 working days of work for the team

‎7. Overdue: 90 ÷ 480 = 18.75% of the backlog. Worked oldest first, they take 90 ÷ 144 = 0.63 working days

Now look at how fragile this is. With one agent off sick, the team resolves 7 × 18 = 126 a day: the backlog still shrinks, but by only 6 a day, so it takes 480 ÷ 6 = 80 working days. With two agents away, 6 × 18 = 108 is less than 120: the backlog grows by 12 a day, 60 a week, and never clears.

When it never clears

Why some backlogs never go down

If new tickets arrive as fast as your team resolves them, the queue stays the same size. If they arrive faster, it grows every day.

Small gaps matter. In the worked example, a difference of 24 tickets a day clears 480 tickets in 4 weeks, and a gap of −12 adds 60 tickets every week. Look at the net change first, not at the backlog size.

Bring fewer tickets in

Find the questions that arrive again and again and answer them before they become tickets: a clear help page, order status the customer can check alone, an AI agent on the website that answers prices, delivery and opening hours. Fix the cause of the most common problem when you can.

Resolve more tickets

Block focused time for the queue, close tickets as soon as the work is done and move stuck ones to someone who can solve them. For tickets waiting on the customer, MetricNet’s Jeff Rumburg suggests following up weekly and closing the ticket if there is no answer.

Add capacity for a while

A clean-up sprint with extra people or overtime clears the existing backlog. It only lasts if the daily balance is fixed too, otherwise the queue grows back.

Rule of thumb from the formula: the backlog only shrinks when resolved per day is higher than new per day. Every other number on this page follows from that gap.

Benchmarks

What is a healthy ticket backlog?

There is no single published number that fits every team. These are the ways recognised sources measure it.

Size relative to demand. For first-level support, MetricNet’s Jeff Rumburg measures the average backlog as a percentage of average daily ticket volume. His example: 10 open tickets at the end of the day with 200 tickets a day is 5%. The calculator shows the same ratio as days of incoming work.

Age. For other support levels, Rumburg also splits the backlog by age: under 10 days, 10 to 30 days and over 30 days. There should be fewer tickets in each older group, and his target for tickets older than 30 days is zero. Zendesk offers a ready-made report for tickets unsolved for more than three days for the same reason.

Trend. Zendesk reports the backlog as a snapshot of unsolved tickets at the end of each day, so you can see whether it grows or shrinks over weeks. A single day’s number says little.

Not necessarily zero. In a Zendesk article on backlogs, advocacy manager Collin Murray says that a ticket queue of zero isn’t exactly healthy. Use the “backlog you’re fine to keep” field for the level that is normal for your team.

How long does a new ticket wait?

Little’s law from queueing theory says that the average number of items in a system equals the arrival rate times the average time each item spends there. Turned around, a queue of 480 tickets with 144 resolved a day means a new ticket waits about 480 ÷ 144 = 3.33 working days if tickets are handled in order. If that is longer than your SLA, the backlog is too big, whatever its absolute size.

Spreadsheets

Ticket backlog formulas for Excel and Google Sheets

Backlog in B2, new tickets per day in C2, resolved per day in D2, start date in E2, target days in F2, tickets per agent per day in G2 and a week number in H2.

WhatFormulaExample result
Net change per day=C2-D2−24
Days to clear (only if D2 > C2)=B2/(D2-C2)20
Date it clears, Mon–Fri (format as date)=WORKDAY(E2,ROUNDUP(B2/(D2-C2),0)-1)12/18/2026
Resolved per day needed for the target=C2+B2/F2168
Extra agents needed=ROUNDUP((C2+B2/F2-D2)/G2,0)2
Days of incoming work=B2/C24
Backlog after week H2 (5-day week)=MAX(0,B2+5*H2*(C2-D2))240 (week 2)

WORKDAY counts Monday to Friday and treats the start date as day 0, which is why the formula subtracts 1. To skip public holidays, add a range with their dates as the third argument. The CSV download in the calculator holds every number from your result, including the weekly projection.

FAQ

Ticket backlog questions

How do you calculate a ticket backlog?

Count the tickets that are not solved or closed at a point in time, for example at the end of each day. Tomorrow’s backlog is today’s backlog plus new tickets minus solved tickets: 155 + 34 − 24 = 165 in Zendesk’s example.

How long will it take to clear my backlog?

Divide the backlog by the difference between tickets resolved and tickets received per working day. 480 open tickets with 144 resolved and 120 new a day take 480 ÷ 24 = 20 working days.

Why is my backlog not going down?

Because new tickets arrive as fast as, or faster than, your team resolves them. Then the backlog never clears, however long you wait. Reduce incoming tickets, raise daily throughput, or both.

What is a healthy ticket backlog?

There is no single standard. MetricNet measures the backlog as a share of daily ticket volume and by age, with a target of zero tickets older than 30 days. Compare your days of incoming work and your oldest tickets with your SLA and your own past months.

How many agents do I need to clear the backlog by a deadline?

Work out the tickets per day you need: new tickets per day + backlog ÷ target days. Subtract what you resolve today and divide by the tickets one agent resolves per day, then round up. In the example: (168 − 144) ÷ 18 = 1.33, so 2 agents.

Should pending and on-hold tickets count?

Freshservice counts every ticket that is not resolved or closed. Decide whether tickets waiting for the customer belong in your backlog, and stay consistent. MetricNet suggests following up on them weekly and closing them if the customer does not reply.

Does the calculator store my data?

No. Everything runs in your browser. The share link keeps your numbers in the address after the # sign, which is not sent to our server.

References

Sources

  1. Backlog as unsolved tickets at the end of each day; the next day’s backlog = backlog + new tickets − solved tickets (155 + 34 − 24 = 165): Zendesk, Backlog Evolution report
  2. Backlog as a snapshot of unsolved tickets at the end of any given date: Zendesk, "Analyzing your ticket backlog history with Explore"
  3. Report on tickets unsolved for more than three days: Zendesk, "Explore recipe: Tickets unsolved for more than three days"
  4. Backlog as a percentage of daily volume (10 ÷ 200 = 5%), age groups under 10, 10–30 and over 30 days, a target of zero tickets older than 30 days, weekly follow-up on waiting tickets: Jeff Rumburg, MetricNet, HDI, "Metric of the Month: Ticket Backlog"
  5. Backlog tickets as all tickets not in resolved or closed status: Freshservice, "How are backlog tickets in the reports calculated?"
  6. "Having a ticket queue of zero isn’t exactly healthy", Collin Murray: Brett Grossfeld, Zendesk, "Time to tackle your ticket backlog"
  7. L = λW, items in a system = arrival rate × time in the system: John D. C. Little, "Little’s Law as Viewed on Its 50th Anniversary", Operations Research, 2011

More free support tools

Related guides and templates

Answer visitors before they leave.

Start on the Free plan: an AI agent answers questions on your website day and night and saves every conversation to one CRM, so your team can follow up. No credit card.

Start free →