Handle a Patient’s Concern About Support Text Messages

A patient calls in upset because a support text just showed up on a phone that someone else in the household can see. Nothing in the message names a condition or a drug, but the patient does not want a partner, a roommate, or a teenager stumbling onto anything that hints at their health status. Your job is not to defend the text program or argue that the message was harmless. Your job is to hear the concern, protect the patient's privacy for the rest of this call, and route the request through whatever channel your program actually uses to change contact preferences.

Why this conversation goes wrong

Liaisons usually want to fix the problem fast, and that instinct causes the trouble. To reassure the patient, a liaison might repeat what the text said, explain why it was sent, or ask a clarifying question that requires saying the drug name or the appointment reason out loud again. Now the patient has heard their health information spoken a second time, on the same call where they raised a privacy concern. That makes things worse, not better.

The other common failure is overpromising. A liaison who wants to end the discomfort quickly says something like today will be the last text. Most programs cannot guarantee that. Preference changes often go through a queue, a system update, or a compliance check before they take effect, and a text already scheduled may still go out. If you promise an immediate stop and one more message arrives tomorrow, the patient loses trust in you specifically, not just in the messaging system.

How to prepare

Before you take a call like this, know three things cold. First, know every approved contact channel your program supports, such as a patient portal, a call in line, or a designated mail option, so you can offer a real alternative instead of a vague one. Second, know exactly what information the preference change process needs from the patient to verify identity and process the request, and nothing more. Third, know how long changes typically take to take effect and what the patient should expect to see in the meantime, so you can set expectations honestly instead of guessing.

It also helps to have a plain sentence ready that acknowledges the concern without restating any health detail. Something like I understand why that message landing on a shared phone is a problem for you. That sentence does real work. It tells the patient you heard them, and it does not repeat a single piece of protected information.

What to say

The patient says, can you stop the texts today. Do not answer that question directly yet, because you do not control the timing and you should not guess. Instead, acknowledge the concern and move toward the fix. You can say, I hear you, and I do not want anything sent to a phone you do not control. I can submit a request right now to change how we contact you, and I can also tell you about other ways to reach you that do not involve texting. Which would work better for you, a portal message or a mailed letter.

The patient says, I would rather use the portal, since I already check it for other things. That is safer. You reply, that works well. I am going to submit the preference change now, and I will send you the portal instructions separately so we are not walking through login details on this call. Once the change is processed, texting to this number will stop. If anything is already scheduled to go out before the change takes effect, it will not contain any detail beyond what you have already received.

Notice what did not happen in that exchange. You did not name a drug, a diagnosis, or an appointment type. You did not promise an exact stop time you cannot control. You gave the patient a real next step and a real alternative channel, and you told them the truth about timing instead of a comforting guess.

If the patient pushes back and asks why a text went out at all, you can explain the general purpose of the messaging program in generic terms, such as it is used for appointment reminders and general support check ins, without connecting that explanation to their specific situation. Keep the explanation short. The patient does not need a defense of the program. They need the problem handled.

Mistakes to avoid

A few habits will undo an otherwise good response. Do not repeat any detail from the original text message, even to explain it, since that just restates the sensitive information a second time. Do not promise texting will stop today if your program cannot guarantee that. Do not ask the patient to confirm their diagnosis or treatment as a way to verify identity, since most programs have a separate verification method that does not require the patient to say health information out loud. Do not leave the call without offering a concrete alternative channel, because a patient who only hears we will note your concern has no reason to believe anything will change.

Also watch what you write down afterward. A case note that says patient upset about text revealing treatment for condition X puts the same sensitive detail into a written record attached to a privacy complaint, which is exactly the outcome the patient was trying to prevent. Keep your notes limited to the administrative facts, such as the patient requested a change in contact method and the request was submitted.

This kind of boundary work shows up across other patient calls too. If you want to see how the same discipline applies when a patient asks for something outside your role, look at how a liaison handles a request for a ride in Clarify a Transportation Resource Request Without Booking a Ride, or how a liaison holds the line when a patient asks what medication to take in Set a Support Boundary When a Patient Asks What to Take. Both cover the same underlying skill, saying no to the wrong action while still helping the patient get to the right one.

How to practice and score it

A manager reviewing calls like this should check three things. Did the liaison avoid restating any protected health detail after the patient raised the concern. Did the liaison offer a specific next step through an approved channel rather than a vague reassurance. Did the liaison avoid promising a result the program cannot guarantee, such as an exact stop time.

Practicing this out loud matters more than reading about it, because the pressure to over explain shows up in the moment, not on paper. DealSpeak lets a liaison rehearse this exact scenario against an AI patient who pushes back the way a real one might, asking for an exact stop date or getting frustrated at a channel switch, so the liaison can find the habit of restating details before it happens on a real call. You can find this scenario and others built around real support situations on the Pharmaceuticals practice conversations page.

Handled well, this call takes under two minutes and leaves the patient feeling heard instead of exposed. Handled poorly, it repeats the very information the patient was trying to protect. The difference comes down to a few rehearsed sentences and a clear sense of what your program can and cannot promise.

You can rehearse this exact conversation in the Pharmaceuticals practice conversations library before it happens for real. When you have this one down, read Clarify a Transportation Resource Request Without Booking a Ride next.