OwnerRez stores Airbnb's temporary guest numbers on the booking, and they stop working two days after checkout

OwnerRez now saves the temporary phone number Airbnb hands over for a booking, and it deliberately keeps it off the guest's profile. The change shipped on 29 October and was written up in the monthly product update on 3 November.

The reason for the split is that these numbers are not the guest's. Airbnb issues a platform number that routes to the guest for the duration of the stay. OwnerRez stores it on the booking record, so it is available where you need it without overwriting anything on the contact.

What you can do with it

The number works for SMS triggers, broadcast messages and replies from the Inbox. Each booking shows the last day on which messages can be sent, which is the detail that saves a guess.

That date matters because the number expires. Airbnb platform numbers stop working two days after checkout, and they can change part way through a stay. OwnerRez refreshes the stored number at each booking sync, so a mid-stay change is picked up without anyone re-entering it.

If a guest already has a real phone number on their contact, OwnerRez keeps it, and SMS continues to go to that number rather than the platform one. So hosts who collect real numbers through their own agreements are unaffected.

Three things it will not do

This is where the release is unusually candid, and where the operational risk sits.

Platform numbers do not merge guests. A repeat guest arriving on a new Airbnb booking comes with a different platform number, so OwnerRez cannot use it to recognise them as the same person. Anyone relying on phone matching to spot returning guests loses that for Airbnb traffic.

They do not match banned guests. If you maintain a blocklist and it keys on phone number, an Airbnb booking from someone on that list will not be flagged by the platform number. That is a gap worth knowing about rather than discovering.

And they do not work for door codes. Any lock integration or access code that uses the last digits of a guest's phone number cannot use the platform number. If your check-in instructions tell guests to enter the last four digits of their phone, Airbnb bookings need a different method or the real number collected separately.

For hosts and managers

For most hosts this is a straightforward improvement. Messaging an Airbnb guest by SMS has been awkward precisely because the real number was often absent, and having the platform number land automatically with an expiry date attached removes the manual step and the guesswork about whether a text will arrive.

The three exclusions are the part to act on. Check whether anything in your setup keys on phone number: a smart lock code scheme, a guest blocklist, a CRM dedupe rule. Those all need to be checked against Airbnb bookings specifically, because the number sitting on the booking now looks like a phone number and behaves like one in messaging, but does not identify a person.

It is also a reminder of where the leverage sits. This is Airbnb's masking policy, not OwnerRez's design choice, and the same constraint applies to every property management system connected to the platform. OwnerRez has handled it about as well as a PMS can, by storing the number where it belongs and telling you plainly what it cannot do. The underlying problem, that the channel stands between a manager and their guest's contact details, is not something a PMS can fix.