Originally published at ictpbx.com
The hybrid work argument is over, and the data called the winner. Workplace surveys through mid-2026 keep landing on the same picture: roughly half of remote-capable employees now work hybrid, splitting each week between home and office, and the loudest return-to-office campaigns barely moved that number. Offices adapted with booking apps and hot desks. The business phone system, in a lot of companies, did not. Desk phones still ring at empty desks on Tuesdays, and customers still end up saved in contacts under someone's personal mobile number.
The work pattern stabilized; the office PBX still assumes an office.
The Mismatch, Concretely
Walk through what half-remote does to a phone system designed for full-office. An inbound customer call hits reception, reception transfers to a desk extension, and the desk is empty because it's a home day. The call bounces to voicemail, the customer calls the salesperson's mobile instead, and now a business relationship lives on a personal SIM that walks out the door if the employee does.
Meanwhile nobody can see availability. Reception doesn't know whether the support lead is at home and reachable or on the school run. Ring groups built around physical departments ring rooms instead of people. The company is effectively running two phone systems, the PBX for the office half of the week and an unmanaged mess of mobiles for the other half, and the seam between them is exactly where customers fall through.
What a Half-Remote Phone System Looks Like
The fix isn't exotic; it's a set of defaults that assume location is variable. One extension per person, registered simultaneously to the desk phone, a browser softphone, and a mobile app, so extension 204 is the person, wherever they sit. Presence everyone can see: office, home, on a call, off shift. And outbound business caller ID from every device, so the customer sees the company number whether the call started at a desk or a kitchen table.
The browser softphone deserves special mention because it quietly solves the worst hybrid problem: the home machine. Installing and maintaining SIP clients on personal laptops is a support burden and a security question. A WebRTC softphone needs nothing installed: the extension lives in a browser tab, encrypted end to end, and disappears when the tab closes. ICTPBX ships this as standard, which is one reason half-remote deployments lean on it heavily.
Four sizing decisions that make Monday morning work.
Sizing It: Four Decisions
First, count people, not desks. Per-user licensing with multi-device registration means 40 staff need 40 extensions, full stop. If a quote prices desk phones and mobile apps as separate line items, you're being charged twice for the same person.
Second, make WebRTC the default endpoint and desk phones the exception. Buy hardware for the roles that genuinely live at a desk, reception, maybe a shared warehouse phone, and let everyone else run browser and mobile. Most companies discover they need a third of the handsets they thought.
Third, route by presence and schedule, not by location. "In the office" no longer predicts availability, so ring groups and IVR targets should follow who's on shift and free. Time-based routing that follows the working day, wherever it's happening, beats any floor plan.
Fourth, split your infrastructure budget correctly: bandwidth for the office, security for the homes. The office link needs capacity for concurrent calls; the home endpoints need TLS signaling and SRTP media so calls stay private on domestic Wi-Fi. We covered the hardening side in our multi-tenant PBX security guide, and it applies doubly when half your endpoints live outside the office firewall.
One opinion from watching these deployments: companies overthink the technology and underthink the directory. The half-remote PBX works when presence is accurate, and presence is accurate when it updates itself from devices and calendars instead of relying on humans toggling a status. Ask any vendor how presence gets set, and be suspicious of answers that start with "users simply remember to."
The Monday Morning Test
Here's the acceptance test for any system you evaluate, including ICTPBX's hosted PBX software: Monday, 9 a.m., half the team at home, half in the office. A customer calls the main number. Does the call reach the right available person on the first attempt, with the company's caller ID on every callback? If yes, your phone system matches how your company actually works now. If no, you're still running a 2019 phone system in a 2026 company, and your customers are the ones absorbing the difference.
FAQ
How common is hybrid work now?
Surveys through mid-2026 consistently show around half of remote-capable employees working hybrid, with a smaller share fully remote and the rest fully on-site. The pattern has held steady for over a year despite return-to-office pushes.
What PBX features matter most for hybrid teams?
Multi-device registration under one extension, a WebRTC browser softphone, mobile apps with business caller ID, visible presence, and time or presence-based routing. Together they make location irrelevant to reachability.
Do remote employees need VPNs for the phone system?
Not with a properly configured hosted PBX. WebRTC softphones connect over TLS and SRTP directly, so calls are encrypted without VPN clients on personal machines. That removes both a support burden and a common failure point.
How much bandwidth do concurrent calls need?
Plan roughly 100 kbps per concurrent call in each direction with common codecs, plus headroom. A 20-person office rarely has 20 simultaneous calls; measuring your real concurrency for a week beats guessing.
Can hybrid teams keep their existing business numbers?
Yes. Numbers port to the hosted platform and ring every registered device. Callers dial the same number they always have; where it rings is what changes.
Top comments (0)