OTA · Guest messaging
The OTA blocked the guest's phone number. What's next?
Why OTAs mask guest phone numbers and emails, and four compliant ways to keep guests informed: OTA inbox, scheduled messages and post-booking forms.
Streamhost Team4 min read
A guest books through Airbnb or Booking.com. You need to send them check-in instructions, an access code and a reminder about the deposit. You open the booking and the phone number is hidden, masked, or replaced with a relay number. The email is an alias. Messages that contain a phone number or a link get filtered.
This is normal, and it isn't going away. Online travel agencies protect guest contact details for good reasons, and they want conversations to stay on their platform. The question isn't how to get around it. It's how to run a smooth operation inside those rules.
Why OTAs hide guest contact details
OTAs earn their commission by owning the relationship between guest and host. Hiding contact details:
- Protects guests from spam and scams by fake "hosts".
- Keeps disputes on the platform, where the OTA can see the full conversation if something goes wrong.
- Stops bookings moving off-platform to avoid commission.
What this looks like varies by platform and changes over time, but operators commonly run into:
| What you see | What's going on |
|---|---|
| Phone number missing or partly masked | Contact details are only shared at certain booking stages, or not at all |
Email like name.123@guest.booking.com | An alias that forwards through the OTA's messaging system |
| Phone numbers or links removed from your message | Automated filters strip contact details, especially before the booking is confirmed |
| Message rejected or account warned | Repeated attempts to take the conversation off-platform |
Trying to sneak a WhatsApp number past the filter is the fastest way to get a listing penalised. Work with the channel, not against it.
What's next: four things that work
1. Treat the OTA inbox as a real channel
The OTA's messaging system is a way to reach the guest, and guests do get notified through the OTA app. The problem is usually on the operator side: OTA messages live in a separate app or tab that nobody watches at 11 p.m.
Bring OTA threads into the same inbox as your WhatsApp and email conversations, so they get the same response times, the same team assignment and the same AI help.
2. Send operational messages through the OTA thread
Everything a guest needs to stay with you can go through the OTA's own messaging:
- Booking confirmation and what happens next
- Check-in instructions and building access guide
- Wi-Fi and house rules
- Checkout reminder
Schedule them against the reservation's check-in and checkout dates, exactly as you would on WhatsApp.
3. Collect contact details the legitimate way, after booking
Once a booking is confirmed, many operators have a genuine operational need for a direct contact. For example, a building may require guest registration, or you may need a number for a lockout at midnight. The clean approach:
- Send a guest information or online check-in form through the OTA thread, and read each platform's rules on links first.
- Ask for what you need for the stay: arrival time, number of guests, ID if required, and a phone number for urgent access issues.
- Explain why you're asking. "So we can reach you if there's a problem with door access" works far better than a bare form field.
- Once the guest shares a number for their stay, you can message them on WhatsApp for operational updates, if they agree.
The rule of thumb: never use a direct channel to move the booking or the payment off the platform. Use it to look after the guest during the stay.
4. Make your AI concierge OTA-aware
If an AI assistant replies to OTA threads, it has to follow OTA rules too. It should never paste phone numbers, emails, external links or "book direct for a discount" offers into an OTA conversation. Give it a stricter set of instructions on OTA channels than on WhatsApp.
A comparison of the options
| Approach | Reaches the guest? | Within OTA rules? | Effort |
|---|---|---|---|
| Ignore the OTA inbox, wait for the guest to call | Sometimes, late | Yes | Low effort, poor experience |
| Paste your WhatsApp number in the first message | Often filtered | No | Risky |
| Watch the OTA app separately | Yes | Yes | High: another app, another login |
| OTA threads in your unified inbox + scheduled messages | Yes | Yes | Low once set up |
| Post-booking info form for stay-related contact | Yes | Yes, if done within each platform's rules | Low |
How Streamhost helps
Streamhost brings Airbnb, Booking.com and Trip.com guest threads, relayed through connected channel managers, into the same inbox as WhatsApp, WeChat and email. OTA conversations get the same assignment, unread tracking and scheduled messages as every other channel. The AI concierge runs with OTA-safe instructions, so it answers guest-support questions without sharing contact details, links or direct-booking offers that would put your listing at risk.
A hidden phone number doesn't have to mean a missed guest. It just means meeting the guest where they already are.
