Guide a Patient Through a Communication Preference Update

A patient calls to change how they receive messages from your program. The request sounds simple, but it sits next to protected health information, consent records, and a call center system that does not update the moment someone asks. Handle it well and the patient feels heard and safe. Handle it badly and you either make a promise you cannot keep or you repeat health details the patient never wanted to hear out loud again.

Why This Conversation Goes Wrong

A Patient Support Liaison wants to fix the problem fast. That instinct is good, but it leads to two common failures. The first is promising an exact stop time for messages when you do not control every system that sends them. Texts, portal alerts, and mail can run through different platforms with different update schedules. If you tell a patient every text stops today and one goes out tomorrow, you have broken trust over something you never needed to promise in the first place.

The second failure is mixing the administrative request with clinical content. A patient who asks you to stop texting is not asking you to summarize their treatment plan or confirm a diagnosis. Yet liaisons sometimes repeat health details while confirming the change, thinking it shows attentiveness. It does the opposite. It tells the patient that a simple request about contact method turned into another moment where sensitive information got said out loud, maybe within earshot of someone else.

There is also a personal safety layer that is easy to miss. A patient asking to stop texts because a partner sees the phone may be describing a situation where privacy matters for reasons beyond convenience. You do not need to investigate that. You do need to treat the request as serious and move quickly to the practical fix, not to reassurance that drifts into asking why.

How to Prepare

Before you take these calls, know exactly what you can commit to. Know which communication channels the program supports, typically phone, mail, and a secure portal, and know which team owns the update once you submit it. Know what confirmation looks like, whether that is a portal notice, a follow up call, or a letter, and know roughly how long that confirmation takes without pretending you can name an exact hour.

Write down the line you will use to separate administrative topics from clinical ones. Something like, I will not include health details in this discussion, said plainly and early, sets the boundary without sounding cold. Practice saying it so it comes out natural, not scripted.

Also prepare for patients who are not sure what they want. Some will describe the problem, my partner sees my phone, without stating a clear preference. Your job is to translate that into a concrete choice, phone, mail, or portal, rather than guessing on their behalf. If the patient changes their mind mid call, that is normal. Confirm the final choice clearly before you end the conversation.

What to Say

Here is how that call can go. The patient says, my partner sees my phone, please stop the texts today. The liaison responds, I understand why that matters to you. I can walk you through the approved way to update your communication preferences and how you will get confirmation once it is done. I will not bring up any health details in this call. Would you rather switch to phone calls or to the secure portal.

The patient says, the portal sounds better, how do I get into it safely. The liaison replies, I will submit a request to switch your primary contact method to the portal. You will get a letter with a secure sign in link and a number to call if you have trouble accessing it. I cannot promise every message stops the same day, since some systems update on different schedules, but I can tell you the change is submitted right now and confirmed within a few business days.

The patient asks, will anyone call or text me before that confirmation comes through. The liaison answers, it is possible you get one more message during the switch, since the systems do not update at the exact same moment. Once the portal is your primary contact method, that will stop future outreach through text. If anything comes through that concerns you, call this line back and reference today's request.

Notice what did not happen. The liaison never named a medication, a diagnosis, or a dose. The liaison never said everything stops immediately. The liaison gave a real answer about timing that was honest instead of comforting.

Mistakes to Avoid

A few patterns cause real damage in this type of call.

1. Promising an exact stop time for every channel, which sets up a broken promise the moment one system lags behind another.
2. Repeating health information while confirming a contact preference, which turns an administrative request into an unwanted clinical disclosure.
3. Asking the patient to explain why they want the change, when a simple acknowledgment and a request for their preferred method is enough.
4. Skipping the confirmation step, so the patient has no record of what changed or when to expect it.
5. Offering clinical advice or reassurance about treatment because the topic of health came up near the request, even briefly.

Any one of these turns a two minute call into a complaint, or worse, into a patient who no longer trusts the program with their information.

How to Practice and Score It

Role play this scenario with a colleague who plays a patient changing their mind twice during the call, first asking for phone, then switching to portal, then asking a follow up question about security. That forces the liaison to track the current preference accurately and repeat it back correctly before closing the call.

Score the practice run on three things. Did the liaison name the correct approved channel for the change. Did the liaison avoid any health details entirely, even in passing. Did the liaison give an honest, non specific answer about timing instead of a guessed exact time. Read back the note the liaison would leave in the file. It should state the requested preference and the confirmation process, and it should not include a promise the liaison cannot control.

DealSpeak is built for exactly this kind of rehearsal. You can run this scenario against an AI counterpart as many times as you need, get scored on the same criteria a manager would use, and see where the language slips before it slips on a real call. For more scenarios built around this kind of work, look at the Pharmaceuticals practice conversations collection, including the related post on how to Respond When a Patient Is Distressed by a Denial Notice. If you also support clinic staff, the post on how to Explain Patient Support Enrollment Steps to a Clinic covers a related conversation from the other side of the program.

A communication preference update is a small request with a low tolerance for error. Keep the administrative and clinical parts of the call separate, promise only what you control, and confirm the final choice out loud before you hang up. Get that right consistently and patients trust you with the bigger conversations too.