Airbnb Temporary Phone Numbers: Which Door Codes Still Work

Airbnb's temporary numbers expire two days after checkout. Whether your door codes still work depends on your PMS, not on Airbnb. Here is what each one does.

An Airbnb temporary phone number is a proxy number Airbnb assigns to a confirmed reservation. It routes calls and SMS between host and guest, and it expires two days after checkout. Airbnb still publishes the last 4 digits of the guest's real number on the reservation details page so hosts can build door codes, which is why a 4-digit code can survive this change and a longer one cannot.

Whether yours survived is not an Airbnb question. It is a question about your property management software, and the seven platforms below answer it seven different ways. Only one of them has published what it does. Every figure here was read off the vendor's own documentation or Airbnb's help centre on 19 and 20 October 2026, and carries the date it was checked.

Is Airbnb removing host access to guest phone numbers?

Partly, and less than the panic suggests. Airbnb withholds the full number and substitutes a temporary one, but it deliberately keeps publishing the last 4 digits of the guest's real number on the reservation details page, under its own heading "Suggested door codes". The feature is also not universal.

The governing document is Airbnb help article 3764, "How temporary phone numbers work", read 19 October 2026. It carries no publication date and no rollout date. Four things in it are worth knowing exactly.

• Expiry: "Temporary phone numbers expire two days after checkout." Airbnb does not say whether that clock starts at the listing checkout time, local midnight, or UTC, so do not write an SOP that assumes an hour.
• Scope: "a limited number of users in the United States and Canada." A reservation with either party outside those two countries gets no temporary number at all. If you host in the UK, Europe or Mexico, this is not your problem yet.
• Caller ID "may show up as" Airbnb guest or Airbnb host. Airbnb hedges with "may", so treat a recognisable caller ID as a bonus rather than a given.
• WhatsApp does not work on these numbers. Airbnb names WhatsApp and nothing else, so Signal, Telegram and FaceTime are undocumented rather than confirmed broken.

Three claims about this change that are out of date

An AI summary of this topic will confidently repeat things Airbnb's current documentation contradicts. Check whatever you read against these three.

First, "Airbnb removed guest last names" is false. Airbnb help article 3144, read 19 October 2026, states that after a booking is confirmed Airbnb shares the guest’s preferred first name and legal last name plus profile photo. The real name change was Oregon residents only, took effect in January 2022, replaced the FIRST name with initials before confirmation, and came out of a 2019 discrimination settlement. Different change, four years older, unrelated to phone numbers.

Second, "it is US only" is out of date. Airbnb's current text reads United States and Canada. Host forum posts quoting Airbnb in January 2026 record it as United States alone, so the page changed and the articles that copied it did not.

Third, the September 30 start date is not published by Airbnb anywhere. It traces to a single OwnerRez forum thread opened 18 September 2025. OwnerRez staff replied on 30 September 2025 that the Airbnb article being circulated was nearly a year old and did not mention the date at all. Article 3764 is still undated today.

Which PMS gives you which door code

Six of the seven platforms below have published nothing about what this change did to their door codes. That silence is the finding, and it matters more than anything Airbnb put out, because the same reservation produces a different code depending on which software generates it. Checked on 20 October 2026.

• Hospitable: codes are derived from the guest phone by default. On a 4-digit lock it uses Airbnb’s real last 4. At any other length it uses a random code. The only vendor that has published what it does.
• Guesty: random code generation by default, four digits by default. Most Guesty users were never exposed. Airbnb masking is not mentioned anywhere in its lock documentation.
• Host Tools: last four of the guest phone on a full Airbnb connection, random on messaging-only accounts. No documentation of masked or temporary numbers, on a page carrying no date.
• OwnerRez: phone-derived, and you choose anywhere from 4 to 10 digits. It has published nothing about receiving Airbnb’s real last 4, and its point-of-contact form is prepopulated with whatever number Airbnb sends. A 4-digit OwnerRez code is not automatically safe.
• Uplisting: generates a unique PIN per reservation, 4 to 9 digits, never phone-derived. Unaffected.
• Smoobu: states it never shares guest phone numbers with its lock provider. Structurally cannot be affected.
• Hostfully and Lodgify: neither publishes how codes are generated, and both help centres block automated reading. That silence is the finding. Ask them directly.

