Back to Blog
Hosting Tips November 5, 2026 12 min read

Airbnb Temporary Phone Numbers: What Changes for Guest Access

Why Airbnb's suggested door code can differ from the number in your booking software, what that means for guest messages, and what hosts should check now.

Last reviewed: November 16, 2026. This is a living guide. This update records Hospitable's withdrawal of its suggested-door-code API field and what it means for GuestsKey integrations. The update history below records material revisions. This date is our review date, not a claim that Airbnb began its rollout today.

If your check-in message says “your door code is the last four digits of your phone number,” review that workflow before your next arrival. The number your booking software receives may no longer be the number your guest expects you to use.

For hosts, the practical goal remains simple: the guest needs the correct code, at the right time, through a channel they can actually receive. Here is what we know and what still needs testing.

November 16 update: Hospitable has withdrawn its suggested-code field

Hospitable has notified integration partners that it rolled back guest.suggested_door_code. The field is no longer available in reservation responses or webhooks. This supersedes the suggested-code support described in our November 12 update.

Hospitable says it intends to revisit the field alongside more granular controls for granting and revoking integration permissions, particularly for sensitive information such as door codes. It has not provided a return date. November 16 is the date of this guide update, not a confirmed time when the field stopped appearing in every reservation.

We are removing GuestsKey's dependency on the withdrawn field. Existing assigned codes should be verified in GuestsKey and communicated as the actual digits; they should not be changed simply because the upstream field disappeared. New reservations must use the information and code-generation settings available to the integration. A phone-based setting cannot recover a personal phone number that the provider no longer supplies.

These changes have consequences beyond the platform making them. A field appearing in a PMS interface does not mean it is available to that PMS's integration partners. When an API field is introduced and then withdrawn, downstream services must revise code generation, regression tests, guest-message guidance and support documentation again. Hosts are left checking that the code on the door still matches the instructions their guest received. Privacy controls matter; so do stable API contracts, clear availability notices and a workable transition for dependent integrations.

What Airbnb documents today

Airbnb describes these as temporary phone numbers. They are contact numbers assigned to a reservation, rather than an encrypted version of the guest's personal number.

  • Temporary numbers are available for eligible reservations in the United States and Canada.
  • Airbnb says connected software no longer receives guests' real phone numbers worldwide. Software receives a temporary number for eligible bookings; other bookings may have no phone number supplied.
  • Airbnb separately displays the guest's real last four digits under Suggested door code.
  • Quick replies containing Airbnb's removed guest-phone-number shortcut no longer send until updated; temporary numbers are not substituted.

These points come from Airbnb's temporary phone number guidance. Availability varies by reservation, so one booking working as expected does not establish that the next one will have the same contact data.

The numbers support calls and SMS, but not WhatsApp. See Airbnb's guidance on contacting guests. They expire 48 hours after checkout or immediately upon cancellation, according to its temporary-number guidance.

Why the door code can differ

In one booking we investigated, we traced the assigned code back to the phone suffix in the original integration record. That establishes where the code came from. It does not establish that the number was the guest's personal phone number, or that the guest entered anything incorrectly.

There are three values to compare for the same reservation:

ValueWhat to verify
Airbnb's suggested codeWhat Airbnb shows for that reservation
The assigned access codeWhat your lock-management system actually created and scheduled
The guest's instructionsWhat the guest was told to enter

A suggested value on Airbnb is not evidence that another system programmed that value onto the door. Likewise, a code visible in a dashboard still needs a successful lock status and the correct access window.

Code timing and code digits are separate checks. Moving the activation time does not explain which source supplied the digits. A last-minute booking leaves less time to catch a mismatch, but it does not by itself prove the cause.

Our recommendation: communicate the actual assigned code, rather than asking the guest to calculate it. If you use a message template field, confirm that it inserts the assigned access code, not a phone suffix. Do not change an occupied stay's code solely to make two screens agree without coordinating with the guest.

A reachable phone number does not prove automated SMS works

Airbnb says unrecognized SMS senders receive a reservation-confirmation-code challenge. See its explanation of unrecognized calls and texts.

That matters for automated arrival messages. A host's successful phone call does not test an automation service's SMS sender. An SMS provider accepting a message also does not prove the guest received it. We need to verify receipt through the actual sending path before calling it reliable.

