Three numbers define guest response time in 2026. The platform floor: Airbnb's own help pages define a 24-hour clock that starts on a new inquiry or reservation request — miss it often enough and your response rate, a Superhost input, degrades. The revenue threshold: around one hour, with hospitality benchmarks showing listings that respond within the hour converting roughly 25% more inquiries. The competitive frontier: AI-assisted operators report median replies under 2 minutes, around the clock, in any language. But the number that trips people up isn't the threshold — it's that every platform starts and stops its own clock differently, and most comparisons quietly mix them up. Below: a sourced benchmark table for six channels, how each platform actually measures you, the overnight problem, and the exact dashboard steps to check your own.
Response time is the rare metric that hits every stage of the funnel at once: it converts inquiries (the first villa to answer often wins the booking), it feeds OTA search ranking on some platforms but not others, and it shapes reviews — a guest answered in two minutes writes a different paragraph about you than a guest answered in five hours, even when the actual fix took the same time. We covered the cost side in our hidden-cost analysis; this piece is the benchmark reference, built from each platform's own published rules rather than secondhand summaries of them.
The three thresholds that matter
The 24-hour floor is a platform rule on Airbnb specifically, not a universal service standard: Airbnb's own definitions page says response rate is the percentage of new inquiries and reservation requests you responded to — by accepting, pre-approving, declining, or replying — within 24 hours over the trailing 30 days, and sustained misses feed into Superhost eligibility. The ~1-hour threshold is where the revenue evidence points for inquiry conversion — travelers message several listings and book with whoever engages first. The sub-2-minute frontier is what changes the guest's perception of the stay itself: at that speed a question feels answered rather than queued, and mid-stay problems get contained before they compound into review material.
Benchmarks by channel
Three of the six channels below are governed by a platform's own published rule; three aren't governed by anyone but you. Knowing which is which changes what "benchmark" even means for that row.
How each platform actually starts and stops the clock
This is the part almost every secondhand comparison gets wrong, because "response time" isn't one metric. Each platform defines its own clock, and the definitions don't transfer between them — a number that's good on Airbnb can mean nothing on Vrbo, and a WhatsApp habit that feels fast can still be too slow for the rule that actually governs it.
Airbnb
Airbnb's own definitions page is specific down to the message type. Response rate is the percentage of new inquiries and reservation requests you responded to — accepting, pre-approving, declining, or messaging back — within 24 hours over the trailing 30 days; response time averages how long that first reply took. Follow-up messages inside an existing thread don't count either way, and you don't need to send the final word in a conversation to protect your response time. Superhost status runs a separate calculation on top of that: first replies over a trailing 12 months, assessed quarterly, so one bad week barely moves it while a bad month visibly dents the dashboard number.
Vrbo
Vrbo publishes more mechanical detail than most hosts would guess. Response rate and response time are only calculated once a property has had at least 10 unique interactions with travelers in the past 30 days, falling back to the most recent 10 interactions in the past 90 days if it hasn't. Response rate counts first messages, inquiries and booking requests answered within 24 hours; anything slower counts as no response, and an unanswered booking request gets auto-declined. The detail that surprises people: Vrbo states plainly that these responsiveness metrics are informational only and don't affect ranking or visibility — the platform that actually enforces a hard, stated consequence for slow replies is Airbnb, not Vrbo.
Booking.com
Booking.com's own partner guidance ties fast, thoughtful replies to lower cancellation risk and better review scores, and points hosts specifically to the Pulse mobile app so replies don't wait for a desktop login. What Booking.com does not do, in the pages it currently publishes, is state a numeric response-time floor or explain exactly how its scoring starts and stops the clock. If a comparison site quotes you a precise Booking.com response-time percentage or threshold, that number isn't coming from a Booking.com page — worth asking where it actually came from before repeating it to an owner.
WhatsApp isn't a response-time metric at all — it's a messaging permission window. Meta's own documentation defines a 24-hour customer service window that opens the moment a guest messages first; inside it, you can send free-form replies, and the window resets every time the guest writes again. Once 24 hours pass without a reply from the guest, free-form messaging closes and you're limited to pre-approved templates until they message back. Practically: a slow WhatsApp reply doesn't just read as rude — past a point, it can cost you the ability to send anything but a template until the guest speaks first.
Email and direct-site enquiries
No platform sits between you and either of these, so no platform publishes a rule for them and none scores you on speed. That's not the same as no consequence — a guest comparing three villas by email still books whoever answers first — it just means the floor is one you set yourself, with no dashboard to check it against.
The overnight problem across timezones
The benchmarks above assume someone's awake. They usually aren't. A villa in Koh Phangan runs on ICT; its guests message from London, New York and Sydney across three different working days, and a message that lands at 2am local time sits exactly as long as if the host had gone quiet for eight hours during business hours — except the guest has no reason to know that, and none of the platform definitions above carve out an overnight exception. Airbnb's 24-hour clock doesn't pause for sleep. Vrbo's 12-hour recommendation doesn't either. A guest asking a normal question at what is, for them, 9pm has no reason to assume anyone on the other end is unconscious.
The arithmetic is what makes this the most expensive gap on the list rather than the most obvious one. A property with guests concentrated in two or three source markets loses real overnight hours only a few nights a week. A property marketed globally — which describes most villa listings the moment they're live on Airbnb — has some guest, somewhere, awake and messaging at almost any hour, which turns the overnight gap from an edge case into a recurring multi-hour outage on a fixed schedule. It's also where the table's practical targets are hardest to hit with a human roster: under-15-minute OTA inquiries and under-5-minute WhatsApp replies around the clock mean either genuine night shifts, a rotating on-call host who sleeps badly, or a system that answers without needing either.
What AI-assisted operations actually hit
Top-quartile luxury villas in 2026 report median response times under 2 minutes, including overnight — a number that isn't achievable by discipline, only by architecture: an AI layer answers routine messages immediately in the guest's language, drafts replies on OTA threads for one-tap approval, and escalates the judgment calls with context. The important nuance: "median under 2 minutes" doesn't mean a bot handles everything — money, complaints and edge cases still route to a human — it means the 70% of messages that are routine stop waiting for one. On the platforms with a send API, the AI can send outright; on Airbnb and Booking.com threads, no third party currently has a send API, so the AI drafts and a human still taps send. That's the same limitation Hostella operates under by design, and it's worth naming rather than glossing over — the speed gain on OTA threads comes from killing the blank-page problem, not from removing the human click.
What this costs at your size
Hostella's Host plan is $69/mo plus $24 per villa for the first 100 units, dropping to $18 marginal per villa past 100. The pricing page breaks down what's included at each size.
See Hostella pricingHow to measure yours honestly
Pull your last 50 conversations and record the gap between each guest message and your first substantive reply — an auto-acknowledgment doesn't count, which is also the test to apply to vendors' speed claims. Use the median, not the mean (one 9-hour overnight gap poisons an average), but look separately at your worst decile: that's almost always overnight and almost always the cheapest thing to fix. Then track it monthly; response time decays quietly as portfolios grow, and the operators who stay fast are the ones who can see themselves slowing down.
Where to actually find these numbers: on Airbnb, response rate and response time sit at the bottom of each listing page. On Vrbo, responsiveness metrics live in the Inbox, and related metrics also surface on the Ranking Metrics and Premier Host pages — Vrbo notes these pages run on different time windows, so don't expect the figures to match each other exactly. On Booking.com, the Pulse app is where partners manage guest messaging on the go; Booking.com's current help pages describe the benefit of fast replies but don't publish the exact clock or thresholds behind the Reply Score, so treat any specific percentage you see quoted on a third-party blog with caution. None of the three give you a WhatsApp, email or direct-site number — those exist only in whatever inbox or AI layer you're using across every channel at once.
What does slow actually cost you?
We put numbers on the response-time gap — lost bookings, ranking decay, rebooking loss — in the companion analysis, with the math shown.
Read: The Hidden Cost of Slow Guest Responses