The Five Questions Your Front Desk Answers 200 Times a Day

• Five recurring questions account for the bulk of front desk interaction volume, and none of them require a human being to answer.
• Two of the five are not information requests at all. They are revenue events, and the answer determines whether money is spent on the property or off it.
• Hotels are running on 7.4% fewer labour hours than in 2019 while paying 22.1% more in compensation, so every minute at the desk costs more than it used to.
• The most expensive question is the one a guest decides not to ask. It never appears in any log.
• You can measure your own volume in one day with a tally sheet. There is one at the bottom of this article.

Ask any front office manager which questions dominate their day and you will get an accurate answer in about four seconds. Ask for the count and the conversation stops.

Hotels measure occupancy to a decimal place, track rate against a competitive set daily, and can tell you the pickup for a Tuesday three weeks out. Nobody counts how many times reception explains where breakfast is served. The interaction leaves no record: no ticket, no line item, no field in the property management system. It happens, it takes ninety seconds, and it evaporates.

This is not an oversight so much as a category error. Answering guest questions is filed under service, and service is treated as an ambient cost of being open rather than as a measurable, improvable process with a price attached. So the volume grows, the staffing gets tighter, and nobody can point to the trade because there is no number to point at.

The labour context makes this worse than it used to be. CBRE, analysing its own hotel operating sample, found that hours worked at the typical hotel are down 7.4% since 2019 while compensation dollars are up 22.1%, summarising the position as hotels paying more for fewer hours worked. On the US side, an American Hotel and Lodging Association survey of 246 hoteliers published in March 2026 found more than half of properties describing themselves as somewhat or severely understaffed, with 70% raising wages to recruit. In Europe, HOTREC has put the hospitality sector roughly 10% short of the workforce it needs.

Fewer hours, each one more expensive. That is the backdrop against which five hours a day goes into repeating the same five answers.

These are the recurring categories, not a measured ranking. Order them yourself with the tally sheet at the end. What matters more than the order is what each one actually is, because two of the five are misfiled.

1. "What is the wifi password?"

The purest form of the problem. Zero revenue potential, high frequency, asked at every arrival and again by every second guest in the party who did not hear it the first time. It is a pure information failure, and it is the easiest of the five to remove entirely.

Worth noting where it usually sits: printed on a card that is in the room, which the guest is not in, because they are at the desk asking you.

2. "What time is breakfast, and where?"

Also an information question, but with a revenue tail. A guest who does not know the breakfast window, or who thinks they have missed it, eats somewhere else. A guest who does not know breakfast is not included in their rate does not buy it. The information gap and the sale are the same gap.

The same shape covers pool hours, gym access, parking, and the question of whether the spa is open today.

3. "Is the restaurant still open?"

This one is not an information request. It is a purchase decision in progress, and the front desk is standing in the middle of it.

A guest asking this at 21:40 has a window and is deciding whether to use it. If the answer arrives fast and confidently, you have a cover. If they have to queue behind two check-ins to get it, or if the phone rings out, they order elsewhere or go to bed. Same kitchen, same menu, same guest. The revenue turns on a ninety-second interaction that nobody has ever measured.

Every hotel with an F&B operation loses covers this way, nightly, invisibly.

4. "Can I get extra towels?"

A routing question. The front desk cannot fulfil it, so the interaction is not an answer, it is a handoff: reception takes the request, relays it to housekeeping, and hopes it lands.

Handoffs are where guest requests die. The desk is confident it passed the message on. Housekeeping is confident it never arrived. The guest, who has no visibility into either, waits, then follows up, which generates a second interaction about the first one. One request has now consumed three staff conversations and produced one mildly irritated guest.

5. "What is there to do around here?"

The most expensive question in the building, and the one most hotels answer worst.

A guest asking this is telling you they have unallocated time and unallocated budget. That is the exact condition every marketing department spends money trying to manufacture, and it has just walked up to your desk unprompted.

The standard answer sends them out. A restaurant recommendation down the street, a map, a walking route. All genuinely helpful, all hospitable, and all of it exports the spend to a business that does not pay your wage bill. Meanwhile the property's own spa has a free slot at 15:00, the bar has a terrace nobody has mentioned, and the guest never learns either thing exists.

This is not a staff failure. A receptionist recommending a good local restaurant is doing their job well. It is a process gap: nothing in the interaction surfaces what the property itself has available at that moment, so the human default takes over.

