Extensions & permissions
Define users, dialing permissions, groups and responsible administrators.
BUSINESS COMMUNICATIONS
IP PBX systems built around your business
Plan internal extensions, external calling and branch connections before choosing the platform and licenses.
DESIGNED AROUND YOUR OPERATION
From a ring to the right person
IVR & call routing
Plan welcome messages, working hours, ring groups and fallback destinations.
Branches & remote users
Review secure connectivity, supported endpoints and network requirements.
Voicemail & recording
Confirm availability, storage limits, access permissions and retention settings.
A CLEAR BASIS FOR COMPARISON
Choose your deployment approach
| Approach | What to review | Operating responsibility |
|---|---|---|
| On-premises appliance | Hardware capacity, power and local network | On-site management, backup and maintenance |
| Software platform | Supported server or virtual machine, licenses and resources | System updates, hosting and recovery |
| Hosted service | Provider availability, connectivity, subscription and data location | Agreed responsibilities with the service provider |
Size the system using real requirements
- Users are not the same as concurrent calls: specify both
- Confirm the type and number of external lines or SIP trunks
- Check expansion limits, recording storage and license renewal terms
- Include switches, PoE, cabling and backup power in the scope
Available features depend on the selected model, software edition, licenses and configuration. Confirm them in the quotation.
Read the PBX selection guideBEFORE YOU DECIDE
Your questions, answered
Can existing phones be reused?
Check the exact model, protocol, firmware and supported provisioning method. SIP support alone does not guarantee every feature.
Are external lines included?
External numbers and calling services require a suitable provider agreement. Confirm supply and configuration responsibilities in the quotation.
A CLEARER PROJECT BRIEF
Tell us how your business communicates
Share your user counts, branch details and requirements so we can discuss the right scope.
PRACTICAL ANSWERS
Business PBX questions
How do I estimate the size of a business phone system?
Separate the number of extensions from the number of simultaneous external calls. Also list sites, users, call routing and growth needs so the proposed system and licenses can be checked against the actual workload.
Should the PBX be on-site or hosted?
Compare administration responsibilities, connectivity, continuity needs and the available support arrangement. Ask for a clear description of what is hosted, what remains at your site, and any recurring licenses or service charges.
Can existing business phones be reused?
Provide the exact phone models and firmware details where available. Check the proposed PBX’s supported device list and required features, then test a representative device before assuming every existing phone can be retained.
Are telephone numbers and call service included with the PBX?
Treat the PBX equipment or software and the telephone service as separate scope items unless the quotation explicitly combines them. Confirm responsibility for numbers, external calling capacity, provider coordination and ongoing charges.
How should business-hours and after-hours calls be handled?
Write the intended call flow before configuration: greetings, departments, fallback destinations and closing-time behavior. Review the wording in the required languages and test each route with a real representative call.
What should be included in a PBX handover?
Agree on the extension list, call-flow diagram, authorized administrator access and configuration backup process. Test the required incoming and outgoing calls, transfers and fallback paths, and document any functions excluded from the scope.