How to Set Up a Hosted PBX for Remote Teams

A phone system built around one office becomes harder to support when employees work across homes, branches, and time zones. Aging hardware adds maintenance costs, while carrier network changes can force decisions about services that still work.

Moving to a hosted PBX gives remote employees access to business calling without depending on the office PBX. A successful migration starts with auditing call flows, checking remote connections, and testing the new system before moving production numbers.

Here’s how to plan and set up hosted PBX for remote teams, from initial requirements through cutover.

Why Hosted PBX Works for Remote Teams

Hosted PBX moves call management into a provider’s infrastructure. Employees connect through supported devices and apps, while administrators manage users and routing centrally.

Work From Any Device, Anywhere

Desktop, mobile, and browser apps can give employees access to their business extensions without routing every call through the office network. Confirm which apps the provider supports and whether corporate security policies require a VPN.

Find-me/follow-me rules can ring a desk phone, laptop, or mobile destination in sequence or together. Test those rules so a personal voicemail greeting never captures a business call unexpectedly.

One Business Number and Caller ID Across Every Location

Configure approved company numbers as outbound caller ID so employees can call customers without exposing personal numbers. Check caller ID during testing, since receiving carriers influence how names appear.

Presence indicators and shared ring groups help colleagues see availability and route calls to someone who can answer.

Voice, Video, and Messaging in One Platform

UCaaS platforms can combine calling, chat, and video meetings. Sangoma’s business collaboration tools include TeamHub, which brings telephony, SMS, video meetings, chat, and an operator console into one interface.

When evaluating platforms, also check voicemail-to-email and transcription availability. Those features let employees review messages between meetings without dialing into a voicemail box.

Add Users and Locations in Minutes

Once licenses, templates, and devices are ready, creating an extension can take minutes through an admin portal. Number porting and site preparation still need separate lead time.

Standardize department settings before expanding. A repeatable setup makes it easier to scale a business phone system across locations without recreating routing rules at every site.

No On-Site Hardware to Maintain or Replace

The provider maintains the hosted platform, including its infrastructure and software updates. Your team still manages endpoints, local networks, permissions, and user access.

Call reports and queue dashboards also help managers identify missed calls and overloaded teams. If recording is required, confirm licensing, access controls, and retention settings before enabling it.

What You Need Before Setting Up a Hosted PBX

Sort out network readiness, user devices, analog equipment, and ownership before scheduling the migration.

Network Requirements at the Office and at Home

Size office connectivity for peak concurrent calls alongside ordinary business traffic. Configure quality of service on managed network equipment to prioritize voice during congestion. Local QoS cannot control congestion throughout the public internet.

Give remote employees a short readiness checklist:

• Bandwidth: Start with roughly 100 Kbps in each direction per concurrent G.711 call, then add headroom. Confirm the provider’s requirements for its codecs and apps.
• Latency: Target less than 150 milliseconds of one-way delay.
• Jitter: Target less than 30 milliseconds.
• Packet loss: Aim for near zero and keep loss below 1%.
• Connection: Prefer Ethernet. Test Wi-Fi from the actual workspace during busy household hours.
• Router settings: Check the provider’s guidance on disabling SIP ALG, which can interfere with SIP traffic.

The quality targets align with Cisco’s voice network guidance; actual bandwidth depends on codec and packet overhead, as its bandwidth calculations explain.

A download speed test alone cannot establish readiness. Test calls while other household members use the connection, especially during uploads.

The Right Devices for Each Type of User

Choose devices around daily work.

User role	Practical starting setup	What to verify
Receptionist	Operator console, headset, optional desk phone	Presence, transfers, and shared-line handling
Home-based employee	Desktop softphone and USB headset	Audio quality and incoming-call notifications
Field salesperson	Mobile app on a managed or approved personal phone	Cellular performance and business caller ID
Shared office workstation	Supported desk phone	Shared access and emergency location

For bring-your-own-device arrangements, define supported operating systems, screen-lock requirements, and how business access is removed.

Provide approved headsets. Laptop speakers and built-in microphones can introduce echo and pick up household noise.

A Plan for Legacy Analog Endpoints

Inventory fax machines, alarm dialers, elevator phones, door entry systems, and paging equipment separately from employee extensions.

Fax may move to an online service or a supported analog telephone adapter. Paging and door entry may need compatible gateways or replacement interfaces.

Alarm and elevator connections require review with the equipment vendor and relevant authority. An ATA alone does not establish suitability for life-safety use. Evaluate approved cellular POTS replacement, backup power, or a retained compatible service before disconnecting anything.

An Owner and a Budget

Name one person responsible for the rollout and ongoing administration, plus a backup administrator.

Budget for subscriptions, devices, headsets, onboarding, possible porting fees, network improvements, and temporary overlap with the old service. Include recording storage or advanced queue features where needed. Small business hosted PBX projects can exceed expectations when shared devices and add-ons are missing from the initial quote.

