In hospitality the phone is not a channel, it is a guest. The question is not whether to answer it but what a good answer consists of when the floor is full.
Sort calls into three buckets
- Must reach a person: complaints, anything about safety or accessibility, anything involving a guest currently on site with a problem.
- Should be handled consistently: availability, bookings, opening hours, prices, policies, directions, parking.
- Should be captured, not solved: supplier calls, callbacks, anything requiring a decision from a manager who is not there.
Most teams never write this down, so every call gets treated as urgent — which means the genuinely urgent ones queue behind the routine.
For the second bucket, define the wording
Consistency is the whole point. A guest who is told two different cancellation policies by two members of staff has been given a reason to argue. Write each answer once and make it the only version in use.
Make the handover fast and named
For the first bucket, a caller should reach a person quickly and only once. Decide per shift who that is, and make sure the route to them works when the desk is busy — that is exactly when it will be tested.
Insist every call leaves a record
Who called, what they wanted, what was agreed. Without it, the handover between shifts is a conversation someone forgets to have. With it, the next person opens the record and knows.
Check the after-hours behaviour
Guests ring when it occurs to them, which is frequently after your desk closes. Decide what happens to those calls: an honest answer about opening times and a captured request is worth far more than a ringing tone, and costs a guest nothing to receive.
Review it monthly
Read a sample of calls once a month with the three buckets in front of you. If routine calls are reaching people and urgent calls are not, the problem is the routing, not the team.