Real human, first ring
When patient lines drop audio at 8:15 a.m. Monday, a real human picks up the support line. Not a chatbot, not a queue, not a ticket number — the same team that configured the BAA and the multi-location routing.
The 30-second version
A phone system that signs the BAA and protects the call.
Netexem is a business phone, SMS, and voicemail platform built for healthcare practices that handle Protected Health Information. We sign the BAA on day one. You get a softphone on every device, multi-location call routing across covered entities, after-hours triage, encrypted call recording with role-based access, and audit logs on every call, text, and voicemail. A real human picks up our support line when you need us.
Built on the same business VoIP platform we run for every customer — cloud PBX, SIP trunking, native SMS, and E911 — with encrypted recording, multi-location routing, and audit logs configured for practices that need a BAA on day one.
BAA + compliance, on day one
Business phone, SMS, and voicemail. BAA signed before you go live. Encrypted in transit and at rest.
Four standard controls, published up front so your compliance officer can match them to your risk register without guessing. We do not claim HIPAA status of any kind. We sign the BAA, we encrypt the infrastructure, and we publish what the BAA covers.
BAA available for covered entities
We sign the Business Associate Agreement before you go live. Same-week countersign on most plans.
Encrypted in transit and at rest
TLS for signaling, SRTP for media, and encrypted storage for voicemail and recording.
Audit logs on every call, text, and voicemail
Caller, duration, direction, routing, and user access — queryable and exportable.
BAA-covered 10DLC SMS
Patient texts run on a registered practice number. Threads belong to the practice, not the staff member.
HIPAA compliance is a shared responsibility. Netexem provides the BAA and the encrypted infrastructure. Your covered entity is responsible for your own end-to-end compliance practices, policies, and procedures — including staff training, access policies, and breach response. Talk to us about your specific requirements. Request your BAA to start the process.
The patient-confidentiality problem
Phones are the #1 PHI exposure risk in small and mid-size practices.
Here is what makes phones hard for a healthcare practice. Front-desk staff text patients from personal cell phones. Voicemails get forwarded to the wrong inbox. On-call routing breaks at 7 p.m. and a triage call lands at a personal mobile that does not record, does not log, and does not carry the practice's number. Add multiple locations, multiple covered entities, and a vendor that won't sign a BAA — and you have a compliance gap your office manager spends every Monday morning patching. Over 275 million individuals were affected by healthcare data breaches in 2024. After a single breach, practices lose 40-50% of their patient base. You need a phone system that signs the BAA, encrypts the call, and logs the trail — without slowing down the people who actually answer the phone.
Personal phones are the leak
When front-desk staff text patients from personal cell numbers, the practice has no audit trail, no encryption, and no way to revoke access when the employee leaves. Your phone system should own the conversation, not the person.
Multi-location routing breaks at the edges
A patient calling the main clinic gets bounced between locations, hits a different voicemail at each one, and gives up. Multi-location practices need one number, smart routing, and an audit log that follows the call across covered entities.
After-hours triage cannot land on a personal mobile
On-call clinicians need calls that route to them, record properly, and log to the practice — not to their personal voicemail. The triage call at 11 p.m. has to be as protected as the one at noon.
What you get with Netexem
Six features built for practices that handle PHI.
Most VoIP vendors ship 60 features and won't sign a BAA. We start with the six that healthcare practices actually need — and we sign the BAA on day one.
BAA available for covered entities — signed on day one
Netexem signs a Business Associate Agreement with covered entities before you go live. The BAA covers business phone, voicemail, SMS, call recording, and audit logs. HIPAA compliance is a shared responsibility — your practice is responsible for your own end-to-end policies and procedures — and the platform is built to support them.
Multi-location routing across covered entities
One number for the whole practice. Smart routing by location, specialty, or provider. Patients reach the right front desk without bouncing through five voicemails, and the audit trail follows the call across every covered entity in your group.
Encrypted call handling with role-based access
Calls are encrypted in transit (TLS) and at rest. Role-based access controls let you scope who can hear recordings, read voicemail transcripts, and pull audit logs. Front desk sees scheduling calls. Clinical staff sees clinical calls. Admin sees the audit trail.
Audit logs on every call, text, and voicemail
Every call, every SMS, and every voicemail captures caller, duration, direction, routing, and user access. Logs are queryable and exportable. When your compliance officer asks who heard what and when, you can answer with a search instead of a meeting.
After-hours triage and on-call routing
Configure on-call routing with simultaneous ring to the duty clinician, fallback to a covered backup, and a recorded handoff to the answering service. The triage call at 11 p.m. lands inside the practice — with the practice's number, the practice's recording, and the practice's audit log.
Business-line SMS on the practice number — covered by the BAA
Patients text the practice number for appointment reminders, recall messages, and scheduling — not a staff member's personal cell. SMS is covered by the BAA, runs on a 10DLC-registered business line, and stores message history on the practice account. When staff leave, the conversation stays.
The softphone runs on every device a practice already owns — see the softphone page for the per-platform breakdown, or browse desk-phone hardware if the front desk wants a Yealink at every check-in window.
How healthcare practices actually use it
Five real scenarios from the practices we serve.
Not hypotheticals. These are the day-to-day patterns we see across primary-care groups, specialty clinics, and multi-location practices coast to coast.
Multi-location primary-care group
One published phone number routes patients to the right clinic by zip code and provider. Each location keeps its own voicemail, its own audit log, and its own staff access — under one BAA and one platform.
Specialty practice with on-call rotation
After-hours calls route to the duty physician through sim-ring, with fallback to a covered backup and a recorded handoff to the answering service. Every step logs to the practice — not the clinician's personal phone.
Behavioral-health clinic with sensitive intake
Intake calls record with role-based access — only intake coordinators and the clinical director can pull the recording. Voicemail goes to an inbox the practice controls under the BAA, not a staff member's personal email.
Surgery center coordinating across covered entities
The surgery center, the anesthesia group, and the imaging partner each have their own BAA scope. Calls between them log to the practice ledger. The compliance officer pulls a quarterly export instead of chasing screenshots.
Solo practitioner with a part-time medical assistant
One number, two seats. The practitioner takes calls on a personal iPhone using the practice softphone — without giving out the personal cell. The medical assistant handles SMS recalls on the practice number from a laptop softphone.
Pricing your practice administrator can read
Per seat. No contract. BAA included on every plan.
Per-seat pricing with no contract, no per-minute charges on US calls, and no surprise add-ons for the features practices actually need. Recording, SMS, voicemail-to-email with encryption, after-hours routing, and audit logs are included — not paywalled. The BAA is included for covered entities on every plan. Enterprise contracts include custom terms for multi-location groups — talk to us. See full pricing on the pricing page, then port your numbers when you're ready.
More from the same product: business VoIP platform, softphone for every device, desk-phone hardware, or talk to a real human.
FAQ
Healthcare phone questions, answered.
Eight questions we hear from practice administrators and compliance officers every week — BAA scope, multi-location routing, after-hours triage, SMS coverage, and Enterprise terms.
Business phone for your practice
Stop letting personal phones own your patient conversations.
Talk to us about the BAA, multi-location routing, and the configuration that fits your specialty. We'll port your numbers, sign the BAA, and walk your staff through the softphone before go-live.