Inheritance you can see
Every line, group and device shows which of its values came from the site and which were overridden, with one control to revert to the site default. You should never have to guess why a phone is in the wrong time zone.
Stage in a call · FOUNDATION
Several offices, one system, settings that inherit.
A site is an office: an address, a time zone, a set of business hours, a calling policy. Everything below it inherits those, so setting up the second location is mostly a matter of saying where it is.
What the call does
- inCall to the branch number
- step 1Branch hours
- answeredBranch team
What a site carries
Set once per office, used everywhere underneath.
- Street address, which is what a 911 dispatcher is handed
- Time zone and language
- Business hours and the holiday set
- Outbound caller ID
- Calling permissions — what this office may dial
Extensions still work across sites
Dialling an extension reaches that person whichever office they belong to. Sites organise settings; they do not partition the dial plan.
Two modes
Simple by default, detailed when you ask
Most people never open the second column. It is one click away rather than spread across the first.
Simple mode
- Add a site by name and address; everything else has a sensible default
- Move a line to another site and watch which settings change before you confirm
Advanced mode
- Per-site dial-plan prefixes
- Site-level toll-fraud matrices with per-line overrides
Where multi-location stops
- A site is a place, not a permission boundary. If one office must not see another office's call records, that is a question about roles, and roles are account-wide.
- Site count is bounded by plan. The plans page states the bounds.