OwnerRez documents its own handling: it keeps the Platform Phone on the booking, separate from the guest's contact record, and registers its SMS sender with Airbnb when sending. Its documentation also says the temporary number can change during a stay. Those capabilities describe OwnerRez's service; they do not establish equivalent delivery for another application's sender. OwnerRez's Airbnb contact guide

The same distinction applies to replies. Delivering an outbound message does not prove that an incoming text can be matched to the correct guest and reservation. Names and booking dates can help locate a stay; they are not sufficient proof to authorize unlocking a door.

Set up code messages for your PMS and booking channel

Start with the system that supplies your bookings to GuestsKey. These instructions describe GuestsKey-managed codes. A PMS's own smart-lock product may have different fields and delivery rules. Creating a custom field does not connect it to GuestsKey automatically.

For every delivery route, honor the reservation's release time, agreement requirements and any host hold before sharing access details.

OwnerRez: booking custom field and channel trigger

OwnerRez confirmed to GuestsKey on November 5 that its booking-level platform phone field went live on October 29. Empty personal contact fields can be expected; there is no alternate OwnerRez API permission or endpoint that supplies the real number. OwnerRez also confirmed that its API does not currently expose Airbnb's suggested code to third-party integrations. October 30 was our earliest observed occurrence in a retained webhook sample, not a confirmed worldwide Airbnb launch date.

  1. Enable code sync in GuestsKey. Open the property's Automation tab, enable Sync codes to OwnerRez under guest automation, and select Save Guest Settings. Check the booking's code-sync status.
  2. Find the booking field in OwnerRez. GuestsKey creates or reuses GuestsKey Access Code when it syncs a code. In Settings → Custom Field Definitions, confirm it is a Booking field. New definitions use GKCODE, with template code {BXGKCODE}. Select your account's actual field if it has a different code; do not create a second field and assume GuestsKey will fill it. OwnerRez custom fields
  3. Create the channel template. Go to Settings → Messaging → Templates → Channel, create a Booking template and use Insert Field to select GuestsKey Access Code. For the default field, the message can include: Your door code is {BXGKCODE}. Save and Preview it against a specific reservation. OwnerRez channel templates
  4. Check when the field becomes available. If GuestsKey's OwnerRez Code Release Gate is enabled under Settings → OwnerRez automation, code publishing is delayed until the configured window. Schedule the code message after release and successful sync. An earlier message can contain a blank field even though the lock code is already scheduled.
  5. Add a trigger. In Settings → Messaging → Triggers, attach the booking template to an appropriate arrival-time trigger and scope it to the intended properties and booking channels. Saving a template alone does not schedule delivery. Review last-minute bookings whose normal send time has already passed. OwnerRez arrival-message setup
  6. Verify one reservation end to end. Compare the rendered code with GuestsKey, check the access window and each entrance's lock status, then check the sent channel conversation. If the code is due for release and all access requirements are satisfied, a blank, stale or failed sync can be handled by manually sending the verified code for that reservation. An intentional release delay or host hold is a reason to wait.

Optional portal link: when GuestsKey's guest portal is enabled and its URL has synced, the default booking field is GuestsKey Portal URL, {BXGKPORTAL}. Preview that field separately and confirm the guest can open the link. It is a link, not the door-code field, and does not establish that browser unlocking is available. OwnerRez integration help

Lodgify: add the KeyCode placeholder to the check-in message

GuestsKey syncs the assigned code to Lodgify's reservation access-code field. Use {{KeyCode}} to include it in your scheduled message; no custom field is required.

  1. In Lodgify, open Inbox → Automate → Scheduled messages → Check-in instructions → Edit content → Messaging placeholder.
  2. Insert {{KeyCode}}, for example: Your door code is {{KeyCode}}. If your message already contains {{CheckinInstructions}}, keep it for directions and add the code placeholder separately.
  3. Save the content, check that the message is enabled and select the intended delivery channels. For Airbnb bookings, verify Airbnb-channel delivery. Schedule the message after the code is available and due for release.
  4. Check a rendered reservation message against the actual assigned code in GuestsKey, then check the sent conversation and guest receipt. Review last-minute bookings and any separate arrival templates for conflicting instructions.

Keep the placeholder in the shared template, rather than one guest's literal PIN. The Lodgify help-center walkthrough covers setup, the distinction between {{CheckinInstructions}} and {{KeyCode}}, and blank or mismatched values.

