Measuring Whether No-Show Follow-Up Starts Inside the Agreed Window

Research question and evidence scope

When a customer misses an appointment, does the first follow-up attempt start inside the window the client agreed to? The scope is one appointment-setting queue during a defined review window, not an industry benchmark. The audit compares the appointment end time with the first outbound call or message and records the channel and outcome. It asks a narrow operational question: can the team show that a missed appointment entered a follow-up path on time?

The review does not judge why the customer missed the appointment or whether a fee applies. It does not measure recovered revenue, customer satisfaction, or the quality of the conversation that follows. Those outcomes depend on the offer, the customer's circumstances, and the closing team's skill. Separating timing from outcome keeps a queue problem from being blamed on the customer or the caller.

The unit is one missed appointment occurrence, not one customer and not one booking. A customer who misses two appointments creates two occurrences with separate end times and separate follow-up clocks. A rescheduled appointment is a new occurrence even when the original booking remains in the system. Keep the appointment identifier, the scheduled start and end, the time zone, the service type, and the closing owner together so the chain stays visible.

Operating scenario and evidence

Missed appointments are usually discovered through three routes, and each route starts the clock at a different moment. The customer may call to say they cannot attend, the setter may see the calendar status change, or the closing team may report the absence after the slot passes. The audit should use the scheduled end time as the clock start unless the client has approved a different trigger. That choice keeps the rule independent of who noticed first.

A common failure is follow-up that begins after the window because no one owns the missed-appointment queue. Another is a note that says the customer was called while the phone system shows no dial at that time. A third is two people assuming the other will call, so the first attempt happens only when the customer reaches out again. These cases look similar in a summary but require different repairs, so the audit must capture the actual attempt event.

Method and review criteria

Collect a dated export of appointments marked missed, no-show, or unattended in the review window. Include the appointment identifier, scheduled start and end, stored time zone, status-change time, service type, closing owner, and the customer's stated contact preference. Add the dial and message logs as separate sources, with timestamps and outcomes. Join on the appointment identifier and keep the original offsets rather than a normalized local time.

Define the follow-up window before reading the records. The window starts at the scheduled end and lasts for a length the client has approved for that appointment type. It ends when the first outbound attempt is made or when the deadline passes, whichever comes first. Write both the start rule and the length beside the coding sheet so another reviewer can reproduce the classification.

Use the phone or message event as evidence that an attempt happened, and use the note as evidence of intent. A note written at four o'clock about a call at two o'clock is still a late attempt if the dial log shows two. A note that promises a call without a matching event is an unverified record. Neither source is sufficient alone, which is why the audit joins them on the appointment identifier.

Authority and practical implications

The Federal Trade Commission's Telemarketing Sales Rule requires sellers and telemarketers to keep records of telemarketing activity for twenty-four months and sets conditions for calls to numbers on the National Do Not Call Registry. The Federal Communications Commission's guidance on the Telephone Consumer Protection Act addresses consent and revocation for automated calls and texts. The National Institute of Standards and Technology Privacy Framework offers a structure for limiting the data used in the review. These sources frame record-keeping and contact conditions, not the attendance outcome of any appointment.

Implications should be specific to the pattern. If late attempts cluster at the end of a shift, the missed-appointment queue is competing with live calls and needs a protected slot. If no attempts cluster around one client, the closing owner may believe the client handles its own follow-up. If unverifiable records cluster around one integration, the calendar status and the dial log are not synchronized. Each pattern points to a different owner and a different repair.

The audit has limits. An appointment marked missed may have been attended and never updated, and a customer may have arrived late enough to be recorded as absent. A time-zone error can move the scheduled end by an hour and change whether an attempt was inside the window. A contact preference recorded after the appointment may not reflect what the customer wanted at the time. Report these cases as uncertain rather than forcing them into a passing or failing bucket.

Limitations, conclusion, and sources

Use a census for a small queue and a documented sample for a larger one. Oversample appointments at the end of the service day, appointments on the first day after a weekend, appointments with a high value to the client, and appointments for first-time customers. These groups carry the highest risk of a delayed or missing follow-up. Freeze the selection rule before reading records and report later additions separately.

Have a second reviewer recompute the window boundaries and the first-attempt time for a subsample. Disagreement usually comes from a different view of when the appointment ended or from a status change that was entered late. Resolve it by writing the boundary rule more precisely and recoding the disputed rows. A smaller sample with a clear rule is stronger than a large sample with guessed times.

Protect the joined file as personal data. Appointment times, contact details, and call notes can identify a person and reveal where they were expected to be. Restrict access to the fields the review needs, store the working file in an approved location, and remove it when the review closes. Do not paste phone numbers or full addresses into a slide deck. Aggregate counts are enough for the owner discussion.

The result should name an owner for each pattern and a due date for the repair. A late attempt caused by queue capacity belongs to the shift lead, a missing attempt caused by unclear ownership belongs to the client manager, and an unverifiable record belongs to the systems owner. Do not assign every finding to the caller, because most missed follow-ups start in the queue design. Check the repair on the next sample before announcing an improvement.

Run the review after any change to the appointment status list, the missed-appointment queue, the follow-up script, or the client's service hours. A monthly cadence suits a stable queue, while a weekly check may fit a campaign with frequent same-day bookings. Archive the export, the coding sheet, the window definition, and the repair log so another reviewer can reproduce the result. Keep the same unit and states for the next comparison.

A passing review is not a substitute for a working follow-up conversation. The caller should confirm the customer still wants the appointment and offer a realistic new time. The audit can show that an attempt happened inside the window, but it cannot show that the customer understood the options. Pair the timing check with a short call-quality sample before changing the script.

Report the distribution of time from appointment end to first attempt, not only the average. A queue with a good average can still fail a group of customers who wait most of a day, and an average hides the appointments that received no attempt at all. Split the result by client, service type, and shift before drawing a conclusion. Do not average across clients with different windows, because the average hides the cases that matter.

A missed follow-up window is not proof that the customer is lost. It is evidence that a control the team promised did not operate as written. State that limit plainly when presenting the result, and separate the timing finding from any later recovery outcome. That discipline keeps the audit useful to operations without turning a small sample into a claim about the market.

Sources: FTC guidance on complying with the Telemarketing Sales Rule, https://www.ftc.gov/business-guidance/resources/complying-telemarketing-sales-rule; FCC guidance on telemarketing and the Telephone Consumer Protection Act, https://www.fcc.gov/general/telemarketing-and-telephone-consumer-protection-act; NIST Privacy Framework, https://www.nist.gov/privacy-framework; U.S. Small Business Administration guidance on managing a business, https://www.sba.gov/business-guide/manage-your-business. Each source was checked on November 11, 2026 and is used for general operating context, not as a local performance benchmark. These references frame calling rules, privacy, and record-keeping but do not validate any single queue's follow-up timing. Record the definition and sample size beside the result so the review can be repeated.