Guest Phone Numbers Stopped Arriving: Rebuilding the Contact Chain

When the booking no longer carries a number, the answer is not a better spreadsheet. It is an order of contact that assumes the first route is already closed.

Last updated: October 29, 2026

A booking that arrives without a phone number isn't a booking you can't service. It's one you service in a different order. The channel still hands you a name, dates and a thread. What's gone is the assumption that you can call the guest the moment something goes wrong, and that assumption was quietly doing more work than most hosts realised.

Key Takeaways

• The number was never yours. The channel brokered it, which means the channel can withdraw it.
• The thread comes first, not last. It carries timestamps and read receipts you can point at later.
• A relay number expires. It routes during the stay and stops when the stay does.
• Email is the link most hosts skip, and the only one you can capture before arrival.
• Write the chain into the listing, so the guest knows the route before they need it.

What the booking still gives you

Start with what's still there, because the list is longer than it feels on the day a number fails to appear. A confirmed booking carries a guest name, the dates, the number of guests, the amount paid, and an open message thread inside the channel. On most channels that thread reaches the guest's app and their inbox at the same time, which makes it the closest thing to a guaranteed route you have.

What changed is the phone number itself. Booking.com stopped passing guest phone numbers to connected software providers from 28 September 2026, as reported by eHotelier. Skift reported on 28 October 2026 that Airbnb now issues a temporary number instead of the guest's own when a booking comes through a PMS connection in the US and Canada. Both are platform policy, both are as published, and either can change again. Check each platform's current terms rather than this page.

The consequence is the same on both: the number you dial may not belong to the guest, and it may stop working when the stay ends. Treat any number you're handed as a route with an expiry date rather than a contact record you own.

That distinction sounds academic until the night it matters. A host who thinks they hold a number waits for a call that can't come. A host who knows they hold a route keeps the thread open and works down a list.

The four-link chain

Build the chain before you need it: four routes, in a fixed order, each one tried only after the one above it has failed.

The channel thread. This is the only route the platform guarantees, and the only one that produces a record with a timestamp on it. Make it the default for everything that isn't urgent: arrival times, door instructions, late check-out, a question about the parking. A guest who has been messaged in the thread three times before arrival is a guest who knows where to reply at nine at night.

The relay number. Temporary numbers route calls through to the guest for the length of the stay. Some accept messages, some don't, and the details sit in each platform's terms rather than in this article. Use it while it lives. Don't store it in your own system as the guest's number, because next season it will belong to someone else.

Email. This is the link most hosts skip, and it's the only one you can capture ahead of the stay. Ask in the thread, with a reason attached: you'd like to send the arrival details and a receipt. Keep it for the stay, then delete it on whatever schedule your privacy policy says. The ask works far better at booking than at ten at night on arrival day.

The door. The last link is physical. If every digital route fails, something at the property has to work. A lockbox code already issued in the thread. A key safe. A co-host or neighbour who can walk over. A printed note inside the unit with a number that answers. It's the least elegant link and the one that saves the booking.

localsbnb.com connects Airbnb, Booking.com, Agoda and Trip.com into one calendar and shows which channel each booking came from. That tells you which thread to open first. Its inbox covers Airbnb messages, so for the other three the conversation stays in that platform's own app, and the chain has to be run from there.

Where the chain breaks first

Four failures account for most of the nights that go wrong, and none of them are exotic.

The relay number only works one way. It's issued to route calls to the guest. Dialling it from your phone may not behave like a normal number, and a host who assumes otherwise spends twenty minutes listening to it ring. Test it once, on a booking where nothing is at stake.

The email was captured and never tested. A typo at booking surfaces on arrival night, when it's too late to send anything. Send one message to that address as soon as you have it, even if it only says the booking is confirmed and here's how to reach us.

One person owns the thread. The channel inbox lives on one phone, and that phone is with someone who's asleep, driving, or on another booking. An owner per arrival day fixes it, written into the rota rather than assumed.

The guest isn't the account holder. Bookings made for a parent, a colleague or a group's nominated organiser put a name on the reservation that won't be at the door. Ask one question in the thread before arrival: who's checking in, and how do we reach them if plans change?

What to write in the listing

The chain only works if the guest knows it exists, and the listing is where you say so once instead of explaining it per booking.

Put the primary route in the arrival message, in plain words: message us here, it's the fastest way to reach us, and it keeps a record of what we agreed. Ask for an email with a reason attached, not as a demand. Name the route that works outside business hours, and make sure it's a number a human answers, because the platform's number isn't one.

Then check the things guests need at the worst moment. If the wifi password, the parking instructions or the door code only lives behind a channel that wants a phone number, move a copy somewhere else: the unit, the thread, or a page the guest can open without logging in.

One more line is worth the space. If you host international guests, say which language you answer in and roughly when. A guest who knows you reply in English between eight and ten in the evening will wait. A guest who doesn't know will book a hotel instead.

FAQ

Can I still get the guest's phone number?

Not from the channel's booking feed, and not from us. The number is brokered by the platform, and platforms are tightening what they pass on rather than loosening it. What you can control is how many routes you have and what order you try them in.

The guest won't answer in the thread. What now?

Move to the next link instead of repeating the one that failed. Relay number, then the email you captured, then the physical route. Log each attempt with a time against it, because if the booking ends in a dispute the sequence is the evidence, and a memory of having tried isn't.

Should I collect ID or a number at the door?

Only what your local rules require, and no more. Where registration rules apply, they'll say what to record and for how long. Collecting a phone number at the door because the platform stopped sending one is a data-protection question dressed up as an operational one, so take advice on it rather than improvising.

A missing number looks like a systems problem and behaves like a routing problem. Four routes, tried in order, and the guest still gets in. localsbnb.com keeps the bookings, the channels and the dates in one place, so a guest you can't call is still a guest you can find.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. What a platform passes to connected software is set by that platform's terms and can change without notice, and rules on recording guest data differ by jurisdiction. Confirm both with the platform and, where registration applies, with the competent authority.