Booking Intake

Key takeaways

  • Record the guest, the payer, and the person who can approve changes.
  • Confirm the payment path before the guest plans the trip.
  • Send access details only to the person who will be on site.
  • Keep billing data in the financial system, not the guest thread.
Talk through the executive workflow that needs clearer ownership.

Bring the recurring tasks, handoffs, and access boundaries you want dependable support to manage.

Talk with our team

Operating data

Primary workflowBooking Intake
Reading time5 minutes
Internal next steps3 links
External citation1 source

Playbook

Why a third-party booking needs its own intake

A third-party booking arrives when one person reserves a stay for someone else, such as an employer booking for a contractor or an adult child booking for a parent. The reservation may carry the payer's name while the arrival message goes to a different guest. Without a separate intake, the property loses track of who will actually be on site. The coordinator should treat the request as its own booking type rather than a normal reservation with a note.

The risk is not only a mismatched name on the door. A payer who is not staying may not know the house rules, and a guest who did not pay may not know the cancellation terms. The coordinator needs both people reachable before arrival. A short intake that records the roles prevents the confusion that appears at check-in.

Identify who is staying and who is paying

Record the guest who will stay, the person who will pay, and the person who can approve changes. These may be three different people, and each needs a clear contact path. Ask which name should appear on the arrival message and which phone number should receive access instructions. The answers decide how the rest of the booking is handled.

If a caregiver is traveling with the guest, record that relationship without collecting medical detail. If the booking is for a business trip, confirm who signs the damage agreement and who receives the receipt. Do not assume the payer is the decision maker for every change. The record should name the authority for each kind of request.

Check the payment path before confirming

Confirm that the payment method belongs to the payer and that the guest knows the cancellation terms. A booking paid by a company card may need an invoice with a different name than the arrival record. The coordinator should check the platform rules for third-party payments before promising a method. A failed payment at check-in is harder to resolve than a question asked in advance.

If the platform does not support the arrangement, say so before the guest plans the trip. Offer the approved path, such as a direct invoice or a transfer of the reservation to the guest's account. Do not hold a unit on a verbal promise from a payer the property cannot verify. The answer should reflect what the systems can actually do.

Protect guest information in the handoff

The arrival message should go to the guest who will be on site, with a copy to the payer only when the guest agrees. Access codes, lockbox details, and alarm instructions should not be sent to a person who is not staying. The coordinator should record who received each sensitive message. A forwarded code is a security event, not a convenience.

Talk through the executive workflow that needs clearer ownership.

Bring the recurring tasks, handoffs, and access boundaries you want dependable support to manage.

Talk with our team

Keep the payer's billing details in the approved financial system rather than the guest thread. If the guest asks about a charge, route the question to the payer instead of sharing the payment record. The property should collect only the information the stay requires. Privacy rules apply to the payer as well as the guest.

Put the arrangement in writing

Send a short confirmation that names the guest, the dates, the total, and the person responsible for damage. State who can request a change and who will receive the refund if one applies. Ask both parties to confirm the arrangement in one reply. A written agreement prevents a later dispute about who authorized what.

Update the reservation so the guest name and the contact number match the arrival record. Add a note that identifies the payer without exposing payment details in the operations view. Tell the cleaner only what affects the stay, such as an accessible unit or an early arrival. The handoff should be useful without being intrusive.

Work through two requests

An office manager books a unit for a visiting contractor and asks that the receipt go to the company. The coordinator records the guest and the payer separately, confirms the company's payment method, and sends access instructions to the contractor. The office manager receives the invoice and the damage terms. The arrival message names the contractor, so the cleaner expects the right person.

In a second case, a guest books for a parent who uses a wheelchair and asks for a late arrival. The coordinator confirms the accessible features with the property record, sends the arrival details to the adult child as well as the parent, and notes who can approve changes. The stay begins without a call to the office. The record shows both contacts and the reason.

Review the third-party pattern

At the end of the month, count third-party bookings by payer type and by whether the guest and payer were both reachable. Look for arrivals where the guest name changed after confirmation, because those are the cases most likely to fail at the door. A pattern of company bookings may justify a standard invoice path. The review should name one improvement for the next month.

Assign the intake form to one owner and review it with the team after any confusing arrival. Check that the arrival message always goes to the person on site. A simple test is whether the cleaner and the guest both know who is expected. A third-party booking works when every role is named before the first night.

Related services

- Guest communication - Property documentation - Reservation coordination

Sources

- FTC data security guidance

- FTC privacy and security resources

Talk through the executive workflow that needs clearer ownership.

Bring the recurring tasks, handoffs, and access boundaries you want dependable support to manage.

Talk with our team

FAQ

When should a leader delegate this workflow?

Delegate it when repeated coordination, routing, or follow-up is taking time away from decisions that only the leader can make.

What should the assistant own first?

Start with intake rules, status visibility, and escalation timing so the assistant can act consistently before the workflow expands.