Call operations research
Measuring how often callers ask whether a manager is available
A measurement method for manager-availability requests, covering need codes, routing outcomes, wait time, and escalation criteria.

Table of contents
A request for a manager can be a request for authority, recognition, or speed. The words are the same, but the route is different. Measuring the requests without measuring the need produces a number that cannot guide staffing. A small code set and a clear outcome measure make the data useful.
Key takeaways
- Count the request at the first mention of a manager.
- Code the need behind the request, not only the words.
- Measure whether the caller reached a decision-maker.
- Track the promised and actual response window.
- Keep urgent exceptions separate from routine requests.
Research question and scope
The question is how often callers ask whether a manager is available and what they need. The unit is the call with at least one manager request. A call with two requests is still one call, but the second need is noted. The coding should not double-count the same conversation.
The scope covers inbound calls to a general queue. It includes requests for owners, supervisors, and duty managers. It excludes calls that arrive on a manager's direct line. A direct line changes the meaning of the request.
Record the queue, the business hours, and the escalation rules. A small office may have one manager on call. A larger office may have a duty roster. The rules shape both the request rate and the response time.
Definitions and coding
Define a manager request as an explicit ask to speak with someone in authority. A request for "someone in charge" counts. A request for a named supervisor counts if the person has authority. A request for a different agent does not count unless the caller asks for a manager.
Define the need as the outcome the caller wants from the manager. Common codes include decision, complaint, exception, safety, and unknown. The need helps explain the route. It also shows whether the manager is the right owner.
Define a reached request as one where a person with authority spoke with the caller during the call. Define a scheduled request as one with an agreed window. A message in a general queue is neither reached nor scheduled. The manager script gives the operational detail.
Sampling and data collection
Select calls from a fixed period and a fixed queue. Include every request if the volume is small. Draw a random sample if the volume is large. Keep the export filter and date in the report so the result can be reproduced.
Use the call note as the primary source. Use the phone log to confirm the transfer or the scheduled callback. A note can claim a transfer that did not connect. The log is a useful cross-check, and the data reliability guidance supports that step.
Do not copy the caller's sensitive details into the audit file. Use a record identifier. The study needs the need code and the outcome, not the full complaint. This keeps the measurement inside the office's access rules.
Measures and reporting
Report the number of calls with a manager request and the share of all calls. Show the count beside the share. A rate from a small sample can look large without being stable. Group the results by week and by queue where possible.
Report the outcome for each request: reached, scheduled, message only, or unresolved. The four categories are more informative than a single success rate. They show where the process breaks. A high message-only rate may mean the schedule is the problem.
Report the promised and actual response window. A same-day response is different from a three-day response. Show the distribution rather than only the average. The first-call resolution study offers a related outcome lens.
Urgent exceptions
Keep a separate count for urgent requests. A safety issue or a service outage may need an immediate route. Mixing urgent cases with routine requests hides both patterns. The urgent count should have its own criteria and owner.
Review the urgent cases weekly. Check whether the criteria were applied correctly. A high volume may mean the normal route is too slow. A low volume may mean the criteria are too narrow. The callback completion study shows how to track a related promise.
Record the time from the request to the first contact by the on-call owner. A fast response is part of the service. A slow response is a process failure even if the caller eventually gets help. Report the time with the outcome.
Limitations
The study cannot show why the caller asked for a manager. The note may contain a reason, but the reason is the caller's account. Treat it as context, not as a cause. A pattern across many calls is more useful than a single explanation.
The sample may exclude callers who gave up before asking. Those callers never entered the count. Pair the request count with the total call volume and the abandonment count. A low request rate may simply mean fewer callers reached the queue.
The manager's availability may change during the period. A vacation or a new duty roster can shift the result. Record the roster version and the dates. The comparison should separate availability from demand. The abandoned call review discusses a similar selection issue.
Repeating the study
Repeat the study after a routing change with the same definitions. A new escalation rule can shift the request rate. Keep the sample window and the queue constant. The comparison should be reproducible.
Share the result with the front desk and the managers. Ask which requests could have been handled by another team. Their answers often reveal a faster route. Then change one step and measure again.
The aim is not to reduce requests for a manager. The aim is to route each request to the right authority. A caller who asks for a manager is telling the office that something needs a decision. Measure the need, fix the route, and check whether the next caller gets an answer.