On this page
For an Australian business with 3–20 handsets, the right multi-site phone system is not the biggest platform available. It is a system that keeps numbers, users, call handling and administration manageable as the business adds offices without forcing you into a 500-seat carrier environment.
A practical enterprise phone system in Australia should give each site a consistent customer experience while allowing the business to control costs, access and future growth. The focus should be on the number of people using the system, how offices operate, and what the business may need next—not on buying features that will never be used.
Is an enterprise phone system too much for a business with 3 to 20 handsets?
Usually, “enterprise” describes the way the system is managed rather than the size of the business using it. A small organisation can need enterprise-style control across two or three locations without needing a platform designed for hundreds of agents.
For a growing Australian SMB, the useful requirements are normally straightforward:
The risk is choosing a product because it has a long feature list. A system may advertise contact-centre functions, workforce management and complex integrations, but those features can add cost and administration without improving a 10-handset business.
NexGen is not positioned here as a 500-seat carrier platform. This guide is aimed at Australian businesses that are moving beyond a single site and need a more structured system while remaining within a practical 3–20 handset environment.
What changes when a business moves from one site to multiple offices?
The main change is governance: someone must decide how numbers, users, call flows and permissions work across the whole business. Without that structure, each office can gradually develop different settings, different answering habits and different expectations for customers.
A multi-site phone system should therefore be planned around the business rather than around individual offices. Before requesting proposals, write down:
The mechanics of connecting sites and supporting inter-site dialling belong in the [guide to how a multi-site phone system connects offices]( /phone-systems/how-does-a-multi-site-phone-system-connect-offices-and-support-inter-site-dialling/). The important point here is to define the operating model first, then select a system that can support it.
A useful distinction is between site requirements and business-wide requirements. A branch may need a local number and a small ring group, while head office may need central visibility, administration and reporting.
Which enterprise phone system features matter most at 3 to 20 handsets?
The most valuable enterprise phone system features for a small multi-site business are the ones that reduce confusion as people, numbers and locations increase. The system should be easy enough for an office manager to understand but structured enough to avoid every change becoming a provider support request.
| Requirement | Why it matters across multiple sites | What to ask the provider |
|---|---|---|
| Central administration | Keeps users, numbers and settings consistent | Can one administrator manage every site? |
| Site-level permissions | Lets branch managers manage local settings without seeing everything | Can access be limited by location or role? |
| Auto attendant | Gives callers a predictable first point of contact | Can menus vary by site, time or public holiday? |
| Ring groups | Helps distribute calls among a small local team | Can calls overflow to another group or location? |
| Business hours and holiday rules | Prevents calls reaching unattended offices | Who can change schedules and how are changes logged? |
| Voicemail management | Reduces missed messages and unclear ownership | Can voicemail be assigned to a person, team or site? |
| Mobile and desktop access | Supports staff who move between offices or work away from a desk | Which devices and operating systems are supported? |
| Call reporting | Shows where calls are being missed or delayed | Which reports are included, and how often are they available? |
| Number management | Helps preserve existing numbers and plan new ones | Can local, 13, 1300 and 1800 numbers be supported or ported? |
| User lifecycle controls | Makes onboarding and offboarding more reliable | How quickly can a user be added, changed or removed? |
Do not assume that every feature is included in every plan. Ask for the exact licence, handset, setup, number and support costs attached to each requirement.
For example, a system may offer call recording but charge separately for storage, administration or access. If calls contain personal information, also ask how recordings are stored, who can access them, how long they are retained and how they can be deleted. The OAIC Australian Privacy Principles guidance explains that Australian organisations need to consider how personal information is collected, used, disclosed and secured. (oaic.gov.au)
How should you size a phone system for multiple offices?
Start with active users and call behaviour, not just the number of physical handsets. A business with 12 handsets may have fewer active callers than a business with six sales staff, a reception number and regular simultaneous inbound calls.
Use three counts:
Then add a growth allowance based on a realistic business plan. Do not pay for an unlimited future scenario if the business has no firm plan to expand, but do not design a system that becomes difficult to administer as soon as one new office opens.
| Business position | Sensible planning question | Common mistake |
|---|---|---|
| 3–6 handsets across two sites | Can the system keep administration simple? | Buying a complex platform because it is labelled enterprise |
| 7–12 handsets across two or three sites | Can calls be shared or redirected without confusion? | Giving each site completely separate rules |
| 13–20 handsets across several sites | Can permissions, reporting and onboarding be managed centrally? | Treating every office as an isolated phone system |
| Approaching 20 handsets | What will the next stage require? | Waiting until the system is difficult to change |
Businesses approaching 20–50 seats have a different sizing conversation involving capacity, user types and more detailed planning. Use the guide to sizing a 20–50 seat multi-site phone system rather than applying a larger-business design to a small team.
The provider should be able to explain what happens when you add one user, one handset or one location. If the answer is unclear, the system may not be suitable for a growing office environment.
What should you ask about internet, continuity and support?
A cloud phone system depends on more than the phone application. The business should understand the internet connection at each site, the local network, power arrangements, device configuration and the provider’s response process before moving essential numbers.
Ask the provider:
Do not turn an unconfirmed target into a promise. Unless the provider documents a specific service level, treat uptime, restoration times and service credits as questions for the proposal—not assumptions.
The Australian Cyber Security Centre’s cloud security guidance recommends that small businesses consider security controls, access, authentication and the responsibilities shared with cloud providers. Its detailed cloud guidance also encourages organisations to ask vendors direct questions about availability, security incidents and compensation rather than relying on generic assurances. (cyber.gov.au)
NexGen states that it is ISO 27001 Certified and maintains offices in NSW, Queensland, Victoria, Western Australia and South Australia. Those locations may be relevant when comparing support coverage, but you should still ask for the service details that apply to your proposed system and contract. (nexgen.com.au)
How can you compare enterprise VoIP providers in Australia?
Compare providers against the same written requirements, not against different sales demonstrations. This makes it easier to see whether a proposal solves the actual multi-site problem or simply includes a large catalogue of features.
| Comparison area | Minimum question | Warning sign |
|---|---|---|
| Fit for business size | Is the service designed for a 3–20 handset business? | The proposal is built around hundreds of users |
| Administration | Who can manage users and site settings? | Every minor change requires a paid request |
| Site growth | How is a new office added? | No clear process or lead time |
| Numbers | Can current numbers be ported and new numbers ordered? | Porting is treated as an afterthought |
| Hardware | Which handsets are supported and who configures them? | Hardware compatibility is unclear |
| Applications | Can staff use approved desktop or mobile options? | Apps are mentioned without support boundaries |
| Security | What controls, access rules and audit information are documented? | “Secure” is the only answer |
| Continuity | What is the plan if internet, power or provider service fails? | No documented fallback |
| Support | What are the support hours and written commitments? | Informal promises are not reflected in the contract |
| Exit | What happens to numbers, recordings and configuration if you leave? | No clear offboarding process |
A good enterprise VoIP Australia proposal should be specific about what is included, what is optional and what depends on another service. Ask for the proposal in a format an office manager can use: users, sites, numbers, handsets, applications, support and assumptions.
You can also ask the provider to separate “needed now” from “possible later”. This helps prevent a small business from paying for contact-centre functionality before it has the call volume or workflow to justify it.
When does a multi-site phone system become a contact centre?
A business may be ready for contact-centre capabilities when calls are handled by a defined service team rather than simply answered by staff in different offices. Indicators include formal queues, service-level measurement, supervisor monitoring, detailed interaction records and dedicated customer-service workflows.
That does not mean every business with multiple sites needs a contact centre. If you mainly need reliable answering, sensible routing, voicemail and visibility between a small number of offices, a well-configured business phone system may be more appropriate.
For the boundary between a standard phone system and a contact-centre platform, use the guide to when a standard phone system becomes a contact centre in Australia.
What is the practical next step for choosing a multi-site phone system?
Write a one-page requirements brief before speaking to providers. Include each site, handset count, active users, existing numbers, opening hours, call-handling preferences, expected growth and the support questions that must be answered in writing.
Then compare proposals on fit, administration and continuity—not just price per handset. If your requirements are spread across multiple sites, put your multi-site requirements to a person at NexGen so the discussion can focus on the way your offices actually operate.
Frequently asked questions about enterprise phone systems in Australia
Can a small business use an enterprise phone system?
Yes. A business with 3–20 handsets may need enterprise-style administration across multiple sites without needing a platform built for hundreds of seats.
Is VoIP suitable for businesses with more than one office?
It can be, provided each site has suitable connectivity, a documented fallback plan and a provider that can manage users, numbers and support across locations. Confirm those assumptions before signing.
Should every office have its own phone number?
Not necessarily. Use separate local numbers where they support customer access or branch operations, and use a shared main number where central answering provides a simpler experience.
What should I ask an Australian phone-system provider first?
Ask how the system will be sized for your current handsets, how a new site will be added, how numbers will be ported, what continuity options exist and which service commitments are written into the contract.
Talk to Nexgen about your phone system
Get a like-for-like comparison against a managed cloud phone service.