It picks up on the first ring, at any hour, and answers what guests actually ask—checkout times, pet policy, whether the pool is heated, how far the airport is at six on a Friday. No queue, no hold music, no voicemail. This is the concierge and FAQ module, running your answers.
The same arrivals that fill the lobby fill the phone
The queue at the desk is four deep: a family off the Madrid flight, passports fanned out on the marble, a luggage cart still squeaking toward the lift. Behind the counter, the phone starts. Your front desk agent has a registration card half-printed and no good way to choose which guest is hers.
She picks up, because the standard says she must. The caller wants the pool hours and whether his dog can come; he asks in French, and her French runs out just past the greeting. The family at the desk watches her apologize to a phone while their room keys sit uncut.
Or she lets it ring, and the call rolls to a voicemail nobody will check until the shift turns. The caller — already booked, already paying — hangs up having learned something about the property it never meant to teach him. Both choices are defensible. A guest loses either way.
More coverage only moves the choice down the hall
The well-run property has already made the obvious fix. The PBX is staffed, the back office cross-trained to catch overflow, the answer book current, every shift briefed on hours, rates, and policies. Someone was hired for Spanish. All of it is exactly what the best operators do, done well.
It fails anyway, because the lobby and the phone draw on the same people at the same moment. The arrivals filling one are the arrivals filling the other, so demand peaks together no matter how the shifts overlap. Add a person to the phone and you have subtracted one from somewhere a guest can see. The choice never disappears; it relocates.
And no roster can promise what the caller will need. You can hire Spanish for the desk; you cannot guarantee Russian on the shift a Russian guest happens to dial, or that whoever grabs the overflow line states the pet policy as precisely as the person who wrote it. Answers that live in people arrive unevenly, and training cannot make unpredictable volume and unpredictable languages line up with a schedule. That is the structural fact under every staffing plan.
The same rush, and nobody has to choose
Now replay that arrival rush with the module on the line.
- Answered while she works The line is answered, and the agent at the desk never lifts her eyes from the family in front of her.
- The caller's own language He opens in French and the whole conversation stays there; Spanish, Russian, and more are the same call.
- Your protocol, word for word The pool hours and the pet policy come back exactly as the property approved them, because approved answers are the only answers the system gives.
- Fluent past the front door Asked what is nearby, what is still open, or how long the drive to the terminal runs, it answers like someone who knows the brand, the building, and the streets around it.
- A person when it needs one A complaint, a request that appears on no approved page, anything that asks for judgment: the system hands the call to a person the moment a person is what it needs, on paths your property sets.
- The queue never knew The family gets their keys, the caller gets his answer, and nobody behind the desk apologized to either one.
It answers from your protocols, or not at all
What answers the phone on this page is the concierge and FAQ module: the part of the system that takes direct guest questions about hours, policies, amenities, directions, the property, and the area around it, and answers them from material the property has approved. It runs on your protocols and nothing else; where no approved answer exists, it does not improvise, it brings in your staff.
What it needs from the property is what a good shift briefing already contains: your policies, your hours, your standards, and the corrections you would give a new hire. It can be purchased entirely on its own; the PBX stays as it is, no other module is required, and nothing else about the operation changes.
- Answers the property's phone twenty-four hours a day, seven days a week, in season and out.
- Gives only answers the property has approved, under the property's protocols.
- Converses in the caller's own language, with Spanish, French, and Russian among them.
- Transfers to staff on escalation paths the property defines.
- Stands alone: it can be bought without any other module, with no change to existing systems.
- Holds under unpredictable volume: calls that arrive together are all answered, and none rolls to voicemail.
The phone stopped depending on who picks up
The phone behind my desk used to force a choice: the guest standing in the lobby or the guest on the line. Someone lost every time, and it was usually the caller, rolled to voicemail, often in a language nobody on shift spoke anyway. Now every call is answered, in the caller's own language, with answers I signed off on, and anything that needs judgment comes straight to my staff. Nothing else changed — same phone system, same team, same standards. Trying it risked nothing: one thing switched on, and if it hadn't held up, switched off, with the property exactly where it started.