Every few weeks a host asks why Staykey doesn't SMS their guests. It's a reasonable question — text messages have near-100% open rates, they land on lock screens instead of an app inbox, and every other business the guest interacts with uses them. A check-in tool that texts the code at 2 p.m. on arrival day feels like the obvious move.
We've deliberately chosen not to. This post is why.
The core constraint: stay in the booking thread
Airbnb and VRBO both have the same rule, phrased slightly differently: communication before and during a stay should happen inside their message thread. Not off-platform. Not in a side channel. Not over SMS from a third party.
The reasoning is theirs, not ours, but it maps onto real host interests:
- AirCover evidence. When a claim gets adjudicated, the adjudicator reads the Airbnb message thread. If half your communication with the guest happened over SMS, that context is invisible to the process, and your claim gets weaker.
- Dispute resolution. A "they said it was fine" argument is much easier when the whole conversation is on-platform and timestamped by Airbnb itself.
- Guest protection. Airbnb knows — and most regulators increasingly know — that asking a guest to move to WhatsApp or SMS is how scams work. Hosts who stay on-platform look credible. Hosts who don't, don't.
Airbnb doesn't suspend listings for every off-platform message. But they do treat it as a signal, and they deprioritize hosts whose message volume on-platform drops below the norm. When we looked at whether we should text guests directly, the answer was "not if we want our hosts in good standing with the marketplace they depend on."
The 10DLC and A2P problem
There's also a mechanical problem, even if you wanted to ignore the platform rules.
Sending SMS to guests from a business you own is regulated traffic. In the US it falls under something called 10DLC (10-digit long-code messaging) and requires A2P registration — Application-to-Person. You register the business that's sending, the use case, the kind of content, the expected volume, and the consent model.
For a software company that texts millions of guests across thousands of hosts, the compliance answer is "the software is the sender, and the recipient must give consent to the software, not to the host." That's the model a standalone guest-texting app has to run. It works, but:
- The messages come from a number the guest doesn't recognize
- The sender is labeled as the software, not the host
- Every guest sees the same sender ID across hosts, which dilutes the host's brand
- Consent flows are long, legalistic, and often where the whole flow breaks down
We could do this. A couple of competitors do. But the guest experience is noticeably worse — a text from "+1 855..." on arrival day that references your property is uncanny, not reassuring. And the host's brand takes a back seat to the platform that's legally responsible for the send.
Fragmentation across booking sources
The third problem is practical. Most hosts don't sell only on Airbnb. Bookings come from:
- Airbnb
- VRBO
- Direct (the host's own website)
Each platform has its own message thread with its own notification mechanics. If you move the authoritative communication to SMS, you've now got multiple threads where the guest might reply — because if SMS is how they got their check-in info, SMS is where they'll ask a question — and you're manually triaging across channels.
Keeping messaging in-platform preserves the single source of truth: the Airbnb thread is the Airbnb conversation, and the VRBO thread is the VRBO conversation. Replies land where they originated. Nothing gets crossed.
The durable guest link we generate works the same way across platforms — it's dropped into whatever scheduled-message template that platform supports. The guest's entry point varies; the destination (the durable link, the code, the house guide) does not.
What we do instead
Here's the model Staykey is built around:
- Staykey generates a single durable link for the booking — the moment Airbnb or VRBO confirms the stay, or the moment a direct booking is created.
- You drop that link into your booking platform's scheduled-message template once. Airbnb sends it on your behalf at booking confirmation and again at T-minus-48h. VRBO has the equivalent. For direct bookings, you send it in your own confirmation email.
- The link stays live for the whole stay. The access code becomes visible at check-in time. Wi-Fi, parking, house guide, and the emergency contact are all there from the start. If anything changes — an extended stay, an updated Wi-Fi password, a house-guide fix — the guest sees it instantly. No new message required.
- The guest messages you in the platform's own thread. They ask, you reply, Airbnb logs everything. AirCover paper trail intact.
What we don't do: text the guest from a +1 855 number with the code at 2 p.m. We've looked hard at whether there's a version of that worth building, and we keep landing at no. The workflow above is slightly more work to set up — you have to paste a link into your Airbnb auto-message template once — and significantly less work to live with.
Where SMS does fit
One clarification, because we do send SMS elsewhere: SMS is a real part of how Staykey handles cleaning workflows. Cleaners and cleaning companies opt in during onboarding, provide their own phone number, and receive operational notifications — new cleaning assigned, schedule change, back-to-back alert. That's consented, operational, point-to-point messaging between the host's staff and the software, not a third party broadcasting to a paying guest.
The distinction matters. Cleaners are in a working relationship with the host; guests are in a commercial relationship with the booking platform. The same tool applied to both would be wrong in opposite directions.
The one-paragraph version
Airbnb wants communication in their thread. 10DLC wants SMS senders to be the software, not the host. Multi-platform hosts benefit from a single source of truth per booking. And guests respond better to a link from their host inside the Airbnb conversation they already trust than to a text from an unknown number. All four pressures point the same direction: send messages in-platform, make the link durable, and let the link do the heavy lifting.
That's why Staykey doesn't text your guests. It's not a missing feature. It's the design.
Related reading
- Why we rebuilt the guest portal around one link — the companion piece on the guest-side experience
- How to send check-in instructions that actually get read — the 3-message, in-platform cadence
- Automating Staykey links in Airbnb messages — the exact template drop-in
- Guest Experience — what your guests actually see when they open the link