Auditing Whether Callers Record the Customer's Preferred Contact Window

Research question and evidence scope

When a customer names a preferred contact window, does the caller record it in a field the next shift can use? The scope is one outsourced calling queue during a defined period, not an industry benchmark. A preferred window can be as simple as weekday mornings or as specific as a single hour, and both forms can be lost in free text. The audit asks whether the recorded window is findable, complete, and tied to the customer reference.

This review does not judge whether the caller honored the window or whether the customer was pleasant on the call. Those questions belong to a separate quality review with the recording. The narrow purpose is to show whether the window survives the note-taking step and reaches the person who dials next. Record the definition and the sample beside the result so another reviewer can repeat the check.

The unit is one customer record that contains a preferred contact window. A record with two different windows should be reported as conflicting rather than counted as a single clean observation. If the customer later changed the window, keep the earlier value and the new value linked. That history shows whether the team recorded a change or silently replaced the original request.

Operating scenario and evidence

Start with a dated export of records touched during the review window. Record the customer reference, the call time, the caller, the campaign, and the field or note where the window appears. Include records with no window so the audit can report the share that is simply missing. Exclude test records and internal calls, and write those exclusions in the note.

A preferred window is usable when a later reviewer can read a day range, a time range, a time zone, and any stated exception. A free-text sentence can be usable if it contains those elements, but it is harder to count. A structured field is easier to compare as long as the team fills it honestly. Record which form was used so the result does not mix two kinds of evidence.

Method and review criteria

Classify each record as complete, partial, conflicting, or absent. Complete means the window has a day range and a time range in a stated zone. Partial means one element is missing, such as the zone or the end time. Conflicting means two values disagree in the same record. Report counts by state rather than a single pass rate, because each state points to a different repair.

Split the result by campaign and by shift, since the working rules may differ. A renewal campaign may accept a weekday morning window, while an event campaign may need a tighter range. Compare the recorded format with the campaign's written instruction. A mismatch is a process finding and should be assigned to the campaign owner rather than to a single caller.

Check whether the note preserves the customer's own words when the request is unusual. A customer who says after two in the afternoon in Manila should not be translated into a default local time without a recorded reason. Record the source zone and the zone used by the dialer. If the zone is absent, mark the record unverified rather than assuming the office default.

Authority and practical implications

Include the channel the customer prefers and any instruction about voicemail or text. A preferred window is incomplete if the team knows the time but not the channel. Record whether the customer asked for a call, a message, or either. If the customer asked not to be contacted, the next event should be a suppression rather than a scheduled call.

Use a census for a small queue and a documented sample for a larger one. Oversample records that crossed a weekend, a holiday, or a shift boundary, because windows are easiest to lose there. Freeze the selection before reading the notes and report any later addition separately. Have a second reviewer check a small subsample and record disagreements against the written definition.

Separate a missing window from an unreadable one. A blank field is a clear absence, while a note with several times can be ambiguous without being empty. Ask a second reviewer to read a sample of ambiguous notes before scoring them. That step keeps the audit from turning a formatting problem into a false accusation about a caller. Report the ambiguous share beside the complete rate.

Limitations, conclusion, and sources

The result can support a change to the intake form, the script, or the handoff checklist. It cannot prove that the customer was satisfied or that the promised window was honored on the next attempt. Pair the audit with a sample of next attempts that used the recorded window. Preserve the original note when a definition changes and label the transition.

Run the audit after any change to the form, the dialer, or the campaign brief. A monthly cadence is practical for a stable queue, while a weekly check may suit a campaign with frequent rule changes. Archive the export, the coding sheet, and the notes so another reviewer can reproduce the result. Use the same states next time so the comparison stays honest.

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 6, 2026 and is used for general operating context, not as a local performance benchmark. Record the definition and the sample size beside the result so the review can be repeated.