Coordinating a Health System Reference Conversation Respectfully

A health system evaluating an expansion often wants to hear from someone who already lives with your device in their facility. That request usually lands on your desk fast, and it carries an assumption that you can just make it happen. You cannot. The reference site is a customer too, with its own schedule, its own staff, and its own limits on what it will share. Your job is to run this conversation so the requester gets a useful answer and the reference site never feels used.

Why This Conversation Goes Wrong

Most account managers stumble here because they treat the reference request as a task instead of a negotiation between three parties. The prospect wants proof, right now, from a peer who looks like them. You want the deal to move. The reference site wants none of the pressure that comes with either of those goals. When you promise a date before you ask, you put your own credibility on the line against a schedule you do not control. When you let the requester dictate exactly who they talk to and what they ask, you risk exposing operational details the reference site never agreed to share. And when the site says no, and it will happen sometimes, you have nothing prepared to tell the requester except an apology, which reads as a stall.

The pressure compounds because urgency is baked into the ask. An operations executive who is close to a budget decision does not want to wait a week for you to check with someone else. They want a name and a date. Giving them either before you have real permission is the fastest way to burn a reference relationship you will need again next quarter.

How To Prepare Before You Ask

Write a short brief before you contact the reference site. Note who is asking, what decision the reference call needs to support, and the specific questions the requester wants answered. List who should attend from both sides. Mark clearly which parts of your brief are approved for sharing and which are still pending consent from the reference site.

Do not describe the reference site's environment, volume, or results to the requester until the site has agreed to those details being shared. A reference organization that let you mention their patient volume last year has not automatically agreed to it again this year, especially if their staff or leadership changed. Ask each time.

Send your manager the brief before you reach out. Ask them to check every sentence against one test, is this approved, or is it still pending. That single check catches most of the damage before it happens. It also matches the discipline account managers use in other sensitive conversations, like sitting down for Running a Risk Register Review for a Complex Device Accountwhere you are again speaking about commitments and information that belong to someone else's account, not just your own.

What To Say

Here is a realistic exchange showing the shape of this conversation.

The operations executive says, "You know a site like ours. Set up a call this week."

You reply, "I can request a reference conversation and share the topics you want to cover. The reference organization has to approve the participation and the timing, so I cannot commit to a date yet. Send me your top three questions, and I will make the request with a focused agenda today."

The executive pushes back. "We are trying to close this by the end of the month. Can you at least tell me it will happen?"

You answer, "I understand the timeline, and I will move on this today. What I can promise is a status update by Wednesday, either a confirmed call or a clear next step if the site cannot host one this month. I do not want to give you a date I cannot keep."

Notice what happens in that second reply. You do not fold under the deadline pressure, and you do not pretend you have more control than you do. You give the executive something concrete, a date for an update, instead of a date for a call you have not secured.

Mistakes That Cost You The Reference

The most common mistake is promising a date before you have permission. It feels helpful in the moment and it damages you twice, once when the site cannot meet that date, and again when the requester remembers you overpromised.

A second mistake is sharing information about the reference site's operations, results, or challenges without checking each time. Approved once does not mean approved always. Treat every reference request as its own permission event.

A third mistake is letting the requester run the call without a plan. An open ended conversation where the requester asks whatever comes to mind can drift into territory the reference site never agreed to discuss, staffing levels, cost details, internal complaints. Bring a short list of approved topics to the call and keep the conversation inside it.

A fourth mistake is going back to the same reference site every time you need one. That organization has a business to run. If you call on them for every deal in the region, they will start declining, and you will have burned a resource the whole team depended on. Rotate references and keep a record of who has been asked recently.

Finally, if the site declines, do not go quiet. Tell the requester the outcome plainly and offer the approved next step, another site, a written case summary, or a call with your own implementation team. Silence reads as avoidance even when the real reason is a legitimate scheduling conflict.

How To Practice And Score This

This conversation is hard to get right the first time you face real pressure, so rehearse it before you need it. Have your manager play the impatient executive and push you toward a date you cannot deliver. Notice whether you hold the line calmly or start negotiating away your own conditions.

Score yourself, or have your manager score you, on a few specific things. Did you avoid naming the reference site or describing its operations before permission was confirmed. Did you give the requester a concrete next step instead of a vague reassurance. Did you stay calm when the executive pushed on the timeline, or did you start making promises to end the discomfort.

DealSpeak is built for exactly this kind of rehearsal. You can run the scenario against an AI counterpart that plays the impatient executive, get scored on how you handled the permission boundary, and try it again until the calm, specific version becomes your default response. You can find this scenario and others built for account managers in medical devices through Medical Devices practice conversationsalongside related situations like Handling a Health System Device Security Questionnairewhere the same rule applies, confirm before you commit, and never speak for information that is not yours to share.

The Point

Protecting the reference site's permission is not bureaucracy, it is what keeps references available at all. A requester who gets a clear process and a real update trusts you more than one who gets an empty promise. Handle this conversation well once, and the next reference request gets easier for everyone involved.