Response rate is the Airbnb metric hosts understand the least and lose the most sleep over — sometimes literally.
It is also the one most likely to cost you Superhost, because unlike your rating, it can collapse in a single bad month and there is no way to repair it retroactively.
What Airbnb actually measures
Two different numbers get confused constantly, so let us separate them.
Response rate is the percentage of new guest messages you replied to within 24 hours. It is a yes/no test per message. You either made the window or you did not.
Response time is how fast you typically reply, shown publicly on your listing as "responds within an hour" or similar. This one is a display badge, not a Superhost requirement.
For Superhost you need response rate at 90% or above. That means out of every ten new guest conversations, you can miss at most one. It is one of four requirements you have to hold at the same time, and the one hosts most often lose.
Why the 24-hour clock is harsher than it looks
Twenty-four hours sounds generous. The trap is what starts the clock.
It is the first message in a new thread — an inquiry, a booking question, a mid-stay problem opening a fresh conversation. Not every reply in an ongoing back-and-forth. So the messages that hurt you are precisely the ones that arrive unannounced, from someone you were not already talking to.
And those arrive on the guest's schedule, not yours:
- Someone in a different time zone browsing your listing at 3 AM your time
- A guest who lands at 11 PM and cannot find the lockbox — the most common late-night message there is
- An inquiry that arrives on the one weekend you were camping without signal
Miss three of those in a quarter when you only had thirty conversations, and you are at 90% exactly — one message away from losing the badge.
The part that catches people out
A missed response is permanent for that assessment period. Replying nine hours late does not convert a miss into a hit. There is no appeal, no partial credit, and no "but I was very helpful once I woke up."
This is why response rate punishes coverage gaps rather than bad hosting. Hosts who lose it are rarely rude or negligent. They are asleep, at work, on a plane, or on holiday themselves.
Four ways to protect it
1. Turn on push notifications and actually separate them
Most hosts have Airbnb notifications buried in the same undifferentiated pile as everything else on their phone. Give the Airbnb app its own notification sound, and allow it through Do Not Disturb if your platform supports per-app exceptions.
This is the cheapest fix and the one most hosts skip. It will not solve the problem, but it converts a chunk of misses into hits for zero cost.
2. Use saved replies for the questions you already know
Airbnb has a built-in saved-messages feature. Write one for each of your top questions — check-in steps, Wi-Fi, parking, checkout, pets, early arrival — so replying is two taps rather than two paragraphs.
This does not extend your coverage, but it dramatically reduces the friction of replying, which means you are more likely to do it at a moment when you could but would rather not.
3. Add a co-host for the hours you genuinely cannot cover
If you have a partner, a cleaner you trust, or another host you swap with, adding them as a co-host means their replies count. This is the only method that genuinely extends human coverage, and it is worth doing if you have someone reliable.
The catch is that reliable someones are rare, and they get tired of 11 PM Wi-Fi questions at roughly the same rate you did.
4. Remove the reason for the message entirely
This is the one that actually moves the number, and it is a different kind of fix from the other three.
The other three help you answer faster. This one reduces how many messages get sent at all.
Go through your last three months of guest messages and sort them into two piles:
Pile A — things only you can resolve. The boiler is broken. A neighbour is complaining. They want to extend by two nights.
Pile B — things that are just information. Wi-Fi password. Bin day. Checkout time. How the coffee machine works. Where to park. Is there an iron. What time is the pool open.
For most hosts, pile B is the overwhelming majority. And every message in pile B is a message that started a 24-hour clock for no reason other than the guest could not find a fact.
If a guest can get those facts themselves — at the moment they have the question, in the property, without downloading anything — they never open the thread. No thread, no clock, no risk.
That is what Askbnb is for. Your property's information becomes an AI the guest reaches by scanning a QR code on the fridge. They ask "what's the wifi" in their own words at 11 PM and get your answer immediately. You find out in the morning, if you care to look.
The effect on response rate is arithmetic rather than effort: shrink the denominator of low-stakes conversations and the handful of real ones become easy to cover.
What to do if yours has already dropped
If you are sitting below 90% right now:
Check the actual figure, not the vibe. Your dashboard shows it directly. Hosts routinely assume it is fine when it is not, and assume it is ruined when it has recovered.
Understand it recovers by dilution. You cannot fix past misses, but the figure moves as new conversations come in and are answered on time. A run of good months pulls it back up.
Fix the coverage gap that caused it. If you lost it during a holiday, you need a co-host or self-serve information before your next holiday. If you lost it to a run of midnight Wi-Fi questions, the fix is the Wi-Fi question disappearing, not you sleeping worse.
It is worth knowing the same gap costs you twice: the guest who had to wait also tends to leave a 4-star review rather than a 5.
Response rate rewards being reachable. It does not require being personally awake — and the hosts who hold it comfortably long-term are almost always the ones who stopped trying to be.