Guests keep messaging me at 2am. How do I get my sleep back?
15% of guest messages land between 22:00 and 07:00. What the night traffic really is, how fast an answer goes out, and the four ways to stop losing sleep.
Most 2am messages have one of four answers. Write the answer down before the guest arrives. Fit a keypad lock. Pay a co-host to read the inbox overnight. Or hand the messages off completely. The first two cost an afternoon and remove most of what wakes you.
They also arrive less often than they feel. Across the Warsaw flats we run, 309 of 2,062 inbound guest messages came in between 22:00 and 07:00 Warsaw time, February to September 2026. That is 15.0%, about one message in seven. Hardly any of them are a burst pipe.
What the night traffic actually is
Two nights out of the logs, both central Warsaw.
August 2026. A guest wrote just after 22:00 to ask what time check-in was. An acknowledgement went back in about 15 seconds. The check-in time was confirmed the same evening.
February 2026. Five short messages came in between roughly 01:50 and 02:05, the night before arrival. The first were about flight timing. Then the guest-app link would not open on their phone. The reply pointed at the browser version, which needs no download, and the rest of the thread waited for morning.
Neither guest was in trouble. One wanted a number that was already written down somewhere. The other was awake at 2am with a phone that would not cooperate, the night before flying.
The ticket record says the same thing at a larger scale. Of 57 guest tickets raised across those homes from February to August 2026, 23 were about access. A code that did not work. A door a guest could not find. A lock with no instructions loaded. Maintenance came next at 11, then ID verification at 6 and housekeeping at 5. Two of the 57 are still open. For scale, the same homes took 663 reservations in the last twelve months, cancellations included, and roughly 2,332 nights. Four in ten of the tickets that do arrive are about getting through a door.
How fast is fast, and what that misses
Median time to the next message in a guest thread is about 27 seconds. That is across 1,607 paired exchanges, February to September 2026. Treat the number carefully, as we do. It measures the next outbound message in the thread, which is often an acknowledgement rather than a full answer. It tells you a guest stops waiting in silence within half a minute. It does not tell you the door opened.
Airbnb measures something else again. Response rate is "the percentage of new inquiries and reservation requests you responded to within 24 hours in the past 30 days", and a plain message counts, alongside accepting, pre-approving, declining or sending a special offer. (airbnb.com/help/article/430, checked 2 September 2026) Superhost status asks for 90% of new messages answered inside 24 hours, and response rate can affect where a listing sits in search results. (airbnb.com/help/article/2414, checked 2 September 2026)
So a reply at 09:00 keeps the platform happy. It does nothing for the guest at 02:00, and the guest writes the review.
Write the answers down before arrival
Five things go into one pre-arrival message. The door code. The wifi name and password. How the heating works. Where the bins go. One line about noise at night. The same text goes into the listing's house guide, because a guest in a dark stairwell will not scroll back through a chat thread to find it.
Send it 24 hours before arrival rather than on the day, so a guest reads it before the airport instead of in the stairwell.
Two more lines earn their place. Say when routine questions get answered, so the coffee machine has a daytime slot to wait in. Then give one number for water, gas, smoke or a door that will not open. The real thing should not be queued behind the coffee machine.
What paying for cover buys
| Option | What it covers | Cost | The honest trade-off |
|---|---|---|---|
| Written answers before arrival, plus stated reply hours and one emergency number | The questions that repeat: getting in, wifi, heating, bins, noise | Your own time | Removes most of the night traffic and none of the real emergencies |
| Keypad lock or lockbox | The commonest night message, a guest who cannot get in | One-off device cost | Access was 23 of our 57 guest tickets, so this is the best-value hardware on the list, and it still needs the code to be right |
| Co-host reading the inbox for you | Somebody answers on your listing, day and night | Airbnb's co-host marketplace defaults are reported at 20% of the net payout for a hands-off co-host and 25% for a full-service one (rakidzich.com, 13 May 2026, checked 2 September 2026) | Somebody is awake instead of you, but you vet, brief and manage them, and the cut is monthly |
| Letting agent or full manager | Guest contact plus the running of the flat | A share of revenue, terms differ by firm | Read the contract before you sign, and what to check inside it is a question of its own |
Which messages need a person on the ground
Answering through the night is not sustainably one person's job. The split worth making is between the message somebody has to walk to and the message that closes inside the thread.
Central Warsaw, July 2026. Just after 22:00 on the night before checkout, a guest reported alarm-like beeping in the building and said nobody seemed to be dealing with it. It was logged as an urgent escalation and closed. No further reports about the noise followed.
Central Warsaw, August 2026. A guest asked for the smart lock instructions, and none had been loaded into the system for that flat. Staff added them and the ticket closed in well under a minute. That was a missing paragraph dressed up as an incident.
Building noise at 22:00 wants somebody local and awake. The missing paragraph wanted writing months earlier.
Where we got this wrong
Central Warsaw, July 2026 as well. An access code failed to sync to a flat's smart lock around the guest's check-in time. A ticket went up the same afternoon asking for the code to be verified or another way in provided. The lock was resynced and the ticket closed about 8.2 hours later, the same day.
Eight hours is not an answer at check-in time. That case is why the 27-second median sits on this page beside it rather than on its own. Replying fast and fixing fast are two different numbers, and only one of ours is good.
Where we fit, and who this is wrong for
Resipilot answers guest messages day and night, and every number above comes out of its own logs. (resipilot.com, checked 2 September 2026) When something needs a person on site, a lockout at 22:00, the turnover between bookings, a repair, it goes to a local person in Warsaw, Krakow, Gdansk or Athens instead of into a longer thread. Nothing that costs money happens without your approval, repair quotes included. The fee is 8% of revenue, with no setup fee, no minimum and cancellation at any time. The owner contract is readable in full at /agreements before you sign it. Keep your own cleaner and handyman and hand over only the coordination if you would rather: that is /self-serve.
It is the wrong answer if all you want is the night inbox. That 8% is one fee covering messages, turnovers and repair coordination together, and the night shift is not sold on its own. It is also wrong for an owner who hosts partly because they like the contact. Hand the messages over and you lose the part of this you would have kept.
Questions owners ask next
Usually not. In our own message logs, 309 of 2,062 inbound guest messages arrived between 22:00 and 07:00 Warsaw time from February to September 2026, and the ticket record for the same homes is dominated by access: 23 of 57 tickets, against 11 for maintenance. A door code, a check-in time or a guest who cannot find the flat is the normal night message. Plan for the rare real one anyway.
No. Airbnb defines response rate as the percentage of new inquiries and reservation requests you responded to within 24 hours in the past 30 days, and sending a message counts, whether you typed it or pasted it. Superhost status asks for 90% of new messages answered inside 24 hours. What a template will not do is help a guest standing outside the door at midnight, and a template that answers the wrong question usually produces a second message you have to answer anyway.
Writing the answers once, before arrival: door code, wifi, heating, bins, noise at night. After that a keypad lock, because access was 23 of the 57 guest tickets in our records from February to August 2026. Everything past those two is paying somebody to read the rest.
In our logs the median time to the next message in a guest thread is about 27 seconds, over 1,607 paired exchanges from February to September 2026. Read that honestly: it counts the next outbound message, which is often an acknowledgement rather than a full answer. One night in August 2026 a guest asked about check-in just after 22:00 and got a reply in about 15 seconds, with the time confirmed the same evening. Fixing something physical is far slower. An access code that failed to sync to a smart lock in July 2026 took about 8.2 hours.
A co-host takes a share of the payout, and Airbnb's co-host marketplace defaults are reported at 20% for a hands-off co-host and 25% for a full-service one. A letting agent or manager charges a share of revenue and rarely prices messaging on its own, so read what the contract actually commits them to on response times before you sign it.
Partly. Writing the answers down first transfers, but the stakes differ: an 11pm message about a leak is not an 11pm message about wifi. Tenants increasingly expect the availability they would get texting a friend, which sits badly with a landlord holding a day job (OpenRent). Agree the emergency number and the daytime channel at the start of the tenancy, in writing.
Sources
- Airbnb Help Center: Improve your response rate and response time
- Airbnb Help Center: Why hosts are asked to respond within 24 hours
- Airbnb Co-Host Marketplace 2026: how pay, splits and vetting actually work (published 13 May 2026)
- OpenRent blog: WhatsApp, email or letters, what's best for landlord-tenant communication
- Resipilot
Drafted with AI from the sources above and checked against Resipilot's own operating records. Resipilot holds editorial responsibility for this page.