Set an identity boundary for direct-booking inquiries

Reservation intake

Key takeaways

• Capture inquiry identifier, requested dates, property, contact channel, information requested, information received, verification owner, payment route, risk signal, response status, and retention action.
• Follow this sequence: keep the inquiry in the approved channel, collect the minimum required details, verify unusual changes independently, route payment decisions, redact unnecessary data, and document why the request proceeded or stopped.
• Escalate when the sender pressures for secrecy, changes payment instructions, supplies an identity document without request, refuses the approved channel, or asks the assistant to bypass a screening or occupancy rule.

Operating data

Playbook

Reservation intake field note 1. Set an identity boundary for direct-booking inquiries starts with a situation that is easy to misread. A prospective guest requests a manual booking and sends more personal information than the team asked for. The message also asks the operator to move payment and communication into an unfamiliar channel. For a short-term rental operator, the useful response is a bounded operating record. It should make the current facts, missing facts, decision owner, and next safe action visible without pretending the uncertainty has gone away. The assistant's job is to keep that record usable while the reservation or property work continues.

Reservation intake field note 2. Begin with these fields: inquiry identifier, requested dates, property, contact channel, information requested, information received, verification owner, payment route, risk signal, response status, and retention action. Keep each value tied to its source and effective time. If a field is unknown, leave it visibly unknown and name who can establish it. A blank is safer than a confident guess. The record should also show the local property date and time when timing affects guest access, turnover, a vendor visit, or a channel deadline.

Reservation intake field note 3. Run the work in this order: keep the inquiry in the approved channel, collect the minimum required details, verify unusual changes independently, route payment decisions, redact unnecessary data, and document why the request proceeded or stopped. The order matters because a polished response can be wrong when it is sent before the source is checked. Use one accountable closer for the case. Other people may provide evidence or approve a choice, but the operating record should always show who is watching the next action and what will prove it happened.

Reservation intake field note 4. The assistant may qualify the inquiry and follow approved verification steps. The operator and payment provider own acceptance, identity requirements, fraud response, contract terms, refunds, and exceptions to booking policy. Tool access does not widen that authority. A person who can edit a reservation, message a guest, change a calendar, view an owner statement, or place an order may still lack permission to make the underlying business decision. Put the authority statement beside the workflow so a covering coordinator can use it during a live case.

Reservation intake field note 5. Create an exception path before the routine becomes busy. Escalate when the sender pressures for secrecy, changes payment instructions, supplies an identity document without request, refuses the approved channel, or asks the assistant to bypass a screening or occupancy rule. A useful escalation is short but complete: observed fact, reliable source, affected reservation or property, consequence of waiting, decision required, and latest safe response time. Avoid recommendations that depend on facts the assistant cannot verify. Preserve the owner's answer, any conditions, and the person responsible for execution.

Reservation intake field note 6. Do not use a copied identity document as a substitute for an approved verification process. It may be stolen, altered, unnecessary, or unsafe to retain. Explain which details the team needs and why. Store only what the authorized booking record requires, limit access, and use a defined removal trigger for material that arrived unexpectedly. This is where generic checklists tend to fail. They collect completion marks but miss the property-specific condition that changes the decision. Keep the extra detail proportionate to the risk, and avoid copying confidential information into a convenience tracker when a permissioned link or stable identifier is enough.

Reservation intake field note 7. The inquiry workbook distinguishes email header, reply-to address, telephone country code, messaging profile, referral source, prior guest, repeat device, requested property, adult count, child count, infant count, pet count, vehicle count, visit purpose, arrival origin, stay length, billing country, cardholder mismatch, payment link, bank transfer, cryptocurrency, gift card, urgency cue, secrecy request, proxy booker, third-party guest, company traveler, relocation agent, travel advisor, accessibility request, consent statement, privacy notice, identity provider, verification result, sanctions escalation, fraud review, declined reason, retention category, deletion date, and appeal owner.

Reservation intake field note 8. Verification signals may include disposable domains, Unicode lookalikes, caller-ID spoofing, remote-access requests, overpayment stories, refund redirection, mule accounts, synthetic identities, stolen credentials, fabricated employers, altered utility bills, mismatched signatures, cropped metadata, reused portraits, impossible travel timing, and conflicting household details.

Reservation intake field note 9. Compare approved contact records, verified referrals, payment-provider results, device history, address consistency, traveler details, corporate authorization, agency credentials, consent capture, privacy notices, screening outcomes, chargeback indicators, communications continuity, booking purpose, and escalation findings.

Reservation intake field note 10. The FTC phishing guidance provides a useful outside reference for this operating area. Read it as source material, not as a replacement for the booking channel's current terms, local requirements, owner instructions, or professional advice. When an external source and an internal rule appear to conflict, the assistant should record the mismatch and route it to the person authorized to resolve it.

Reservation intake field note 11. Connect this routine to the relevant STR virtual assistant support lane. Intake, communication, and closure should use the same ownership model. Otherwise, a guest message can say resolved while the property task remains open, or a vendor ticket can close while the reservation record still contains an outdated promise. The connecting record should expose those mismatches instead of hiding them in separate tools.

Reservation intake field note 12. Use plain status labels that describe evidence. Received means the request entered the system. Qualified means the required context is present. Awaiting owner means a named person must decide. Scheduled means a dated action exists. Complete means the defined outcome has evidence. Closed means remaining records and access were handled. Do not use done when the only evidence is that someone sent a message or moved a card.

Reservation intake field note 13. Review the routine through inquiries moved off channel, excess data received, redactions completed, verification failures, duplicated profiles, abandoned requests, and cases escalated before payment information was exchanged. Counts need context. More escalations may show poorer intake, but they may also show that coordinators stopped making unauthorized assumptions. Read a sample of ordinary and exceptional cases. Look for fields nobody can answer, two people acting as owner, repeated clarification, stale permissions, and closure claims that cannot be reconstructed from the retained record.

Reservation intake field note 14. Coverage is the final test. Give a trained backup the written procedure and one redacted example. Ask that person to identify the current state, next action, authority boundary, escalation owner, and closure evidence without interviewing the primary assistant. If the backup has to rely on memory or a private chat, revise the record. Good coverage protects daily routines during weekends, absences, turnover, and unusually busy arrival periods.

Reservation intake field note 15. Human review should stay part of the process. Templates can reduce typing, and automations can surface deadlines, but neither knows whether a new fact changes the guest, owner, vendor, or property consequence. After a real exception, update only the rule or field that would have improved the decision. Do not pile on controls that create recordkeeping without a clear operating use.

Reservation intake field note 16. A mature reservation intake routine makes restraint visible. It shows what the virtual assistant completed, what the short-term rental operator decided, what a local or professional specialist verified, and what remains open. Teams adapting the workflow can request a tailored support plan with one recent example stripped of sensitive data. The most useful design will follow the actual handoffs rather than a generic property-management checklist.