The four calls your front desk takes all day, and how to move them to WhatsApp

Ask any front desk which calls came in this morning. The answer is nearly always the same four: check-in time, parking, directions, and "do you have a room this weekend?"

None of those needs a voice. Every one of them pulls a staff member away from the guest standing at the desk, and the guest at the desk notices.

The fix is not to answer faster. It is to move routine calls into a channel where the answer is written once and sent in seconds. If you have not yet counted which questions actually repeat, audit the questions your team answers forty times a day first. The list is usually shorter and more boring than anyone expects, which is exactly why it works.

Turn calls into chats

With a connection between your phone system and WhatsApp, three things become possible.

"Press 1 to continue on WhatsApp." The caller leaves the queue, gets a WhatsApp message within seconds, and the assistant answers there. No hold music.

Missed call? After a set number of rings, or when nobody picks up, the caller automatically receives a message: "we saw you called, how can we help?" This is the one that pays for itself, because today those calls simply end.

A different message per extension. Reception, restaurant, bar and events can each open with their own message, so the conversation starts in the right place instead of being transferred.

The part that decides your cost: who sends first

This is where hotels get caught out.

Meta opens a 24-hour customer service window when a WhatsApp user messages you or calls you on WhatsApp. If they message again before it expires, the timer resets. While that window is open you can send ordinary free-form messages, text, images, PDFs and buttons, with no pre-approval at all. When the window closes, you can only send pre-approved template messages (read 28 September 2026).

Now apply that to the telephone. A call to your switchboard is not a WhatsApp interaction. It opens nothing. So when your system messages that caller first, it is a business-initiated message with no window behind it, and a template is the only kind of message that can be sent (read 28 September 2026).

That is why the missed-call message needs an approved template. There is no way around it.

"Press 1" has two implementations, and they are not equivalent:

1. Your system sends the WhatsApp message. Seamless for the caller. Business-initiated, so it needs an approved template and is charged per delivered message.
2. The caller opens the chat. The menu texts them a click-to-chat link, or your recorded message points them to it. The guest sends the first message, which opens the 24-hour window, and everything after that is free-form.

Option 2 is cheaper and more flexible, because you are not bound to fixed template wording. It also loses people at the extra tap. Most properties use option 1 for missed calls, where there is no alternative, and option 2 where the caller is already listening to a menu.

One thing that changed under everyone this autumn: since 1 October 2026 Meta charges per message for service messages too, the free-form replies sent inside an open window, which had been free since November 2024. Each business phone number gets 1,000 delivered service messages free per month, resetting with no roll-over, and charging starts after that (Meta, pricing, read 1 October 2026).

So a property answering a few hundred messages a month pays nothing, while a busy attraction in high season has a real line item. Staying inside the window is still simpler than sending templates. But "it's free" is no longer the reason. The October pricing change has the full working, and the pricing calculator will do it by guest country.

Why guests like it

• No waiting on hold, and no calling back later.
• Links, maps and prices arrive in writing, where they can find them again at the station or in the car park.
• They can answer at their own pace, between meetings, instead of holding.

Why staff like it

• Fewer interruptions at the desk.
• Answers are consistent. The new starter and the duty manager give the same parking instructions.
• Complex requests arrive as a ticket with a summary rather than a sticky note that falls off the monitor. From guest message to ticket covers the routing side of that.

Edge cases to decide before you switch it on

Withheld and non-mobile numbers. You can only message the number that called. A withheld caller ID or a landline cannot be messaged, so keep voicemail alive as the fallback rather than letting those calls vanish.

The caller who is not on WhatsApp. The send will simply fail. Decide what happens then: usually a callback task for reception.

Out of hours. A message at 02:00 that promises an answer implies someone is reading it. Either say plainly when a human is back, or route genuine night issues to a phone that rings.

Emergencies. A guest locked out of the car park at midnight should not be steered into a chat queue. Keep an obvious route to a person on every menu. Which requests always need one is a decision worth writing down in advance: see the requests you must not automate.

Language. If a third of your callers are international, the opening message and the template need to exist in their language too. Each language version is a separate template.

What to prepare

1. Your phone menu tree, written down, with the option each department owns. Most hotels discover here that two options go to the same handset.
2. An opening message for each option. One sentence of who you are, one of what you can do.
3. An approved template for the missed-call message. Submit it early: a review decision can take up to 24 hours (read 28 September 2026), and rejections over formatting or wording are common.
4. A decision on how "press 1" starts the chat. Your template, or their tap.
5. A fallback for withheld numbers and failed sends.

Takeaway

You cannot stop the phone ringing. You can stop routine calls from costing your team its attention. The trick is knowing who sends the first message, because that decides both the paperwork and the bill.

None of it holds up on a handset behind reception, so settle the choice between the app and the official platform first.