Hospitable account: suggested-code API support has been withdrawn

Hospitable's guest.suggested_door_code field is no longer supplied in reservation API responses or webhooks. GuestsKey cannot rely on it for new reservations. Our November 12 description of using that field has been superseded by Hospitable's rollback notice; no date has been announced for its return.

The Hospitable PMS connection and Hospitable Connect remain separate integrations. This rollback does not establish that Connect exposes the field or that either connection delivered a guest message. Verify the actual assigned code, access window and each guest entrance's status.

Hospitable documents %smartlock_code% for compatible smart-lock integrations. GuestsKey does not currently write its assigned codes into that shortcode. Adding it to a Hospitable rule therefore does not establish that the message will contain your GuestsKey code. Hospitable's shortcode guidance

For a GuestsKey-managed lock:

  1. Verify the reservation's code and access window in GuestsKey.
  2. In Hospitable's Inbox, open the matching reservation and use the reply box to send the actual digits and entrance instructions. Hospitable's inbox supports manual guest messages. Hospitable inbox guide
  3. Check the conversation and upcoming automated messages for conflicting instructions. Do not type a shortcode into a manual reply expecting it to expand: Hospitable says that sends the literal shortcode text. Hospitable shortcode usage

If Hospitable itself manages the lock, follow its own smart-lock setup and before-check-in messaging rules. That is a separate setup; do not turn on a second code manager just to obtain a template tag.

Airbnb through Hospitable Connect: template messaging is not enabled yet

Hospitable Connect lets hosts connect Airbnb to GuestsKey without a Hospitable PMS subscription. That booking connection does not give you Hospitable's messaging-rule setup.

GuestsKey has deployed support for a provider-created template to send the assigned code directly into the Airbnb reservation conversation. Messaging remains switched off while provider access and controlled delivery are verified. This is not yet an available automatic delivery route for hosts. Connecting Airbnb or entering a shortcode does not enable it.

The intended template route uses the reservation conversation, not SMS. It is designed to respect the access start time, confirmation status, agreement requirements, host holds and confirmation of the same code on every applicable door. We will add activation instructions after the complete delivery path is verified. For now, use Airbnb Messages:

  1. In Airbnb, go to Messages → Settings → Manage quick replies. Edit any shared arrival template that still promises the last four digits of the guest's phone number.
  2. Open the guest's conversation. Send the verified GuestsKey code directly, or choose Add (+) → View scheduled quick replies and edit that reservation's upcoming message. Put the PIN in the reservation-specific message, not the shared template.
  3. Check the message timeline for sent or skipped messages, especially for last-minute bookings. Airbnb lets hosts edit an individual scheduled reply without changing the shared template. Airbnb scheduled quick replies

Airbnb does not expand OwnerRez's {BXGKCODE} or Hospitable's %smartlock_code% when you paste those tags into an Airbnb quick reply. Use the actual digits for manual messages.

BookingDirect and other booking channels

BookingDirect connected directly to GuestsKey: there is currently no GuestsKey code-writeback field to configure in BookingDirect. Verify the assigned code in GuestsKey and send it through the reservation's established guest communication route. If you rely on GuestsKey email or SMS notifications, confirm the booking has usable contact details and check receipt. BookingDirect bookings managed through OwnerRez: use the OwnerRez instructions above for the OwnerRez booking. BookingDirect integration help

The message destination matters as much as the field:

Booking channelDelivery check
AirbnbUse the reservation's Airbnb conversation, directly or through a connected PMS channel inbox. A PMS email template is not an Airbnb-channel message.
Vrbo or Booking.comUse your PMS's supported channel-message route for that connected reservation and check the sent thread. OwnerRez supports channel messaging for all three platforms.
Direct bookingThere may be no platform inbox. Use the booking's established email, SMS or other agreed contact route and confirm receipt.

See OwnerRez's channel-messaging overview for its supported channels. Template tags belong to the PMS that expands them; do not copy them unchanged into another system. A channel change or a missing contact field should prompt a delivery check, not an assumption that a different route worked.

Our Airbnb contact-change FAQ covers missing contacts, random codes, portal links and the host checklist.

