
Third-party booking screening before arrival
A protocol for measuring how completely a reservation identifies the guest, the payer, and the change authority before the first arrival message is sent.
A third-party booking is screened when the guest, the payer, and the change authority are separately recorded and each has a reachable contact before arrival.
Methodology
- The unit of analysis is one reservation in which the person who books or pays is not the person who will occupy the unit. A case enters the population when the booking record, the payment record, or the arrival message shows different people in those roles. Corporate bookings for a named traveler, family bookings for a relative, and caregiver arrangements all qualify. Ordinary reservations where one guest books for a partner are excluded unless the payer and occupant are separate.
- Role completeness is scored on three fields: the occupant, the payer, and the person authorized to approve a change. A case is complete only when each role has a name and a contact path. A record that says company booking without naming the traveler is incomplete even when the payment is clear. The reviewer records which role is missing rather than collapsing the three into a single score.
- Identity is checked against the arrival record, not against a document copy. The reviewer confirms that the name on the arrival message matches the occupant and that the phone number reaches that person. A payer's name on the reservation is not treated as a failure when the occupant is also recorded. The protocol avoids collecting identity documents because the review concerns routing, not verification of legal identity.
- The payment path is recorded as supported, manually approved, or unsupported. Supported means the platform's own flow allows a separate payer and occupant. Manually approved means a manager accepted an invoice or transfer outside the platform. Unsupported means the property could not complete the arrangement as requested. The reviewer keeps the evidence for a manual approval and the reason an unsupported request was declined.
- Sensitive-message routing is scored separately because a correct reservation can still leak access details. The reviewer lists every message that carried a code, lockbox instruction, or alarm detail and records its recipients. A send to the occupant is expected; a send to the payer or a third party is flagged unless the occupant agreed. The count of sensitive messages with a verified recipient is reported alongside the role score.
- The booking is followed through the first night, not only to confirmation. A case is marked as an arrival success when the occupant reaches the unit without a call to the office about access, payment, or a name mismatch. Early failures are recorded with the issue type so a payment problem is not merged with a door-code problem. The reviewer uses the operations log rather than the guest's later review.
- Sampling uses every eligible reservation in the window when fewer than forty cases exist. Above that volume, the frame takes a fixed interval across properties and booking dates, stratified by payer type and by whether the booking came through a channel or directly. The frame is frozen before the first record is read. Replacements are allowed only for a missing record and are listed with the reason.
- Two reviewers code the first fifteen cases independently and compare the role fields, the payment path, the sensitive-message routing, and the first-night outcome. Disagreements are resolved by the property manager, who records the rule that settles the case. Reliability is reported as the share of matching fields. Neither reviewer contacts the payer to reconstruct the booking.
- The report separates business payers from family payers because the two create different risks. A business booking may need an invoice and a damage agreement in the company's name, while a family booking may need a second contact for a guest who cannot manage a phone. The grouping is fixed before coding so a strong business process cannot be presented as a general result.
- The report states the number of reservations, the share with all three roles recorded, the share with a supported payment path, and the share that reached the unit without an access or payment call. It names one proposed change, the role that owns it, and the next observation date. No local rate is presented as an industry benchmark, and no association is described as proof of cause.
Findings
- The payer is recorded far more often than the change authority. Most booking records name who paid and who will stay, but few name the person allowed to approve a date change or a refund. The gap appears at the moment a request arrives and the coordinator has to guess which person can decide. The protocol scores the missing authority as a completeness failure even when the stay itself goes well.
- Sensitive access messages are the most common routing defect. A coordinator who is trying to be helpful sends the door code to the payer as well as the guest, and the payer forwards it to someone else. The reviewed cases rarely show a clear harm, but the exposure is real. The protocol counts the recipients rather than waiting for an incident.
- Business bookings through a company card are more likely to have a supported payment path than family bookings paid by a relative. The platform's invoice flow fits the company case, while a family booking often ends in a manual transfer. Those manual cases need a recorded approval and a clear refund route. The report keeps the two payer types separate for that reason.
- Name mismatches at arrival cluster around bookings made by an assistant or an office manager. The reservation carries the booker's name while the traveler's name appears only in a message. The cleaner and the arrival message then point at the wrong person. A required traveler field at intake would remove most of these cases without adding a document check.
- Guests who did not pay are less likely to know the cancellation terms. The reviewed cases show questions about refunds arriving from the occupant rather than the payer. The coordinator can answer the policy question without sharing the payment record, but only if the roles are recorded. The protocol treats that routing as part of screening rather than customer service.
- Third-party bookings that include an accessible-unit request are more likely to be complete because the coordinator asks follow-up questions. The extra conversation surfaces the guest's contact and the person who can approve changes. This is an association rather than a causal result, because accessible requests may also come through more careful channels. The pattern still suggests that a short script improves completeness.
- Manual approvals are the least documented part of the payment path. A manager may accept a transfer in a chat and the reservation may never show the approval. When the guest later asks about the charge, the coordinator cannot find the decision. The report recommends a single approval field with a reference rather than a new payment system.
- First-night access calls are more common when the arrival message goes only to the payer. The occupant arrives without the code and calls the office from the door. The call is easy to resolve but it delays the check-in and creates a record of avoidable contact. The protocol links the routing choice to the arrival outcome without claiming that routing is the only cause.
- The strongest predictor of a complete third-party record is a named owner for the intake form. Properties that route these bookings to one coordinator show fewer missing roles and fewer access calls. The local sample cannot prove causation, so the result is a hypothesis for the next cycle. A second window after a staffing change is required before the rule is treated as settled.
- A final check compares the role recorded in the reservation with the person who actually arrived. A mismatch is coded separately from a missing contact because the fix is different: one needs a data correction, the other needs an intake change. The reviewer keeps both readings visible. A booking is only screened when the record and the arrival agree.
Research standards
Every review freezes its observation window before findings are calculated. Reviewers retain a row-level evidence ledger with the original artifact reference, timestamp, responsible role, status at cutoff, correction history, denominator, exclusions, and unresolved cases. Ambiguous records are coded independently before reconciliation, and both readings remain visible until an accountable adjudicator applies a documented rule. Missing information is treated as unknown rather than silently classified as success or failure. Sensitivity checks remove major record classes in turn so a pattern that depends on one owner, channel, event type, or reporting cycle is disclosed instead of presented as stable. Elapsed time is not translated into labor, an association is not described as causation, and local observations are not converted into external benchmarks.
Interpretation begins with counterexamples and the cases still open at the cutoff. A formally complete record may lack usable evidence, while an authorized alternative path may achieve the intended outcome without matching the expected workflow. The review therefore states the strongest alternative explanation, identifies the additional artifact that could distinguish it from the preferred reading, and records what would reverse or retire the resulting operating rule. Comparisons use the same field definitions and equivalent work classes; a material change in coverage, tooling, policy, or sample composition creates a new baseline rather than a trend. Follow-up records name the decision taken, responsible owner, anticipated signal, review date, exception path, and evidence required before a stronger intervention can be justified.
Governance checks keep only information necessary for the research question. Sensitive content is replaced with a controlled reference whenever an authorized reviewer can reproduce the classification without holding a copy. Access boundaries, retention expectations, correction ownership, disputed-interpretation routes, duplicate handling, spanning-record rules, and cutoff treatment are documented before release. Absolute counts appear beside percentages, small samples avoid false precision, and every external statement links to a listed source without implying that the publication measured the local record set. The proposed action must be proportionate, reversible, and reviewable. If the available evidence cannot support it, the gap becomes an explicit evidence request rather than an assumption.
This research note supports the STR Virtual Assistant topical map for vacation-rental guest communication, property readiness, issue routing, and evidence-based operational follow-through.
Sources
- Data security guidanceFederal Trade CommissionChecked 2026-11-11
- Privacy FrameworkNISTChecked 2026-11-11
- Cybersecurity FrameworkNISTChecked 2026-11-11
- Secure Our WorldCISAChecked 2026-11-11
- Cyber threats and advisoriesCISAChecked 2026-11-11
- Privacy RuleU.S. Department of Health and Human ServicesChecked 2026-11-11
- Fair Housing ActU.S. Department of JusticeChecked 2026-11-11
- Business guideU.S. Small Business AdministrationChecked 2026-11-11
- Consumer complaint resourcesConsumer Financial Protection BureauChecked 2026-11-11
- Small business and self-employed resourcesInternal Revenue ServiceChecked 2026-11-11