Hospital groups, banks and restaurant chains rarely have one waiting area. Running a separate queue system at each site means a separate set of settings per site, separate upgrades and no fair way to compare one location with another. Queue management software that supports multiple branches puts them all in one system without merging their day-to-day work. For the basics, start with what a queue management system is.
How Are Branches Set Up in One System?
The structure works like a tree, from the head office down:
- Main account: the head office holds the top-level account and can see every branch.
- Branches: each branch is its own space, with its own manager, its own team and its own data.
- Sub-branches: a branch can have sub-branches of its own, as many levels deep as the business needs, for example state, then city, then site.
- Branch users: each user is given access to their own branch's queue only.
Inside each branch, the setup is the same as for a single site: spaces such as a floor or a department, counters, a token display for the waiting area and a check-in screen. A new location is added to the tree rather than installed as a new system.

What Does Each Branch See, and What Does Head Office See?
A branch manager sees their own counters, staff, tokens and records, not a merged view of the whole group. That keeps each site's work clean and keeps each branch's records with that branch.
Head office sees every branch. Reports give daily, weekly and monthly visitor numbers with the history behind them, for each branch on its own or for the group as a whole. If the check-in screen asks for a reason for visit, those answers show what people come in for at each location, which helps plan staff and services branch by branch. The software runs in the cloud or on your own server (on-premise). In the cloud version, a regional manager can check any branch from a browser, wherever they are.
Can a Visitor Be Sent to Another Branch?
Yes. Because the branches share one system, staff can transfer a token to another branch in one tap, for example when a doctor refers a patient to a specialist at a different location. It is a single action instead of a phone call and a fresh check-in at the other end. The calling step, including transfers, is covered in how queue management software calls tokens.
What Should You Test If You Run More Than One Site?
- Adding a branch: ask what happens when a new location opens, since that is the moment a badly structured system shows itself.
- Data boundaries: confirm what one branch manager can and cannot see of another branch, and check that it matches your internal rules.
- Referrals: if you will move visitors between locations, walk through what the receiving branch sees.
- Reports: ask to see one branch's report next to the group view, in the format your managers will actually use.
For a single site, none of this applies, and you should judge the system at the counter. For a hospital group, a bank with branches across a state or a restaurant chain, the branch structure deserves more attention than any single feature, because it is the part you cannot change later without moving everything.
See how branches work in our queue management system, or book a live demo with your own branch list in hand.




