Zendesk Backlog by Ticket Form Report

Total backlog tells you how much work is open right now. Backlog by ticket form tells you which intake flows are actually creating that pressure.

That matters because a queue can look manageable overall while one specific form quietly collects old tickets. Those aging tickets might be attached to one request type, one internal dependency, or one broken intake path. If you only look at total backlog, you miss the part of the system that is creating most of the drag.

This guide shows how to build a Zendesk backlog by ticket form report, how to interpret it, and how to use it to fix the forms that keep work stuck open.

What this report should answer

A useful backlog-by-ticket-form report should answer:

Which ticket forms hold the most open work?
Which forms contain the oldest tickets?
Is backlog concentration getting worse in a few intake paths even while total backlog looks stable?
Are the worst forms also showing slow first reply time, slow resolution, or high SLA pressure?

For the base definition, see backlog. For trend context, keep backlog burn-down rate and queue velocity nearby.

Why ticket-form-level backlog matters

Backlog is rarely random. It usually accumulates where workflow friction already exists:

forms that create incomplete intake
request types that need specialist review
forms tied to approval-heavy processes
low-priority forms that nobody actively owns

When you review only total open tickets, the queue can look fine because fast-moving forms offset the ones that are quietly stalling. Form-level backlog reporting shows where work actually sits.

How to build the report in Zendesk

Use the Support: Tickets dataset in Zendesk Explore. Review the report weekly and pair it with an aging view whenever you want to see whether backlog is becoming stale.

1. Group open tickets by ticket form

Use ticket form as the main row dimension and filter to open, pending, or unsolved work according to how your team defines backlog.

2. Add an aging lens

Ticket count alone is not enough. Pair backlog size with age buckets so you can see whether a form is holding recent work or truly stale work. For the deeper aging setup, see Zendesk Backlog Aging Report.

3. Pair backlog with inflow

Always compare:

current backlog by form
tickets created by form
tickets solved by form

This helps you tell the difference between a form that simply has more demand and a form that is not moving through the workflow effectively.

4. Add routing context

The most useful supporting cuts are:

assigned group
priority
channel
requester segment
status or time in status

These show whether the problem comes from intake design, queue ownership, or downstream process friction.

5. Trend the concentration over time

A one-week spike may be noise. A form that keeps accumulating open work over several weeks is a structural problem. Trend it so you can see whether the concentration is stable, worsening, or improving.

The most useful report layouts

Backlog by ticket form

This is the main operating view. It shows which forms are holding the most open work.

Backlog by ticket form with aging buckets

This is often the most actionable layout because it reveals whether a form has a lot of fresh demand or a genuine pile of stale tickets.

Backlog by ticket form and assigned group

Use this when you need to see whether the intake path itself is the issue or whether one owner queue is failing to move the work.

Backlog by ticket form and inflow vs outflow

This helps you understand whether the form is building pressure because demand is rising or because throughput is weakening.

How to interpret the patterns

One form holds most of the backlog

That is an important operating signal even if the total queue does not look extreme. A single intake path is creating disproportionate pressure.

One form has moderate backlog, but very old tickets

That often matters more than a large form with fast turnover. The tickets are not just open; they are stalled.

One form has high inflow and rising backlog

This may be a capacity issue, a sudden product problem, or a form that is channeling demand into a narrow specialist queue.

One form builds backlog while the overall queue looks healthy

This is the hidden-concentration pattern. The rest of the queue is moving well enough to hide the fact that one intake path is already degrading.

Common mistakes

Looking only at total open tickets. That hides where the real pressure lives.
Ignoring age. Fresh backlog and stale backlog require different responses.
Treating volume as failure. A busy form is not automatically a broken form.
Skipping inflow and outflow context. Without flow, backlog is hard to interpret.
Using overly broad forms. Catch-all forms create blurry analysis and weak action plans.

What to do when a ticket form stands out

If one form repeatedly creates the most backlog:

Read actual tickets from that form before redesigning the workflow.
Check whether the issue is poor intake quality, specialist dependency, or ownership gaps.
Compare it with Zendesk First Reply Time by Ticket Form Report and Zendesk Resolution Time by Ticket Form Report.
Review whether the form needs clearer routing, better required fields, or capacity changes.
Track the backlog trend after the fix so the same form does not quietly regress.

The goal is not to eliminate backlog from every form equally. It is to identify the intake paths that are manufacturing queue drag faster than the rest of the system.

Where this report fits in your dashboard

This report works best beside:

Together, those views show which forms create open work, whether it is getting older, and whether the same forms are also slowing first touch or full resolution.

FAQ

Should I look at backlog count or backlog aging first?
Look at both, but aging usually tells the more urgent story. A modest backlog with many old tickets is often worse than a larger backlog that is still moving quickly.

What if one form always has more backlog because it is high volume?
That can be normal. The signal matters when backlog is rising faster than demand, staying older than expected, or pairing with slower first reply or resolution time.

How often should I review this report?
Weekly is the best baseline. During incidents, product launches, or seasonal spikes, daily review can help you catch one form building pressure before the whole queue feels it.

See which Zendesk ticket forms are quietly creating most of your open-work pressure - start free