Working Through Authorization Friction With a Practice

A practice manager calls you frustrated because an authorization request has been stuck for days. She wants an answer right now, and she wants it from you. That pressure is real, but the fix does not live in your hands. Your job in this conversation is not to approve or deny anything. It is to find out exactly where the workflow breaks and hand that pattern to the team that can actually act on it.

Why This Conversation Goes Wrong

When someone in front of you is frustrated, the instinct is to make the frustration go away. For a provider relations manager, that instinct is dangerous. You do not sit on the authorization or utilization review team, and you do not have visibility into the clinical criteria behind a coverage decision. If you tell a practice manager that a request will get approved, or that a denial will get reversed, you have made a promise you cannot keep and put your organization at risk.

The conversation also goes wrong because the practice manager is usually not asking about policy. She is describing a symptom. A vague status message, a request that seems to vanish after submission, a portal that will not accept an update. Those are workflow problems, not coverage problems, and they deserve a real answer. If you treat every authorization complaint as a coverage argument, you will spend the call defending a decision you did not make, and the actual operational break never gets fixed.

There is a privacy dimension too. Once frustration builds, people start reading off patient names, dates of service, and clinical details to make their case. You need to redirect that instinct before it happens, not after.

How to Prepare Before the Call

Before you take a call like this, know three things cold.

1. Know who owns authorization and utilization decisions in your organization, and know that you are not that person. Say so plainly and early.
2. Know your intake path for workflow issues. If you cannot name the team or the process that receives these patterns, find out before the next call, not during it.
3. Know how to document an issue without any patient identifiers. You need the shape of the problem, not the specifics of a case.

Walk in expecting the practice manager to ask for an individual outcome. She has a real patient waiting and a real financial concern, so treat that expectation as normal, not as an attack. Your goal is to move from fix my case to here is the pattern, and you get there by asking specific, closed questions about where in the process the workflow actually breaks.

What to Say

Priyanka, an office manager, opens with the case. "Your system keeps sending my staff in circles on this authorization. Can you just approve it?"

Andre, the provider relations manager, answers. "I cannot make that call. Authorization decisions sit with the utilization review team, and I do not have the clinical information to weigh in even if I wanted to. What I can do is figure out where your team is getting stuck. Does the trouble happen when you submit the request, when you check the status, or when someone asks you for more information?"

Priyanka thinks about it. "Mostly the status. The messages we get back do not tell us anything. It just says pending, over and over, for a week."

Andre writes that down. "That is useful. I will pull a few examples of those status messages, with no patient details attached, and take the pattern to the person who owns the authorization workflow. They can tell us whether that message means something specific on their end and whether there is a faster way for your team to see real status. I will have an update for you by Friday."

Notice what Andre did not do. He did not guess at why the messages are vague. He did not promise the authorization would move faster. He named the actual owner, asked one clear question, and committed to a date.

Mistakes to Avoid

The most common mistake is arguing the merits of the authorization itself. The moment you start explaining why a delay might be reasonable, you have stepped into a decision that is not yours, and the practice manager will treat your opinion as the organization's answer.

The second mistake is accepting protected health information over the wrong channel because it feels faster than saying no. If a practice manager starts reading patient details over the phone or into a chat that is not built for it, stop her and redirect to your organization's approved intake method. This protects the patient and protects you.

The third mistake is closing the call with sympathy instead of a plan. Telling her you understand her frustration is not an answer on its own. A practice manager needs to know what happens next, who is doing it, and when she will hear back.

The fourth mistake is treating this as a one time fix instead of a pattern. If three practices report the same vague status message in one month, that is not three separate cases. That is one workflow defect, and it deserves to be reported as one issue with examples attached.

How to Practice and Score It

This exact call is hard to get right the first time, because the pressure to just say yes is strong and the phrasing that keeps you inside your role takes practice. Run it as a roleplay with a partner who plays a practice manager insisting that a delay proves a coverage decision was already made. Your job is to acknowledge the operational cost to her staff, restate the boundary in plain language, ask one focused question about where the workflow breaks, and close with a short issue record that names the step you observed, the examples you are requesting, the owner you are routing it to, and the date you will follow up.

A manager reviewing this roleplay should score three things separately. Did the representative avoid any language that sounds like a coverage opinion. Did the representative ask a specific enough question to actually locate the break, rather than a general request for more detail. Did the call end with a concrete next step instead of a vague reassurance.

You can rehearse this scenario directly inside DealSpeak's Healthcare practice conversations before you have to run it live with an actual practice. The related post Clarifying a Claim Submission Workflow Question walks through a similar boundary problem on the claims side, and Managing a Practice Conversation During a Claims Portal Outage covers what to say when the friction is a system outage instead of a status message.

Keep the Line Clear

Authorization friction calls test whether you can hold a boundary while still being useful. You are not the decision maker, but you are the person who can turn a frustrated phone call into a fixed workflow. Do that consistently, and practices learn to trust the process even when an individual answer takes longer than they want.