An on-premises business phone system runs on a server at your premises or on servers under your control. It can still use modern IP technology for external calls.
Keep control of your business phone system where your operation needs it.
Solutions · Business Communications · Business Telephony · On-Premises
When an on-premises system can make sense
It may suit organisations that want greater control over their phone system, have particular resilience or integration requirements, or want to retain more of their existing setup rather than depend entirely on a third-party hosted platform.
Operationally relevant use cases
It may be particularly relevant where reliable internal calling is important, including hospitality businesses, larger retail premises, shop-front businesses with associated warehouse space and warehouse operations.
More control, with more responsibility
Trade-offs
Hardware, software updates, maintenance, backups, power, network readiness and resilience must all be considered. Additional costs may arise for maintenance, software assurance, engineer visits, upgrades and support services.
Potential benefits
The system can be designed around the organisation's operating requirements rather than a standard hosted-service configuration. Depending on the design, this may provide greater control over settings, equipment, integrations and resilience arrangements.
Working beyond a fixed desk
The precise capabilities depend on the selected system, applications and configuration and must be confirmed during design.
- Physical handsets: desk, conference and cordless phones (DECT)
- Mobile app
- Softphone on desktop or laptop PC
- Microsoft Teams Integration
Design resilience around the whole service
-
Phone-system server or appliance
-
Electrical power and battery backup
-
Local network
-
Internet connection
-
External telephone service
-
Supported handsets and devices
-
Applications and virtualisation platform where used
-
Failover behaviour when a component is unavailable
Integrations and existing equipment
Supported applications may extend the phone system with Microsoft Teams integration, mobile and browser-based calling, CRM or ERP integration, call recording, wallboards and other operational tools. Each integration must be checked against the customer's systems, versions, licences and requirements.
Existing numbers, handsets and legacy line-connected services, including lift alarm lines, telecare, warden call systems, personal triggers, monitoring services, alarm signalling and older fax equipment, should be reviewed before migration. Specialist services such as BT Redcare or equivalents must not be assumed to work over a replacement voice service.
Implementation and support
For supported on-premises deployments, FVC Solutions can provide customer-facing first-line support, with eligible issues escalated to the relevant technology supplier where an applicable supplier support entitlement is in place. The applicable proposal or support agreement defines the final service level and responsibilities.
Emergency calling
Business telephony services may depend on mains power, internet connectivity, network equipment and correctly configured telephone services.
Calls to 999 and 112 should be available from appropriately configured services, but emergency-calling behaviour can vary depending on the telephone system, provider, device and location.
If phones, applications or users move between sites or are used remotely, the location information associated with an emergency call may not reflect the caller’s actual location. Callers should therefore clearly state their location and provide a reliable callback number.
Customers should keep site and service-location information up to date and consider how emergency calls will be made during a power, internet or equipment failure.
In an emergency, call 999 or 112. Do not contact FVC Solutions instead of the emergency services.
Is on-premises right for your operation?
We can assess your existing environment, resilience needs, integrations, working patterns and commercial priorities before recommending an architecture.