Your OTA guests can't reach you on WhatsApp. Now what?

You have built a good WhatsApp operation, and a large share of your guests are never in that channel at all, because you do not hold their number.

Arrival details, upsells, in stay requests, all answered in seconds. Then you look at where your bookings come from and notice who is missing.

This got harder at the end of September, if your bookings come through Booking.com. Two connectivity providers, Smoobu and NextPax, both read 28 September 2026, describe the same change in the same terms: from 28 September 2026 Booking.com stops sending guest phone numbers to connectivity providers, meaning channel managers and property management systems, worldwide. The number stays visible in the Extranet and the Pulse app, so your front desk can still find it, but no connected tool receives it automatically any more. Reservations, rates, availability and guest names keep syncing, and the masked guest email and Booking.com messaging continue to work. The stated reason is the rise in scam texts and WhatsApp messages sent to travellers who have genuine booking details.

Other OTAs differ, and several run guest communication through their own inbox rather than passing you a number. Do not design anything around an assumption here. Open each extranet you use and check what you actually receive today, because the answer has changed more than once this year.

There is also a platform rule underneath all of this. On WhatsApp, the guest has to start the conversation before you can reply freely. Meta's documentation is explicit: when a WhatsApp user messages you or calls you, a 24 hour customer service window opens, it resets each time they message again, and once it closes you can only send pre approved template messages (Meta developer docs, read 28 September 2026). Without a number and a reason for the guest to write first, you have neither the window nor the template.

So the job is not to obtain phone numbers. It is to give guests an easy reason to open the conversation themselves.

What you can do

• Confirmation email. Every OTA guest gets one, from the OTA or from you. Put your WhatsApp link and a one line reason near the top: "get your arrival details and answers in seconds". Not a footer icon. Above the fold, with the benefit stated, because nobody taps a bare logo.
• Extranet auto-reply. Set the auto-reply in your OTA inbox to invite the guest to your WhatsApp, short, with the link. This one is underused. A guest who has already messaged you on the platform has shown they have a question, which makes them the most likely person to move.
• Pre-arrival email with a link, not a form. A form asks for work and gets abandoned. A link is one tap and the guest is in your channel, with the 24 hour window open because they wrote first.
• At check-in. Show a QR code at the desk and ask for the guest's number for in stay requests. Meta's own documentation frames QR codes and short links as a way for customers to start a chat without typing a phone number, and they support a prefilled first message of up to 140 characters (Meta developer docs, read 28 September 2026). Use that prefilled text. "Hi, I've just checked in to room" gets a better first message than an empty box.

Put the same link in the places guests already look: the booking confirmation you send yourself, the pre arrival message, the key card wallet, the in room card, the wifi landing page and your email signature. The move should never require the guest to search for anything.

What not to do

• Don't ask guests to give you their number "to skip the OTA". Your contract with each platform governs what you may do with guest data and how you may communicate. Read it rather than guessing at it. Frame the invitation around service, which is what it actually is, never around the commission.
• Don't message OTA guests from a personal phone. A message from an unknown private number, quoting a real booking, is exactly the pattern the scams use and exactly why the number sharing changed. It undermines the trust you are trying to build, and it puts guest data on a device you do not control.
• Don't buy or guess numbers. Nothing good is at the end of that road.

What to expect

Not everyone will move, and you should plan for that. Keep the OTA inbox properly staffed, because for some guests it remains the only channel you have, and a slow reply there is a slow reply to a paying guest.

In our experience the guests who do move are the ones who ask the most questions, so the ones you most want in your channel. That is a useful bias. The guest who taps the link at 22:00 to ask about parking is the same guest who would otherwise call reception three times before arrival.

One practical note on cost. From 1 October 2026 the free form replies you send inside that 24 hour window are chargeable after a monthly free allowance per number, so a wave of newly moved OTA guests shows up on a bill as well as in your inbox. The numbers are small per message and worth it, but they are no longer zero. The October pricing change, with how to estimate the bill, has the detail.

Takeaway

You can't message OTA guests where they are. You can make the move to your channel the easiest thing they do that day.