Your other channels are not moving in step. On the one platform that publishes this, Vrbo and direct bookings still pass a real guest phone number, so codes derived from them behave as they always did. Booking.com went further than Airbnb: since 28 September 2026 it shares no guest phone number at all, with no last-4 fallback, so those codes go straight to random.

Six of seven platforms left their customers to find this out at a keypad. The one that did publish tells you not to use the feature anyway.

So the universal claim is narrower than the one circulating, and it is this: Airbnb no longer hands any software the full guest number, so no code longer than 4 digits can be derived from a real guest number on any platform. Everything past that sentence is your vendor's implementation choice, not Airbnb's rule.

Which is a visibility problem before it is a lock problem, and it is the reason MagicBNB’s PMS connection covers Hospitable and Hostfully with a scope-aware sync of properties, reservations, reviews, guests, messages and payouts. Running two platforms across one portfolio is normal at this size, and it is exactly when you stop being able to answer "which doors did that reservation actually reach" from memory. Guesty sync is currently in development.

Why the carve-out is exactly four digits wide

Because Airbnb's own smart lock feature is four digits wide. That is the causal link most coverage of this change is missing.

Host Tools states plainly that "Airbnb only accepts 4-digit pins" and that locks using six-digit or other lengths "are not supported by Airbnb and are skipped automatically". Worth being precise about the source: that is a vendor’s statement. Airbnb’s own smart lock page, read 20 October 2026, describes "a unique code that’s only active during their trip" for Schlage, August and Yale, and does not publish a length at all.

Two things follow. Airbnb's native lock integration was never exposed to this change, because it keys codes to the reservation rather than to a phone number. And if you are already using it, the digit question is moot, which makes it the most direct fix available to a US or Canada host with a compatible lock. It does not cover co-host listings, which rules it out for a large share of managed portfolios.

Four digits is not a guarantee either

The one platform that documented this tells you not to rely on it. Its smart lock page says, in its own words, "Please do not use %guest_phone_last4%", recommends the generated code variable instead, and advises against telling guests their code will match their phone digits.

There is field evidence behind that advice. On that vendor's own changelog, a host reported on 21 December 2025 that he was receiving incorrect 4-digit codes from Airbnb while the correct phone number synced to the lock fine. Staff confirmed two days later there is no way to source the code from details held in the platform instead. A separate host question from 29 January 2026, asking whether the real last 4 are still arriving accurately, sits unanswered to this day.

Which points at the actual recommendation, and it is not "switch everything to four digits". It is to stop deriving door codes from phone numbers at all. Use the code your PMS or lock generates, send it as a literal string, and the next time a channel changes its mind about guest contact data your check-in does not notice.

That principle generalises past door codes. Vendor documentation in this market is mostly undated, and three of the Hospitable pages behind this post carry only "Updated this week" or "Updated over 2 weeks ago" rather than a real date. It is why every numeric surface in MagicBNB carries a Freshness pill reading Live, Syncing, Stale or Offline. A number that will not tell you how old it is should not be a number you make a decision on, and that applies to a vendor help page as much as to a dashboard.

What else breaks, and none of it is about digits

Digit count is the part that changed this year. It is not the part that causes most lockouts, and an audit that stops at code length will miss failures that were already happening before Airbnb touched anything.

• Timing. A code is created when the reservation is accepted, but it does not reach the lock then. On documented integrations, Yale, August, Schlage, Igloo and Nuki get the code three days before it activates, SmartThings around thirty minutes before, and KeyNest thirty days ahead. Last-minute bookings are pushed immediately.
• Alterations. Change the dates or the property and the code is updated or cancelled to match. A guest can be holding a message with code X while the keypad has quietly moved to code Y. Same symptom as the digit problem, and far more common.
• Collisions. If the code being set already exists on that lock, one documented platform retries with a different number later, after walking a fallback chain: the phone digits, then those digits reversed, then a completely random code.
• Capacity. Most locks hold about 100 codes, active or inactive. A full lock stops accepting new guest codes, and that failure looks nothing like a phone number problem while you are diagnosing it.
• Two connections at once. Running Airbnb’s own lock integration alongside your PMS integration is documented to make codes fail. Pick one and remove the other.
• Hardware floors. If your keypad cannot do four digits, none of the digit advice applies to you at all. Published ranges run 4 to 9 digits on one platform and 4 to 10 on another, and some locks reject codes containing particular digits.

