Reaching guests before check-in when the OTA hides their number

A guest booked a bed in San Cristóbal through an OTA, landed late and tried to find us in the dark. The reservation had a phone number on it. It was missing the country code, and the e-mail was a relay address that forwards to an inbox the guest checks once a week. They reached our door at one in the morning by asking a taxi driver. We had the door code, the bed and a note about the late arrival ready. We just had no way to give any of it to them.

That night is why we now treat the contact details on a booking as a lead, not a fact. Here is what we do about it across three houses.

Why the number on the booking is often useless

Channels protect the guest from us, and sometimes protect their own relationship with the guest. In practice that means a few things, and which ones apply depends on the channel and the market:

• The e-mail is a relay address. Your message goes through the platform, gets filtered, and lands in the inbox looking like one more notification the guest already skims past.
• The phone number is masked, truncated or simply not passed through to the property.
• The number is real but wrong. Guests type their home number without a country code, or they booked for a friend.
• The number is fine, but the guest is on a prepaid SIM in another country and the phone that owns the number is in a drawer at home.

Backpackers are the worst case for all four. They change SIMs at every border, they book from a phone in a hurry, and many of them never read an SMS. If your pre-arrival plan is "we will call them", you do not have a plan.

What you actually need to know before someone arrives

Strip the problem down and it is three things:

1. Roughly when they are arriving, so the bed is made and someone is at the desk, or the self check-in is ready.
2. One channel that reliably reaches them in the next day. For most of our guests that is WhatsApp. For some it is Instagram, for a few it is only the OTA inbox.
3. Whatever they need from you to get through the door: the address written the way a taxi driver understands it, the door code, what to do if the desk is closed.

Everything else, the passport scan, the signature on the house rules, the deposit, can wait until they are standing in front of you or filling in a form the night before. Trying to collect all of it in the first message is the fastest way to get no reply at all.

Start on the channel you have, move to the one you want

The OTA inbox is slow and ugly, but it is the one place the guest will definitely see a message, because the platform nags them about it. So the first message goes there. It is short: thanks, here is the address, when do you think you will arrive, and what is the best number to reach you on WhatsApp.

In our setup that message leaves from the same screen as the reservation, because OTA guest chat sits inside the PMS rather than in a browser tab per channel. The point is not the software. The point is that the person on the desk does not have to log into three extranets to find out whether anyone has asked the guest a question yet.

The second step is to get the conversation off the OTA. The moment a guest replies with a WhatsApp number, it goes on the reservation and every message after that goes direct. The relay e-mail is forgotten. What you may collect varies by channel; asking for the best way to reach someone on arrival day, which you genuinely need in order to let them in, has never been a problem for us.

Let the form do the asking

Asking one guest at a time works at a ten-bed guesthouse. At a hostel with forty check-ins on a busy weekend it does not. What scales is a link, sent in that first message, where the guest fills in the arrival time and a working number themselves. If the number they type is different from the one the OTA passed along, the form wins.

Our online check-in does exactly this, and the field we care about most is not the passport number, it is "how can we reach you today". Guests fill it in because they want the door code, and the door code is on the confirmation screen. The rest of the form gets finished at the desk if they skip it.

Ask for less than you think

Every extra field costs you replies. We used to ask for nationality, passport number, date of birth, home address, emergency contact and a signature before arrival, and most people stopped at the second screen. Now the pre-arrival form asks for what we need to let them in and reach them, plus whatever local law requires us to register. Registration rules are different in Mexico and Colombia and different again in Europe, so check yours. Everything beyond the legal minimum is optional and clearly marked as such.

Two more reasons to keep it small. You are storing personal data you are then responsible for. And a guest who had to upload a passport photo at midnight in a bus station does not start the stay in a good mood.

Three messages, not thirty

Our rhythm is the same in all three houses, and it lives as templates in the PMS so the night volunteer sends the same text as the owner:

• After the booking: thanks, the address as a map link, "when do you land and what is the best number for you", and the check-in link.
• The day before: door code or desk hours, what to do if they are late, and the arrival time they gave us so they can correct it. If there has been no reply at all by now, this is the moment to check the OTA inbox and to restate the no-show policy in one friendly line.
• Arrival day: one line. "Desk is open until ten, the bell works, your bed is ready." Once they are in, the conversation moves to the house group and the guest app, not the owner's phone.

Three messages is enough. More than that and you become the notification they skip, which is exactly the problem you started with.

Make it someone's job

None of this works if it is nobody's job. Our morning desk shift has one fixed item: open tomorrow's arrivals, look at who has not replied and who has no working number, and nudge them. It takes ten minutes. The same list tells housekeeping which beds need to be ready early and tells the evening shift who is still a question mark at closing time.

The guest from the opening story now gets a WhatsApp with the door code before the plane takes off. The taxi driver still gets asked for directions. That part we cannot fix.

The checklist

• Treat the phone number and e-mail on an OTA booking as unverified until a guest has replied on them.
• Send the first message through the OTA inbox, because that is the one the guest will see.
• Ask for three things only: arrival time, a channel that reaches them today, and confirmation they have the address.
• Send a check-in link in that first message, and let the number the guest types override the one the OTA gave you.
• Move the conversation to WhatsApp or another direct channel the moment the guest offers one, and store it on the reservation.
• Cut the pre-arrival form to what lets them in plus what the law in your country requires; mark everything else optional.
• Use three templated messages: after booking, the day before, arrival day.
• Put the door code and desk hours in the day-before message, not in a PDF attachment.
• Give the morning shift a fixed task: tomorrow's arrivals with no reply get a nudge.
• After check-in, move guests to the house group or guest app so the owner's phone goes quiet.