Three costs, only one of which shows up anywhere.

The visible cost is time. Two hundred interactions at ninety seconds is five hours a day, about 1,825 hours a year at a single 120-room property. That is roughly one full-time position. It is not one person's job, it is a tax spread across every shift, which is exactly why it never gets budgeted or challenged.

The second cost is queue displacement. Front desk capacity is not evenly distributed across the day. It collapses in the arrival window. A guest with a revenue-bearing question, a spa booking, an upgrade, a dinner reservation, arrives at 16:20 behind four people asking about wifi and parking. Some of them wait. Some of them do not. The questions that get abandoned first are the discretionary ones, which is to say the ones with money attached.

The third cost is the one you cannot see at all, and it deserves its own section.

Every question in the list above is a question a guest decided was worth the effort. They got up, went to the desk, or picked up the phone, and waited.

For every one of those, some number of guests thought about it and did not bother. The spa treatment they half-considered. The dinner reservation they were not sure how to make. The bottle of wine they would have had sent up if it had not meant calling reception and explaining themselves.

Those never appear in any log, because there is nothing to log. They are pure margin that quietly did not happen, and no report anywhere in the hotel will ever surface them.

This is the part of the picture that argues against the obvious conclusion. Reading the five questions above, the natural reaction is that the goal is to reduce interaction volume. It is not. The goal is to remove the interactions that carry no value so that the ones that do can actually happen, including the ones guests currently talk themselves out of.

A front desk fielding 200 questions a day is not busy with the wrong things because the staff are doing anything wrong. It is busy with the wrong things because the hotel has exactly one interface, a human being at a counter, and every question in the building has to route through it.

Some numbers from Qreadible's own client properties, which are ours and reported here as such, not as an industry benchmark. Individual properties, small sample, and we say so plainly.

At one US property, 89% of guests who checked in used the platform during their stay, and about 60% of those came back to make more than one request. Adoption is the number hoteliers doubt most before deploying and stop asking about within a month.

One partner property reported a 15% increase in food and beverage revenue through room service after go-live. Not because the kitchen changed, and not because anyone was upsold. The ordering process stopped requiring a phone call.

The pattern behind both is smaller than it sounds. At two properties we watched what happened when the security code required for ordering sat at the start of the flow, before the guest had seen the menu: abandonment ran around 40%. Moved to the final confirmation step, after the order was built, abandonment fell to almost nothing. Same friction, same code, different moment. Guests do not object to being asked for something. They object to being asked before they have a reason to care.

And the operational half, from the F&B manager at Hotel Sunce during a holiday peak: order volume was high, but because guests could see how long the order would take to reach the room, there were no delays reported and no complaints. Nothing about the kitchen's actual speed changed. What changed was that guests could see the wait instead of sitting in silence wondering about it.

What we do not have, and will not invent, is a per-question count across the portfolio. We can see how often guests open the information sections instead of calling down, but we have not published that as a benchmark yet, and until we have, our own number would be as unverifiable as anyone else's.

The strongest version of this article is the one you write about your own property. This takes one shift, a printed sheet, and a pen at the desk.

Pick a normal day, not a Saturday in August and not a dead Tuesday in November. Ask the desk to mark one stroke per interaction, phone and in person both.

Then run four calculations:

1. Total interactions divided by occupied rooms. This is your per-room daily interaction rate, and it is the number to track over time.
2. Total interactions times your average handling time, honestly estimated. Ninety seconds is a reasonable starting assumption. Multiply by 365 for the annual hours.
3. Row three plus row five as a share of the total. This is the portion of your desk's day that is revenue-adjacent and currently being handled as though it were administration.
4. The night column. Between 23:00 and 07:00, most independent properties have one person covering everything. Look at what that person was asked and ask whether any of it needed to be a person.

Take the same tally again in three months. The comparison is worth more than the first number.

Most hotels already have a system that answers these five questions perfectly. It is fluent, adaptable, warm, and it handles edge cases better than any software will.

It also costs roughly one full-time salary a year to run at this volume, it gets a queue behind it at 16:20, it goes off shift at midnight, and when it recommends dinner, it usually recommends someone else's.

Count your own five questions for a day. The number will not be the one in this headline, and that is the point.

Qreadible is the layer that answers the routine questions where the guest already is, so the front desk gets back the hours and the guest gets the answer at 23:40 without calling anyone. If you want to see what your own volume looks like, get in touch.