31 October 2026
Automate guest communication without a phone number: a practical guide
Set up confirmations and arrival messages with language preferences, a fallback contact channel and checks for changed or cancelled bookings.

Guests need the correct address, arrival time and access instructions even when a reservation has no phone number. Start with a message schedule and an alternative contact channel, then automate delivery. This makes it easier to identify the exceptions your team still needs to handle.
What Booking.com changed in September 2026
Since 28 September 2026, new Booking.com Reservations API messages omit guest phone numbers. Previously shared numbers are not erased retrospectively. Booking.com points properties to the Extranet when needed. Telephone contact is not banned. See the official API update.
Check what your connection actually provides. A channel manager that receives bookings does not necessarily support platform messages. Booking.com documents a separate Messaging API for those conversations. Ask your supplier which messaging capabilities are available in your plan and connection.
1. Define the schedule and stop conditions
| When | Message content | Check first |
|---|---|---|
| After confirmation | Dates, accommodation, guest count and agreed terms. | Is the booking confirmed? Has the channel already sent a confirmation? |
| Before arrival | Address, directions, check-in window and business contact details. | Are the arrival date and language still correct? |
| Arrival day | Only the access information the guest needs. | Has access been approved and is the stay going ahead? |
| Before departure | Checkout time, key return and previously disclosed departure arrangements. | Has the stay been extended or shortened? |
This is a setup checklist, not a claim that every PMS supports every condition. If a condition cannot be checked automatically, assign someone to check it before sending. A same-day booking should not trigger a backlog of overdue reminders.
2. Record language and fallback contact
Use the guest's stated language preference and define a fallback language when it is missing. Review dates, times, amounts, addresses and the distinction between a booking deposit and a refundable security deposit in every translation. Have someone check late-arrival and lockbox instructions particularly carefully.
Delivery does not prove that a message has been read. Decide who follows up bounced emails, unanswered arrival questions and missing contact details. For a platform booking, use its available conversation as a fallback. Include a reachable business number for urgent arrival problems.
3. Start with one short arrival template
Adapt this example to your property:
Hello [first name], we look forward to welcoming you on [date] at [property and address]. Check-in is between [time] and [time]. Please reply in this conversation with your approximate arrival time. We will send access instructions through [agreed channel] once access is approved. If you have a problem on the way, contact us at [business contact].
Replace every placeholder and test what happens when information is missing. Share access codes only with the correct guest, through the agreed channel and at the appropriate time. Do not introduce house rules that were not disclosed before booking. See our house-rules checklist.
4. Test exceptions before enabling automation
- Test Dutch, English, German, French and a missing language preference.
- Change one arrival date and cancel another test booking. Check that outdated messages are not sent.
- Test a booking without a phone number and an undeliverable email address.
- Open the message and links on a phone, reply to it and check who receives the answer.
- Compare PMS messages with platform messages to avoid duplicates or contradictory instructions.
What to review in EDICE - PMS
EDICE - PMS offers editable confirmation emails with control over content and sending time, and communication in the guest's language. Its guest module provides access to history, payments and outstanding actions. Bring your test cases to a demo and verify the precise triggers, language settings and channel support. Receiving a booking does not establish that every message can automatically be sent through that platform.
Review the current features. After launch, track failed deliveries and arrival questions that still need manual answers. Those observations are more useful than a promise of flawless communication. Updated 31 October 2026.