Guest Referrals That Stay Inside Platform Rules

A returning guest is the cheapest booking you will ever get. The expensive part is the one message that moves the next booking off the platform.

Last updated: September 23, 2026

Nobody sets out to break a platform rule. They set out to be nice to a guest who has just said they would love to come back, and one sentence later they have proposed moving the payment off the platform that introduced them.

A referral conversation and a payment conversation are two conversations with two risk profiles, and the discipline of repeat business is keeping them apart. This guide covers why they belong in different places, and what the platform protects. It sets out three habits that read well when somebody scrolls back. And it shows how to turn one good stay into a second booking without asking for anything off-platform.

Hosting has one growth lever that costs nothing: a guest who had a good stay and would like another one. Nothing about asking for that is risky.

Key Takeaways

• The referral is fine, the reroute isn't. Asking to be remembered isn't the same as asking to be paid elsewhere.
• One conversation, one purpose. The thread that invites a return should never be the thread that discusses how to pay.
• The platform protects the transaction. It underwrote the payment and the dispute; a booking that leaves removes what it sold.
• Three habits survive a read-back. Ask for the return, give something deliverable inside a booking, write it where it can be seen.
• A repeat guest needs no discount. The thing they want is the same unit on the dates they want, booked normally.

Why a referral conversation and a payment conversation have to stay in different places

A referral conversation is a hospitality gesture. It says: I would like you back, and if you know somebody who would like this place, tell them. It costs you nothing, it makes the guest feel remembered, and it's the ordinary way small lodging businesses have always grown. Every platform benefits from it, because the outcome is another booking.

A payment conversation does something else entirely. It proposes that money move along a route the platform can't see, can't hold, and can't refund. The moment that suggestion is written down, the message stops being hospitality and becomes a proposal to remove the platform from a transaction it considers its own.

The two are easy to confuse because they usually happen in the same breath. A guest says they would love to come back in the spring; you say wonderful, and next time we can sort it directly and you will save the fee. Same guest, same goodwill, and one sentence that changes the nature of the exchange. Keeping the conversations apart is a structural fix rather than a matter of tone: decide in advance that the thread where you invite a return will never contain a sentence about how money should move.

There's a second reason, and it's not about rules at all. An off-platform payment strips protections from both sides. The guest loses the dispute route and the payment record; you lose the booking record, the review link and the channel history. Hosts who take payment outside aren't cleverly avoiding a fee — they're taking on the risk the fee was buying.

What the platform is actually protecting, so you can see the line before you cross it

Treat the following as inference rather than published policy. What a platform protects isn't the introduction, which it gives away freely, but the transaction it underwrites. It holds the money until check-in, runs the dispute process, provides whatever guarantee it advertises, and keeps the review system honest by tying reviews to bookings that actually happened. A booking that closes outside that system removes the thing it sold, and the platform's interest in stopping it is therefore structural rather than spiteful.

That framing gives you a usable test. Ask whether the behaviour you're considering would, if every host did it, leave the platform holding the introduction and the risk while somebody else keeps the transaction. Asking a guest to return doesn't do that — the next booking still runs through the platform. Collecting contact details in order to close a deal later does. Offering a lower price on condition that payment moves off-platform does. Quoting a price for a private arrangement inside a platform thread does.

What isn't at risk is worth naming, because hosts over-correct and go quiet. Reminding a guest that you would love to host them again is safe. Mentioning the season or the unit they liked is safe. Telling them to book early because those dates fill is safe. Encouraging them to tell a friend is safe. The line is not "do not build relationships"; it is "do not move the transaction".

Which behaviours each platform treats as a violation, and what it does about them, is set out in that platform's own terms, and those terms change. Nothing here is a penalty schedule — read the current version for the places you sell on before relying on a boundary described in general terms.

Three referral habits that survive an audit of your message history

Ask for the return, not for the detour. The sentence is: if you come back, book the same listing and tell me the dates. It invites a repeat booking through the same door the first one came through, and there's nothing in it a platform could object to. The variant to avoid is any wording that implies the next stay will be arranged differently.

Give something you can deliver inside a booking. A held set of dates, a late checkout on the return stay, the better unit when it frees up, a lift to the station. All of these are real value, none of them require money to move outside the platform, and all of them are visible in the booking record. If your platform has a returning-guest or repeat-stay setting, use it rather than improvising one; whether such a setting exists and what it's called differs by platform.

Write it where it can be seen. Put the invitation in the thread the platform holds, in plain words, with no mention of payment terms beyond what the listing already states. A referral that reads the same to a guest and to anybody reviewing the thread later is a referral you never have to explain. Three things never belong in that thread: a price conditional on the payment route, contact details collected for the purpose of closing outside, and any invitation to cancel an existing booking and rebook privately.

Knowing which guests actually returned is a data question rather than a memory question. And localsbnb.com connects Claude, ChatGPT and Cursor to your property data, so one sentence returns order detail, today's arrivals and departures, room status or channel rates.

It installs once and adds no new app. Those answers are read-only, which is the right shape for this work: you're looking at history, not changing it.

Turning one good stay into a second booking without asking for anything off-platform

The sequence is short and it works because it asks for nothing unusual.

At checkout, send one message that thanks the guest and names the thing they liked — the season, the unit, the terrace in the morning. Don't attach an offer to it. Write the same thing down somewhere you will find it in eight months, together with the dates they mentioned.

When those dates come into your booking window, send one message with the listing link and a sentence saying the dates are open. Let them book the way they booked the first time. If they were hoping for a returning-guest price and your platform provides one, it applies automatically. If it doesn't, the honest answer is that the rate is the rate. Most guests who want your unit specifically will pay it.

Then close the loop on arrival: a short note welcoming them back, and something small that costs you nothing. That's the whole referral system, and it produces a third stay the same way.

One situation needs a script, because it arrives from the guest's side. When a guest offers to pay you directly to save the fee, the answer is short. Thank you, but booking through the listing keeps your payment protection and my records in one place. So let's do it that way. It's true, it's kind, and it ends the conversation without an argument about rules.

FAQ

Is it against the rules to ask a guest to come back?

No. Inviting a return, or asking a happy guest to mention you to a friend, is ordinary hosting and the outcome is another booking through the same platform. What crosses is proposing that the payment for that next stay move off it.

Can I offer a returning guest a discount?

Yes, through the platform. If your channel has a returning-guest or repeat-stay setting, use it; otherwise the repeat guest gets the ordinary rate. What you can't do is condition a lower price on paying outside.

What if the guest is the one who suggests paying me directly?

Decline, politely and without a lecture. Say that booking through the listing protects their payment and keeps the records together, and let the booking proceed normally.

Referrals are the cheapest growth a host has, and they stay cheap only while the money keeps moving the way it always did. Ask for the return. Give something you can deliver inside a booking, and keep the thread clean. One connection at localsbnb.com puts your order history behind a single question, so spotting a returning guest stops depending on memory.

---

What counts as a violation, and what a platform does about it, is set out in that platform's own terms and changes over time; no figure here is a penalty schedule. This is not legal advice — read the current terms for every channel you sell on.