The 4pm check-in wave
Every independent hotel has one hour where three jobs land on one person. Only one of them needs the person standing at the desk.
The short version
3 things that decide this
- 01Your desk agent can do the check-in in front of them or the call ringing beside them, and at 4pm they are asked to do both plus a towel request.
- 02July runs 16.1 calls per room, and answered lead calls convert at 44 to 46% in summer (Revinate 2026), so the calls landing in that hour are worth real money.
- 03Read a month of your own phone log by hour before you buy anything or hire anyone. The hour where the ring-outs cluster is not always the hour you'd guess.
What 4:10pm actually looks like from behind your desk
You have one agent on. There's a couple checking in who want to know about parking, a line of three behind them, and the reservations phone ringing. A guest in 212 has just texted asking for extra towels. Housekeeping is still turning two rooms, and somebody in your lobby has waited forty minutes to hear that theirs is ready.
Your agent does the only thing a person can do here. They pick up the phone, say the name of the hotel, ask the caller to hold, and press the button. Then they go back to the couple in front of them, because those people can see them and the caller can't.
Operators describe this in almost identical words wherever you ask. Greet, hold, button. Some have stopped answering at all during the worst hour, reckoning that a caller who hangs up will ring back and that held lines eat more attention than a ringing phone. Both responses are sensible. Neither is free.
Why the hold button is the most expensive button on your desk
Here's the part that makes this hard to fix: nothing records it. A caller who hangs up at 4:11 leaves no row in your PMS, no line in the revenue report and no complaint at the desk. You never learn their name, so the wave gets managed with a hold button rather than treated as a problem with a number attached.
That number does exist, though, and it isn't small. July runs 16.1 calls per room, and answered lead calls convert at 44 to 46% in summer (Revinate 2026). Those are people who found you, chose to ring rather than click, and were ready to talk about dates. A caller who gives up has your competitor as the next result on the page they're already looking at.
So the honest way to describe the 4pm wave isn't that your team is slow. It's that you have three jobs arriving at one person in the same minute, and the two that get dropped are the two nobody in the building can see being dropped.
Read a month of your own phone log before you buy anything
Before you look at a single vendor, pull your calls for a full month, split by hour and by shift, and put them next to your arrivals for the same period. You want three things out of it: when the ring-outs cluster, how long the average caller waits before they give up, and what those callers were trying to do.
That last one is the useful part, and it usually surprises people. Most operators expect the wave to be all new bookings. In practice it's a mix: availability questions that are bookings, parking questions that aren't, in-house guests asking for something, and a few calls that genuinely need your duty manager. Only the last group truly needs a person at the desk.
Do the same for the request path while you're there. Time how long a towel request takes to get from a guest's text to a housekeeper who knows about it, and count the hops. If the answer involves a sticky note and a radio, that's your second leak, and it's the one that becomes a review a week later.
- 01Calls by hour and by shift, against arrivals, for a month. Not a week.
- 02Ring-outs and average wait before hang-up, so the cost has a size.
- 03What callers wanted, sorted into bookings, guest requests, and anything needing your manager.
- 04The request path, timed end to end, with every hop counted.
Move two of the three jobs, and leave the third alone
Your check-in stays with your agent. That's the part guests remember and the part you sell. What moves is the phone and the request.
On the phone, that means the overflow call gets answered on the second ring instead of held. It reads live availability from your PMS, quotes by your rate rules, takes the booking and texts the confirmation while the caller is still on the line. Parking, late arrival and "is it cheaper on Booking.com?" get answered the way you decide in advance, because those three questions are most of your wave's volume.
On the request, your guest's text becomes a task with a room number, an owner and a due time, sent into your housekeeping module or task app. Your guest gets an ETA straight back, and if it passes with the job still open, your duty manager hears before the guest does. Room-ready fires from room status rather than a walk, so the guest in your lobby gets told without your agent breaking off a check-in.
- Guest at the deskStays with your agent. Face to face, undisturbed.
- Overflow callAnswered, quoted from the PMS, booked, confirmed by text.
- Guest requestA task with an owner and an ETA, not a note in someone's head.
- Safety callReaches a person before the caller finishes the sentence.
One agent carries the first of these properly. The middle two are what a system is for, and the last one never moves.
What never leaves a person, however busy the lobby gets
Any of this only works if the boundary gets written down first and tested first. Fire, medical, security and any call about a guest's safety reach a person before the caller finishes the sentence. Rate parity, overbooking walks and chargebacks stay with your duty manager. Review replies are drafted for you and never posted on their own. Card details never enter a call transcript or a message log.
That list is short enough to fit on one page, and writing it out is genuinely the first task rather than a compliance step at the end. If a vendor can't show you their version of it, the boundary doesn't exist yet.
Start with the log, not the vendor
Pull the month of calls by hour against your arrivals, and time your request path end to end. Then sit at your own desk from three until six on a normal Friday and count what arrives. You'll finish knowing whether your wave is a phone problem, a request problem or a staffing problem, and most properties find it's two of the three in a split they didn't expect.
Then decide what a person has to carry, write the safety list, and move the rest. If you want a second pair of eyes on the numbers, our free Guest-Journey Audit is exactly that reading, and the one-page map is yours either way.
- 01Pull a month of calls by hour and shift, against arrivals.
- 02Time the request path end to end and count the hops.
- 03Write the safety escalation list before you look at any vendor.
Where the mechanism is written out in full
The direct answer, with the boundary drawn
If you want the short version of what to move and what a person keeps, the answer page states it in a paragraph and then argues it. It covers the same three jobs, plus the four things that never leave a human whatever the lobby looks like.
How should a hotel handle the 4pm check-in wave? →
What the overflow line actually does
The guest desk page goes through the call itself: reading availability out of your PMS, quoting by your rate rules, booking, texting the confirmation, and waking a person by a rule you write. It also covers the line after 11 at night, which is the same problem in a quieter building.
AI guest desk →
Some of the systems we have shipped
What operators ask about the wave
01Isn't a second agent between three and six the simpler fix?+
It's simpler and often the right first move, and it stops working the moment somebody calls in sick or a group arrives early. Front-desk shortages are also common enough that the second person frequently isn't available to hire, with 26% of hotels reporting them (AHLA/Hireology 2025). Move the two jobs that don't need a person, and the second agent becomes a good day rather than a dependency.
02How far back should the phone log go?+
A month, and a representative one. A single week gives you a shape that a conference, a bank holiday or one quiet Tuesday can distort badly, and seasonal properties should read a month from their actual season rather than the shoulder. You're looking for a pattern by hour and shift, which needs enough days to be a pattern.
Related
- How should a hotel handle the 4pm check-in wave? →The direct answer, and where a person still has to stay.
- AI guest desk →The overflow call and the after-hours line answered, quoted and booked.
- Hotels →The whole chain for a property, built around your PMS.
- Operations automation →Request to task to room-ready, without the desk in the middle.
- How to win back direct bookings from OTAs →What that answered call is worth once you can see the commission.
- AI, automation and custom software for hospitality →Which page owns each part of the guest chain.
