Small-business outsourcing research

How long do service callback requests wait before a technician is assigned?

A protocol for measuring the wait between a customer callback request and the assignment of a technician who will make the call.

How long do service callback requests wait before a technician is assigned?

Research question and scope

This protocol asks how long a service callback request waits before a technician is assigned. The unit is one callback request, not one customer and not one repair job. The study measures the share assigned inside the shop's stated target, the median wait, and the requests that never received an owner. It does not judge whether the callback resolved the customer's problem.

Set the scope to one repair shop, one callback queue, and one assignment rule. Record the target time, the priority categories, and the date the rule took effect. If the shop changes its target during the study, keep the original target for requests already open and analyze later requests separately. A new scheduling tool can change the assignment speed without changing staffing.

Define the population as every callback request recorded during the window, including requests that were withdrawn or resolved by a message. State any exclusion, such as a supplier warranty call that did not involve the shop's technician, and apply it to every request. Test the definition on ten closed requests before collection begins. The reader should be able to rebuild the population from the queue.

Definitions that make the measure reproducible

Define a callback request as a customer message that asks the shop to call about a specific job, quote, or repair. Define assignment as a named technician accepting the request with a target call time. A note that says the request was seen is not an assignment. Record the exact moment the technician accepted the case.

Define the clock start as the time the request was recorded in the queue, not the time the customer first mentioned it in passing. Define the clock stop as the assignment time, not the time the customer was eventually reached. Treat a request reassigned to a second technician as one request with the first assignment date kept. A definition that stops at the call rather than the assignment will measure a different question.

Evidence standard and data dictionary

For each request, capture the request identifier, job identifier, customer, channel, received time, priority, assignment time, technician, and target call time. Add the outcome and whether the customer was reached. Keep the original customer message and the job history linked to the entry. Record any request that was merged with another request from the same customer.

Capture the reason for a delay when it is documented: no technician on shift, an unclear job history, a missing part number, or a queue that was not reviewed. Do not infer a reason from an empty field. Mark unknown reasons as unknown and report the count. A guessed reason hides the step that actually needs repair.

Sampling and collection

Collect every request in the window rather than a sample, because the assignment rule applies to each one. If the shop runs several service lines or locations, collect each separately and record the group. A combined rate can hide one line that never assigns until the next day. Report the number of requests behind every percentage.

Draw times from the queue and the scheduling system, not from a spreadsheet maintained after the fact. If either log is incomplete, say so and reduce the claim. Record the export date, the filters, and any request that could not be matched to an assignment. A missing log is itself a finding about the routine.

Analysis and reporting

Report the share assigned inside the target, the share assigned later, and the share never assigned. Show the median and range of hours from receipt to assignment. Present the results by service line, priority, and day of week. Use the same denominator for every rate.

Separate a request that waited because no technician was available from one that waited because nobody opened the queue. A staffing gap is a different finding from an unread queue. Report both because they lead to different fixes. A shop may accept a capacity limit but should not accept a silent backlog.

Limits of the evidence

The queue can show when a technician accepted the case, but it cannot show whether the call was helpful. An assignment is not a resolution. The protocol also cannot capture a callback arranged at the counter and never entered in the queue. State that limitation before presenting the rate.

A small shop may have too few requests to support a stable trend. Describe the request count and the service mix instead of ranking technicians. Do not compare a shop with a two-hour target with one that promises a next-day call. Report the target beside the rate.

What to change

Give the result to the owner and the shop lead and ask them to choose one observable change. The change might be a daily queue review, a named callback owner per shift, a required job history at intake, or a priority list agreed with the technicians. Record the owner, the effective date, and the measure that will show whether the change worked. Repeat the protocol with the same definitions.

If the on-time assignment rate rises but repeat callbacks also rise, the team may be assigning fast without enough history. If both fall but the never-assigned share shrinks, the queue may be clearing without a call. Report the movements together before declaring success. Close the review when the owner accepts the finding and the next collection date is set.

Sources

Frequently asked questions

Does a favorable sample prove the routine caused the result?

No. The design is observational and supports a bounded operating decision, not a universal causal claim.

What should an owner review first?

Start with high-consequence defects, missing denominators, exceptions, and cases that required the owner to reconstruct the evidence.

Related research