research

Measuring the share of support requests that arrive outside the ticket queue

A method for counting the requests that arrive by chat, phone, and corridor conversations, so staffing and reporting reflect the work the helpdesk actually does.

Short answer

Use this benchmark to size repeatable IT work, set the review cadence, and decide what stays with the technical owner before assigning the workflow to an IT virtual assistant.

Research playbook

MeasureVolume and handling time
OwnerTechnical manager validates
Risk ruleName sensitive access
RefreshQuarterly benchmark review
On this pageJump to section

Key stats

Study period2 weeksStudy protocol
Log fields4 per requestStudy protocol
Reason groups5 categoriesStudy protocol

Key takeaways

A helpdesk report can look calm while the team is buried in chat messages and phone calls that never became tickets. Those requests consume the same time as a ticket, but they do not appear in the volume, the response time, or the backlog. This study measures the share of support work that arrives outside the ticket queue. The result helps an IT manager compare staffing with the real demand rather than the recorded demand.

Question and scope

This study asks what share of support requests reaches the team outside the ticket queue, through which channels, and which requests are most likely to bypass it. The unit is one request for help, regardless of how it arrived. The population is every request handled by the support team during a declared two-week period. The result describes that team and that period, not the discipline of any individual user.

Choose a period that includes a normal mix of busy and quiet days, and avoid a week with a major outage unless the study is about outages. Record the start and end dates and the team members included. Exclude project work that was planned in advance. A clear boundary keeps the count from turning into a general productivity survey.

Define a request and a channel

Define a request as any contact that asks the team to diagnose, fix, explain, or grant something. Include a question that takes two minutes and a request that turns into a change. List the channels in advance, such as the ticket portal, email, chat, phone, walk-up, and a message to a personal number. A channel that is not listed will be undercounted.

Decide whether a follow-up on an existing request counts as a new request. The simplest rule is to count the first contact as the request and note follow-ups separately. Record the rule beside the count so a reviewer can reproduce it. Ambiguity at this step is the main reason channel studies disagree.

Collect the evidence

Ask each team member to log every non-ticket request during the study period on a shared form with the time, channel, requester, and a one-line description. Keep the form to four fields so it is completed during the day. Add the ticket identifier when a request later becomes a ticket. A form that takes a minute will be filled in, while a detailed survey will not.

Pull the ticket count from the system for the same period and subtract the requests that were created from a logged contact. Compare the two counts at the end of each day so a missed entry can be fixed while the memory is fresh. Record the source of each number. The daily check is more reliable than a reconstruction at the end of the fortnight.

Match duplicate requests

Match requests that arrived through more than one channel, such as a chat message followed by an email. Use the requester, the subject, and the time window to identify duplicates. Count the request once and record the channels it used. A duplicate that is counted twice will overstate the share of informal work.

Keep a short list of the matches and the rule used to decide. Ask a second person to review the ambiguous matches. Record the number of duplicates as its own figure, because a high duplicate rate is a finding about the intake process. The match should reduce noise without hiding a real second request.

Classify the reason

Tag each non-ticket request with a reason such as urgency, a broken portal, a user who did not know the process, a request that seemed too small, or a message to a known person. Use a short list and allow one primary reason per request. The distribution shows whether the fix belongs in the tool, the communication, or the team's habits. Record who assigned the tag so an unclear case can be reviewed later.

Review the reasons with the team before publishing them. A reason such as user did not follow the process can sound like blame and discourage honest logging. Use neutral labels that describe the situation. The purpose is to remove friction from the ticket path, not to scold the people who avoided it.

Estimate the untracked share

Divide the matched non-ticket requests by the total requests, including the ticket queue. Report the share with a range that reflects the days with incomplete logging. Show the share by channel and by reason. A single percentage is easy to quote but hard to act on without the breakdown.

Calculate the time as well as the count, using a simple estimate per request and a note that it is an estimate. Compare the time with the ticket workload rather than treating it as extra. If the untracked share is large, the team may already be working at capacity while the report shows room. Present the count first and the time second.

Show the daily counts on a simple chart so the reader can see whether the logging was consistent. A day with almost no entries is more likely a missing log than a quiet day. Mark those days and exclude them from the headline share, while keeping them in the appendix. Transparency about the weak days makes the estimate easier to trust.

Compare with staffing

Compare the total request volume, including untracked work, with the hours the team actually has for support. Use the same period and the same team roster. Note the time spent on planned work and meetings so the comparison is honest. A staffing model built on ticket volume alone will underestimate the load.

Look at the peak hours and days for non-ticket requests. If informal requests cluster when a senior person is available, the intake path may depend on that person rather than on a process. Report the pattern to the manager with the channel data. The answer may be a better portal, a clearer service catalogue, or a scheduled walk-up hour.

Check whether the informal requests cluster around one team member or one time of day. A cluster may mean that users know who will answer quickly, not that the ticket path is hard to find. Note the pattern and the person or shift it involves. The observation helps the manager decide whether to change the tool or the rota.

