Small-business outsourcing research

How complete is the call-back record for missed small-business inquiries?

A protocol for measuring whether every missed call gets a complete call-back record, a named owner, and a confirmed customer contact.

Research question and scope

This protocol asks how complete the call-back record is for inquiries that arrive by phone and are not answered live. The unit is one missed inquiry inside a defined observation window. The study measures whether the record captures the caller, the reason, the callback time, the owner, and the outcome. It does not evaluate whether the business should have answered the call in the first place.

Set the scope to one small business, one phone line, and one intake process. Record the phone system, the voicemail or missed-call notification, and the customer record in force at the start. If the process changes during the window, keep the earlier definition for the full sample or analyze the change as a separate period. A new phone menu can change the call mix without changing the team's behavior.

Population and unit of analysis

Define the population as all inbound calls that were not answered live during business hours, including calls that left a voicemail and calls that did not. The unit is the missed inquiry, identified by the phone number, the date, and the time. A caller who calls twice about the same issue is one inquiry with two attempts, unless the second call is about a different matter. A call from an existing customer about a new issue is a new unit.

Record the caller type, the reason, the time of day, and whether the caller left a message. These strata matter because a missed supplier call and a missed new-customer call carry different urgency. Include calls that were returned within the same day and calls that were never returned. Test the unit definition on two ordinary days before collection begins.

Definitions that make the measure reproducible

Define a complete call-back record as one that contains the caller's name and number, the reason for the call, the time of the missed call, the time of the return call, the person who returned it, and the outcome. Define a contact as a two-way conversation, not a voicemail left by the business. Define closure as the point where the caller's question is answered or a next step is agreed. Record who confirmed the closure and when. A voicemail or an unanswered attempt remains an open event.

Do not count a note that says called back without the time and the person. Do not count an email as a call-back unless the caller asked for email. A record with a phone number but no reason is incomplete because the next person cannot prepare. Each definition should include one positive example and one boundary example so a second coder can apply it consistently.

Evidence standard and data dictionary

For each missed inquiry, capture the caller number, the caller type, the date and time, the reason, the message flag, the return time, the owner, and the outcome. Add the number of attempts and whether the caller was reached. Record whether the inquiry became a quote, an order, a support ticket, or no action. Code each field as present, missing, or not applicable.

Also record whether the call was returned within the business's stated window and whether the caller asked not to be called again. These fields matter for both service quality and privacy. If the reason is unknown, record the exact words from the voicemail rather than a guess. A second coder should be able to classify the inquiry from the record without listening to the call.

Sampling and collection

Draw the sample from the phone system and the customer record rather than from a list of memorable calls. Record the export date, the filters, the row count, and the selection rule. Include days with different volumes so the result is not dominated by a single busy Monday. If the population is ordered by call time, a fixed interval spreads the sample across the window.

Collect the phone log and the customer record as they existed at the time of the call. Do not reconstruct a missing call-back from memory or from a later sales note. If a voicemail was deleted, record the deletion and the metadata. Note the collection date separately from the call date so the reader can see how much of the record has aged.

Analysis and reporting

Report the number of missed inquiries, the share with a complete record, the share returned within the stated window, and the share where the caller was reached. Show the counts by caller type and by day of week. Present the median time to return a call and the number of inquiries with no recorded outcome. Use the same denominator for every rate.

Inspect the inquiries with no return call and describe the pattern without naming the caller. A cluster on one day may point to a staffing gap, while a cluster in one reason category may point to a missing script. Compare the result with the business's stated callback window, because a record can be complete and still late. Report the inquiries that became quotes or orders separately.

Limitations and sources of error

The record cannot show whether the caller went to a competitor or whether the business would have won the work. It can show only whether the call was recorded and returned. A complete record is not proof of a good conversation, and an incomplete one is not proof that the caller was ignored. The protocol also cannot capture calls that went to a personal mobile phone outside the system.

Phone logs can omit calls that were answered by another line, transferred, or blocked. A caller who reached a person directly may never appear in the missed-call list. Record those cases and their treatment instead of dropping them silently. If the same person answers the phone and completes the record, note the independence limitation and analyze that subgroup separately.

Review cadence and next action

Give the result to the owner and the person who handles the phone. Ask them to choose one observable change, such as a required reason field, a daily call-back list, or a shorter return window. Record the owner, the effective date, and the measure that will show whether the change worked. Avoid changing the phone menu and the record template at the same time.

Repeat the protocol with the same definitions after the change and compare the same fields. If completeness improved but contact did not, the team may be writing better notes without calling faster. If contact improved but outcomes did not, the conversation may need a better script. Close the review when the owner accepts the finding and the next sample is scheduled.

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