The phone knows who is calling.

Inbound calls ring in the Microsoft Teams your staff already use, while the caller's record opens on their screen. A cloud phone number in your own tenancy answers with your greeting and business hours, a simple menu routes to intake or scheduling, and hunt groups offer the call to whoever has been free longest. By the time someone says hello, HealthOS has matched the number and the chart is already open.

See it in motion.

A short, narrated explainer. Captions included.

A contact centre without a contact centre.

Caller-ID screen-pop: HealthOS matches the incoming number against the person's own phone numbers and their listed family contacts, tenant-scoped. The answering staff member is prompted to open the record, one click, and the chart is on screen. An unknown number opens person search instead, prefilled with the number.
Simple IVR, yours to configure: Your greeting, your business hours, your menu: press one for intake, two for scheduling. After hours, callers hear your after-hours message instead of ringing out. Menus, options and number routes are configured in the admin portal, not by a vendor ticket.
Hunt groups and presence: Staff set themselves Ready, On break or Wrap-up from a phone bar in the app header, and opt in or out of each hunt group they belong to. Calls distribute to the longest-idle ready agent, or round-robin, or ring-all, so nobody gets sprayed and nobody gets skipped.
Answered in Microsoft Teams: There is no softphone to roll out and no headset software to license. HealthOS connects the accepted call into the staff member's Teams, where your organisation already talks. HealthOS does the routing, presence and screen-pop; the audio stays in Teams.

Your number, your tenancy, your rules.

Telephony rides the same sovereignty posture as the rest of the platform. It is a capability of your deployment, not a separate phone product with its own copy of your data.

A number in your own tenancy: The trunk is Azure Communication Services running in your own cloud tenancy. Provision a new number there, or bring your existing numbers across via direct routing.
Behind the same walls: Hunt groups, number routes, IVR menus and call events are tenant-scoped rows in the same database as the care record, under the same row-level security. There is no side system to secure separately.
Every call leaves a trail: Each call, menu choice, routing decision and screen-pop is recorded as call events against the matched person, reviewable later, like everything else in HealthOS.
Presence that respects people: On break means no calls. Wrap-up gives staff time to finish their notes before the next offer. Opting out of a group is a switch they control, not a request to IT.
Admin-configured, like everything else: The telephony connector installs from the marketplace and is managed from the admin portal, connection settings, hunt groups, membership, number routes and IVR menus in one place.
Graceful when it does not know: A caller who is not in the system is still a first-class call: the pop offers person search prefilled with the number, so the conversation starts with creating the record, not fumbling for it.

A phone call is part of the record

Most providers run the phone system and the care system as strangers. In HealthOS the call arrives already joined to the person: the family member's number is on the chart, so the chart opens with the call, and what happens next is written where the next person will look.

Family contact numbers match to the resident or client they belong to
Intake calls land where referrals and enquiries already live
Call events sit against the person, not in a phone portal
The same record the family portal and clinicians already share

Solutions

Modules

Features

More

The phone knows who is calling.

See it in motion.

A contact centre without a contact centre.

Your number, your tenancy, your rules.

A phone call is part of the record

See the screen-pop for yourself.