Setting Up a Hosted PBX for Remote Teams Step by Step

For teams leaving a legacy PBX, work from audit to pilot to number porting. Keep the existing service available until the replacement has passed practical tests.

Step 1: Audit Your Phone System and Call Flows

Export numbers, extensions, hunt groups, auto attendants, queues, voicemail boxes, and forwarding rules. Identify each number’s carrier account and business owner.

Ask department leads which settings still serve a purpose. An old menu option may route to an employee who left years ago.

Draw the required call flows, including after-hours and unanswered-call paths. Record existing greetings and save any voicemail or recordings the business needs to retain.

Step 2: Compare Hosted PBX Providers and Choose a Platform

Use the audit from Step 1 to give each provider the same requirements: users, locations, call flows, and features your team relies on. Ask for a demonstration and an itemized quote covering six areas:

• Remote apps: Have the provider demonstrate transfers, shared queues, and business caller ID on the desktop and mobile apps employees will actually use.
• E911 location handling: Ask how the platform updates a remote worker’s emergency location when they change networks, including what requires manual input.
• Porting support: Confirm that your numbers can transfer, who handles rejected requests, and whether support will be available during cutover.
• Uptime commitments: Read the SLA for the proposed service. Check which outages count, what exclusions apply, and how service credits are claimed.
• Security: Verify MFA availability, administrator permissions, and controls for restricting international calls and detecting unusual usage.
• Per-user pricing: Request a total for your actual setup, including queues, recording, devices, onboarding, and any minimum license commitment.

When choosing a business phone system, make the demonstrated workflows and complete cost part of the decision. Confirm required features are included in the quoted plan before signing.

Step 3: Set Up Users and Extensions

Create individual accounts, assign extensions, and group users by department. Add temporary numbers for testing without disturbing published business numbers.

Configure voicemail greetings, notification destinations, directory entries, and outbound caller ID. Decide who owns shared voicemail boxes and how messages get assigned.

Use role templates to keep settings consistent. Check license availability before inviting users, and restrict administrative access to employees who need it.

Step 4: Configure Call Routing for a Distributed Team

Build the auto attendant around caller needs, then connect each option to the right queue or ring group. Include employees across locations where appropriate.

Set business hours and holiday calendars explicitly. A support queue covering several regions needs a defined time zone and a clear handoff between teams.

For example, morning calls might reach the East Coast team first, then overflow to available West Coast staff. Once both teams close, callers should hear the correct greeting and reach a monitored voicemail box.

Configure maximum wait times, unanswered-call handling, and behavior when every agent is unavailable. Presence status and queue membership may operate separately, so test both.

Document who supports routing when problems span locations. Clear ownership supports reliable communications across multiple sites.

Step 5: Register Remote Workers’ Emergency Locations

Use the provider’s workflow to associate each supported endpoint or user with the appropriate emergency location. Include apartment, suite, floor, or other details needed to find the caller.

Verify how location updates work when employees move. Some systems recognize configured networks; others prompt users to enter an address. Ask what happens on an unfamiliar network and how emergency callbacks reach the caller.

Teach employees the update process before activation. Use the provider’s designated verification method, and coordinate any live emergency-call testing in advance.

Step 6: Provision Devices and Apps Securely

Use supported provisioning links, QR codes, or automated device provisioning so remote staff can activate equipment without an on-site visit.

Assign unique credentials and enable MFA for administrators and users wherever supported. Avoid shared SIP passwords and limit account privileges.

Update device firmware and apps, then verify supported encryption settings with the provider. Treat provisioning links as sensitive information. Give employees clear activation instructions and a support contact for failed sign-ins or registration.

Step 7: Run a Pilot and Test Call Quality

Start with temporary numbers, one representative queue, and employees using different home networks and devices. Include the receptionist or another frequent transfer user.

Test inbound and outbound calls, transfers, hold, voicemail, keypad menus, caller ID, and calls lasting longer than a quick audio check. Repeat tests during busy periods and check app behavior when a laptop sleeps or a mobile screen locks.

Keep the old system operational during the pilot. Record problems by user, device, network, and call time so support can investigate specific examples.

Step 8: Train Your Team and Set Communication Norms

Run short remote training sessions around everyday tasks: answering, transferring, checking voicemail, joining queues, and updating emergency locations.

Define when employees should mark themselves busy, leave a queue, or hand work to another team. Explain who responds to shared voicemail and how urgent missed calls get escalated.

Let employees practice while both systems remain available. Publish a one-page reference with support details and outage procedures.

Step 9: Port Numbers and Cut Over in Phases

Begin porting preparation early, but schedule activation after testing and training.

