How a hotel front desk stops missing calls

Most hotels do not have a phone problem all day. They have a phone problem in two windows, and those two windows account for nearly all of it.

The first is the check-in rush. One person on the desk, a queue in front of them, and the phone going. Whoever is standing there wins, because they can see you ignoring them. The caller gets voicemail.

The second is after hours. Somebody finishes work, thinks about a weekend away, and rings at half past eight. If your line rolls to voicemail, they ring the next place on the list, or they book through a booking site and you pay the commission on a guest who tried to come to you directly.

Find out how bad it actually is first

Before spending anything, get the call records from your phone provider for the last full month. Every provider can produce them. You are looking for four things:

• Calls that rang out or went to voicemail
• Calls that arrived outside your staffed hours
• Average time to answer, by hour of the day
• The same number ringing twice within an hour

Put the missed ones in a bar per hour of the day. In most properties the shape is obvious within about a minute of looking at it, and it is not always where the owner expected -- breakfast and the group check-out can be as bad as the afternoon.

Then do a rough sum. Take the missed calls that arrived when someone might reasonably have booked, and assume only a fraction were bookings at all. Multiply by your average room rate and length of stay. It does not need to be precise. You are trying to find out whether you are looking at a rounding error or a real number, and either answer is useful.

If it is a rounding error, stop here. A small guesthouse where the owner answers the phone from their pocket at all hours genuinely does not need this.

Voicemail is not a safety net

Two things about voicemail are worth saying plainly. Most people who reach it do not leave a message; they hang up and dial the next number. And the ones who do leave a message tend to be existing guests with a problem, not new bookings. So the voicemail box gives you a false picture: it looks like your missed calls are mostly complaints, because those are the only ones patient enough to record something.

Start on overflow, not on everything

The rollout that goes wrong is the one where the agent answers every call from Monday. The rollout that works starts with the calls nobody was going to answer anyway.

Set your phone system to forward to the voice agent on two conditions only: when the desk phone rings more than four or five times without an answer, and when you are outside staffed hours. Nothing changes for a guest who gets through to your team. The agent only ever gets the call that was heading for voicemail.

This matters for three reasons. The risk is close to zero, because the alternative for those calls was nothing. You get real recordings of your real callers instead of a demo. And you can switch the whole thing off in about a minute by removing the forwarding rule, which makes the decision to try it much easier.

After a few weeks, the transcripts tell you whether to widen it. You will know from evidence rather than from a promise on a website.

What it needs to know

The agent is only as good as the information it is given. For a hotel that is usually:

• Room types, what is in them, and how many people each sleeps
• Live availability and rates, ideally read from the system rather than typed in
• Deposit, cancellation and late-arrival policies, in the exact words you would want a guest quoted
• Parking, pets, accessibility, check-in and check-out times
• Restaurant and bar hours, and whether non-residents can book
• Directions from the station and the airport, including the bit the map gets wrong

Writing this down is genuinely half the project, and it usually turns up two or three questions your own team answers inconsistently. Sort those out before launch, not after.

Connecting it to the property system

The difference between a useful agent and an answering machine is whether it can see your availability.

Connected properly, it reads what is actually free, quotes the right rate, takes the booking, and writes it into your property management system so the reservation appears in the same place as every other one. Payment or a card guarantee is handled through your normal payment provider. The agent should never read card numbers back or store them itself.

If your PMS has no usable connection -- it happens, particularly with older systems -- you have a decision. The fallback is that the agent takes the enquiry, captures the dates and the details, and drops it into the desk's queue to be keyed in and confirmed. That is worse than a live booking, and we will tell you so. It is still considerably better than a missed call, and it can run while a proper connection is being worked on.

You should not have to replace your PMS to fix your phone. If someone tells you that you do, get a second opinion.

What always goes to a person

Complaints. Anything about a charge, a refund or a deposit. A guest who is currently in the building and unhappy. Group bookings, weddings and functions. Anything about a booking made through a channel, because those get complicated fast. And anyone who asks for a person, immediately, without being talked out of it.

Agree that list with your duty managers before launch rather than after the first bad call, and write it into the agent as a hard rule instead of a suggestion.

What to measure afterwards

Four things, all countable from your own systems:

Answer rate. The share of calls answered within a few rings, by hour. This is the number the agent exists to move.

After-hours bookings taken. Bookings the agent completed while nobody was on shift. This is revenue that previously went to voicemail.

Handover rate. How often the agent passed a call to a person. There is no correct figure. If it is very low, check whether it is overreaching on things it should be handing over.

Direct versus channel mix. Slower to move, and lots of other things affect it, so do not credit the phone agent with the whole change. Watch it anyway.

Add one manual count. For one week, ask the desk to tick a sheet every time the phone interrupts them mid-guest. Do it again a month after launch. It is unscientific, and it is the number your team will care about most.

Where this does not help

If your desk is understaffed at check-in, the phone agent removes an interruption but the queue is still there. The phone was a symptom. A guest app or a faster check-in flow is a different project and probably the more important one.

If your rates and availability are wrong in your own system, the agent will quote them confidently and wrongly. Fix the source first.

And if you are a ten-room property where the owner genuinely answers every call, this is a cost with no matching gain. The properties this helps are the ones where the phone and a person's full attention are needed in the same minute, several times a day.