Macha
CX & Support Metrics

Backlog Rate

Definition

Backlog rate is a measure of how the volume of unresolved support tickets is changing — typically the ratio of open or incoming tickets to those being resolved over the same period.

Also known as: backlog ratioqueue growth rate

How to calculate it

One common form is the reply/received ratio: tickets resolved ÷ tickets received in a period. Below 100% means the backlog is growing (you're closing fewer than arrive); above 100% means it's shrinking.

For example, if 800 tickets arrive in a week and the team resolves 720, the ratio is 90% — the backlog grew by 80 tickets. Some teams instead express backlog rate as open tickets relative to volume.

Why it matters

Backlog rate is an early-warning signal. A ratio consistently under 100% means the queue is compounding — ticket aging worsens, SLAs come under pressure, and CSAT eventually follows. Catching a growing backlog early lets teams add capacity or automation before it snowballs.

Frequently asked

What backlog rate is healthy?

A resolved-to-received ratio at or above 100% keeps the backlog stable or shrinking. Sustained readings below 100% mean the queue is growing and needs more capacity or automation.

How is backlog rate different from ticket backlog?

Ticket backlog is the count of unresolved tickets at a point in time; backlog rate is about the direction — whether that count is rising or falling relative to incoming volume.

Put these ideas to work

Macha is an AI agent layer that sits on top of the help desk you already run — Zendesk, Freshdesk, Front, Intercom, or Gorgias.

Start Trial