Two numbers sit side by side at the bottom of every Airbnb listing. People read them as one measure of responsiveness. They are not one. Response rate and response time do not count the same messages, do not react to the same delay and are not repaired the same way.
Mixing them up leads to a common mistake in method: chasing speed to save a rate that speed does not touch. Or polishing a rate that is already perfect while the average drifts.
- The definitionsWhat each number really counts
- The trapDeclining is a response, letting a request expire is not
- The costOne miss on the rate, one delay on the time
Two numbers, three populations
The Help Centre gives two separate definitions. Response rate is the percentage of new enquiries and reservation requests you responded to within 24 hours in the past 30 days. Response time is the average time it took you to reply to all new messages in the past 30 days.
The nuance fits in two words. The rate is about requests. The time is about all new messages. The first is binary: a request is handled within 24 hours or it is not. The second is an average. It keeps track of every minute spent waiting.
Superhost status adds a third reading. Its responsiveness criterion asks you to respond to 90% of new messages and to accept or decline new reservation requests within 24 hours. But it is assessed over the past 12 months, not over 30 days.
| Number | What it counts | Period | Shape |
|---|---|---|---|
| Response rate | New enquiries and reservation requests | Past 30 days | Share handled within 24 hours |
| Response time | All new messages | Past 30 days | Average time to reply |
| Superhost criterion | 90% of new messages within 24 hours | Past 12 months | Threshold reviewed every quarter |
One thing they share is the one that surprises people most: neither the rate nor the time includes message threads between hosts and guests after a booking. Everything said during the stay, from the code that will not work to the question about the heating, stays outside both numbers. It is also why an overnight on-call rota buys nothing on the display.
What counts as a response
The official list is broader than people expect. The following keep the rate up: accepting or declining a reservation request, pre-approving or declining an enquiry, sending a special offer, replying to an enquiry.
So declining counts as responding. A request for impossible dates is dealt with in one move. That move protects the rate as much as an acceptance. Many hosts do the opposite and let the requests they plan to turn down linger, out of awkwardness or lack of time. That is exactly the behaviour the metric punishes.
Your response rate will go down if you do not act on a reservation request and it expires. A request left unanswered is not neutral: it counts as no response. If you reply after 24 hours, the reply is late, which lowers the rate and raises the time at once.
The Help Centre adds that the rate determines your eligibility for Superhost status and your placement in search results. The number is not decoration. It weighs on how visible the listing is.
What a single oversight costs
The two numbers do not react to the same fault. Take a listing that receives twenty new requests over thirty days. Each missed request takes five points off the rate, since it weighs one twentieth of the total.
Response rate over 30 days, for twenty requests received
Illustrative model- none missed
- 100 %
- 1 missed
- 95 %
- 2 missed
- 90 %
- 3 missed
- 85 %
- 4 missed
- 80 %
At the third miss, the rate drops below 90%.
Twenty new requests received over thirty days, each missed request being either expired or handled after 24 hoursThe 90% line is reached at the second miss. The third one crosses it. On a small volume, the margin is two requests a month. A listing that receives ten has only one.
Response time degrades differently. Suppose nineteen messages handled in ten minutes and a single one handled after 48 hours. The average goes from ten minutes to about two hours and thirty-four minutes, fifteen times more, for one late message. On the same series, the rate loses only five points.
The practical consequence is simple. To protect the rate, let nothing expire. To protect the time, avoid long isolated waits. Replying in eight minutes instead of three hours changes almost nothing to either.
Holding both numbers without giving up your evenings
- Handle every new reservation request before any other conversation, because it is the only one whose expiry lowers the rate.
- Decline straight away what will not work. A quick refusal is a response, three days of hesitation is a miss.
- Use pre-approval or a special offer when the dates work but a question is still open: both count as responses.
- Watch the long waits rather than the average speed. A message left two days costs the time more than a hundred slightly slow replies.
- Check both numbers in the Performance tab, not only on the listing, to see the drift before it shows.
Airbnb's automated messages help little here: they fire on booking events, while the rate is decided on the requests that arrive before.
Three ways to let no request expire- CopiloteSentioo drafts the reply to each new request from the facts of the listing, you review before sending.
- HybrideQuestions with a stable answer go out on their own, anything that commits you on dates or price comes up to you.
- AutopiloteSentioo replies directly to enquiries at any hour. Anything beyond the covered scope waits for you.
A last point for management companies: Superhost status is assessed only for listing owners. A co-host can hold the rate day to day without ever carrying the status, as the guide to the Airbnb co-host explains. The four requirements and their 12-month window are set out in the article on Superhost requirements.
