Handle an Unsolicited Scientific Question About Use Outside Approved Labeling
Use the medical information process when a specialist asks outside approved product use.
A specialist on a call or in the room asks you a direct scientific question about a use your product does not carry on its label. The question is real to them and urgent. Answering it well is not your job to skip, but it is also not your job to promote. How you handle the next sixty seconds decides whether the exchange stays scientific and compliant or turns into something your legal and compliance teams have to unwind later.
Why this conversation goes wrong
Most Medical Science Liaisons know the rule. Unsolicited scientific questions go through the medical information process, not through a quick answer at the podium or in a hallway. The trouble is not the rule. The trouble is the moment itself. A specialist wants a real answer for a real patient, and they want it now. You feel the pull to be useful, to prove you know the science, to close the gap between what they need and what the label covers. That pull is exactly what turns a compliant scientific exchange into something that looks like promotion of an unapproved use.
There is a second failure mode that gets less attention. Some MSLs overcorrect and shut the conversation down too hard, treating any question about use outside approved labeling as a compliance trap to escape rather than a legitimate request to route properly. That response frustrates the specialist and reflects badly on you and your company. The goal is not avoidance. The goal is a clean, respectful path that gets the specialist a real answer through the right channel. For a closer look at the routing decision itself, read Route an Unsolicited Scientific Question With Care.
How to prepare
Before you are ever in this conversation, know your medical information request process cold. Know what counts as a proper unsolicited request, who receives it, and roughly how long a response takes. Know whether your company accepts questions verbally with a written follow up or requires the question in writing from the start. If you do not know these details precisely, find out before your next field visit rather than improvising in front of a specialist.
Prepare a few lines you can say without sounding rehearsed. You want language that acknowledges the specialist's need, explains the process without sounding bureaucratic, and avoids any hint that you already know what the answer will be. Avoid saying anything like a formal review will confirm what you suspect, because that predicts content you are not authorized to promise. Also decide in advance how you will handle a question that arrives wrapped in patient details. You need a clean way to redirect the conversation to the general scientific question while declining the identifying specifics, without making the specialist feel scolded for asking.
What to say
Picture a specialist who corners you after a session and asks, "Why can't you just tell me now, you clearly know the data?"
You respond, "I do want to get you a precise answer, and the fastest way to do that well is through our medical information process rather than off the cuff. That keeps the response accurate and keeps our conversation focused on the science rather than anything that could look like promotion. Can I get the question from you in writing, even a few sentences, so the response addresses exactly what you're asking?"
The specialist pushes back. "I don't have time to fill out a form. Can't you at least give me your personal read on it?"
You answer, "I understand the time pressure. I can't offer a personal read because that would blur into a promotional opinion, which isn't fair to you or accurate. What I can do is submit your question today if you give me the wording now, and let you know when to expect a response and from whom. That way you get an answer built on the full data set, not my recollection of it."
The specialist agrees and asks how the submission works. You explain the route, tell them roughly how long it takes, and confirm you will follow up personally to make sure it did not stall. Notice what did not happen. You did not guess at the answer. You did not promise a specific outcome. You did not treat the specialist's urgency as a reason to skip the process. You treated it as a reason to move fast within the process.
Mistakes to avoid
A few patterns show up again and again in these conversations, and each one causes real damage.
-
Answering the scientific question directly, even briefly, because it feels like the polite or helpful thing to do in the moment. This is the core violation the process exists to prevent.
-
Letting the specialist volunteer identifying patient details and continuing the conversation as if that did not happen. Stop the disclosure, and redirect to the general scientific question.
-
Promising what the eventual response will say, or hinting at a preferred answer through tone or body language. Your job is to protect the integrity of the channel, not to signal an outcome.
-
Treating the request as a nuisance and rushing the specialist off the phone. That reads as evasive and damages the relationship you need for future scientific exchange.
-
Failing to close the loop. If you submit the question and never confirm it moved, you have not actually helped the specialist and you have not built trust in the process.
How to practice and score it
This conversation is hard to get right the first time it happens for real, so rehearse it before it does. Set up a scenario where a clinician frames a question as hypothetical but slips in identifying patient details partway through, then pushes for an immediate answer when you try to redirect.
Score the rehearsal on three things. Did you stop the patient specific disclosure without making the clinician feel shut down. Did you keep the actual scientific question intact and route it properly rather than answering it or dodging it. Did you explain the follow up path clearly, including who owns it and roughly when to expect movement.
When you review the transcript or recording afterward, check the written record you would have produced. It should contain a factual scientific question and a named owner for the follow up. It should not contain a promotional comparison, a treatment recommendation, or any promise about what the eventual answer will say. A manager reviewing your rehearsal should be able to read that record cold and know exactly what was asked and what happens next.
DealSpeak lets you run this exact scenario against an AI counterpart that pushes back the way a real specialist does, then scores your handling against these criteria. You can find this and other rehearsal scenarios built for your role among the Pharmaceuticals practice conversations. If your team also handles patient support questions that touch process rather than pure science, Prepare Clinic Staff for an Authorization Expiry Workflow covers a related routing conversation worth the same kind of rehearsal.
Get the routing right and the specialist still gets a real answer, just through a channel built to protect its accuracy. Rehearse the pressure moment enough times and it stops feeling like a trap and starts feeling like a normal part of the job.
Practice these next
Prepare for a scientific advisory conversation with a clear scope and balanced evidence plan.
Provide dated references for a committee discussion without directing a protocol change.
Clarify a medical director’s request and coordinate balanced materials before a committee meeting.
Clarify an early study idea and explain the submission path without promising support or funding.
Capture a researcher's early scientific question clearly while avoiding a commitment about study support or protocol direction.
Clarify a literature question and provide an appropriate scientific information route without selectively building a clinical argument.