Resetting a Practice Relationship After Portal Training Friction

A practice manager calls you frustrated the day after a portal training session that was supposed to fix things and did not. Staff sat through the material, followed along, and still cannot do the one task that matters most to their day. That frustration lands on you because you are the person they know at your organization, even though the training itself may have come from a separate team. What you do in the next ten minutes decides whether this practice trusts your team enough to raise the next problem calmly, or starts working around the portal and stops telling you what breaks. Treating this as a specific operational gap instead of a complaint to smooth over is what separates a manager who fixes the relationship from one who just delays the next blowup.

Why This Conversation Goes Wrong

Portal training usually ships as one generic session covering every screen and every role. A front desk coordinator and a billing specialist do different work in the same system, and a single walkthrough rarely maps to either job well. When someone hits a wall on the one task they actually do every day, they do not file a precise bug report. They generalize. Training does not work. The portal is broken. We are done with webinars. That reaction is not exaggeration, it is what frustration sounds like when someone has already lost time they needed for patient work.

The provider relations manager often makes it worse by trying to soothe the emotion instead of isolating the task. Offering another webinar to make the call end well repeats the exact failure that caused the complaint, because the practice already told you a generic session did not help. Guessing at a technical cause and promising a fix is just as risky, since you have no way to know yet whether this is a training gap, a workflow mismatch, or an actual system defect. The staff on the other end are usually already stretched thin, and one blocked task can cost them real time every single day until someone closes the loop.

How to Prepare Before You Sit Down

Before the call, pull the training material the practice actually received and confirm the version and the date it was sent. Find out who is raising the complaint and what their role is, since a scheduler and a claims specialist will describe the same portal completely differently. Identify who owns portal support on your side, so you are not promising to personally diagnose a system issue you cannot see into.

Walk in planning to ask questions, not give answers. Your job in this call is to extract one concrete task, the exact point where it stalls, and what confirmation the staff member expects to see when it works. If patient information could come up while describing the problem, know your approved access and privacy procedure in advance. Never ask a practice to send screenshots containing patient data through ordinary email. If you handle rollouts like this often, the article on Preparing a Practice for an Operational Process Change covers the earlier stage of this same relationship, before training friction even starts.

What to Say

Priya, an office manager, opens the call already frustrated. She says, "We sat through the entire training, and my staff still cannot tell if a submission actually went through. We are done with webinars."

Marcus, the provider relations manager, does not defend the training or offer another session. He says, "I hear that the session did not solve the task your team needs every day. Walk me through exactly where they get stuck, using one real submission as the example."

Priya says, "They enter the claim, hit submit, and then have no way to know if it was received or if it is just sitting somewhere unprocessed."

Marcus answers, "That is specific enough for me to act on. I will bring this to portal support and ask them to walk through that status step directly with your staff. Let's agree on one test submission this week, and I will confirm who on your side signs off that the new instructions actually work."

Notice what Marcus does not do. He does not claim the portal has a defect before support has looked at it. He does not accept a vague complaint as the final word. He turns an emotional statement into an operational one, then names an owner, a task, and a way to confirm success.

Mistakes to Avoid

The most common mistake is scheduling another broad training session just to end the call on a positive note. That tells the practice you were not really listening to what they said. A second mistake is guessing at a technical cause and promising it will be fixed before anyone with access to the system has confirmed there is a system issue at all. If you are wrong, you have now made a promise you cannot keep, and the next complaint will come in twice as hot.

A third mistake is accepting vague language like the portal is broken without pushing, gently, for the specific task and screen. Vague complaints cannot be routed to anyone, so they die in your inbox and the practice notices nothing changed. A fourth mistake, and a serious one, is handling any description involving patient information outside your approved channels, even informally over email or chat because it feels faster in the moment. Last, do not get defensive about the training team's work. Your job in this call is not to protect a colleague's slide deck, it is to solve the practice's problem.

How to Practice and Score This Conversation

This conversation is hard to get right the first time you try it live, so rehearse it before you need it. Ask a colleague to play a frustrated practice contact and describe a failed task without naming the exact screen or button. Your job is to extract the user's goal, the exact stopping point, and what confirmation they expect to see, then state a training request specific enough for a support owner to act on immediately.

Score yourself, or have someone else score you, on a few concrete things. Did you ask for one real task instead of accepting a general complaint. Did you avoid promising a fix before the right owner had looked at it. Did you name a specific next step, an owner, and a timeframe before ending the call. Practicing this kind of exchange is exactly what DealSpeak is built for, since it scores whether you actually pulled out the specific breakdown or just let a vague complaint pass. The Healthcare practice conversations hub has more scenarios like this one if you want to build the skill across other friction points, not just training.

Closing

A frustrated practice is not a lost one. It is a signal telling you exactly where to send your next escalation, if you take the time to translate the complaint into a task. Handle this moment well and you can build on it, turning individual friction points into a real process using the approach in Turning Practice Feedback Into an Operational Improvement Loop.