Agent vs Requester Wait Time

Agent Wait Time and Requester Wait Time measure different waiting periods in customer service or support systems. Agent Wait Time tracks how long support agents are idle between handling requests, indicating potential workforce inefficiency or overstaffing. Requester Wait Time measures how long customers or users wait before their issue is addressed by an agent, directly reflecting the customer experience and service quality. While one focuses on agent productivity and resource allocation, the other emphasizes customer satisfaction and service responsiveness.

A customer support manager should focus on Agent Wait Time when evaluating staffing levels or agent productivity, particularly when looking to optimize costs or workforce efficiency. For instance, consistently high Agent Wait Times might indicate overstaffing during certain shifts, suggesting a need to redistribute resources. In contrast, Requester Wait Time should be prioritized when assessing customer experience and satisfaction metrics, especially during peak periods or after implementing new support processes. If a company notices increasing Requester Wait Times despite reasonable Agent Wait Times, this might indicate inefficient ticket routing or skill matching rather than simple understaffing, requiring process improvements rather than just hiring more agents.

Agent Wait Time

Requester Wait Time

What is it?

Agent Wait Time is the total combined time a support ticket spends in pending status, waiting for a response from the requester. Unlike customer-facing metrics such as First Response Time or Resolution Time, Agent Wait Time measures how long the support agent waits between interactions. High pending time reduces agent efficiency and makes it harder to maintain context across complex tickets.

Requester Wait Time is the total combined time a ticket spends in the new, open, and on-hold statuses, measured until the ticket reaches a pending, solved, or closed status. It excludes pending time, which is when the ticket is waiting on the requester to reply, making it a direct measure of support team responsiveness rather than total ticket lifespan.

Formula

ƒ Sum(total time a ticket was in pending status)
ƒ Sum(total time a ticket is in new, open, and on-hold status)

Example

A support agent responds to a ticket and waits 4 hours for the requester to reply. After that reply, the agent spends another 26 hours gathering necessary information before responding again. The ticket is in pending status for both intervals. Total Agent Wait Time: 4 + 26 = 30 hours. That figure shows how much of the ticket's lifecycle was spent waiting rather than being actively worked on.

A user submits a ticket at 9:00 AM. A support agent is assigned and the ticket moves through new and open statuses. At 10:00 AM the agent replies and the ticket moves to pending — the user now needs to respond.

At 12:00 PM the user replies, reopening the ticket to open status. At 2:00 PM the agent fully resolves the issue and marks the ticket as solved.

Requester Wait Time = 1 hour (9:00–10:00 AM) + 2 hours (12:00–2:00 PM) = 3 hours

The 2-hour pending window (10:00 AM–12:00 PM) is excluded because the requester — not the support team — was responsible for the delay.

Track this metric

Published and updated dates

Date created: Jan 23, 2023

Latest update: Jun 12, 2026

Date created: Jan 23, 2023

Latest update: Jun 12, 2026