The Repeat Guest Nobody Noticed

Most of the effort in short-term rental goes toward getting new guests. Listings, photos, OTA algorithm optimization, pricing tools, getting that next inquiry to convert. It's a constant acquisition treadmill.

The person who stayed with you last October and left a four-and-a-half-star review mostly gets missed. If they book again, they get the same welcome message, the same property introduction, the same parking instructions you send to everyone. Nothing wrong with any of that. But you've just treated a returning customer like a stranger.

That's mostly a software problem, not a hospitality failure.

Why a second stay is worth more than it looks

The obvious math: a returning guest who found you on Airbnb last year and books your website this year saves you the commission. Depending on the platform and your pricing structure, that's 3% at the low end, often 15% or more on Airbnb stays. On a five-night stay at $300 per night, you're talking $225 in fees that simply don't happen.

But the math understates it. A returning guest:

Already knows the property. They won't call asking where the TV remote is or how to work the pool heater. Check-in support drops sharply.
Has self-selected as someone who had a good enough time to come back. The odds of a bad review are low.
Often books further out. First-time OTA guests tend to book close to the date. Repeat guests, especially direct bookers, tend to secure their dates weeks earlier.

None of this shows up in your ADR or occupancy rate. It shows up in the margins and in the reduced labor per booking.

The identity problem

Property management systems track reservations, not relationships. A guest books, that creates a lead. The lead has contact details and dates and a channel. That's the extent of it.

The same person books two years later under the same email, or under a slightly different name, or through a different platform. In most setups, you now have two leads with a coincidental match somewhere in the details. Nobody connected them. There's no flag that says "this is the third time Ms. Reyes has stayed at the Palm Springs property." There's no note from the previous stay about how she mentioned the espresso machine was broken, and you fixed it the week after she left.

This is why the recognition gap exists. It's not that operators don't care about returning guests. It's that the data model treats every booking as new, because from a transactions perspective, it is.

The word "guestbook" has an old-fashioned ring to it. The function is modern: a consolidated view of who has stayed across all your properties, which channels they've used, and what they've said. Without that, you're meeting people for the first time every time.

What recognition looks like

Recognizing a returning guest doesn't require a grand gesture. A small adjustment in the welcome message is enough to land differently.

"Welcome back" carries more weight than "Welcome" in a way that's hard to explain but easy to feel. If you can add one specific detail from their previous stay, or acknowledge the property they stayed at before, it moves from a template to a note. Guests notice when they're not treated as interchangeable.

The higher-value version: you have notes from their previous stay. They mentioned last time that they were celebrating an anniversary. They asked about hiking trails near the property. They had a late checkout because of a flight delay and were grateful for the flexibility. Any of these, surfaced before check-in, gives you something to work with.

That record of past stays also connects to reviews. A guest who left a thoughtful four-star review with a mention of the outdoor shower being hard to find, and is now booking again, is worth noting. If you fixed the signage, you can say so. That's a conversation, not a form letter.

Not every returning guest warrants a custom message. But a guest who has stayed more than once, left a positive review, and is booking a longer stay is worth two minutes before their arrival.

Building a workable system

You don't need a CRM. What you need is a way to flag the repeat, and a place to record anything notable.

At check-in time, a quick scan of the name against your history catches most returns. The challenge is that guests don't always use the same email across platforms. Someone who books through Airbnb and then books direct may look like two different people even if the name matches.

This is where a consolidated guest identity layer earns its keep. When the same email, phone number, or name appears across reservations and across channels, a system that links those records lets you see the full picture without cross-referencing manually. Tools like Pomello build this as a guestbook: a cross-property view of every guest you've hosted, with their reservation history attached. A manager checking in a guest can see at a glance whether this person is new or returning.

A few habits make the rest of it work:

After a stay ends, log any notable feedback while it's fresh. One sentence is enough: "Asked about EV charging, said the dock was hard to find."
If a guest mentioned a specific preference or problem, tag it somewhere. Not in a complex way. A field in your PMS notes, or a line in whatever internal tool your team already uses.
Check the history before sending check-in details, not after.

None of that requires a new workflow. It requires plugging a step into the one you already run.

The direct booking play

A returning guest you've served well is your best candidate for a direct booking conversion. They know the property. They trust you. The OTA is no longer providing discovery value, because you already found each other.

The moment to make the offer is after a successful stay. A brief note in the post-stay message: "If you'd like to book a return visit, you can do it directly at [your booking site] and we can usually offer a slight discount on the OTA rate." Some operators include a small loyalty discount. Others offer the convenience alone.

Not everyone will switch. But some will, and each one who does removes the platform fee from every future stay. A guest who books with you twice a year for three years, converting to direct after the first visit, might account for thousands of dollars in recaptured fees over that window. You can read more about building out that direct channel in our post on OTA fees.

What you're actually managing

Running a portfolio isn't just managing reservations. It's managing relationships at a scale that makes personal memory impossible.

The guests who come back are telling you something. Not all of them will feel the difference if you recognize them, but the ones who do often become the most reliable revenue in a portfolio. Those are the guests worth knowing.