Philippines staffing research

Measuring How Often Booked Appointments Keep the Original Attendee

An audit protocol for measuring attendee continuity between booking and meeting, covering how to define a retained attendee, code substitutions, distinguish a delegate from a replacement, check consent, and report the limits of a small queue review.

Measuring How Often Booked Appointments Keep the Original Attendee

Research question and evidence scope

Do the appointments on the calendar still belong to the person who will attend? The scope is one appointment-setting queue during a defined review window, not an industry benchmark. The review compares the attendee named at booking, the attendee on the calendar at the time of the meeting, the person who joined, and the contact who received the reminder. It asks a narrow identity question: can the team show that the meeting kept the attendee it was booked for?

The review does not judge whether the substitute was qualified, whether the meeting was valuable, or whether the original attendee was the real decision-maker. It does not measure show rates, close rates, or revenue. Those outcomes depend on the offer, the buyer, and the closing team. Separating attendee continuity from meeting outcome keeps a booking-record problem from being blamed on the person who happened to join.

The unit is one booked appointment, not one attendee and not one join event. An appointment may name two attendees, one of whom sends a colleague, and the appointment still has one booking history. Keep the appointment identifier, the original attendee name and role, the attendee on the calendar at the meeting, the person who joined, the booking contact, and the reminder recipient together. That chain shows whether the person the setter qualified was the person the closer met.

Operating scenario and evidence

A common failure is a substitution made by an assistant. The setter books a meeting with a director, the assistant accepts the invite, and the director sends a junior colleague without telling the closer. The calendar may show the director as an optional attendee while the colleague appears as a guest. The closer arrives expecting one conversation and gets another, and the qualification work behind the booking no longer matches the room.

Another failure is a replacement that looks like a clarification. The customer says a colleague will join to help, and the colleague becomes the main speaker. A third failure is a silent swap after a reschedule, when the new invite keeps the old attendee name but the reminder goes to a different address. These cases are not the same, and the audit should record who changed, when the change appeared, and whether anyone told the closer.

Method and review criteria

Collect a dated export of appointments in the review window. Include the appointment identifier, the original attendee name and role, the booking contact, the calendar attendee list with required and optional flags, the reminder recipient, the join log, and the meeting start and end. Pull the attendee list as it stood at three moments: at booking, after the last reminder, and at the meeting. Record the export time and the time zone used by the calendar.

Use a census for a small queue and a documented random sample for a larger one. Oversample appointments with several attendees, bookings made by an assistant, appointments that moved after the first booking, appointments with a role-based inbox on the invite, and appointments where the reminder recipient differs from the calendar owner. These groups carry the highest risk of a silent substitution. Freeze the selection rule before reading any record.

Define four coding states before reviewing records. Retained means the person who joined matches the attendee the setter qualified. Delegated means a named substitute attended with the original attendee informed and the closer told in advance. Substituted means a different person attended without a documented handoff. Unverifiable means the join record or attendee list cannot establish who attended. Code the appointment once and cite the evidence for the code.

Authority and practical implications

Distinguish a delegate from a replacement by what the original attendee retains. A delegate speaks for the attendee on a defined topic and reports back, while a replacement takes over the decision. The difference matters because a delegate can still advance the deal while a replacement may need a fresh qualification. Record the role of the person who joined and whether they could commit to the next step. Do not assume that a senior title means authority or that a junior title means none.

Record when the change appeared, not only that it happened. A substitution decided during the booking call is part of the qualification, while one made after the reminder is a scheduling event. A change made after the closer prepared is the most expensive, because the preparation no longer fits the room. Sorting by timing tells the team where to intervene: the booking script, the reminder message, or the pre-call confirmation.

Keep attendee continuity separate from attendance. A substituted attendee may join on time, and the original attendee may attend with an extra colleague who was never named. The first is a continuity problem, the second is an attendee-list problem. Report continuity, attendance, and punctuality as separate counts so a good show rate does not hide a room that no longer matches the booking. Each count needs its own owner and repair.

Limitations, conclusion, and sources

The Federal Trade Commission's Telemarketing Sales Rule sets record-keeping duties and calling conditions for covered telemarketing, including 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 personal data used in the review. These sources frame the control environment, not the attendee continuity of any single queue.

Implications should point to a specific repair. If substitutions cluster around one client, its brief may allow an assistant to accept without naming the attendee. If they cluster around one setter, the booking form may treat a coordinator as the primary contact. If they cluster around one reminder system, the recipient field may be mapped from the lead list rather than the calendar. Each pattern belongs to a different owner and a different fix.

The result should name an owner for each pattern and a date for the repair. A missing confirmation step belongs to the client manager, a booking-form habit belongs to the team lead, and a field mapping belongs to the systems owner. Do not assign every finding to the setter, because most substitutions start in the brief, the form, or the reminder tool. Check the repair on the next sample before announcing an improvement.

The audit has limits. An attendee may send a colleague with full authority and a written brief, which is a legitimate delegation rather than a failure. A join log may show a shared room or a single device used by several people, and a display name may not match the person speaking. Report these cases as uncertain rather than forcing them into a passing or failing bucket, and describe what evidence would settle each one.

Protect the joined file as personal data. Names, roles, email addresses, and join times can identify a person and reveal their schedule. 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 attendee lists or join logs into a shared report. Aggregate counts and role categories are enough for the owner discussion.

Run the review after any change to the booking form, the qualification script, the reminder template, or the calendar permissions. A monthly cadence suits a stable queue, while a weekly check may fit a campaign with frequent same-day changes. Archive the export, the coding sheet, the definitions, and the repair log so another reviewer can reproduce the result. Keep the same unit and the same coding states for the next comparison.

A retained attendee is not proof that the appointment will be useful. It is evidence that the person the setter qualified was still the person the closer met. State that limit plainly when presenting the result, and keep the continuity finding separate from any later sales outcome. Sources: FTC guidance on 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. Sources were checked on November 17, 2026 for context, not as a local benchmark. Record the definition and sample size beside the result so the review can repeat.

Philippines staffing intake

Define the calling role before hiring begins.

Share the scripts, systems, schedule, and approval limits. The intake turns those details into a practical staffing brief.

Contact Us