A family of four checked out of the cabin on a Sunday in July. They stripped the beds without being asked, ran the dishwasher, left a note on the counter thanking me for the extra blanket. My cleaner texted me a photo of the kitchen and the word “immaculate.”
I meant to review them that night. I was at a barbecue. I meant to do it Monday, and then a water heater at another property started leaking, and by the time I opened the app again it was the following weekend and there was a different checkout to think about.
The window closed. I never reviewed them. And — this is the part that took me a season to connect — they never reviewed me either.
That stay is invisible now. It happened, it was perfect, and it contributed nothing to the listing. The guest’s next host got no signal about them, and the next traveller comparing my cabin against three others saw a review count one lower than the truth.
I ran the same pattern for about eighteen months across three properties: reviewing maybe half my guests, always late, always the ones I happened to be free for. Then I fixed the one half of the system I actually control, and the other half started fixing itself.
Reviews Are Two Systems Wearing One Name
When a host says “I need to work on reviews,” they’re compressing two problems that behave completely differently.
The review you write is fully under your control. It costs two minutes. It has a deadline. Nobody else’s behaviour affects whether it happens. It is, in software terms, a scheduled job you are running manually and badly.
The review you receive is not under your control at all. You can only influence it, and almost all of that influence is spent long before the guest sits down to type — during check-in, on the first night, in how fast you answered a question on day two.
Almost every tool sold as “review automation” works on the second one, and works on it in the weakest possible way: a scheduled message asking for a review. That message is fine. It is also the least leveraged thing in the entire system, and it’s the part hosts spend all their attention on.
The review you leave is a deadline problem. The review you get is an operations problem. Asking nicely sits somewhere in the middle and moves the least.
Get clear on which one you’re solving, because they need opposite kinds of fixing.
The Clock Is the Whole Mechanic
Airbnb gives both sides fourteen days after checkout to write a review, and the system is double-blind: neither review is visible until both are submitted, or until the window runs out. VRBO’s timing works differently and is more generous — check the current window in your own dashboard rather than assuming it matches Airbnb’s, because the two platforms have changed it independently over the years.
That fourteen-day clock is the entire reason review automation matters, and it has two consequences most hosts never make explicit.
First: a missed review is silently deleted. Not delayed. There is no backlog, no catch-up, no “I’ll do it at the end of the month.” The stay simply leaves no record. Every other operational failure in hosting gives you a second chance; this one doesn’t.
Second: your review is the event that starts the conversation. Once you’ve filed, the platform has a concrete reason to put a review prompt in front of the guest — and the guest is being asked while the trip is still a thing they’re telling people about, not a vague memory of a house somewhere.
I can’t give you a study, and I’d distrust anyone who quotes you a precise lift. What I can tell you is what changed in my own account: once I stopped reviewing guests whenever I remembered and started reviewing every guest inside a day of checkout, my review count started tracking my booking count instead of drifting behind it. Same properties, same guests, same listing copy. The only variable was that I stopped missing the window.
What’s Actually Worth Automating
Here’s the honest split, because “automate your reviews” gets used to mean four different things with wildly different value.
| What it is | Worth automating? | |
|---|---|---|
| Filing your guest review | A two-minute task with a hard deadline, repeated every checkout | Yes. This is the highest-value, lowest-risk automation in the whole category |
| Asking the guest to review you | One message after checkout | Yes, but it’s one line in a schedule you already have |
| The content of your guest review | A judgement about specific people | Partly — a rubric, not a robot writing whatever it likes |
| Responding to a bad review | A public, permanent, reputational act | No. Never. This one is yours |
The first row is where the leverage is, and it’s the row nobody sells. A scheduled “please review us” template is easy to build, which is why every tool has one. Reliably filing a truthful review of the guest, on time, on every stay, on both platforms, forever — that’s the boring job that actually compounds into a review count.
This is the specific thing I wanted software for. Outkeepr files the host-side review after checkout so the fourteen-day window stops being something I have to hold in my head at a barbecue. It’s an unglamorous feature and it fixed a problem I’d failed to fix with willpower for a year and a half.
Write Your Rubric Before You Automate Anything
If something is going to file reviews on your behalf, you need to have decided in advance what those reviews say. Not the wording — the standard.
Mine, after some trial and error:
- Five stars is the default for a guest who did nothing wrong. Not a guest who was delightful. A guest who followed the rules, communicated when needed, and left the place in normal post-stay condition. On these platforms the scale is compressed whether we like it or not, and treating five as “exceptional” punishes ordinary good guests in a way the next host will misread.
- Four stars means something specific happened that the next host would want to know about, and I say what it was.
- Three or below means I would think hard before hosting them again, and I write the review accordingly, factually, without adjectives.
- Anything I wouldn’t say to their face goes in the private feedback, or nowhere.
The rubric matters more than the prose. Once it’s written down, the review itself is nearly mechanical: a sentence about how they communicated, a sentence about how they left the property, a sentence about whether I’d host them again. Guests aren’t reading your review for style. The next host is reading it for a decision.
And a line I’d defend anywhere: never file a review you don’t believe. Automation that posts a glowing review of a guest who trashed your kitchen isn’t automation, it’s a lie with a cron job attached. Whatever you use, make sure a bad stay can reach you before anything goes out. The rule I hold Outkeepr to is the same one I’d hold a co-host to: file the ordinary ones, and put the exceptions in front of me first — which is only possible if the tool knows the stay had a problem, and that means it has to be watching the messages too, not just the calendar.
The Score Is Decided Before Anyone Types
Here’s the uncomfortable part of the second half. By the time a guest opens the review form, the number is already set. It was set in the first twenty minutes of the stay, and possibly in the ninety seconds they spent standing at a door with a code that didn’t work.
The things that actually move review scores, in rough order of how much damage they do when they go wrong:
- Check-in friction. A guest who couldn’t get in is writing a different review than one who walked straight through the door, no matter how good the rest of the week was. This is why I treat check-in instructions as a review-score document rather than a logistics one.
- Cleanliness. The single most mentioned thing in critical reviews, and the one most dependent on a turnover that had enough hours in it. A cleaner rushing a same-day turn is a three-star review being written in advance.
- Response time during the stay. Not the pre-arrival messages — the question at 9 PM on the second night about the thermostat. A guest whose problem got solved often writes a better review than a guest who had no problem — which is the entire reason I let Outkeepr answer the thermostat question at 9 PM instead of finding it at breakfast.
- Accuracy. The gap between the listing and the house. Free to fix, never fixed, because you stopped seeing your own listing years ago.
Notice that three of those four are operations, not writing. This is why “review automation” that only sends a polite ask is such a weak lever — it’s optimising the last step of a process whose outcome was determined four steps earlier.
The practical version of this: if your reviews are slipping, don’t go shopping for a review tool. Go look at your turnovers and your reply times. I wrote up the turnover half in automating cleaner scheduling, and the reply half is the reason I run messaging automation at all.
Asking for the Review Without Being That Host
The ask is worth doing. It’s just worth about a tenth of what people think it is.
Three rules I’ve settled on:
Ask once. A second ask converts almost nobody and annoys the people who were going to review you anyway. If they didn’t respond to the first one, the answer is that they’re busy, not that they didn’t hear you.
Ask in the thread, not by email. The message that arrives where the conversation already happened gets read. An email from an address they’ve never seen gets filed with the airline receipts. This is one of the quiet arguments for handling guest communication in the platform threads themselves rather than routing everything out to a separate system — Outkeepr sits in the Airbnb and VRBO thread the guest is already using, which means the post-checkout note lands in the same place as the check-in instructions they actually read.
Never trade. “Leave us five stars and we’ll leave you five stars” is against platform policy on both sites, it’s obvious to guests, and it makes an honest review system into a haggle. If you’ve been reviewing guests honestly and promptly, you don’t need the trade anyway.
What the message should actually say is short, specific, and gives them something to write about:
Thanks for looking after the place so well this week — the kitchen was spotless and I appreciated the note. If you have a minute, a review helps other travellers decide, and helps us keep improving the cabin. Either way, you’re welcome back any time.
Naming a specific thing they did is what separates this from the template everyone ignores. It also only works if someone actually looked at the property after they left, which brings the whole thing back to operations again.
When It Goes Wrong
Sooner or later you get a review that’s unfair, or fair and painful.
The response is public and permanent, and it’s read by future guests, not by the reviewer. So:
- Wait a day. Nothing written within an hour of reading a two-star review has ever helped anybody.
- Respond once, briefly, factually. Acknowledge, state what changed, stop. Three sentences.
- Never relitigate. A host arguing in a review response looks worse than the review did, every single time.
- Write it yourself. This is the one part of the review system that should never be delegated to software or to a VA. It’s your voice in public about a conflict.
Then do the thing the review is actually for: if two separate guests mention the same problem, that’s not bad luck, that’s a defect report you’ve now received twice.
What This Costs
The filing half costs nothing but consistency, which is exactly why it fails — there’s no bill to remind you, and no alarm when you skip it. The fourteen-day window is the only enforcement, and it enforces by deleting.
If you want it off your plate, the comparison isn’t software versus nothing; it’s software versus you remembering at a barbecue, or versus paying someone to remember for you. Outkeepr is $5 per property per month plus 0.5% per booking, with a 14-day trial, and the review filing rides along with the messaging rather than being a separate product to buy. I mention the shape as much as the number: it’s per property, so the fourth listing is an incremental decision instead of a plan upgrade.
If you’re evaluating this alongside a broader tooling decision, the guide to handling guest inquiries across platforms covers the messaging side of the same system, since in practice they’re the same inbox.
The Setup, Condensed
- Write your rubric first. What earns five stars, what earns four, what goes in private feedback. One page, once, for all properties.
- File the host review within a day of every checkout — manually if you must, automatically if you can. This is the whole ballgame.
- Add exactly one review ask to your post-checkout message, in the platform thread, naming something specific.
- Fix check-in and turnovers before you touch anything review-shaped. That’s where the stars are actually decided.
- Keep bad-review responses manual. Always.
- Read your own critical reviews quarterly, in a batch. Individually they’re noise. Five of them in a row tell you what to fix.
The cabin family from July never got reviewed, and I still think about it — not because one review would have changed the listing, but because it was a perfect stay that produced nothing. The system had exactly one job that week and the job was mine, and I was at a barbecue.
That’s the case for automating this specific thing. Not because reviews are hard to write, but because they’re easy to write and trivially easy to skip, and the platform’s response to skipping is to quietly pretend the guest was never there.
Outkeepr answers your guests in their own Airbnb and VRBO threads and files the host review after checkout, alongside whatever PMS or channel manager you already run, with nothing to migrate. Download the app, connect one property, and check the review count against the booking count after a single turnover cycle — that gap is the one this closes.
Ready to automate your vacation rental?
AI guest messaging, smart lock codes, cleaner scheduling, and more — starting at $5/mo per property.
Try Outkeepr Free