Giving a Practice One Owner for an Escalation

A practice that calls four times about the same enrollment problem and gets four different answers is not just annoyed about the delay. The practice is annoyed because nobody has claimed the problem as their own. Every provider relations manager runs into this moment sooner or later, and how you handle it decides whether the practice trusts your process again or assumes every future call means fighting for attention.

Why This Conversation Goes Wrong

When a request bounces between departments, each person who picks it up treats it as a brand new case. The practice repeats the same story to a new voice every time, and nobody carries the history forward. By the time the call reaches you, the administrator on the other end is not really asking about enrollment anymore. They are asking whether anyone in your organization is actually tracking this at all. If you respond with another generic reassurance, you confirm their fear. If you try to solve the underlying enrollment or payment question yourself, you step into territory that belongs to claims, credentialing, or contracting, and you risk giving an answer that gets reversed later. The real failure here is structural, not personal. Nobody assigned a single owner to the issue, so it lives nowhere and everywhere at once, and the practice pays for that gap with their time. This pattern shows up across many Healthcare practice conversationsnot only in enrollment disputes, wherever an issue crosses more than one internal team.

Prepare Before You Respond

Before you get on the call or answer the message, build a short factual record. Pull every prior contact with its date, the reference number if one exists, and the exact step where the process stalled. You want a tight paragraph, not a full file. Note what has already been said to the practice, so you do not repeat a promise that already fell through once. Identify the operational team or queue that actually owns this type of request, not just a general department name that sounds close enough. If you cannot name a specific owner, find out who can before you speak with the practice again. Decide in advance what you can commit to and what you cannot. You can commit to logging the issue, confirming ownership, and giving a date for the next update. You cannot commit to a payment outcome, a coverage determination, or a contract interpretation, because those decisions sit with teams that have the authority and the full record to make them. Keep those two categories separate in your head before the call starts, so you do not blur them once the practice applies pressure.

What to Say

Priya, a practice administrator, opens with the complaint you expected. "We have called four times about this enrollment issue," she says. "Every person tells us to start over." Do not defend the prior calls or explain why the handoffs happened that way. Acknowledge the specific pain first. "I hear that having to explain this from scratch every time is the real problem," you say. "I am going to log the four prior contacts, confirm which team owns this request, and give you one contact for the next update." That sentence does three concrete things. It shows you took notes, it names a next step, and it takes the job of tracking your internal routing off the practice's plate.

Priya pushes further, because she wants more than process. "Will the practice get paid for the services affected by this delay," she asks. Resist the urge to guess or to soften the answer with a hopeful tone. "Payment and coverage decisions go through the review process built for that," you say. "My job right now is making sure this workflow problem reaches the right owner with enough detail that they can actually investigate it, instead of asking you to start over again." Priya may not love that answer, but she can trust it, because it is honest about what you control and what you do not.

If she asks for a timeline, give her a real one. "You will hear from the assigned owner within two business days," you say, "and if that date slips, I am the one who calls you, not the other way around." That last part matters more than it sounds. Practices stop trusting update promises the moment they have to chase the update themselves.

Mistakes to Avoid

A few habits turn this conversation from a save into another entry in the practice's complaint file.

1. Speculating about payment, coverage, or contract outcomes to make the practice feel better in the moment. It feels kind, and it backfires hard the moment the real answer turns out different.
2. Naming a department or a person as the reason for the delay. The practice does not need a scapegoat, it needs a fix, and internal blame talk makes you look defensive instead of in control.
3. Promising a specific resolution date you do not control. You can commit to an update date. You cannot commit to when claims or credentialing will finish their review.
4. Treating the call as closed once you hang up. If you said you would follow up in two days, put that on your own calendar immediately, because the practice is watching whether your word matches your action.

How to Practice and Score It

This is a skill you build through repetition, not something you get right on instinct the first time a hard call lands on your desk. Set up a mock scenario with a timeline that has gaps and conflicting notes, the kind of messy record a real escalation actually produces. Ask the trainee to read it once, then summarize the issue out loud in one paragraph, name a single accountable owner, and state a specific next update date. Do not let them narrate the full history back to you. If they cannot compress it, they have not actually understood it yet.

Score the response against three questions. Would this summary stop the practice from having to repeat their story again. Did the trainee name one owner instead of a department or a shrug. Did the trainee avoid making any promise about payment, coverage, or contract terms. A manager reviewing this exercise should also listen for tone, because a flat, procedural read of the right words still sounds like another department passing the practice along.

DealSpeak gives you a way to run this drill against an AI counterpart that pushes back the way Priya does, asks the payment question you are tempted to answer, and scores whether your response actually names an owner and a date instead of drifting into vague reassurance. Running the same scenario several times, with the difficulty varying, builds the muscle you need before a real practice administrator is on the line testing your patience for the fourth time in a month.

Two related situations are worth practicing alongside this one. The piece on Investigating a Practice's Repeated Fax Routing Failure covers a parallel operational escalation where the fix again depends on naming one owner, and the piece on Clarifying Network Status Questions From a Practice covers a related boundary problem, where the practice wants an answer that only another team is authorized to give.

Close

An escalation stops being painful the moment one person owns it out loud. Your job is not to solve the enrollment problem yourself, it is to make sure the problem cannot get lost again. Get that part right, and the fourth call becomes the last one the practice ever has to make about it.