Coordinate Duplicate Requests From One Account
Bring overlapping questions into one account conversation without suppressing the expertise each request needs.
A hospital account can generate three or four separate email threads in the same week, one to sales, one to medical affairs, one to patient support, one to market access. Each contact answers only the piece in front of them, with no idea the others are running similar threads at the same time. As the key account manager, you are usually the first person to see the whole pattern, and closing the gap well means pulling the requests into one clear view without pretending you can answer questions that belong to a different expert.
Why This Conversation Goes Wrong
Duplicate requests happen because pharmaceutical accounts are large and organized by function, not by vendor relationship. A pharmacy director, a quality lead, and a clinical champion at the same hospital can each reach out about the same formulary decision without knowing the others did too. Left alone, this produces one of two bad outcomes. Either you try to answer everything yourself to look responsive, and end up giving a clinical opinion that should have come from medical affairs, or you say nothing and let each department reply on its own, so the account gets three partial answers that never add up to a full picture. Both outcomes cost trust. The account starts to wonder whether anyone on your side actually knows what is happening across the relationship, and every future question comes in three times because that has become the pattern that gets a response. This also spikes during organizational change. If you have handled a health system merger before, you already know how fast new stakeholders start asking the same question through different doors, a pattern covered in detail in Remap Stakeholders After a Merger of Health Systems.
How to Prepare
Before you contact the account, build a simple map of every open question. List who asked it, which internal function owns the answer, and whether it connects to a shared deadline like a formulary review or a contract renewal date. Check with each internal owner what has already been sent, so you do not propose a consolidated update that contradicts an answer already sitting in the account's inbox. Decide what you are asking the account to do. You are not asking them to stop reaching out to different contacts, you are asking them to help you route the questions so each one reaches the right expert without three people answering the same thread. Have a clear line ready for what you will and will not do yourself. You can own scheduling, status, and consolidation. You cannot answer a scientific or clinical question on behalf of a medical science liaison or a clinical pharmacist, even if you know the answer, because that response has to come through an authorized channel and be documented that way.
What to Say
Open by naming the problem plainly instead of asking the account to explain it again. You tell the hospital liaison, "I noticed your team sent similar questions to three of us this week, and I want to make sure none of them get lost or answered twice. Can I map what came in and send back one agenda showing who owns each item?" The liaison responds, "That would help. We received three different follow ups and none of them answered the whole question." You reply, "That is a coordination failure on our side, and I want to fix it before it happens again. Once I send the agenda, who on your team should confirm the plan works, so we are all working from the same page?" The liaison names a pharmacy manager. You close the loop by separating the items instead of collapsing them, "I will group the operational and contracting questions under one status update from me, and I will arrange a direct answer to the clinical question through our medical team, since that one needs to come from them." Notice what that last line does. It keeps the coordination role with you and keeps the clinical answer with the person authorized to give it, so the account gets speed on the parts that can move fast and accuracy on the part that cannot.
Mistakes to Avoid
- Do not answer a clinical or scientific question yourself just because you know the answer. Route it, even if that adds a day to the response time.
- Do not consolidate the account's questions before checking with your internal colleagues about what they already sent. You will contradict someone and make the confusion worse.
- Do not promise a single deadline for all the questions when they do not share one. Ask the account directly which items are tied to their decision date and which are not.
- Do not let the account keep doing the coordination work for you by chasing three people on their own. If you spot duplicate threads, say so before they have to point it out.
- Do not close the conversation without naming who confirms the plan on the account side. Without that, your consolidated agenda has no owner and nothing changes next time.
How to Practice and Score It
This is a skill you can rehearse before it costs you real trust with an account. Pull four fictional emails that overlap in subject but were sent to different functions, then practice identifying which questions are duplicates, which are distinct, and which require a specialized answer you cannot give yourself. Score the attempt on whether the manager consolidates status without flattening different question types into one generic reply, and whether the closing summary names a preferred contact, an owner for each question, and a next communication date. A manager reviewing this with a team can watch for the same failure modes described above, especially the habit of answering a clinical question just to move the conversation along. DealSpeak's Pharmaceuticals practice conversations include this scenario alongside related ones, including how to Answer an Executive's Question About Patient Outcomes Responsiblywhich draws the same line between what a key account manager should own and what belongs to a specialist.
Close
Coordinating duplicate requests is not about intercepting every question that comes to your account. It is about giving the account one clear route to each answer while keeping the right expert attached to the right question. Get that balance right and the account learns it can send you one question instead of three, which is the outcome you actually want.
Practice these next
Create a clear review rhythm when an account reports repeated service issues across more than one team.
Help a director for a service line describe staff burden before coordinating approved resources.
Create one focused agenda when a hospital liaison is tired of overlapping vendor meetings.
Give a clinic operations leader accountable follow-up when support responses seem inconsistent.
Earn a new planning conversation by listening for system priorities and coordinating one clear purpose.
Use a request review to surface ownership gaps and give a partner in a health system a clear update.