Direct answer: For a hotel-arranged cross-border transfer, the handoff should identify the booking contact, travelling guest, route, flight details, passenger and luggage counts, pickup instructions and the person authorised to approve changes. Send the guest the confirmed meeting instructions and contact details. Keep one current itinerary so a hotel shift change or flight update does not leave the guest following an outdated plan.
01
Quick answer
02
Key takeaways
- Separate booking contact (concierge/travel desk) from travelling guest
- Name one change approver for delays and pin changes
- Templates below are planning examples, not claims that every hotel already runs this standard
- Related: Business · HKG pickup guide · How to book · Cancellation policy
> Scope: Editorial handoff checklist for hotel teams arranging CrossBorder MPV chauffeur transfers. Not a statement that hotels cannot arrange cars, and not a certified hotel-industry SOP.
03
Three-party responsibility map
Swipe to see the full table →
| Party | Owns | Must not assume |
|---|---|---|
| Hotel concierge / desk | Collecting guest data, forwarding written meeting instructions, night-shift continuity | That the guest saw the latest version without forwarding |
| Operator coordinator | Written fare, vehicle/meeting plan, driver assignment | Guest preference changes without approver |
| Travelling guest | Being ready at the meeting point with documents | That lobby staff can silently change the destination without payer approval |
04
Concierge → operator briefing fields (planning template)
Swipe to see the full table →
| Field | Example prompt |
|---|---|
| Booking contact name + WhatsApp/email | Night manager on duty |
| Guest name(s) as on travel docs | |
| Bill-to / payer | Room / company / guest self |
| Change approver | Named person + contact |
| Route pins | Hotel entrance → SZ/HK destination |
| Flight number / ETA | If airport related |
| Pax + bags + child seats | |
| Language notes | |
| Privacy notes | What not to announce on a lobby sign |
05
Guest-forward message (planning example)
Dear <Guest>, Your cross-border transfer is confirmed as follows: Pickup time / meeting point: <…> Destination: <…> On-the-day contact: <coordinator WhatsApp thread / number in confirmation> Please message if your flight or readiness changes. Change approvals go through: <approver name>. — <Hotel desk>
Label: planning example—not a universal hotel script.
06
Night shift and flight-change protocol
Swipe to see the full table →
| Event | Concierge action | Guest action |
|---|---|---|
| Flight delay overnight | Update operator + refresh guest message | Reply with new ETA / readiness |
| Guest asks new destination | Contact approver before operator moves | Wait for reconfirmed fare/scope |
| Shift handover | Pass single current itinerary file/thread | Ignore older printouts |
| Guest no-show risk | Call/message per hotel policy; inform operator | Keep phone reachable |
Airport exception detail: HKG pickup.
07
What to confirm in the written supplier quote
Swipe to see the full table →
| Item | Why hotels care |
|---|---|
| Total fare currency | Guest bill or company chargeback |
| Waiting terms | Delay nights |
| Meeting instructions | Concierge can forward one version |
| Cancellation window | Policy |
| Payment method | Confirm in writing—do not invent rails |
08
Next step
Hotels and desks: send the briefing fields via WhatsApp. For multi-vehicle groups, use the group manifest.
Useful next steps
Compare all published transfer pricesBrowse all cross-border travel guides