A Post-Stay Summary Guests Actually Read

Most post-stay messages are written for the host's own records and read by nobody. Two lines change that, and neither is a request for a review.

Last updated: October 12, 2026

A post-stay summary is easy to send and hard to get read. Most of them are written for the host's own records, so they list everything and say nothing a guest needs. The ones that get opened carry two lines: what the stay was, and what happens next. Neither line asks for a favour, and that's exactly why they work.

Key Takeaways

• Write it for the guest, not for your records. If it reads like your own log, it won't get opened.
• Two lines do the work. What the stay was, and what the guest needs to do next.
• Don't hide a review request inside it. The ask is what makes guests stop reading.
• It sits under the receipt, not over it. Money first, courtesy second, and the summary last.
• Keep it sendable in one breath. If it's too long to send, it's too long to read.

What a summary is for

Start with a plain question: who is this message for? If the honest answer is "me", it belongs in your own notes, not in the guest's inbox.

Hosts often write these messages as a record. They list the check-in time, the nights stayed, the checkout, the fees and the thank-you, all of it useful to the host and none of it news to the guest. The guest already knows what they booked and when they left. Reading it back to them is how a summary gets deleted unread.

A summary is for the guest instead, and it answers one of two questions. Either "what was that stay", which is the warm close, or "what happens next", which is the practical one. Most good summaries do a little of both, and none of them do anything else.

That reframing changes the draft in front of you. Take out everything the guest already knows, and what's left is usually the whole message.

A quick rewrite makes the point. Take a typical message, cross out every line the guest already knows, and what's left is usually two sentences. That's not a sign you wrote too little. It's a sign of how much of the first draft was for you.

There's a second job the summary does, and it's worth naming. It closes the stay in the host's own records too, but as a by-product rather than the point. Write for the guest, and the record takes care of itself.

One more thing it isn't: a review ask in disguise. The moment a message opens with a compliment and closes with a rating request, guests spot the trade. Keep the two jobs apart, and each one works better.

The two lines that get read

The first line names the stay. Not a template, but the thing that actually happened. "I hope you enjoyed the balcony on the warm evenings" tells the guest you remember their stay. "Thank you for staying with us" tells them you send this to everyone.

The second line gives the next step, or says there isn't one. If there's a deposit to return, say so and say when. If they left something behind, say what you found and how to get it. If nothing is pending, say that plainly, because "all settled, nothing more needed" is a surprisingly welcome sentence at the end of a trip.

The order matters. Lead with the stay, close with the practical line. A summary that opens with logistics reads like a bill. One that opens with the stay reads like a host.

Then leave it there. The best summaries have no third line, because the third line is where the ask sneaks in. No request for a five-star review, no reminder about the next booking, no link to a listing. Say the two things and stop.

There's a simple way to test the second line. Ask whether the guest has to do anything because of it. If the answer is yes, it earns its place. If the answer is no, it's decoration, and decoration is what gets skimmed.

One test settles the draft. Read it aloud as if you were the guest, three days after you got home. If you'd feel nudged, cut the nudging line. If you'd feel remembered, send it.

Where it sits against the receipt

A summary that lands before the money is sorted reads as pushy, warm as it may be. Sequence it after the practical bits, not before them.

The receipt comes first. The stay's charges and the deposit return are what a guest checks in the days after checkout, and they arrive from the platform, not from you. Let that settle before a friendly note lands on top of it.

Then the summary, once the deposit question is closed. If the deposit is still pending, the summary either waits or says plainly when it will clear. A friendly message sent while a guest is still waiting on a refund is the one that gets read as a chase.

Then nothing, unless the guest answers. A summary that expects a reply puts work on the guest. A summary that invites one, without needing it, is the one that gets a reply anyway.

The platform's own message carries the facts the guest needs, so yours doesn't have to. That division of labour is what keeps your summary warm instead of transactional, and it's why the two don't compete for the same space.

This sequence also keeps the summary short. Once you know it follows the receipt rather than replaces it, the money talk drops out of it, and you're back to the two lines.

Keeping it short enough to send

The last rule is the one that decides whether any of this happens. A summary you put off because it feels long is a summary that never goes out.

Aim for a message you can write in two minutes and read in ten seconds. That's roughly three short sentences. If it's running longer, the extra words are almost always facts the guest already knows.

Send it at the right moment, too. A day or two after checkout works better than the same evening, because the guest has unpacked and the stay has settled. Send it a week later and it reads as an afterthought.

Draft it the day before you send it, then read it once more before it goes. A sentence that felt fine at midnight often reads as cold in the morning, and one edit is cheaper than one regret.

It helps to see the stay clearly while you write. The LOCALSBNB Home dashboard shows occupancy, average daily rate and revenue per available night, so you know which bookings were the good ones and which deserve a warmer close. The read-only assistant answers plain questions about a booking's detail and today's availability, which saves you opening another app to check a stay's dates mid-sentence. You can see a month's picture on your own listing at localsbnb.com.

Then keep a simple habit. Note which summaries got a reply and which went quiet. Over a season, that list tells you more about your guests than any template, and the replies are where repeat bookings usually start.

FAQ

Should I ask for a review in the summary?

No, and this is the line that matters most. A review request turns a courtesy into a transaction. If the stay went well, the guest may review on their own. If you ask, you risk the message going unread, and the ask is why. If the stay was good, that shows in how you write, not in what you ask for.

What if nothing happened worth mentioning?

Then say the plain thing. A short "thanks for leaving the flat so tidy, everything's settled" is a complete summary. It doesn't need a story to be worth sending. A short, honest line beats a padded one every time, and guests can tell the difference.

Is one summary enough, or do I send more?

One is enough. A second message a few days later reads as a nudge, and the guest has moved on. If you want to stay in touch, better to do it when they book again. Repeated contact is what turns a friendly note into noise.

A post-stay summary isn't a marketing message and isn't a review request. It's two lines that close a stay and leave the door open for the next one. Write it for the guest, put it after the receipt, and keep it short enough to send without thinking. If you'd like to see a stay and a month's numbers side by side before you write it, localsbnb.com is a sensible place to start.

---

This is general guidance for hosts, not legal, tax or insurance advice. Local rules and platform terms change, so check the current requirements of your local authority and the terms each platform applies today.