Skip to main content

An anonymized cloud-phone client story

One business number across office phones, computers and mobile apps

A distributed healthcare organization wanted its staff to make and receive business calls without relying on a handset in one office or sharing personal mobile numbers. We moved them to an ACS-managed cloud phone system that follows each person’s assigned number and extension across office phones, a desktop app, a supported browser and a mobile app.

No client name or identifying details. Features depend on the organization’s numbers, carriers, locations and emergency-calling requirements.

The problem was more than the phone bill

The organization was paying for a setup built around physical locations. Remote staff needed a practical way to answer as the business, office teams still needed familiar handsets, and nobody wanted a separate phone identity for every device.

Keep the established identity

Customers and partners continue to see the assigned business caller ID instead of an employee’s personal mobile number. Existing numbers and call flows are reviewed before the move.

Support every work style

A person can use a physical office phone, a computer with a headset, a browser or a mobile app. Different people can have one or multiple numbers or extensions according to their roles.

Reduce unnecessary cost

Consolidating the phone service reduced cost and avoided making remote work depend on additional office hardware. The exact saving depends on the old contract, call patterns and devices, so we do not publish a made-up percentage.

What the new phone setup lets people do

Everything is managed as one service rather than a collection of unrelated personal phones.

Person or teamDevice and way of workingBusiness capability
Overseas and remote workersMobile app on a supported phoneMake and receive calls using their assigned business number and extension without exposing a personal number
Computer-based staffDesktop application or supported browser with a suitable headsetHandle calls at the computer, use the same extension and avoid being tied to a desk phone
Office employeesPhysical handsets, with apps available as wellKeep the familiar desk experience while staying reachable under the same identity when away
People covering multiple rolesOne or more assigned numbers or extensionsUse the appropriate business identity for each role, team or call flow
Reception and support teamsShared queues and call routing matched to coverageRoute the call to the right team instead of depending on one person’s physical extension

International calling, roaming, emergency services, lawful intercept, number registration and local regulations vary. We confirm those requirements before enabling a location or worker.

How the migration stayed controlled

A phone change should not interrupt patient, client or supplier calls. We handle it as a business-system migration, not just an app installation.

1
Map the current serviceNumbers, carriers, extensions, call groups, business hours, devices and the people who cover each role.
2
Design identity and accessAssign numbers, extensions, MFA, device rules, voicemail, call recording choices and offboarding. Decide what each role should reach.
3
Test with real call pathsCheck inbound and outbound caller ID, mobile and computer audio, office handsets, queues, failover and emergency-calling configuration.
4
Move and support the teamPort or configure numbers in controlled steps, train each work style and monitor the service after launch.

Service profile and related controls

This engagement included the cloud phone system alongside managed IT and security. A phone rollout is not isolated from identity, endpoint or data governance.

LayerWhat we manageReason
Cloud callingNumbers, extensions, apps, handsets, call flows and user onboarding/offboardingConsistent communication across office and remote teams
Identity and devicesMFA, account access, managed phones and computers, supported applicationsA stolen password or personal device should not silently become a trusted business line
Network and continuityInternet quality, call testing, backup connectivity and failover where requiredCloud calling depends on a working connection at every location
Privacy and recordsRetention, voicemail, call recording choices, access and applicable healthcare or local requirementsConversations and call metadata can contain sensitive information
SupportUser changes, device issues, call-quality review and ongoing service managementThe system stays aligned with staff and business changes

Could this work for your team?

Tell us your locations, current phone numbers, remote workers, call flows and which devices people prefer. We will map the features and costs before you change providers.

Also read the wider Microsoft workplace and security story or our cloud-phone pricing.

SOC 2-aligned controlsHIPAA-first30-day money-back guarantee24/7 monitoring

Request a Quote

Fill out the form below and our team will get back to you within one business day.

Free IT & HIPAA security assessment