Report to the owner

Lead with the share of requests outside the queue, the top two channels, and the most common reason. Add one example of a small request that consumed time and one that became a ticket later. Keep individual names out of the summary and use team-level figures. The report should be short enough to read before the next staffing meeting.

Ask for one specific change, such as fixing the portal sign-in, publishing a short intake guide, or adding a chat-to-ticket step. Name the owner and the date for the next measurement. If the decision is to leave the channels as they are, record the reason and the expected load. The next study can then test whether the choice held.

Limits and next use

The study depends on team members remembering to log informal contacts, so it likely undercounts the smallest requests. It also cannot capture help that was given by someone outside the support team. The time estimates are approximate and should not be used as a billing figure. State those limits so the result is read as a direction rather than a precise audit.

Repeat the study after the intake change and compare the same channels and reasons. A fall in informal requests without a rise in ticket volume may mean the change worked, or it may mean people stopped asking. Check both numbers together. Record the study dates so the comparison is not confused with a seasonal change.

Sources and next step

Use the NIST Cybersecurity Framework 2.0 and the CISA Cross-Sector Cybersecurity Performance Goals as primary references for the identity, platform support, request intake, data export, and licence inventory controls discussed here. The NIST SP 800-53 Rev. 5 supports the access and audit record checks, and the GAO data reliability guidance supports the sampling and verification approach used in these methods. Apply your own policies, contracts, and system documentation when adapting the method.

Compare this study with the access revocation measurement and the software licence entitlement audit before combining them into one review cycle. If the measurement work is recurring and your technical owner can define the scope, review the service areas and contact ITVirtualAssistant to discuss a limited pilot.

Benchmark brief

What this research page must produce

Working number

A practical estimate for volume, review time, escalation rate, and assistant capacity.

Operating boundary

A clear split between routine support, preparation work, and technical ownership.

What the measuring the share of support requests that arrive outside the ticket queue data shows

Treat this as a planning benchmark, not a universal number. Compare the benchmark against your ticket volume, SaaS stack, documentation backlog, and support risk before assigning recurring work.

The useful output is a decision about capacity, not a static statistic. If the workflow is high volume and low judgment, an IT virtual assistant can absorb coordination and upkeep. If the workflow is low volume but high risk, keep it with the technical owner and use the assistant only for preparation, reminders, and documentation.

Workflow

Recommended operating workflow

1

Collect a baseline

Pull the last 30 to 90 days of examples related to measuring the share of support requests that arrive outside the ticket queue, including completed work and unresolved exceptions.

2

Classify the work

Tag each item by routine admin, manager approval, technical decision, security risk, or vendor dependency.

3

Set the operating number

Use the median weekly volume and review time to decide how many assistant hours the workflow deserves.

4

Refresh the benchmark

Recheck the numbers quarterly so tool growth, new systems, and security requirements do not silently change the scope.

Decision rules

MetricUse it to decideManager action
Weekly volumeWhether the workflow is worth assigning as recurring assistant work.Approve a weekly capacity target and backlog threshold.
Access sensitivityWhether the assistant can work directly or only prepare review notes.Set least-privilege permissions and removal dates.
Escalation rateWhether the workflow is stable enough to delegate.Rewrite the SOP when exceptions exceed the agreed threshold.

Consolidated statistics

StatisticFigureSource
Study period2 weeksStudy protocol
Log fields4 per requestStudy protocol
Reason groups5 categoriesStudy protocol

Sources

  1. NIST SP 800-53 Rev. 5Incident handling and operational event tracking controls.
  2. CISA Cross-Sector Cybersecurity Performance GoalsIncident reporting and response goals for small organizations.
  3. NIST Cybersecurity Framework 2.0Response and continuous improvement outcomes for support operations.
  4. GAO Assessing Data ReliabilityData collection and estimation checks for the request count.
  5. SBA Strengthen Your CybersecurityPractical guidance for small-business security and support practices.

Measurement checklist

FieldWhat to captureOwner
VolumeWeekly request count, backlog age, and repeat issue patternsAssistant prepares, manager reviews
RiskAccess level, customer impact, security sensitivity, and approval needsTechnical owner
CadenceDaily, weekly, monthly, or quarterly review rhythmManager
EvidenceSample tickets, logs, screenshots, and before-after examplesAssistant collects, owner validates
EscalationTriggers, approval path, response time, and stop-work rulesTechnical owner

How to read the result

A good research page should leave the manager with a working number and a clear boundary: what the assistant can do every week, what the assistant can prepare for review, and what must never move without the accountable technical owner.

Source and refresh note

This planning page is dated for 2026 and should be refreshed quarterly as tool stacks, ticket patterns, and security expectations change.

How should teams use this benchmark?

Use it to define task volume, access limits, review cadence, and escalation rules before assigning work.

Get free benchmark review