What hosts can do now

  1. Check upcoming arrivals. Compare the assigned code, its status on each guest entrance and the activation time with the instructions the guest will receive.
  2. Review message templates. Replace assumptions about phone digits with the actual assigned code. Check the final rendered message, including any scheduled messages maintained separately in Airbnb and your property-management system.
  3. Use the reservation's Airbnb conversation for essential instructions. Where supported, that can be through your property-management system's Airbnb inbox. If SMS or email delivery is unverified, do not make it the only place the guest can find their code.
  4. Confirm the guest can access the instructions. If you share a private guest portal link, verify it arrives and opens. Airbnb says its message screening can block external links or require content to be removed. Airbnb's message-review guidance
  5. Keep a practical arrival fallback. Give your co-host or assistant the current assigned code, the relevant entrance and a way to reach you. For an imminent arrival with a discrepancy, resolve the code and communication together.

For example, after confirming the assigned code and access window, a message can say:

Your door code is [assigned code]. It works at [entrance] from [activation time]. Please use this code when you arrive. Reply here if you need help.

Replace the brackets with the verified details before sending. A random reservation code can avoid dependence on phone digits, but the guest still needs to receive it.

What has shipped, and what still needs verification

GuestsKey has released temporary-contact handling and OwnerRez-backed Airbnb SMS confirmation-challenge support. These address identifying a delivery contact and answering Airbnb's sender challenge. The Hospitable suggested-code support described in our November 12 update is being rolled back following the provider's withdrawal of the field; it is no longer an available source for new reservation codes.

Automatic temporary-number SMS recovery is not yet verified end to end. In an authorized manual exchange, Airbnb accepted a reservation confirmation, asked for earlier messages to be resent, and then reported the resubmitted SMS was sent. The current automatic handler answers the confirmation challenge but does not perform that follow-up resend. Inbound routing also needs completion and controlled verification. Do not treat provider acceptance as proof of guest receipt or rely on this unfinished automatic path for essential arrival instructions.

Hospitable Connect template messaging is deployed but switched off, pending provider access and a controlled delivery test. Continue sending verified access instructions in the reservation conversation. Private portal links and door-unlock actions are separate capabilities; sharing a link does not establish that the guest received it or can unlock a door with it.

Questions we are tracking

  • Which integrations expose Airbnb's suggested code to connected applications, separately from a contact number?
  • Can GuestsKey's SMS sender reach the reservation's temporary number consistently, including any verification step?
  • What information reaches us on the return path, and how can a guest securely authorize an access request?
  • How do number changes, cancellations and expiry affect messages already scheduled?

OwnerRez documents suggested-code use in its own Seamless Entry feature. That does not, by itself, establish access to the same value for third-party integrations. OwnerRez confirmed to GuestsKey on November 5 that its public API does not expose that suggested value today. OwnerRez's door-code guidance

Hospitable has withdrawn its Public API suggested-code field pending more granular permission controls, with no return timeline. The separate data contracts for Hospitable Connect and Lodgify must be verified independently; availability in one integration should not be assumed for another.

We cannot predict whether Airbnb will revise this behavior or when. Our guidance will follow documented changes and observed results.

If an upcoming GuestsKey reservation has conflicting access instructions, contact us with the booking reference, integration and a description of the mismatch. Keep guest contact details, door codes and private portal links out of public posts.

Update history

  • November 16, 2026 — Hospitable rollback. Recorded the withdrawal of guest.suggested_door_code from reservation responses and webhooks, the stated plan for more granular permissions and the absence of a return timeline. Superseded the November 12 availability claim, explained the downstream impact and updated the linked Hospitable and Airbnb help guides. Existing assigned codes remain the values hosts should verify and communicate.

  • November 12, 2026 — Hospitable and messaging update. Added released Hospitable Public API suggested-code support; separated it from Connect's not-yet-enabled conversation templates; corrected the SMS release status and documented the remaining automatic resend and delivery-verification work. Updated the linked integration guides and FAQ.

  • November 5, 2026 — Channel setup update. Added OwnerRez custom-field, release-timing and trigger steps; current Lodgify, Hospitable, Connect and BookingDirect delivery routes; and reservation-specific Airbnb quick-reply instructions.

  • November 5, 2026 — Host guidance update. Added OwnerRez's confirmed API release date and third-party limitations, PMS-specific delivery instructions and a dedicated FAQ.

  • November 5, 2026 — Initial review. Added documented contact-number changes, host checks, the distinction between assigned codes and phone digits, and the current verification status of GuestsKey's messaging and access work.

GK
GuestsKey Team
Building automation tools for vacation rental professionals