Hotels spend a lot of thought on the phone in the room and almost none on the phone that rings at the front desk. One of those is a service feature. The other is a distribution channel with no commission attached, and it is the only channel in the business that nobody reports on.
Every hotel runs two phone systems
They usually sit on the same hardware, which is why the distinction gets missed. But they serve two different populations with opposite requirements.
| Guest-facing telephony | Revenue telephony | |
| Who is calling | Someone already staying with you | Someone deciding whether to |
| Where it lives | In-room handsets, wake-up calls, room status, call billing | Reservations, groups, functions, and events |
| Usually measured by | Service response and complaints | Nothing, in most properties |
| What failure looks like | A comment at checkout or in a review | A booking you never knew you lost |
| Where the budget goes | Most of it | Almost none of it |
The bottom two rows are the argument. Guest-facing failures are visible, because guests tell you, and hotels have decades of practice managing them. Revenue-side failures are silent. A traveller who rings, waits, and hangs up does not fill in a card about it. They book somewhere else, or they book with you through a channel that takes a cut.
The imbalance is understandable. In-room telephony has a specification, a compliance angle, and a vendor asking about it, so it gets attention during procurement. The reservations line has none of those things. It is just a number that has always been there, answered by whoever is at the desk, and nobody has ever presented a board paper about it.
What does a hotel phone system need to do?
A hotel phone system serves two separate jobs. Guest-facing telephony handles in-room phones, wake-up calls, room status, and call billing, and usually needs to talk to the property management system. Revenue telephony handles reservations, groups and functions enquiries, and needs queues, reporting, and after-hours cover.
Make Property Management System (PMS) integration your first question to any supplier, not your last. Support varies by system and version, and the answer determines a surprising amount of daily operation. Working integration is what lets housekeeping mark a room clean by dialling a code from the room phone rather than radioing the desk, clears the previous guest’s voicemail automatically at checkout, posts call charges to the folio without anyone keying them, and drives wake-up calls from the booking rather than a paper list.
Without it, all of that becomes manual, and the gap usually shows up three weeks into a deployment rather than during the quote. Name your platform when you ask, whether that’s Opera, RMS, SiteMinder, Little Hotelier, or something else, and get the answer in writing before you compare prices. It is the single most common reason a hotel phone project has to be re-scoped halfway through.
Why a phone booking is worth more than an online one
A phone booking is a direct booking, so it carries no online travel agency commission. Industry sources put major OTA commissions between 15 and 25 per cent, against roughly 4 to 5 per cent for direct acquisition. On the same room rate, an answered reservations call is worth materially more than the same booking made through a channel.
Your own commission rate is the number that matters here, and you already know it. Take your average room rate, apply your blended commission, and you have the value of a phone booking over the same booking arriving through a channel. Then, work out how many reservation calls went unanswered last month.
Most properties can’t answer that second question, which is the point. Room nights are perishable in a way almost nothing else is: an unsold Tuesday is not recoverable on Wednesday. Combine perishable inventory with an unmeasured channel, and you have the one part of hotel revenue management that runs on assumption.
The fix is not complicated. Put reservations behind a queue rather than a direct line, so a second and third caller waits instead of hanging up. Then look at call logs and history for unanswered calls by hour. Properties that do this usually find the losses clustered in two predictable windows: checkout morning, when the desk is busy with departures, and early evening, when arrivals and dinner service overlap.
Both windows are staffing problems disguised as phone problems, which is why the report matters more than the hardware. Knowing you lose 11 calls a week between 5 pm and 7 pm is an argument for an overlapping shift, for overflowing those calls to a second property in the group, or simply for putting a message on the queue that tells callers where they are. Without knowing that, the calls keep disappearing and the roster never changes.
After reception goes home
Most Australian accommodation is not staffed around the clock. After reception closes, calls need a stated greeting that separates the three reasons people ring at night: an arriving guest who can’t get in, a current guest with a problem, and someone wanting to book. Only the first two require waking anyone.
That separation is what makes after-hours cover workable for a small property. An IVR menu that offers late-arrival instructions, an urgent option that reaches the duty manager’s mobile, and a booking option that takes a message or diverts to a reservations line, handles almost everything without anyone sitting by a phone.
Two details matter more than the menu. Record the late-arrival instructions properly, because a guest standing outside a locked door at 11 pm is the single worst moment in the guest experience, and it’s entirely preventable. And make sure the urgent option genuinely reaches a person, because an emergency option that goes to voicemail is worse than no option at all.
The enquiry that pays for the system
Functions and events are the revenue line most often handled worst. A wedding, conference, or Christmas party enquiry is worth thousands, sometimes tens of thousands, and at most venues, it arrives on the main line during service and gets answered by whoever is closest.
It then sits in someone’s memory rather than a system. Nobody knows how many of those enquiries came in last month, how many were returned within a day, or how many booked elsewhere while waiting for a callback.
Giving functions their own published number and queue costs nothing and changes the economics immediately, because it makes the enquiries countable. Venues running a central booking desk across several properties get the same benefit at scale through a 3CX contact centre setup, with reporting per venue and enquiry type. A dedicated 1300 number for functions is worth considering for the same reason: it separates the traffic so you can see it.
Ring your own hotel
You do not need a project to find out whether this applies to you. You need a mobile and 20 minutes.
- Call your reservations number at 10 am on a checkout morning. Count the rings. Note whether you reach a person, a queue with a message, or a voicemail box.
- Call it again at 6 pm. This is the window most properties lose calls in, because arrivals, dinner service, and the last of the day’s admin all land together.
- Call the main line at 9 pm and pretend you cannot get in. Time how long it takes to reach someone who could actually help. If you get a voicemail box, you have found tonight’s one-star review.
- Call and ask about booking a function for 40 people. See where the call lands, and then check tomorrow whether anyone recorded that it happened.
Four calls, 20 minutes, and you will know whether your hospitality phone system is a service tool or a revenue leak. If the results are uncomfortable, that is useful information rather than a purchasing decision, and most of the fixes are configuration rather than hardware. Com2 is a certified 3CX partner working with businesses across Australia and can look at what your current 3CX phone system or existing hotel PBX is doing with those calls today. Call 1300 887 495 or request a quote today.