Review Unresolved Requests From a Health System Before They Age

An unresolved request from a health system rarely stays contained to the person who filed it. It gets mentioned in a staff meeting, repeated to a colleague, and eventually shows up as a complaint about your whole account team, not one slow ticket. As a key account manager, you are often the last person to learn that a request sat untouched for two weeks, because nobody inside your organization flagged it as urgent. A regular review of open items, done before the health system has to ask twice, keeps a small gap in ownership from turning into proof that your team does not follow through.

Why This Conversation Goes Wrong

Requests from a health system rarely land with a clear owner attached. A portal issue goes to a support queue. A pricing question goes to an inbox that three people watch and nobody actually owns. A formulary request gets forwarded to a medical science liaison who assumes someone else is tracking it. Each of these paths feels reasonable in the moment, and each one quietly removes the item from anyone's daily list. Two weeks later, the operations manager who filed the original request has no idea it stalled, and you have no idea it was ever open. When you finally hear about it, you are reacting instead of managing, and the conversation starts from a position of catching up rather than staying ahead.

The second failure mode is worse than silence. It happens when someone on your side reports a request as resolved before the work is actually confirmed. A teammate assumes a fix shipped because a ticket status changed, and you pass that assumption to the account as fact. When the health system finds out the issue is still live, you have not just failed to answer a request, you have given a partner a wrong answer with confidence. That costs more trust than an honest gap ever would.

How to Prepare Before You Call

Before you reach out to the account, pull every open item tied to that health system and sort it by four things.

1. The date the request was opened.
2. The need the partner actually stated, in their words, not a summary someone wrote for a ticketing system.
3. The internal owner currently assigned, if one exists.
4. Any dependency that is holding the item up, such as a pending decision, a technical fix, or information the health system still needs to provide.

Once you have that list, split it into two groups. The first group is requests that look open only because nobody confirmed receipt. These are the easiest to fix and you should close that gap the same day, even if the underlying issue takes longer to resolve. The second group is requests genuinely waiting on a legitimate review, a technical build, or a decision above your level. For that group, go to the internal owner before you go to the account. Ask two direct questions. What can be shared right now. When will the next verified update be ready. Do not accept a vague answer like soon or we're on it. Push for a date or a specific next step, and write it down before you pick up the phone with the health system.

This preparation step matters more than the call itself. A confident, accountable update to a partner is only as good as the internal fact behind it. If you skip the internal check and rely on memory or assumption, you risk repeating the exact problem you are trying to fix, a claim that turns out to be wrong.

What to Say on the Call

An operations manager at the health system opens with frustration that has been building for two weeks. "We flagged a problem with your provider portal two weeks ago, and nobody on your side has told us anything since. I don't even know if it's being worked on."

You do not defend the silence or explain why it happened. You acknowledge the gap and commit to something specific. "You should not have had to wait two weeks without an update, and I'm not going to guess at where this stands. I'll confirm the current owner today and get back to you by tomorrow afternoon with a verified next step, not a status I'm assuming is true."

You contact the internal service team that afternoon and learn the real holdup. The team needs a screenshot of the error to reproduce it, and nobody had asked the health system for one. You call the operations manager back with that exact fact. "Here's where it stands. Your team ran into an error our support team can't reproduce without a screenshot. I've set up a secure link where you can upload it directly, and once that comes in, they've told me they'll turn around a diagnosis within two business days." The operations manager now has a real reason for the delay, a concrete action to take, and a date to expect something back. That is a very different conversation than the one you started with.

Mistakes That Make the Gap Worse

Do not tell the account a request is resolved because a ticket changed status. Confirm the actual work before you report it as done. Do not promise a specific fix date unless an internal owner has committed to it in writing or in a conversation you can point back to. Do not let more than a few days pass between updates on a genuinely open item, even if the update is only that you are still waiting. Silence reads as neglect even when work is happening behind the scenes. Do not blame another internal team when you talk to the account. The partner does not care which department is slow, and naming names internally in front of them makes your organization look disorganized rather than accountable. Finally, do not treat this as a one time cleanup before a renewal or a business review. A health system remembers whether updates came consistently over months, not just before the meeting where you needed to look good.

How to Practice and Score This Conversation

A manager reviewing this conversation should listen for three things, a named internal owner, a specific date tied to a verified fact, and language that takes responsibility for the gap without over apologizing or getting defensive. Score the account manager down any time they use a vague timeframe like soon, or any time they state a fact about internal progress they have not personally confirmed. Score them up when they separate what they know for certain from what they are still checking, and when they give the partner a concrete next action rather than a general reassurance.

DealSpeak's practice conversations for pharmaceuticals let a key account manager rehearse this exact exchange against an AI counterpart that pushes back the way a frustrated operations manager would, and get scored on the specifics rather than the tone alone. You can find that full library through Pharmaceuticals practice conversations. The same discipline carries into related scenarios, including when you need to Map an Appeal Workflow Barrier With an Office Access Lead to find where a process actually stalls, or when you need to Clarify a Benefit Design Question Without Making Coverage Claims instead of guessing at an answer you have not confirmed.

Keep the Review on a Schedule

A single good call does not fix an ownership gap that will reopen next month. Put the request review on a recurring schedule, weekly for active accounts, so an item never sits long enough to become a complaint. The health system will judge your team on whether updates keep arriving on their own, not just on how well you handle the moment they finally ask.