Investigating a Practice’s Repeated Fax Routing Failure

A practice calls to report that faxed documents keep landing in the wrong place. This is the third time. The staff are frustrated, patient information may be involved, and nobody on your side has confirmed whether the problem sits with the practice's directory listing, your vendor's transmission system, or an internal routing rule. This conversation goes wrong fast when a provider relations manager tries to diagnose the cause on the call instead of building a clean record for the team that actually owns the fix. Handled well, the same call becomes the moment the practice decides whether they trust your operation again.

Why This Conversation Goes Wrong

Repeated fax routing failures are not just an annoyance. For a practice, a misrouted fax can mean a delayed referral, a missed authorization, or a document that never reaches the right desk before a deadline. By the time someone calls you, they have already told a colleague, checked the number twice, and decided the problem is on your end. They are not looking for sympathy. They want to know it will stop.

Provider relations managers often make the mistake of trying to solve the problem live. You start guessing whether it is a directory issue or a vendor issue, the practice hears uncertainty, and the call turns into a debate about whose system is broken. Or you go the other direction and over promise, telling the practice every missing document will be recovered and the issue is fixed by tomorrow, a promise you cannot back up because you have not seen the routing logs yet. Either mistake costs you credibility. The goal of this call is narrower than most managers think. You are not there to diagnose. You are there to capture the pattern accurately, hand it to the right owner, and give the practice a single point of contact until it is resolved.

How To Prepare Before You Pick Up The Phone

Before you respond to the practice, get clear on what you actually need from them and what you do not. You need the destination number or address that was used, the dates the failures occurred, and whether the practice received any error notice from their own fax system. You do not need the full content of the documents, and you do not need more patient detail than the investigation requires. Asking for extra patient information beyond what the routing review needs slows the practice down and raises a privacy question you do not want to create.

Check your own systems before the call if you can. Look at whether the practice's contact record was recently updated, since a stale directory entry is one of the most common causes of this exact complaint. Know who on your operations or IT side handles routing escalations, because you will want to name that team on the call rather than saying "someone will look into it." If your organization has a secure channel for submitting redacted examples, know the exact steps so you can walk the practice through it without fumbling.

This kind of preparation matters more in healthcare than in most other industries, because the practice is often juggling several outside relationships at once, payers, referral partners, technology vendors, and you. If you want a broader sense of how these conversations differ from other network questions a practice might raise, the Healthcare practice conversations hub covers the range of situations a provider relations manager handles, and the piece on Clarifying Network Status Questions From a Practice walks through a related scenario where the practice is confused about status rather than a technical failure.

What To Say

Open by acknowledging the pattern without guessing at the cause. Dana, a practice manager, says, "This is the third time this month. Two notices went to our old fax line even though we updated it with your team weeks ago." Your first job is to get specific and stay calm.

You respond, "I want to get the exact dates and the number that appeared on those notices so our operations team can trace where the routing broke. Can you send those through our secure submission line rather than reading the patient details to me directly? I will own getting this in front of the right team and come back to you with an update." Notice what this sentence does. It asks for the minimum information needed, it names a next step, and it puts a person, you, behind the follow up.

Dana asks, "How do I know the next one will actually go to the right place?" This is the question every practice asks, and there is no shortcut past it. You say, "I cannot confirm the fix until the review team traces where the routing broke, whether it is the directory entry, our vendor's system, or something internal. What I can tell you is that you will have one contact, me, until they do, and I will update you by Thursday even if the cause is still open." That last part matters. You are not promising a fix on a timeline you do not control. You are promising a specific update, on a specific day, from a specific person. If the practice pushes further and asks whether their patient care has been affected, answer directly. Say you do not have that information yet and that the review will surface it, rather than guessing to fill the silence.

Mistakes To Avoid

Do not speculate about which system failed. Naming a directory problem, a vendor issue, or an internal routing bug before the review team confirms it puts you on record with a guess that might be wrong, and practices remember which guess turned out false.

Do not ask for more than the investigation needs. Requesting full patient records or reading document contents over the phone when a redacted reference or a date and destination number would do the job creates unnecessary risk and unnecessary friction.

Do not promise recovery of every historical document. Some faxes sent to a wrong number are simply gone, and telling a practice otherwise sets up a second disappointment on top of the first.

Do not leave the update point vague. "We will look into it" gives the practice nothing to hold onto. A specific day and a specific person gives them something concrete, even when the underlying cause is still unresolved.

How To Practice And Score It

This conversation rewards a narrow set of behaviors, and you can train for them directly. Run the scenario as a role play where the counterpart plays an increasingly frustrated practice manager and pushes on the same questions Dana asked. Score yourself, or have a manager score you, on four things. First, did you capture the specific pattern, the destination, the dates, and any error notice, instead of accepting a vague complaint. Second, did you avoid naming a cause before the review team confirmed one. Third, did you request only the information the investigation actually needed. Fourth, did you give a concrete next update with a name and a date attached to it.

DealSpeak is built for exactly this kind of rehearsal, letting you run the fax routing scenario against an AI counterpart that reacts the way a frustrated practice manager would, then scores your handling against those same four points. Running it more than once matters, because the second and third pass is where you notice you are still hedging on the update point or still tempted to guess at the cause. If you manage a team, having each provider relations manager run this scenario before they take a live version of it catches the over promising problem before a real practice hears it. For a related situation where the friction comes from a training gap rather than a technical failure, see Resetting a Practice Relationship After Portal Training Frictionwhich covers a similar approach to owning a problem without over committing to a fix you cannot control.

A repeated fax routing failure is a trust problem wearing a technical costume. Handle the call by capturing the pattern, naming an owner, and committing to a real update, and the practice walks away believing the process will work even before the cause is found.