The Five-Minute Rule: How Reply Speed Changes Enquiry Conversion

An enquiry is not a queue item. It is somebody else's decision that is still open, and it closes on its own.

Last updated: September 24, 2026

An enquiry isn't a task in your queue. It's somebody else's decision, still open, and it closes on its own — usually on the next listing they open. Speed doesn't win these by being impressive. It wins them by landing while the guest is still choosing. Below: where speed enters the sequence, the single job your first reply has to do, and how to hold a decision open through the hours you're asleep.

Key Takeaways

• The window belongs to the guest. An enquiry stays open until they book somewhere else, and nobody tells you when that happened.
• Your first reply has one job. Settle the question they actually asked. Everything else is ballast.
• Fast beats complete. A short answer in four minutes does more work than a perfect one at midnight.
• Templates leak at the seams. The greeting and the sign-off are where a canned message gives itself away.
• Coverage is a rota, not a promise. Name the hours nobody answers, then decide what those hours say.

What happens between an enquiry and a booking, and where speed enters that sequence

A guest who sends an enquiry hasn't chosen you. They've shortlisted you. Most of the time they've fired some version of the same question at two or three places inside ten minutes, then gone back to whatever they were doing — dinner, a flight, a conversation.

The clock that matters isn't the one on your phone. It's the one in their head, and it stops when the first of those replies lands. That reply becomes the comparison set. Arrive second and you're no longer judged on your own terms; you're measured against a host who already answered, and you'll usually lose on something as small as tone.

So where does speed enter? Not at the booking. It enters while several options are still live and the guest hasn't started defending a choice. Once they've decided, nothing you send reopens it. Before they've decided, a fast reply is the only reliable way to stay in the set.

Three things happen in that window, and only the first is yours to control. They wait. They keep browsing. Then they stop waiting — usually because somebody answered, not because they gave up on the trip. Nobody sends a message saying they've booked elsewhere. The enquiry just goes quiet, and gets filed under tyre-kickers, which is a comforting story and mostly wrong.

That's the practical reason the five-minute rule exists. It isn't about looking keen. It's about being present during the only stretch of time when your answer can still change the outcome.

Why the first reply only has to do one job, and what that job is

Most hosts write the first reply as though it were the only reply. That's exactly what makes it late.

An enquiry usually carries one question doing the work. Is the parking real. Can the dog come. Is the second bedroom an actual bedroom. That's the thing they'll judge you on, and it's the only thing the first message has to settle. The welcome, the check-in instructions, the restaurant list — all ballast at this stage. Answer the load-bearing question inside two sentences and you've done the job.

Why does brevity convert? Because a guest who asked one question and got five paragraphs learns something: this is going to be a lot of correspondence. Plenty of people read that as risk. Four sentences in four minutes signal the opposite — you're reachable, you know the unit, and the stay will be easy to run.

Fast isn't sloppy, though. Being fast means the short version was written in advance, when nothing was on fire. Compose it once. Reuse it. That's the whole trick, and it's why the next section is about templates rather than about typing speed.

Building templates that still read as written by a person

A template fails at the seams, not in the middle. The middle is facts — parking, distance to the station, bed configuration — and facts should be identical every time. The greeting and the sign-off are where a reader hears the machine.

So fix the middle and leave the ends loose. Open with their name and the thing they asked about rather than with a welcome. Close with one sentence specific to their dates. Two variable ends around a fixed middle reads like a person who has answered this question before. Which you have.

Three rules keep it honest. Never let a template answer a question that wasn't asked — an unrequested paragraph about the bins is the loudest possible tell. Never let one go out with a wrong detail, because a message naming the wrong dates costs more trust than a slow reply ever will. And read each one aloud before you save it; if you wouldn't say it out loud, delete it.

How many do you need? Five or six covers most of a year: availability, parking, pets, late arrival, long stays, and the one about whether the photographs are current. Past that you're maintaining a library instead of answering guests, and the library goes stale faster than the unit does.

The test is simple and worth running once a quarter. Take your most-used template, swap in a real guest's name and dates, and read it as though you'd never seen it. If you can hear where the slots are, so can they.

The hours you cannot cover, and how to hold the decision open across them

Nobody covers twenty-four hours, and pretending otherwise is how enquiries go cold at two in the morning. Start by writing down the hours you genuinely don't answer — in the timezone your guests are in, not yours. A listing in Europe taking enquiries from North America has a dead zone that falls in their afternoon.

Then decide what those hours say. An automatic acknowledgement promising "soon" is worse than nothing, because it invites them to wait without giving them a reason to. One that names an hour — I'll reply by 08:00 local time — does the same job the five-minute rule does during the day: it holds the decision open.

Two things break this. The first is a promise you then miss; a named hour you blow is worse than silence, because now they've waited and been let down. The second is the gap you forgot. The turnover window between ten and three is when most hosts physically can't type, and it's prime enquiry time for anyone looking at tonight.

And check every channel, not just the one you like. Airbnb conversations sit in one inbox at localsbnb.com, but the other three connections still deliver into their own apps, so give those a fixed slot on the clock too. Otherwise the five-minute rule is holding for a quarter of your enquiries and you won't know which quarter.

FAQ

Is five minutes realistic if I have a day job?

No, and that's fine. The rule applies to the hours you're actually working. Cover nine to six properly, name the hour you'll answer outside it, and you've captured most of the value without pretending to be awake at three.

Should I use an automatic first reply?

Yes, if it commits to a time. A note that says "thanks, I'll be in touch" starts the clock without pausing it. One that says "by 08:00 local" pauses it, and that pause is the entire point.

Does answering at midnight help or hurt the stay?

It helps the booking and sets an expectation. Reply at two in the morning often enough and guests learn you're available at two in the morning — including during their stay. Send it, but don't advertise the hour.

Speed isn't a personality trait. It's a short first reply written in advance, a rota for the hours you're asleep, and one honest promise about when the answer arrives. Set those three and the five-minute rule stops being advice and starts being something your week does. If you'd rather read Airbnb conversations from the same screen you work the calendar on, that inbox is at localsbnb.com.

---

Which channels deliver messages where, and any performance measure a platform shows on your account, are set by that platform's current terms and change without notice; read them off your own admin. This is general guidance for hosts and isn't platform policy advice.