The case for dropping phone-derived codes entirely

The digit framing makes four digits look like a reprieve. It is closer to a warning. A code derived from a guest's phone number is guessable by anyone who has that number, it does not rotate between stays at the same door, and it cannot tell you who actually opened it.

Part of the market never offered the feature at all. Guesty's lock documentation answers the question in one line: "Generating the code based on the guest's phone number is not supported." Uplisting generates a PIN per reservation and nothing else. Operators on those platforms have nothing to fix this week, which is the most useful argument available for how the rest of us should have set this up.

Entry attribution is the part that gets expensive later. If the code came from data the guest hands out freely, a keypad event is not evidence of who walked in. That becomes the problem the first time you file a damage claim or deal with a party you did not authorise.

Do Airbnb quick replies with the guest phone shortcut still send?

No. They are not sent at all, and nothing tells you. Airbnb states it in article 3764: the guest phone number shortcut in quick replies is no longer available, existing quick replies using those codes will no longer be sent, and templates must be updated. The sentence operators keep missing comes next: temporary numbers are not substituted for shortcodes.

There is no bounce, no warning, no flag in your inbox. A check-in sequence that has run for two years stops producing its third message, and you find out from a review mentioning that nobody told them how to get in. If you want to know whether this has already cost you, read the last sixty days of reviews for arrival complaints rather than waiting for the next one.

The vendor guidance around this has aged in a way that costs you a check-in. Guesty's inbox error documentation scopes contact-detail blocking to Inquiry status only and never mentions proxy substitution. Hospitable's tutorial on asking a guest for a phone number is dated 2 September 2025, a month before its own proxy changelog, and was never updated for it.

How do cleaners and co-hosts reach a guest on a temporary number?

A co-host can. A cleaner cannot. The temporary number only routes calls from a phone linked to the reservation, and Airbnb's documented fallback asks an unrecognised caller to enter a host or co-host number, or the reservation confirmation code, followed by the hash key. Confirmation codes contain letters, so Airbnb instructs callers to convert them on the keypad.

• H becomes 4. M becomes 6. The confirmation code HMKY53JZAS becomes 4659535927.
• Then press hash to connect.
• Texting instead gets you a reply asking for the confirmation code, which you send back.

Now read that as an instruction you are giving a cleaner standing in a driveway. Your housekeeper, your handyman and your office line are unlinked phones, and none of them was ever a party to the Airbnb message thread, which is the one channel Airbnb guarantees survives expiry. The fix most operators land on is a published ops number in the house manual and a standing rule that crews contact you rather than the guest.

The scheduling half of that is worth separating from the contact half. MagicBNB’s Today's schedule card gives a per-property strip of the day’s check-ins and check-outs with exact times, guest name, property and a status of pending, arrived or late. Crews who can see the day stop calling you to ask about it, which leaves the ops number free for the arrivals that actually went wrong.

Can you ask an Airbnb guest for their real phone number?

You can ask a confirmed guest to confirm that the contact information Airbnb gave you is a suitable way to reach them. That specific sentence is the compliant lane, and it is narrower than most advice on this topic suggests.

Airbnb’s Off-Platform and Fee Transparency Policy, read 19 October 2026, draws its line at booking confirmation and at purpose. Prohibited: all guest communications prior to booking must be on Airbnb; asking for contact information after a booking in order to run credit or background checks; asking guests to send photos of government ID prior to arrival; soliciting an email or mailing address after booking; and selling, sharing or using guest contact information for marketing.

Permitted, and useful: extra contact or identity information required by law, HOA rules or building security rules, provided your listing explains what is required and why before the guest books, and provided you can show Airbnb the requirement if asked. Airbnb also allows moving to another channel such as a chat app when the guest asks for it first.

