Most short-term rental reviews are decided long before a guest ever opens the review form, and they are decided by messages. Seven of them, sent at fixed points between booking and checkout, do almost all the work: they set expectations, hand over access cleanly, invite problems early enough to fix, and then ask for feedback once. I have spent 18+ years in real estate, focused on short-term rentals since 2016, and trained more than 10,000 operators, and the pattern holds across markets and price points — the hosts with thin review counts almost always have thin, late, or panicked messaging.
This is the sequence, the timing, the content rules for each message, the recovery script for the stay that breaks, and what the platforms actually allow you to say when you ask for a review.
Why Messaging Drives Reviews More Than Amenities
A guest writes a review from memory, and memory is built out of moments where they felt either handled or abandoned. The towel count matters less than whether they knew, at 9 p.m. on a Friday with a car full of luggage, exactly which door to use and what the code was.
Three things happen when the sequence is tight:
Expectation gaps close before arrival, so the listing and the reality match.
Small defects surface on night one, while you can still fix them and while the guest still has four nights to forget about it.
The review request arrives once, politely, after the guest has had a good departure — not as a third nudge during their stay.
One caution on numbers. The prior version of this article claimed a 15–25% ADR premium for high-review listings and a 60–70% reduction in day-of questions. I cannot support either figure with a source I would stand behind, so I am not repeating them as data. What I will say as my own observed result, in my own portfolio: after I moved the access instructions into a scheduled pre-arrival message instead of answering them live, arrival-day inbound messages dropped noticeably and my check-in-related review mentions turned positive. That is one operator's experience, not a statistic.
The Seven Touchpoints, With Timing and Content Rules
Each message has one job. The most common failure is a message trying to do three jobs at once — the "welcome packet" sent at booking that nobody reads, so the same questions arrive anyway on arrival day.
# | Message | Timing | Its one job | Must contain | Must not contain |
|---|
1 | Booking confirmation | Within minutes of booking | Confirm the reservation is real and handled | Dates, check-in and checkout times, who to contact, what comes next and when | Access codes, full house manual, parking diagrams, rules essay |
2 | Pre-arrival | 3 days before arrival | Deliver everything they need to arrive without asking | Address, directions, parking, access instructions, code or lock method, Wi-Fi name | Upsell pressure, review talk, anything that changes later |
3 | Morning of check-in | 7–9 a.m. local, arrival day | Remove day-of friction | Confirmation that the place is ready, restated access line, one sentence offering help | A re-send of the entire pre-arrival message |
4 | Night one | 7–9 p.m., first evening | Surface defects while they are cheap to fix | A direct question inviting problems, a promise of response time | A request for a review, or "hope you love it!" with no question |
5 | Mid-stay | Midpoint, stays of 4+ nights only | Stay present without hovering | One specific local recommendation, one open door for needs | Anything on stays of three nights or fewer |
6 | Day before checkout | Late morning, day before | Make departure easy and predictable | Checkout time, the three things you want done, how to leave keys or lock up | A long chore list, cleaning threats, fee warnings |
7 | Post-checkout | Within a few hours of checkout | Thank, then ask once | Sincere thanks, one plain review request, an offline channel for complaints | Bribes, incentives, pressure, star-rating coaching |
What each message sounds like
Message 2 is the load-bearing one. Mine reads close to this: "You're in on Friday after 4 p.m. The door is the blue one on the left side of the driveway; the lock code is 4821# and works from 4 p.m. Friday until 11 a.m. Monday. Park in the two spots marked 3B. Wi-Fi is 'Oakline-Guest', password on the fridge card. Anything you need before you land, just reply here."
Message 4 is the one hosts skip and then regret: "Checking in — is everything right in the house tonight? If anything is off, tell me now and I'll get it handled tonight or first thing tomorrow." You are not fishing for compliments. You are buying back a one-star review for the price of a $40 handyman visit.
Message 7 stays short: "Thanks for taking such good care of the place. I left you a review. If the stay worked for you, a review back helps other travelers find us — and if anything fell short, reply here first so I can fix it." That last clause matters. Airbnb's reviews policy bans coordinating, extorting, incentivizing or pressuring anyone over a review, and bans reviews given or withheld in exchange for something of value — a discount, a refund, or a reciprocal positive review. Inviting a guest to raise a problem with you is not a trade, so keep the two separate: no offer attached to the ask.
Automate the Predictable, Write the Human Ones
Messages 1, 2, 3, and 6 are fully schedulable in any modern messaging tool — Hospitable, Guesty, and OwnerRez all support time-anchored scheduled messages with reservation variables. Pricing for these tools is per-listing and tiered, and it changes often; check the vendor's own pricing page before you budget rather than trusting a number in an article.
Messages 4, 5, and 7 should carry one line only you could have written. "The farmers market two blocks up runs Saturday until noon — the bread stand sells out by 10." That one sentence is what separates a listing guests describe as "clean and easy" from one they describe as a host they liked.
Message | Automate? | Personal line required | Common failure if automated badly |
|---|
1 Booking confirmation | Yes, fully | No | Sends stale check-in time after a date change |
2 Pre-arrival | Yes, fully | No | Sends an old lock code after a code rotation |
3 Morning of check-in | Yes, fully | No | Fires at 3 a.m. in the guest's time zone |
4 Night one | Draft only | Yes | Reads as a survey, so nobody answers it |
5 Mid-stay | Draft only | Yes | Fires on 2-night stays and feels intrusive |
6 Day before checkout | Yes, fully | No | Turns into a chore list and sours the ending |
7 Post-checkout | Draft only | Yes | Sends twice, or reads as pressure for stars |
Two operating rules I hold to. Rotate access codes between stays and verify the code inside the scheduled template each turnover, because a wrong code at 10 p.m. is the single most reliable way to lose a five-star review. And put a real response-time commitment in writing, then meet it — a stated two-hour window honored beats an implied instant reply missed. For reference, Airbnb's Superhost criteria require responding to 90% of new messages within 24 hours and holding a 4.8 overall rating, so a two-hour internal standard leaves you room on a bad day.
When the Stay Breaks: A Five-Step Process
Something will fail. The unit will be too warm, the cleaner will miss a bathroom, the neighbor's dog will bark until 2 a.m. Recovery is a script, not a mood.
Acknowledge inside your stated response window, in writing, on the platform thread. No explanation yet — just "I've got this, here's what happens next."
Name the fix and the time. "A tech is scheduled between 9 and 11 tomorrow morning." Specificity is what calms people; vagueness is what escalates them.
Fix it, then confirm in the thread that it is fixed. The written trail is what protects you if the guest later disputes the stay or asks the platform to intervene.
Offer proportional restitution once, not repeatedly. A partial refund for one bad night, or a credit for a future stay. Over-compensating reads as guilt and invites more claims.
Close the loop before checkout: "Was the rest of the stay comfortable?" A guest who answers yes in writing rarely writes a review that says otherwise.
What not to do: argue facts in the thread, blame the cleaner, or bring up reviews while the problem is open. Airbnb's reviews policy says a review stays published unless it violates that policy; disagreement with a star rating, subjective opinions, and mentions of things outside your control are all listed as grounds that do not qualify for removal. Assume the review stands and earn it instead. This is operational guidance from experience, not tax or legal advice; read the platform's own policy pages before you act on a dispute.
The Review Request Rules You Cannot Bend
The ask is where otherwise careful hosts get themselves suspended. Keep it inside these lines:
Ask once, after checkout. A second ask is a nudge; a third is harassment.
Never offer money, discounts, upgrades, or gifts in exchange for a review, and never imply it.
Never ask for a specific star rating or tell a guest what "five stars" means to your business. Guests are rating defined categories, communication and check-in among them; your job is to earn those, not to coach the score.
Do not ask a guest to change or remove a review as a condition of a refund.
Leave your review of the guest first, and write it accurately. It is a normal courtesy, and both reviews publish together or at the end of the window.
On Airbnb homes, both parties have 14 days from the day of checkout to submit, and reviews publish once both sides have written or the 14 days end — whichever comes first, with no exceptions for late reviews (as of September 2026). Build message 7 to land in the first day or two of that window, while the stay is fresh.
Building the Seven Messages in One Afternoon
Sit down with your calendar and your messaging tool and do it in one sitting, because half-built sequences are worse than none — guests get message 2 and nothing else, and you stop expecting the tool to cover you.
Write the seven messages in a plain document first, with the variables marked in brackets.
Read each one out loud. If it sounds like a form letter, cut a third of it.
Load 1, 2, 3, and 6 into the tool with time anchors, not day counts, so they fire at civilized local hours.
Set 4, 5, and 7 as drafts or reminders you approve before sending.
Test on a dummy reservation and read every message on a phone screen, not a laptop.
Then audit monthly: pull the last ten stays, read every thread end to end, and mark every question a guest had to ask. Each one is a hole in message 2. This is the same review loop I walk owners through on a complimentary one-on-one diagnostic call, and it usually takes twenty minutes to find three fixable gaps.
What Good Looks Like After 90 Days
Three signals tell you the sequence is working. Arrival-day inbound questions drop toward zero. Defects show up on night one in the thread instead of in the review. And your review text starts naming the communication — "host was responsive," "check-in was simple" — which is exactly the phrase future guests scan for.
If your review volume is still thin after a full quarter of clean sequencing, the problem is usually message 7 timing or a listing that overpromises, not the messages in between. Fix the promise, then the ask.
Frequently Asked Questions
How many messages is too many for a short stay?
For a two or three-night stay, send five: booking confirmation, pre-arrival, morning of check-in, night one, and day before checkout, then the post-checkout thank-you and review request. Skip the mid-stay message entirely. Mid-stay check-ins only earn their place on stays of four nights or longer, where the guest has settled in and a recommendation is still useful.
When should I send the access code?
Three days before arrival, in the pre-arrival message, and repeat the code line in the morning-of message. Do not send it at booking — codes rotate, plans change, and a code buried in a two-week-old thread is a code the guest cannot find. If your lock supports it, set the code to activate at check-in time and expire at checkout.
Can I offer a guest a discount for leaving a five-star review?
No. Platform review policies prohibit incentivizing or conditioning anything on a review, including discounts, refunds, gifts, and future-stay credits, and doing it can cost you the review, the listing, or the account. Ask once, plainly, with nothing attached.
What do I do about a bad review I think is unfair?
Read the platform's reviews policy first. Airbnb removes reviews only for policy violations; it states plainly that a review will not be removed just because you disagree with the star rating, dislike a subjective opinion, or think the guest blamed something outside your control. If it does not qualify, write a short public response: one sentence acknowledging, one sentence on what changed. Future guests read the response as much as the review.
Should I leave my review of the guest before or after they review me?
Leave yours promptly after checkout and write it accurately. On Airbnb homes, reviews publish when both parties have submitted or the 14-day window ends, so going first does not expose you to retaliation in the way hosts fear, and it makes your post-checkout thank-you land as genuine courtesy rather than a trade.
Related Reading
Keep reading:
Sources
