Back to blog

One organization, several sites: plan numbering and local call routing

Standardize extensions and administration while preserving branch hours, destinations and ownership.

By Telfron Editorial Team · Updated 8 October 2026 · 4 min read

Three office sites linked by illustrated communication paths.
Original AI-generated editorial illustration.

A multi-site phone system should feel coherent to employees and local to callers. Central administration can simplify maintenance, but branch names, opening hours and destination teams still need careful design. A shared platform does not remove local operating differences.

Choose a numbering convention

Reserve extension ranges for sites or roles and leave space for growth. Avoid overlapping ranges that make directory lookup ambiguous. Decide whether a staff member keeps the same extension when moving between offices. Document shared destinations, such as a central service desk, alongside local reception extensions.

Keep public numbers tied to context

When someone calls a branch number, preserve the branch identity through the menu, queue and any AI answer. A shared support team should be able to recognize which location the caller intended. Make a deliberate decision about overflow to another site rather than letting a default rule send the call somewhere unexpected.

Use local hours and exceptions

Branches may observe different time zones, weekends or holiday closures. Give each location an owner who maintains those schedules. Test time boundaries and temporary closures. If central staff cover a closed branch, make the greeting explain the service available and avoid implying that the local office is open.

Define administrative boundaries

Separate organization-wide settings from changes a branch can make. Reception staff may need to update availability without altering trunk or security settings. Review who approves new extensions, device assignments and call-flow changes. Maintain a change record so a routing fault can be traced to a recent modification.

Test inter-site and failure scenarios

Rehearse a call between branches, a transfer to an unavailable site and a public call while one location loses connectivity. Verify how the chosen deployment reaches each branch. In Telfron, review multi-site routing, branch-aware AI and administration together; capacity and continuity should be validated against the actual infrastructure.

Worked example: three branches with different schedules

An illustrative organization operates a head office and two branches. The numbering design reserves 2xx for head office, 3xx for the north branch and 4xx for the south branch, with spare capacity in each range. These are example ranges, not a Telfron requirement. Shared functions such as central support have clearly documented destinations outside the local reception flow.

A public call to the north branch retains that branch context if central support answers it. On a local holiday, the north-branch greeting and destination change according to its schedule while the other sites remain open. The acceptance test includes that exact situation so the shared system does not erase local differences.

Decide what follows a person and what follows a location

Some extensions belong to employees who move between sites; others belong to fixed roles such as reception or a loading bay. Record that distinction in the directory. When someone transfers branches, update their team membership and access without accidentally changing a location-specific destination that other callers rely on.

Review outbound identity as part of the move. Decide whether the person should present a branch number or a central business number, and confirm the carrier behaviour. Make a controlled test call rather than relying only on what the settings appear to specify. Directory and caller-ID policies should reflect the same organization structure.

Rehearse a branch outage

Choose a site and test the agreed scenario in a controlled window. Observe what happens to public calls for that branch, inter-site transfers and remote access. If another site provides cover, confirm that its staff can recognize the branch and offer the service available. Do not imply the affected office is open if it cannot serve walk-in customers.

Assign an owner for restoring the local route and checking schedules afterward. Keep each branch’s contacts, network dependencies and required endpoints in the operations inventory. A central view helps administration, but recovery still depends on knowing which local services and people are affected.

Illustrative numbering and responsibility plan

ScopeExample numberingOperational owner
Head office2xx rangeHead-office administrator
North branch3xx rangeLocal schedule and reception owner
South branch4xx rangeLocal schedule and reception owner
Shared supportDocumented common destinationCentral service lead
Fixed facility endpointLocation-specific assignmentSite facilities contact

Implementation checklist

  • Reserve extension ranges with room to grow.
  • Preserve branch identity through transfers and AI answers.
  • Assign local schedule owners.
  • Test inter-site calls and an unavailable branch.

Frequently asked questions

Should every site use the same greeting?

Use common branding where helpful, while preserving the branch’s hours, services and destinations. The caller should understand which location they reached.

Can branches manage their own settings?

Define the required permissions and validate them in the selected deployment. Keep local availability changes separate from organization-wide trunk and security administration.

Explore Telfron