For the local number portability request, gather the signed authorization and carrier records the new provider requires. Account names, service addresses, account numbers, billing telephone numbers, and applicable PINs must match the losing carrier’s records. 

Use a phased cutover where number groupings and call flows allow it. Move a smaller department first, then expand after validation. Ask whether partial porting affects remaining numbers or bundled services.

Do not cancel the existing service before the port completes. After activation, test every ported number from external networks.

A completed port cannot necessarily be reversed immediately. Arrange fallback routing and escalation contacts with the new provider before cutover.

Step 10: Monitor and Decommission the Legacy PBX

Review failed calls, missed calls, queue waits, and user feedback closely during the first few weeks. Compare findings across locations to identify recurring network or routing problems.

Keep a shared issue log with an owner for each unresolved item.

Once service is stable, confirm that analog devices and retained services still work. Export required records, remove old forwarding rules, and cancel only the services approved for retirement. Reuse compatible phones after secure reprovisioning, or wipe and retire them. Revoke old credentials and remove unnecessary network access.

Common Challenges and How to Solve Them

Remote deployments introduce different home networks and more locations to manage. Most problems become easier to isolate when the rollout includes documented settings, a pilot, and named support owners.

Downtime During Migration

Porting before testing exposes the whole business to unresolved problems. Use temporary numbers for the pilot in Step 7, then move production numbers after the call flows work.

Copying every old setting creates another risk: hidden forwarding rules and unused queues survive into the new system. Use the audit in Step 1 to simplify routing.

Forgotten analog connections can fail when an old account closes. Review the analog inventory before approving cancellation.

Maintain separate contingency plans for the pilot and the completed port. Returning pilot users to the old system may be straightforward; restoring service after porting usually requires routing changes through the new provider.

Call Quality on Home Networks

Start troubleshooting with the symptom and a specific call example. Sangoma’s guide to VoIP audio issues describes how network and media-path problems affect audio.

Symptom	Likely causes	First checks
Choppy or robotic audio	Packet loss, jitter, congested uploads	Try Ethernet, pause large uploads, and measure quality during calls
One-way or missing audio	NAT, firewall, or SIP ALG interference	Follow provider firewall guidance and check SIP ALG
Calls dropping	Wi-Fi instability, session timeouts, app power settings	Compare wired calls and check device logs
Echo	Speaker audio feeding into a microphone	Use a headset and verify audio devices
Noticeable delay	Network latency or an indirect traffic path	Compare connections and review VPN routing with IT

Follow instructions for the selected service rather than making broad firewall changes.

Capture timestamps, affected numbers, and whether one or both callers heard the problem. Support teams can match those details to call records.

Internet Outages at the Office or at Home

Configure unanswered or unreachable calls to move to another employee, queue, or approved external destination. Test the fallback by deliberately disconnecting a pilot device.

A mobile app needs a working data connection. During a home broadband outage, cellular data or a tested hotspot may provide an alternative. A power outage may also disable the modem and router unless backup power is available.

Confirm whether switching connections preserves an active call; do not assume it will.

Review the provider’s SLA carefully. Platform availability does not guarantee that every employee’s ISP, Wi-Fi network, or device remains available.

Emergency Calling for Remote Workers

A softphone can travel while its registered address stays behind. Assigning the headquarters address to every remote extension can therefore send responders to the wrong location.

For covered multi-line telephone systems, Kari’s Law addresses direct 911 dialing without an outside-line prefix and emergency-call notifications. FCC rules implementing RAY BAUM’S Act address dispatchable location information.

The FCC’s rules distinguish fixed, non-fixed, and off-premises devices, with different provisions for providing location information. Confirm the applicable configuration with the provider using the FCC’s adopted rules.

Static registration works only while the recorded location remains accurate. Dynamic location capabilities can help associate a device with its current location, but depend on the platform, endpoint, and network configuration.

Security Risks on Remote Connections

Stolen credentials can expose voicemail, enable account changes, or lead to toll fraud.

Use MFA where supported, restrict international and premium-rate calling to users who need it, and configure usage alerts. Keep apps, phones, and home routers updated.

When someone leaves, disable their account promptly, revoke active sessions and provisioning access, and reassign business numbers and messages. Removing a person from the directory alone does not necessarily remove calling access.

Move Your Remote Team to Hosted PBX With Sangoma

Most problems in a remote rollout come from home connections and leftover analog lines, not from the phone system. Sangoma runs both the phone system and the network under it. 

Remote staff take calls, messages, and video meetings in TeamHub on desktop, mobile, or the web, and a Managed VPN covers their home connections. Sites that need phones to keep working during an internet outage, or that still run analog devices, can use hybrid communications. Hybrid keeps call processing on site, so that outage protection applies to hybrid and on-premises deployments, not to the cloud service.

Share your Step 1 audit on the first call so the quote reflects your real users, locations, and call flows. Talk to Sangoma about your rollout.