Small-business outsourcing research
How often do customer voicemails wait more than one business day for a reply?
A protocol for measuring voicemail reply delay, the handoff between phone and inbox, and the calls that never get a recorded outcome.

Research question and scope
This protocol asks how often a customer voicemail waits more than one business day for a reply. The unit is one voicemail message, identified by the caller, the phone line, and the time the message was left. The study measures the first reply attempt, the channel used, and whether the caller reached a person or only a recording. It does not evaluate whether the customer's request was reasonable.
Set the scope to one small business, one phone system, and one inbox where messages are logged. Record the business hours, the holiday calendar, and the expected reply time at the start. If the schedule changes during the window, keep the earlier definition for the full sample or analyze the change as a separate period. A new auto-reply can look like a faster response when it is only a new message.
Population and unit of analysis
Define the population as every voicemail left on a customer-facing line during the window, including messages that were returned and messages that were never answered. The unit is the voicemail, not the caller, because a caller can leave several messages. A message that is forwarded to another team remains one unit with a handoff interval. A return call that reaches voicemail again is a new contact attempt, not a new original message.
Record the phone line, the day of week, the time of day, and whether the caller was an existing customer. These strata matter because a sales line and a support line carry different expectations. Include messages that arrived after hours, because the clock should start at the next business opening. Test the unit definition on two ordinary messages before collection begins.
A caller can leave a message on a general line and then call a direct number, which creates two units for one issue. Record the related message and link the units so the delay is not counted twice. Do not merge messages that describe different requests, even when the same person left them. The link should show the relationship without erasing either record.
Definitions that make the measure reproducible
Define the start time as the moment the voicemail was recorded in the phone system. Define the first reply attempt as the first outbound call, message, or email that references the voicemail. Define a business day as a weekday excluding the holidays on the recorded calendar. Define a late reply as a first attempt after the next business day has ended.
Do not count an internal note as a reply attempt. Do not count a generic auto-reply as a customer response. A call that rings without an answer is an attempt only when the phone system records it. Each definition should include one positive example and one boundary example so a second reviewer can apply it consistently.
Evidence standard and data dictionary
For each voicemail, capture the caller, the phone line, the timestamp, the duration, and the call-back number. Add the first reply time, the channel, the person who replied, and whether the caller answered. Record the outcome and whether the message was linked to an existing customer record. Keep the call log with the inbox note.
Also capture whether the voicemail was transcribed and whether the transcription was accurate enough to act on. A message that requires repeated listening is a different delay risk. If the call was returned from a personal phone, record that fact and the business number used. A second reviewer should be able to rebuild the timeline from the call log.
If calls are recorded, check the consent notice and the retention rule before transcription. A recording that cannot be used is not evidence, and a transcript without the audio is harder to verify. Record the system that stores the message and the person who can retrieve it. The packet should be usable by someone who was not on the shift.
Sampling and collection
Draw the sample from the phone system rather than from a list of complaints. Record the export date, the filters, the row count, and the selection rule. Include messages from every line and every day of the week so the result is not dominated by one busy period. If the population is ordered by time, a fixed interval spreads the sample across the window.
Collect the message and the reply as they existed at the time, not as they look after a later cleanup. If the inbox note was added days later, record the addition date and analyze the original delay separately. Do not infer a reply from a customer who called again. Note the collection date separately from the message date.
Analysis and reporting
Report the number of voicemails, the share replied within one business day, the share replied later, and the share with no recorded reply. Show the counts by phone line, time of day, and customer type. Present the median time to first attempt and the share of callers who answered. Use the same denominator for every rate.
Inspect the late messages and describe the pattern without naming the caller or the assistant. A cluster on one line may point to an ownership gap, while a cluster after a certain hour may point to a handoff that stops at the end of the day. Compare the result with the day of week, because a Friday message has fewer business hours before the deadline. Report the after-hours messages separately.
A useful additional view is the share of messages that were returned but never closed. A return call without a recorded outcome can leave the customer waiting for a second contact. Show the closure rate beside the reply rate and describe the difference. That view helps the owner decide whether the problem is speed or follow-through.
A useful cut is the hour of day when the message arrived. A message at four in the afternoon has far less of the first business day left than one at nine in the morning. Show the arrival hour beside the reply rate and describe the pattern. That view helps the owner decide whether the phone coverage or the end-of-day handoff needs the change.
Limitations and sources of error
The record cannot show whether the customer was satisfied or whether the issue was resolved on the first call. It can show only when the first attempt happened and what was recorded. A fast reply is not proof of good service, and a late reply is not proof of neglect. The protocol also cannot capture a call that was returned from a personal phone and never noted.
Phone systems can mislabel the time zone, drop a message, or record a call attempt without a duration. A message that appears unanswered may have been returned through another channel. Record those cases and their treatment instead of dropping them silently. If the same person listens to the messages and returns the calls, note the independence limitation and analyze that subgroup separately.
Review cadence and next action
Give the result to the owner and the person who covers the phone and ask them to choose one observable change. The change might be a named owner for each line, a next-business-day rule, or a required outcome field. Record the owner, the effective date, and the measure that will show whether the change worked. Avoid changing the line ownership and the reply standard at the same time.
Repeat the protocol with the same definitions after the change and compare the same fields. If the reply time fell but the closure rate did not, the team may be calling back without solving the issue. If closure improved but reply time rose, the new outcome step may be adding work. Close the review when the owner accepts the finding and the next sample is scheduled.
Give the cover person the same protocol and a short list of the lines they own during the leave. A cover plan that changes the measurement halfway through the week produces a result nobody can compare. Record the cover dates, the lines covered, and the person who approved the temporary ownership. The next review should use the same definitions and the same sample method.
Sources
- Federal Trade Commission, business guidance, Federal Trade Commission; checked 2026-11-06
- U.S. Small Business Administration, manage your business, U.S. Small Business Administration; checked 2026-11-06
- U.S. Government Accountability Office, internal control standards, U.S. Government Accountability Office; checked 2026-11-06
- U.S. Department of Labor, Wage and Hour Division, U.S. Department of Labor; checked 2026-11-06
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
What share of supplier records contain a usable contact and payment term?
A protocol for measuring supplier master data quality, with clear tests for a usable contact, a current term, and an approved bank record.
How often does a task handoff note name an owner and a due date?
A protocol for measuring handoff note completeness, including the next action, the named owner, the due date, and the evidence attached.
How much shared-inbox work sits unassigned after one business day?
A protocol for measuring unassigned shared-inbox work, the age of the backlog, and whether a named owner picks up each conversation.