Create an Intake for a Request That Needs Several Teams

A chief pharmacy officer or health system leader will sometimes hand you one request that actually contains three or four separate problems, mixing operations, medical evidence, and service issues into a single ask. As a key account manager, your first job is not to solve any of them. It is to break the request apart, assign each piece to the right owner, and give the account one coordinated plan instead of a vague promise to look into it.

Why this conversation goes wrong

A busy account leader is not going to organize the request for you. They hand you a full list of concerns and expect you to sort it out. If you try to answer everything yourself, you end up giving a half answer on a topic outside your role, and a wrong or incomplete answer from you carries the same weight to the account as an official one. If you route the whole thing to a single internal team, you slow down the parts that could be answered today. If you ask too many clarifying questions before showing that you understood the point, the leader feels like you are stalling instead of helping. The account does not see your internal team structure. They see one relationship, and if that relationship produces confusion, they remember it as your failure, not as a coordination problem that three departments actually share.

How to prepare before you respond

Before you say anything back, do three things. First, restate each distinct question in the words the account used, not in internal shorthand. If the officer says recurring portal issue, write it down as stated, not as system access ticket. Second, sort each question by the team that owns it, commercial, medical, or service, and note who the accountable person is today, not just the name of the department. Third, figure out which items are urgent this week and which can wait for a scheduled follow up. Do not guess at urgency. Ask directly.

You also need to know your own limits before the conversation starts. A medical question needs an approved medical resource, not your own summary of a study, even one you know well. A pricing or access question needs the right owner on the commercial side. A service issue often already has an escalation channel that works faster than a generic ticket. If you do not know who owns a topic, say so plainly rather than inventing an answer on the spot. Guessing wrong here costs more trust than admitting you need to check.

What to say

Here is a fictional exchange that shows the shape of this conversation. A chief pharmacy officer opens with a mixed request, saying, "I need help on three things, staffing support for our infusion clinic, a question about the evidence behind the new dosing protocol, and a portal problem that has been going on for weeks."

You respond by separating the request out loud instead of answering any one part yet. "Let me split those apart so each gets the right person. Of the three, which one is actually blocking your team this week, and who on your side should get updates on the other two."

The officer answers, "The portal issue is causing daily problems. The other two can wait a bit, but I want someone accountable for them too."

You confirm the plan back in plain terms. "Here is what happens next. I am opening a service escalation today for the portal issue, and that team will contact you directly. I am also logging a request for a medical resource on the dosing question and a request for approved materials on staffing support, and I will send you a written summary today with an owner and a next checkpoint for each item."

That exchange does three things. It separates the request into parts, it confirms which part is urgent instead of assuming, and it closes with a commitment the officer can hold you to.

Mistakes to avoid

The most common mistake is answering the easy sounding question yourself because you happen to know something about it. If a question belongs to medical or access teams, send it there even if you could offer a rough answer. The account will not distinguish your rough answer from a formal one, and if it turns out wrong, they remember you as the source.

The second mistake is folding everything into one generic meeting. A single meeting with three unrelated owners and no stated purpose wastes the leader's time and makes the account feel like their request was passed along rather than handled.

The third mistake is skipping the written summary. A verbal plan sounds solid in the room and gets forgotten within a day. Send a short note that lists each question, its owner, the route it took, and the date the account should expect an update. This is the same discipline described in Coordinate Duplicate Requests From One Accountwhere the core skill is also keeping separate requests from blurring into one blob of work.

The fourth mistake is treating urgency as your own call to make. Ask the account which item is blocking them right now. Do not assume the scientific question outranks the operational one just because it sounds more serious on paper.

How to practice and score it

A manager can build this into a short roleplay. Give a representative one paragraph that hides three or four distinct requests inside normal sounding complaints, then ask them to sort it out loud in real time, without notes prepared in advance. Score the attempt on four points. Did they restate each question in the account's own words. Did they ask which item was urgent instead of guessing. Did they name an accountable owner for every item, not just the urgent one. Did they close with a specific next step instead of a vague promise to follow up.

This is also a good scenario to rehearse against an AI counterpart that plays a demanding account leader and pushes back when your plan sounds vague or incomplete. Running this scenario on Pharmaceuticals practice conversations lets a key account manager repeat it with different mixes of requests until separating them becomes automatic instead of something you have to work out mid conversation. DealSpeak scores each attempt against the same points a manager would use, so you get direct feedback on which part of the split you skipped.

The same discipline applies when a leader's question drifts into territory you should not answer alone, such as patient outcomes. The reasoning in Answer an Executive's Question About Patient Outcomes Responsibly is worth reviewing alongside this scenario, since both come down to knowing what is yours to answer and what belongs to someone else.

Close

A mixed request is not one problem, it is several problems wearing one coat. Your job is to take that coat off, name what is underneath, and hand each piece to the person who actually owns it. Do that well, and the account leaves the conversation with a plan instead of a promise.