Billing PortalSupportPartner Portal+1 407 598 TALK
Blog

Voicemail in a Medical Office: What Should and Shouldn't Be Left

Medical office voicemail sits inside HIPAA's minimum-necessary principle: leave enough to prompt a callback, not enough to disclose a condition. Practically that means name, practice, callback number, and nothing clinical. Shared boxes need a defined access list, and AI transcription should stay off wherever PHI can appear, pending a BAA.

No phone system makes a practice HIPAA-compliant. What it gives you is controls — PINs, access roles, delivery destinations, per-box settings — that your policies then use. What follows is how those controls map to the decisions.

What can you leave on a patient's voicemail?

Enough to identify who called and how to reach back. Not the reason.

A defensible message: "This is Dana from Lakeside Family Medicine calling for Robert Chen. Please call us back at 555-0142." A name, an organization, a callback number, no clinical content. A patient hearing it on a speakerphone in a shared kitchen has disclosed nothing about their health.

What does not belong: test results, diagnoses, medication names, appointment types that imply a condition ("your oncology follow-up"), or referral details. Even the practice name can be sensitive where the specialty is the diagnosis — a behavioral health or infectious disease practice may reasonably identify itself by a neutral name or the caller's first name only.

Two habits worth adopting. Confirm the callback number in the chart is current before leaving anything, because a reassigned mobile number is a disclosure to a stranger. And honor stated patient preferences — if someone asked that you not leave messages, that instruction should live where the caller sees it before dialing.

What should your own voicemail greeting say?

Four elements, and one of them is often missing.

State the practice name, the hours you return calls, what the caller should leave, and — the one that gets skipped — an instruction not to leave clinical detail. "Please leave your name, date of birth, and a callback number. Do not leave medical details; we will discuss them when we reach you." Patients describe symptoms into voicemail unless you tell them not to, and each of those messages becomes a record you have to handle.

If the box is an after-hours destination, the emergency instruction comes first: hang up and dial 911. Voicemail greeting scripts for small offices has structures you can adapt; voicemail box setup covers PINs, greetings, and per-box behavior.

Are shared departmental voicemail boxes a privacy problem?

Not inherently. They become one when nobody can say who has access.

Shared boxes are the right tool for a function rather than a person: scheduling, billing, referrals. A message about a bill should reach whoever works billing today, not sit in the personal box of someone on vacation. What makes a shared box defensible is an access list that is deliberate and current.

Three rules we recommend writing down:

  1. Name an owner per box. One person is accountable for who has the PIN and for the box being checked.
  2. Keep the access list minimum-necessary. The referrals box does not need the whole front desk in it.
  3. Change the PIN when someone leaves. A shared PIN is a credential that walks out the door with the employee, and it is the most commonly forgotten item on an offboarding checklist.

Match the box structure to the message content. Clinical messages should not land in a general box the whole office can play — route clinical intake to a box with a narrow access list, and keep the general box for scheduling and directions. Shared and departmental voicemail boxes covers the configuration.

Who should be able to play back voicemail?

Fewer people than can currently, at most practices.

There are three doors into a voicemail message, and each needs its own decision:

Access path

Who it grants

Control

Dial-in retrieval from a handset (a *97-style feature code)

Anyone with the box PIN

Per-box PIN, changed at offboarding

In-portal playback

Portal users whose role permits it

Client-side roles: owner, admin, agent, read-only

Voicemail-to-email

Anyone with access to the destination inbox

Choice of destination address

The third row is the one practices under-think. Voicemail-to-email attaches the audio to an email, which is what makes messages actually get returned — and it means the message now lives wherever that mailbox lives, under whatever protections that mail system has. Send patient voicemail to a practice-controlled mailbox on your organizational email, never to a personal address or a shared alias including people outside the practice. Voicemail-to-email delivery covers the setup; the destination is a policy decision, not a technical one.

Roles are the underused control. Signal supports owner, admin, agent, and read-only roles managed by the client, so a practice manager can see reporting without every staff member gaining playback rights to every box. Review the user list quarterly against your roster.

Should you turn on AI voicemail transcription?

Not where PHI can appear. This is the clearest line in this post.

Signal offers AI voicemail transcription and AI call summaries. They are useful — reading a message takes a fraction of the time listening does, and summaries surface action items and flag calls where a caller had a bad experience. They also send audio or text to third-party AI providers, and Signal has no BAA with those providers.

For that reason both features are off by default per client. A practice whose voicemail or calls can carry PHI should leave them off pending a BAA, and should treat "we would like this on" as a conversation with its privacy officer rather than a settings change. We would rather say this plainly than sell a feature that puts a practice in a bad position. HIPAA and your phone system covers what parts of telephony the rule actually reaches.

The same reasoning applies to call recording, with an added requirement. Inbound recording requires a consent announcement — in two-party-consent states that announcement is legally load-bearing, not a courtesy. Before recording in a clinical setting, decide who can access recordings, how long they are kept, and whether those calls contain PHI you are prepared to store.

A short voicemail checklist for a practice

  1. Every box has a named owner and a stated check frequency.
  2. Greetings tell patients not to leave clinical detail.
  3. Callback messages contain a name, the practice, and a number — nothing more.
  4. PINs change at offboarding, on every shared box.
  5. Voicemail-to-email points at a practice-controlled mailbox.
  6. AI transcription and summaries stay off wherever PHI can appear.

Frequently asked questions

What can a medical office leave on a patient's voicemail? The caller's name, the practice name, and a callback number. No test results, diagnoses, medication names, or appointment types that imply a condition. Confirm the number in the chart first, and respect patients who have asked that no messages be left at all.

Are shared departmental voicemail boxes a privacy problem? Not by design. They fail when the access list is undefined or stale. Assign one accountable owner per box, keep access minimum-necessary, and change the PIN whenever someone with it leaves. Route clinical messages to a narrow box rather than a general one.

Who should be able to play back voicemail in a practice? Only staff whose role requires it. Access comes through three paths: dial-in retrieval with the box PIN, in-portal playback governed by user role, and voicemail-to-email governed by mailbox access. Review all three against your roster, not just the portal user list.

Should a medical practice turn on AI voicemail transcription? Not where PHI can appear. Transcription and AI call summaries send data to third-party AI providers, Signal has no BAA with them, and the features are off by default for that reason. Leave them off pending a BAA and raise the question with your privacy officer.

Does using a phone system with these controls make us HIPAA-compliant? No. Compliance is a function of your policies, workforce training, agreements, and safeguards across every system you use. A phone system supplies controls — PINs, roles, delivery destinations, per-box settings. How you configure and govern them is what matters, and no vendor can make that claim for you.

If you are writing or refreshing a voicemail policy for a practice, we are happy to walk through which controls exist on your account and which decisions are yours to make. Tell us how your boxes are structured today and we will tell you where we would tighten them.

We are here to help.

Talk to a Signal specialist about the right package for your team, your industry, and your budget.

Let's Talk