One caution on the tooling. Several guest-portal products now capture and verify a real phone number by one-time passcode, on the reasoning that channel-supplied numbers may be virtual. Capturing a new number is not the same as confirming the one Airbnb supplied, so if you run one of those flows, make sure it sits inside the legal or compliance exception above and that your listing says so.

The three-minute audit

Run this on your next Airbnb reservation. Scope it to your own stack rather than to anything you have read, this post included.

• Find your code length. If your locks are integrated, it is in your PMS lock settings. If you program keypads by hand, it is whatever you have been typing, and the audit still applies to you: the number on the reservation page is now a proxy, so stop reading digits off it.
• Ask your PMS the one question that matters, in writing: for an Airbnb reservation, do you derive my door code from the guest’s real last 4 digits, from the Airbnb temporary number, or from a random code, and at what lengths? One platform has published its answer. The other six have not.
• Search your message templates and house manual for "last four digits of your phone" and every variant. On a 4-digit Hospitable lock that copy is still true today. Everywhere else it is a guess, and it is the sentence that strands a guest at a keypad.
• Open your Airbnb quick replies and delete any built on the guest phone shortcut. They are not sending, and Airbnb does not substitute the temporary number in.
• Give crews a route to you that is not the guest message thread, because the keypad confirmation-code fallback is not usable in a driveway.
• Check your second channel. Hospitable documents that since 28 September 2026 Booking.com no longer shares guest phone numbers with it at all, with no real-last-4 fallback, so those codes go straight to random.

Replacement copy that works on every code length and every platform: "Your door code is 4417. It works from 3pm on the day you arrive until 11am on the day you leave." Literal, checkable, and immune to whatever a channel decides about guest contact data next quarter.

What this costs if you ignore it

Start with the part that is not a forecast. On a Hospitable account with a non-four-digit lock, every Airbnb arrival gets a random code. Not some. Every one, already, today. If your house manual still derives the code from a phone number, every one of those guests is holding instructions that do not match their keypad.

A worked example. Six doors, six-digit keypads because that is what the locks shipped with, house manual copy unchanged since 2023, around thirty Airbnb arrivals a month. Sending someone out to let one guest in costs a modelled estimate of $52.15 in burdened labour, and that is before any refund and before the review.

How this estimate was built

• Label: Modelled estimate, not reported data. It prices one person attending one lockout and nothing else.
• Formula: hourly median wage, divided by the wage share of total compensation, multiplied by labour hours per callout.
• Wage: $23.84 an hour, the 2025 median pay for General Maintenance and Repair Workers, BLS Occupational Outlook Handbook, May 2025 reference period, read 20 October 2026.
• Burden: wages and salaries are $33.61 of $49.01 total hourly compensation for installation, maintenance and repair occupations in private industry, BLS Employer Costs for Employee Compensation, June 2026 reference month, released 9 September 2026. A 68.58% wage share.
• Worked line: $23.84 divided by 0.6858 is $34.76 an hour burdened, times 1.5 hours is $52.15. Sensitivity: $34.76 at one hour, $86.91 at two and a half.
• Assumption: 1.5 labour hours per callout, covering travel and resolution. No government source publishes this, so it is tested rather than asserted.
• Excludes, and these dominate: refunds and goodwill credits, the rating cost, after-hours premiums, vehicle cost, and your own time if you drive out yourself. It also does not model how many mismatched arrivals become callouts, which is the variable that turns this into a portfolio number.
• Checked 20 October 2026. Rerun it: your hourly cost divided by 0.6858, times your real door-to-door time.

Both inputs are public: the Occupational Outlook Handbook wage page and the Employer Costs for Employee Compensation release. Check them rather than taking the figure.

The part the model leaves out is the one that compounds. A failed arrival lands in the communication sub-score, which Airbnb breaks out separately from cleanliness and accuracy, and three of them at one door in a quarter will show up as a rating problem months before anyone connects it to a keypad digit count.

Watching that as a portfolio metric rather than a per-property surprise is what MagicBNB’s Guest Experience dashboard is for: review aggregation across every door with the rating breakdown by category, including communication, next to review submission rate per property. A door whose communication score slides while cleanliness holds steady is telling you something specific about arrivals.

Frequently asked questions

Is Airbnb removing host access to guest phone numbers?

