A location is a named physical site (an office, a building, a floor) that users and SIP devices are assigned to, so routing can target "everyone at the Zurich office". Each user and device has one location at a time.
Overview
A location is the place-based dimension of your tenant. Where Tags say "what kind of person" and Groups say "what team", locations say "where physically". Each user and device has one location at a time, and reassigning moves them - there is no multi-location membership.
What it does
A location does not affect callers directly. It affects which users and devices ring when a routing entity filters by location. Locations become routing-relevant when consumed by:
- Pools - both Include and Filter phases accept locations.
- Multicasts - target devices at a specific site, for example a Building A overhead page that Building B never hears.
- Call flow steps - the Dial step type can target users by location.
The Enable location as presence status toggle is opt-in per location. When on, users can select the location in the Voxbi app to show colleagues where they are working from. Use it for places people actually occupy (office, home office, customer site) and leave it off for organizational-only locations like a warehouse or server room.
See also
- Users - the primary location-bearer.
- SIP devices - the secondary location-bearer.
- Pools - the main consumer.
- Multicasts - paging by location.
- Tags - the attribute-based counterpart.
- Languages - the language-based counterpart.