Clarify a Transportation Resource Request Without Booking a Ride

A patient on the phone is worried about getting to an infusion appointment, and asks the liaison to just book the ride. That single ask sits right on the line between practical support and a service the program does not offer. Handling it well means giving the patient something real to act on, without stepping into a role that belongs to a transportation vendor or the clinic.

Why This Conversation Goes Wrong

The instinct to help is strong, and that is exactly the trap. A liaison hears real worry in a patient's voice and wants to solve the problem on the spot. So the call drifts into territory it should not touch. The liaison starts describing a ride service as though it is guaranteed, or says something like I will get that set up for you, when the program only refers patients to outside resources it does not control.

The same drift happens with scheduling. A patient mentions they might need to move their appointment because of the ride problem, and the liaison, trying to be useful, starts weighing in on whether that is a good idea. That decision belongs to the clinic, not to a support liaison. Once the conversation strays into scheduling or care advice, the liaison has taken on risk the program never assigned.

Vague language creates a second problem. If a liaison says something like there is a ride program that should be able to help, the patient hears a promise. When the outside vendor cannot serve that patient's zip code, or the application takes longer than expected, the patient feels misled, and the complaint lands back on the liaison who made it sound simple.

How to Prepare

Read the current program materials before you take these calls, not after a patient stumps you. Transportation resources change. A vendor that covered a region last quarter might not this quarter, and eligibility rules for mileage reimbursement or ride vouchers get updated more often than people expect. Know which resources are fully approved, which require an application or referral, and which are still under review internally. Those are three different answers, and mixing them up is how a liaison ends up overpromising.

Have the actual contact information ready, not a general sense of where to find it. A patient in a stressful moment does not want to be told to check the website later. They want a phone number, a form, or a name, something concrete before the call ends.

Also decide ahead of time how you will talk about the clinic's role. If a patient raises the idea of rescheduling because of transportation trouble, your job is to point them to the clinic scheduling line, not to weigh in on whether rescheduling makes sense. Keep that boundary clear in your head before the phone rings, so you are not improvising it live. This same discipline, describing what is available without stepping into a clinical or scheduling decision, shows up in Set a Support Boundary When a Patient Asks What to Takewhere the risk is a treatment question instead of a logistics one. The underlying skill is the same, stay inside the resource lane and hand off the rest.

What to Say

Start by finding out what kind of help the patient actually wants. A general list of transportation resources is a different request than an eligibility question for a specific approved service, and both are different from wanting the clinic's scheduling number. Asking first saves you from a long explanation the patient did not need.

The patient says, Can you just book a ride for me? I have an appointment Thursday and no way to get there.

The liaison says, I cannot book transportation directly, but I can walk you through the approved resources our program lists and get you the right contact for logistics. Would it help more to have the general resource list, or the clinic's scheduling contact in case Thursday needs to move?

The patient says, The resource list, I think. My daughter might be able to drive me too, but I want a backup.

The liaison says, That makes sense. I will send you the current list of approved transportation resources, including which ones need an application ahead of time. One note, I cannot confirm whether a specific service is available in your area, that comes from the provider directly once you contact them. Is the phone number and address on file still the best way to reach you?

Notice what the liaison never does. No promise that a ride will show up. No opinion on whether the daughter should drive instead. No comment on whether Thursday's appointment should change. The liaison hands over one clear resource and one next step, and leaves the rest to the people who actually control it.

Mistakes to Avoid

Do not describe an outside resource as though the program guarantees it. Saying our ride program will pick you up sets an expectation the liaison cannot back. Say instead that the resource is available for patients to apply to or contact, and let the vendor confirm the details.

Do not answer scheduling questions. A patient asking if they should push their appointment back is asking a clinical logistics question, and that belongs to the clinic. Redirect it every time, even when the liaison has a strong personal opinion about what makes sense.

Do not let the call end without a concrete next action. Vague reassurance, like someone will follow up with you, leaves the patient with nothing to hold onto. End with one resource and one contact method instead.

Do not overload the patient with every possible option. A patient dealing with transportation stress does not need five resources read aloud. Pick the one or two that fit the person's stated need, and offer more only if asked.

Do not collect or discuss unnecessary medical detail while sorting out a logistics question. The call is about a ride, not about the patient's treatment plan or condition. Staying on topic protects the patient's privacy and keeps the call focused.

How to Practice and Score It

A manager running a team huddle can turn this into a short role play with two variations, one where the patient just wants information and one where the patient pushes back and asks the liaison to just handle it. The second version is the one that matters, because it tests whether the liaison holds the line under mild pressure.

Score the call on three things. Did the liaison correctly identify what type of help the patient wanted before launching into an explanation. Did the liaison avoid promising availability, scheduling advice, or medical input at any point in the call. Did the call end with one specific contact and one specific action, rather than a vague assurance.

Some teams run this kind of scenario through Pharmaceuticals practice conversationswhere a liaison can rehearse the exchange with an AI patient that pushes back the way a real caller might, and get scored against those same three points. Repetition matters here more than any script. The wording will vary call to call, but the boundary should not. For a broader look at building this kind of practice into onboarding or team training, see Design a Nonclinical Workflow Review for Office Staff.

Closing Thought

A transportation request feels small next to a medical conversation, but it carries its own risk when a liaison promises more than the program can deliver. Stay inside the resource lane, name the exact next step, and let the clinic and the outside vendor own the parts that are theirs. That is the whole skill, and it holds up under pressure once you have practiced it a few times.