How old do callback promises become before a documented attempt?

Research question and evidence scope

How long does a callback promise wait before a documented call attempt? The scope is the callback register in one outsourced calling operation during a defined period, not an industry benchmark. The measure matters because a promise the customer has already heard is different from an internal task that can move without notice. The protocol describes the age of open promises and the stage where time accumulates.

This note does not decide whether a caller performed well or whether a customer was satisfied. Those questions require a wider review of call quality, staffing, and the customer relationship. The narrow purpose is to make the promise path visible so the team can fix the handoff or the coverage window with evidence. Record the definition and the sample size beside the result so a later reviewer can repeat the check.

The unit is one callback promise, from the moment it is recorded with the customer to the first documented attempt or the close. A promise that is rescheduled remains the same unit with an additional commitment, not a new unit. If a customer calls again and a new promise is made, keep the new promise separate and link it to the original. Keep the source reference with the observation rather than relying on a summary that may be edited later.

Operating scenario and evidence

Start with a dated export of promises recorded during the review window. Record the customer reference, the promise time, the time zone, the owner, the backup, the channel, and the reason. Include promises that were closed during the window so the review can compare open and closed aging. Exclude test records and internal reminders that were never spoken to a customer, and record those exclusions with reasons.

A promise begins when the caller confirms the time and channel with the customer. A promise closes when a documented attempt reaches the customer and the promised question is addressed, or when the customer agrees to a new time. A note that says 'left voicemail' is an attempt, not a close, unless the customer later confirms the new arrangement. State the observation window in the report so the reader can compare it with the next review.

Method and review criteria

Compute age in whole hours for same-day promises and in whole days for promises that cross a date boundary. Report the median, the 75th percentile, and bands such as under one hour, one to four hours, four to twenty-four hours, and over one day. Report the share of promises with no attempt inside the promised window separately, because a late attempt and a missing attempt are different failures. Separate the unavailable evidence from a confirmed negative before drawing a conclusion.

Split the age into wait before the promised window, wait inside the window, and wait after the window. The first two are often driven by scheduling and staffing, while the third is usually a handoff or ownership problem. The split shows which correction is likely to help instead of treating every late promise as a coaching issue. Name the owner of the next action so the finding does not become an orphaned observation.

Each record needs the promise text, the customer's time zone, the owner, the attempt time, the outcome, and the next action. If the attempt was recorded after the fact, mark the time as reconstructed and note who recorded it. A reconstructed time is weaker evidence than a system timestamp and should be reported separately. Preserve the original record when a definition changes and label the transition for later cases.

Authority and practical implications

Preserve reschedules and missed attempts. A promise that moved three times has a different history from one that was attempted once and closed. Record the handoffs and the reason for each change rather than overwriting the original promise. If the customer was not told about a change, record that gap as an exception for the supervisor.

When the register is small, review every promise in the window. When it is large, use a documented sample and add a targeted sample of promises due outside normal hours, promises without a backup, and promises that were rescheduled more than once. Freeze the sample before collection and report any later expansion separately. Report the limitation in the same note as the result rather than moving it to a separate memo.

Have a second reviewer check a small subsample and record disagreements. Most disagreements come from an unclear promise time or from treating a voicemail as a completed callback. Resolve those definitions before reporting the full result. The coding sheet should show the definition version used for each promise.

Limitations, conclusion, and sources

The result can support a decision about staffing windows, the handoff rule, or the callback capture form. It cannot prove that the customer was satisfied or that the issue was resolved. Pair the timing measure with a sample of call outcomes and a review of complaints before drawing a conclusion about service quality. Use the same unit and window in the next review so the two results remain comparable.

Report open promises and missed windows separately, and keep the limitations beside the finding. The output should name one process change, one owner, and one recheck date. That is more useful than a single average that mixes routine callbacks with complex customer issues. Check the audit trail before treating a displayed date as the date the event occurred.

Run a baseline review, then repeat after any change to the callback form, the shift pattern, or the owner assignment. A weekly cadence is practical for a busy calling floor, while a monthly review may be enough for a stable team. Archive the export, the coding sheet, and the notes so another reviewer can repeat the measurement. Describe the exception with enough detail that a second reviewer can identify the same item.

Sources: FCC consumer guidance on unwanted calls; FTC guidance on the Telemarketing Sales Rule; NIST Privacy Framework; U.S. Small Business Administration guidance on managing business finances. Each source was checked on November 3, 2026 and is used for general operating context, not as a local performance benchmark.