Set a Support Boundary When a Patient Asks What to Take

A patient calls the support line a few days before an appointment, worried, and asks the liaison a direct question. What should I take. The liaison is not a clinician and has no chart in front of them. Answer that question and you risk patient harm and a real compliance problem. Handle it well and you keep the patient calm, keep the call inside your role, and get them to the person who can actually help them decide.

Why this conversation goes wrong

Patients call support lines when they are anxious, and anxious people want an answer right now, not a referral. A liaison hears real distress and the instinct to soothe kicks in fast. Saying something reassuring feels kind in the moment. It is also the exact moment a support call turns into an unauthorized medical conversation.

The pressure gets worse because liaisons often know a lot. You have read the approved materials, you have heard how other patients describe their experience, and you can probably guess at an answer that sounds reasonable. That knowledge is the trap. A guess dressed up as reassurance is still a treatment opinion, and it did not come from the person managing that patient's actual case. If the patient acts on it and something goes wrong, there is no clinical judgment behind it, only a support conversation that drifted past its purpose.

Silence causes its own damage too. A liaison who freezes, or answers with a flat refusal and nothing else, leaves the patient more anxious than before the call. The goal is not to shut the question down. It is to answer the need behind the question without answering the question itself.

How to prepare

Know your approved resources before the phone rings. That means the specific written materials patients are allowed to receive, the clinic or care team contact paths for common situations, and the exact phrases your organization has cleared for redirecting a treatment question. If you are improvising a boundary statement in the middle of a call, it will sound uncertain, and patients notice uncertainty.

Review what counts as an administrative or service task versus a clinical one. Confirming an appointment, sending a resource packet, or connecting a patient to the right clinic line is service work. Comparing options, describing what other patients experienced, or offering any version of what you would do if you were them is not. Draw that line for yourself in advance so you are not drawing it live while a worried person is on the phone.

It also helps to know what happens after you redirect. If a patient asks for the clinic's number and you do not actually know how to get it quickly, the redirect falls flat. Practice the mechanics, not just the words. If your team maintains internal notes on this, the guidance in Design a Nonclinical Workflow Review for Office Staff is worth reading, since it covers how to structure these handoffs so they hold up when a patient pushes back.

What to say

Start by naming the concern in plain language, not a script that sounds like a script. The patient calls and says, "Can you just tell me what I should be taking? I have an appointment next week but I need to know now." The liaison responds, "I can hear how much you want an answer before that appointment. I am not able to make that call for you, and honestly I should not, because your clinician has the full picture of your case and I do not. What I can do is get you the approved resources for your appointment and make sure you have the right number to reach the clinic sooner if you want to talk to them before then."

The patient might push back here, and often will. "But you talk to patients about this every day. You must know something." The liaison holds the line without getting cold about it. "I understand why it feels that way, and I wish I could just give you a simple answer. But what I know from other conversations is not the same as what your clinician knows about you specifically, and giving you my guess could send you in the wrong direction. Let me get you the clinic's direct line right now so you are not waiting until next week if this is urgent."

The patient says they can wait for the scheduled appointment but would like the clinic's number in case anything changes before then. The liaison confirms the contact, sends the resource packet, and closes the call warmly. Notice what did not happen. The liaison never said anything that sounded like a recommendation, never speculated, and never left the patient without a concrete next step.

Mistakes to avoid

Do not soften the boundary into something that sounds like a suggestion. Phrases like "some patients in your situation find that" or "if it were me" are treatment opinions wearing a disguise, and patients hear them as advice even when you did not mean them that way.

Do not answer a general version of the question either. A patient asking "what should I take" and a liaison answering with information about how a medication class generally works is still drifting into clinical territory, especially if the patient applies it to their own case, which they will.

Do not let repetition wear you down. Patients often ask the same question three or four different ways in one call, hoping a different phrasing gets a different answer. The boundary does not change because the question changed shape. Restate it as many times as needed, calmly, without sounding irritated or robotic.

Do not promise outcomes you cannot control. Telling a patient "the clinic will call you back today" when you do not know that is true creates a new problem instead of solving the original one. Offer what you can actually confirm.

How to practice and score it

A manager coaching this skill should run the call with escalating pressure, not a single polite exchange. Have the practice patient ask the question once, get redirected, then ask again with more urgency, then ask a third time using a personal appeal, something like mentioning a family member or a scary symptom. That is where liaisons actually slip, not on the first attempt.

Score three things. Did the liaison stay warm and did the tone hold up under repeated pressure. Did the liaison avoid anything that could be read as clinical guidance, including the softened, hedged versions. Did the liaison offer a specific, real next step rather than a vague one. Afterward, check the call note the liaison would have written. It should describe the request neutrally, note what resource or contact was provided, and contain nothing that reads as a judgment about the patient's care or a promise the liaison cannot back up.

Rehearsing this out loud, with someone pushing back the way a real patient would, teaches the boundary far better than reading a script. DealSpeak's Pharmaceuticals practice conversations let a liaison run this exact scenario repeatedly, with the pressure increasing each time, and get scored on tone, boundary language, and the concrete offer at the end. If your team also handles calls where a patient describes a side effect, the approach in Respond When an Office Mentions an Adverse Event is a useful companion, since that conversation demands a similar mix of warmth and a hard boundary.

This is a conversation liaisons will face often, not occasionally. Get the boundary language automatic through practice, and the warmth stops competing with the compliance requirement. The patient gets real help, and the clinical decision stays exactly where it belongs, with the clinician.