HOSPITALITY USE CASE

Managers Across Multiple Properties

A regional general manager splits the week across three hotels. So does the group's head of revenue, its cluster engineer and whoever is covering a vacancy this month. Each property has its own switchboard, its own extension range and, often, its own handset sitting on a desk the manager occupies on Tuesdays.

The result is a person with several numbers, none of which reliably reaches them. This use case sets out what changes when one business line follows the role instead.

At-a-Glance

Sector: Hospitality
Department: Regional and cluster management
Setting: Group or estate of several properties
Deployment: Business line on staff-owned handsets
Platform: The group's existing UC platform

Solution Highlights

One business number across every property
No SIM swapping between sites
Calls on the group's platform record
The number belongs to the role

The Challenge

Multiple numbers is not a tidiness problem, it is a reachability one. A supplier tries the number they were given eighteen months ago, a duty manager tries the desk extension at the property the manager is not in today, and both give up and use a personal mobile that somebody found.

That personal number then becomes the working one. It appears in supplier records, in guest correspondence and on a contract, and it belongs to an individual rather than the group. When the manager moves on, the relationships attached to it move with them or simply stop.

The Solution

The manager carries one business line on their own handset, delivered by eSIM. It is an extension of the group's phone system rather than of any one property, so it reaches them on Tuesday at one hotel and on Thursday at another without anything being changed.

Inbound, a colleague at any site dials the same internal extension and a supplier dials the same external number, whichever property the manager is standing in. Outbound, the group's number is what the recipient sees.

Because the line is issued centrally, cover arrangements become routing rather than administration. A manager on leave, a vacancy being covered across two sites, or a new cluster role all resolve to a change in the platform rather than an email telling everybody a new number.

What Changes

The first change is that there is one number to know. Colleagues, suppliers and owners stop keeping a list and stop guessing which site to try.

The second is that the number belongs to the group. Supplier records and correspondence point at something the business controls, so a departure is a routing change rather than a set of relationships walking out of the door.

The third is visibility. Calls made across the estate run through the group's platform, so activity at cluster level is something that can be looked at rather than something that happened on somebody's own phone.

Key Changes

One number across every property
Suppliers hold a number the group owns
Cover arranged by routing, not by email
Cluster call activity visible centrally

Assessment

Nine questions about your own group. The ones you can't answer are the ones worth looking into.

How it works today

How many numbers does a regional manager have across the estate?
Which one do suppliers actually use?
How does a duty manager reach them on a day they are elsewhere?

What it is costing

How many desk extensions sit unused at properties they visit?
How much cluster call activity happens on personal mobiles?
How much of it appears in group reporting?

What would change

What happens to those relationships when the manager moves on?
How is cover arranged when they are on leave?
Which cluster role would you start with?

A manager who works across several properties is reachable on whichever number the caller happens to have, which in practice means a personal mobile. One business line that follows the role puts them back inside the group's phone system without giving them a second device to carry.

It also means the number, and the relationships attached to it, stay with the business.

Looking Ahead

List the numbers per managerConsolidate one cluster roleUpdate supplier recordsRetire unused extensions

Learn More

Visit tango-networks.com or contact your local Tango Extend partner
for a personalised demonstration.

Browse all resources

Version 1.0 · August 2026