Preparing a Practice for an Operational Process Change

A practice does not push back on an operational change because the change itself is a problem. It pushes back because nobody has told the staff what is changing, when it takes effect, or who to call when something breaks during a shift. As a provider relations manager, your job on this call is not to sell the change. It is to make the transition specific enough that a skeptical office administrator can build a plan around it.

Why This Conversation Goes Wrong

Most change notices fail for the same reason. The manager tries to calm the practice down instead of informing it. Reassurance sounds good on the phone, but it does not survive contact with a front desk that has lived through a bad rollout before. If a scheduling system update once caused two weeks of denied claims, a promise that this update will be fine does not land. It sounds like the same script that failed last time.

The second failure is scope. A provider relations manager who tries to answer every question, including ones about network terms or payment timing, ends up guessing. A guess stated with confidence is worse than admitting you do not know, because the practice will remember the guess if it turns out wrong. The fix is not to avoid hard questions. It is to sort them correctly the first time, so the right person answers each one.

There is also a trust cost that compounds over time. A practice that gets a vague answer once will treat your next notice with more suspicion, not less. Provider relations managers who show up with specifics, even when the specifics include limits on what they know, build a reputation that makes every future call shorter and calmer.

How to Prepare Before the Call

Before you say anything to the practice, gather four things. Pull the approved change notice itself, not a summary someone wrote from memory. Know the effective date and whether it is fixed or still subject to change. List the specific workflow steps the update touches, not the whole system, since most changes affect a handful of screens or fields, not everything the staff does. Identify who owns training on the new process and who handles support tickets after launch. Write down where the question log lives and who checks it, since a log nobody monitors is worse than no log at all.

You also need to know the practice you are calling. A single physician office with two front desk staff absorbs a system change differently than a group practice with a dedicated billing team. Ask ahead of time, or check your notes, on who does data entry, who handles denials, and whether the practice has weekend or evening coverage that needs the same materials. A generic notice sent to every practice on your list wastes the call. A notice matched to how that practice actually works is what makes the training useful. This kind of preparation applies across most Healthcare practice conversationsnot just process change notices, because practices respond better to specifics than to reassurance in almost every scenario.

What to Say on the Call

Omar, the office manager at a midsize practice, opens with the concern you expect. He says the practice heard the claims submission portal is changing next month, and he wants to know if his staff will need to redo work they already have queued up.

You answer with what you actually have. You say you can share the approved change notice today, and that it lists the specific steps in the submission process it affects. You say you want to walk through which of those steps his team uses most, so the training owner can build a session around their actual workflow instead of a generic walkthrough. You tell him that questions about contract terms or claim payment outcomes go to the authorized reviewers, not to you, and you will get those questions in front of them before the effective date.

Omar pushes further. He asks for a guarantee that nothing will be delayed during the switch. This is the moment most managers get wrong, because the honest answer feels weak compared to what the practice wants to hear. You say you cannot guarantee operational results, since you do not control how the new system performs on launch day. What you can guarantee is that his concerns reach the change team before the effective date, and that he has a named contact for support once the new process goes live.

Omar is not fully satisfied, and that is fine. He did not call to be satisfied. He called to know what is happening and to have a place to send problems when they show up. You gave him both.

Mistakes to Avoid

A few habits turn this call from useful into empty reassurance.

1. Promising outcomes you do not control, such as no delays or no disruption, instead of promising a process for raising problems.
2. Answering contract or payment questions yourself because the practice wants a fast answer, instead of routing them to whoever actually owns that decision.
3. Sending the same generic notice to every practice regardless of size or role mix, which makes the training that follows less useful.
4. Ending the call without a named owner for the practice's specific concern, so the issue has nowhere to go after you hang up.
5. Suggesting or implying that the process change affects network status, coverage, or payment rules when no authorized source has confirmed that connection.

Any one of these turns a routine notice into a promise you cannot keep, and the practice will hold you to it.

How to Practice and Score This Conversation

This conversation is easy to get wrong live and easy to fix in rehearsal. Run through it with a colleague playing a skeptical administrator, someone who pushes on guarantees and asks the questions you would rather not answer on the spot. DealSpeak is built for exactly this kind of rehearsal, since it gives you an AI counterpart that reacts the way a real administrator would, including the follow up questions that catch managers off guard. Run this scenario more than once, since a practice's questions change once early adopters share their own experience with the update, and your answers should keep pace with what the field is actually reporting.

Score yourself, or have your manager score you, on three things. Did you state only what the approved notice actually says, without adding reassurance that is not in the document. Did you capture a specific, actionable concern from the practice, not just a general sense that they were unhappy. Did the call end with a named owner and a next step the practice can point to if nothing happens. A call that hits all three turns a single conversation into material the training team can actually use, which is the point made in Turning Practice Feedback Into an Operational Improvement Loop. The same preparation habits carry over when the news is bigger, such as when you are Responding When a Practice Announces a Merger.

Close

A process change notice is not a sales pitch and it is not a script for reassurance. It is a short, specific conversation that tells a practice what changes, when, and where their questions belong. Get those three things right, and the practice absorbs the change instead of fighting it.