Airbnb is replacing the guest's full number with a temporary one that expires two days after checkout, but it still publishes the last 4 digits of the guest's real number on the reservation details page so hosts can build door codes. You lose the full number, not every digit, and only on reservations inside the limited United States and Canada rollout.

When does an Airbnb temporary phone number expire?

An Airbnb temporary phone number expires two days after checkout, in Airbnb's own published wording. Airbnb does not say whether that clock starts at the listing's checkout time, at local midnight, or in UTC, so treat the final hours as unreliable and move anything time-sensitive into Airbnb Messenger, which keeps working after the number dies.

Is a masked phone number the same as an Airbnb temporary phone number?

Yes. Airbnb calls the feature temporary phone numbers, while property management software vendors including Hospitable describe the same thing as a masked number, and operators often call it a proxy number. Three names, one mechanism: a routed number that sits between host and guest and expires two days after checkout.

Can I still use the last 4 digits of a guest's phone number for a door code?

On Hospitable, yes, and only at 4 digits, because it receives Airbnb's real last 4 and falls back to a random code at any other length. On every other platform checked, the answer is undocumented or different, and Hospitable itself advises against the practice. The safer answer on any platform is to send the literal generated code instead.

Does Airbnb still show the guest’s last name to hosts?

Yes. Airbnb's current documentation, read 19 October 2026, says it shares the guest's preferred first name and legal last name plus profile photo after a booking is confirmed. The claim that last names were removed conflates this with an Oregon-residents-only change from January 2022 that replaced first names with initials before confirmation.

Can I ask a guest for their real phone number without breaking Airbnb’s rules?

You can ask a confirmed guest to confirm that the contact information Airbnb already provided is a suitable way to reach them. The Off-Platform Policy prohibits asking before booking, asking in order to run credit or background checks, soliciting an email or mailing address after booking, and using guest contact details for marketing or to move future bookings off the platform.

Why do some hosts still see real guest phone numbers?

Because the rollout covers only a limited number of users in the United States and Canada, and Airbnb has never quantified how many. A reservation with either party outside those two countries gets no temporary number at all, which is why operators in the UK, Europe and Mexico were still reporting full numbers in January 2026.

Key takeaways

• Airbnb temporary phone numbers expire two days after checkout, and Airbnb Messenger is the only channel it guarantees still works afterwards.
• Airbnb publishes the last 4 digits of the guest’s real phone number on the reservation details page, which is why a 4-digit door code can survive and a longer one cannot.
• Whether yours actually survived depends on your software, not on Airbnb: Hospitable uses the real last 4 at 4 digits and a random code at any other length, Guesty and Uplisting were never phone-derived by default, and OwnerRez, Host Tools, Hostfully and Lodgify have published nothing.
• The one vendor that documents any of this tells hosts not to use the phone-digit short code at all, and to send the generated code instead.
• Airbnb quick replies built on the guest phone shortcut no longer send, and Airbnb does not substitute the temporary number into them.
• Calls from any phone not linked to the reservation, including your cleaner and your office line, do not auto-route and fall back to typing a letter-to-keypad confirmation code.
• Since 28 September 2026 Booking.com shares no guest phone numbers at all with Hospitable, with no last-4 fallback, so a second channel is already degraded.

Related reading

If this audit turned up a keypad problem, self-check-in and smart locks across a multi-property portfolio covers code strategy at scale. If it turned up a template problem, the messaging system multi-property operators actually run is where the replacement sequence lives.

Find out which of your doors still runs a phone-derived code, and what each one actually kept this month. See your portfolio in MagicBNB →

About MagicBNB

MagicBNB is portfolio analytics for operators running 2 to 20 short-term rental doors, built for the case where the operations live in one system and the money lives in another. It connects to Hospitable and Hostfully on one side and your bank accounts on the other, then reports what each door actually kept rather than what the booking screen said. The Smart transaction ledger matches every deposit against the payout records pulled from your PMS, so reconciliation stops being a quarterly archaeology project. The Monthly Portfolio Report Builder turns that into owner statements with PDF and Excel export, which is the part co-hosts managing other people's doors spend their Saturdays on. And the Property Health Grid puts a margin-derived health dot on every property, so the door going wrong surfaces before the quarter closes.