Audit the Questions Your Team Answers Forty Times a Day

Ask a reservations manager what their team does all day and you will get a considered answer about service, upselling and problem-solving. Ask them what their team actually types and says all day and the answer is much shorter, and much more repetitive.

That gap is where most operational improvement in guest communication lives, and it is measurable in about a week.

The number worth knowing

Studies in hospitality put roughly 40% of hotel phone inquiries in the category of repetitive questions about basic information - opening hours, prices, availability.

Four in ten. Not complex requests, not complaints, not anything requiring judgement or warmth. Hours, prices, is it available.

Two things make that worse than it sounds.

The share rises during peak periods. School holidays, long weekends, the run-up to a season - the volume of basic questions grows fastest exactly when the team has least capacity to absorb it.

And the cost is not the staff time. It is the calls that go unanswered while the team works through the queue. A missed call about availability is a person who was actively deciding, at the moment they were deciding, with alternatives one search away. Bookings do not fall through because the answer was wrong. They fall through because nobody answered in time.

Run the audit

This does not require a system or a consultant. It requires a week and a sheet of paper at the desk.

For each inbound question, record four things:

1. The question, in the guest's words rather than a category. 2. The channel it arrived on. 3. Roughly how long it took to resolve. 4. Whether it needed judgement - could a well-briefed new starter with the right information have answered it?

At the end of the week, sort by frequency.

The result is almost always the same shape and still surprises people: a small number of questions account for the large majority of interactions, and nearly all of them fall in the no judgement required column.

Read the exact wording

The most valuable column is the first, and it is the one people are tempted to compress into categories.

Availability as a category tells you nothing useful. The actual phrasings tell you a great deal:

• Do you have anything for Saturday night?
• Is the pool open in October?
• Can we bring kids?
• Do you do the crocodile feeding on weekdays?
• Is there parking, and is it free?

Those are five different questions with five different sources of truth. Two need a live system, two are static facts, one is seasonal. Categorising them all as availability hides exactly the distinctions that determine how each should be handled.

Keep the guest's words. They are also, incidentally, the best possible source material for the answers themselves.

Start with the single most frequent question

The temptation after an audit is to address everything. Do not.

Take the one question at the top of the list and handle it properly, end to end, including what happens when the answer is no or the guest asks a follow-up.

Starting narrow has three advantages:

• It is provable. You have a count from before. You can produce a count from after. That comparison persuades a general manager in a way that a satisfaction score never will.
• It is fixable. If the answer is wrong or the tone is off, you find out on one question rather than across forty.
• It builds trust with your own team. Staff who watched one thing work properly are more receptive to the second than staff who were handed a whole system.

What to measure

Measure the volume of that specific question reaching staff, before and after. Not overall satisfaction, not total conversations handled - those move for many reasons and prove nothing.

Then look at two second-order effects that usually matter more than the headline:

Response time on everything else. If the repetitive question stops consuming the queue, the non-repetitive ones get answered faster. That is often the larger operational gain and it is invisible unless you look for it.

Conversion on the automated question specifically. If it is an availability or price question, whether guests who asked it went on to book is the number that turns an operational improvement into a revenue argument.

The reframe

The purpose of automating a question your team answers forty times a day is not to remove the team from the conversation.

It is that the fortieth time somebody asks what time check-in is, they get the same clear answer as the first time - and the person who would have answered it is free for the guest whose flight was cancelled, who is standing at the desk with two tired children, and who needs somebody to actually be present.

That trade is the whole argument. It is worth making with a number from your own property rather than a claim from a vendor, and the audit that produces that number takes a week.