Guide

HIPAA-compliant missed call text back

Most businesses can text a missed caller anything they want. A med spa, dental office, concierge practice, or wellness clinic cannot. But the answer is not to skip the text back and let inquiries die in voicemail. The answer is a first touch designed to contain nothing sensitive. This guide covers the pattern, the scripts, and the mistakes that create exposure.

This is operational guidance, not legal advice. Run the final workflow past your compliance officer or counsel.

Why standard text back is a problem here

Two reasons. First, standard SMS is not encrypted, so any protected health information inside a message travels exposed. Second, most texting and automation platforms will not sign a business associate agreement, which means even a well-written message on the wrong platform leaves the practice carrying risk. The fix addresses both: control what the message says, and control what carries it.

The PHI-free first touch pattern

  1. Acknowledge fast, say nothing sensitive. The first text confirms you saw the call and offers a path forward. No conditions, no treatments, no appointment details.
  2. Move detail collection to a covered channel. A phone call, a secure intake form, or a patient portal. The text's job is to keep the inquiry alive, not to gather a medical history.
  3. Use a platform that signs a BAA. If patient communication will ever flow through it, the vendor signs or the vendor is out.
  4. Capture texting consent at intake. Once someone becomes a patient or client, record how they want to be contacted and what they have agreed to receive.
  5. Write it all down. Scripts, rules, and the platform list, in a document your compliance counsel can review once and approve.

Scripts that stay on the safe side

First touch

Hi, this is {Practice}. Sorry we missed your call. Would you like a call back, or is there a good time to reach you?

Scheduling nudge

Hi, this is {Practice}. We have your inquiry and can get you scheduled. Call us at {number} or use our booking link: {link}

What not to send

Anything naming a treatment, condition, medication, test, or result. "Following up on your Botox consult" is exposure. "Following up on your inquiry" is fine.

Common mistakes

  • Running patient texting through a marketing automation tool that will not sign a BAA.
  • Letting individual staff text from personal phones with no script and no record.
  • Putting appointment and treatment details in the reminder text instead of a neutral confirmation.
  • Freezing entirely and responding to nothing, which is the most expensive mistake of all.

FAQ

Can a medical or dental practice text back missed calls?

Yes, if the workflow is designed for it. The first message must contain no protected health information, the platform should be one that signs a business associate agreement, and texting consent should be captured at intake.

What counts as PHI in a text message?

Anything that ties an identifiable person to their health condition, treatment, or payment. A message that mentions a procedure, an appointment for a specific treatment, or test results can qualify. When in doubt, leave it out of the text.

Is a missed call text back marketing or treatment communication?

A simple acknowledgment that you missed a call and an offer to help is generally operational. The line moves when the message starts promoting services or referencing care. Keep the first touch neutral and let your compliance counsel define the boundary for your practice.

Related reading

Want this designed for your practice?

The AI Operations Audit maps your inquiry-to-booking workflow, prices the leaks against your client value, and defines the compliant fix worth installing first, documented for your counsel to review.

HIPAA-aware response systemsThe consulting approach for inquiry response, intake, and follow-up. HIPAA-compliant appointment remindersConfirmation and reminder workflows with clearer boundaries. Which texting tools sign a BAAWhat to verify before a tool enters a regulated workflow.
By Logan Stahl Updated

Founder of Stahl Automation. I design and implement the systems between demand and delivery, including websites, lead response, AI workflows, intake, routing, approvals, and handoffs.