Pylon vs Plain: A Runbook for a PT Network's Referral Queue

A referral from a physician's office is the closest thing this business has to a sales lead, and it behaves like one: the longer it sits unacknowledged, the more likely the patient ends up somewhere else or the referring office stops sending you cases at all. Whichever tool you configure, make referral intake its own category with the fastest response standard in your entire queue, and make sure a referral never gets lost in the same inbox as a routine internal question from your own staff.

The referring office rarely knows or cares how your intake process works internally. What they notice is whether their patient got contacted quickly, and a network that treats every referral with the same urgency as a routine internal request will eventually earn a reputation for being slow, even if most individual requests are actually handled reasonably well.

An authorization question that lands with a front desk coordinator who doesn't handle insurance gets a guess or a promise to find out, neither of which actually helps a referring office or a patient waiting to start care. Build a routing rule that sends authorization questions directly to whoever owns insurance verification at your network, and make sure that person has visibility into which clinic and which payer the question involves, since authorization rules vary enough by payer that a generic answer often isn't a correct one.

A clinic director calling about a broken piece of equipment or an HVAC problem is a facilities and operations issue, not a clinical one, even though it can sound urgent and disruptive when it's affecting a full day of scheduled patients. Route facility issues to whoever manages vendor relationships and building maintenance directly, separate from clinical or referral questions, so a broken treatment table doesn't end up in the same queue as an authorization question competing for the same person's attention.

A network operating across state lines has to track each clinician's license status, renewal date, and any state-specific continuing education requirements, and a lapsed license at even one location is a real compliance and liability problem, not just an administrative inconvenience. Build this as its own tracked category with reminders well ahead of renewal deadlines, rather than trusting that individual clinicians will flag their own upcoming expirations in time for your credentialing team to act.

This matters more the faster a network grows, since a clinician who picks up shifts at a second location across a state line can quietly fall out of compliance without anyone at either individual clinic noticing, because neither one has the full picture on its own. Central tracking is the only view that catches this kind of gap before it becomes a real problem.

A referring physician's office that sends a patient and never hears anything back about how treatment went is less likely to send the next referral your way, and this relationship maintenance often falls through the cracks once the initial intake is handled. Whichever tool you use, build a light, recurring check-in into the referral category itself, a status update sent back to the referring office at a defined point in the plan of care, so the relationship gets tended even when nothing has gone wrong.

Once you've configured either tool, pull your slowest referral intake from the last month and walk it through the new setup end to end. If the new process wouldn't have caught the delay faster than what actually happened, that's a configuration gap worth fixing immediately, since a slow referral intake is the failure mode most likely to cost your network a whole relationship with a referring practice, not just one patient.

Walk your slowest recent referral through the new setup in this order:

1. Pull the slowest referral intake from the last month and note when it arrived, who acknowledged it, and when the patient was contacted.
2. Replay it through the new referral category and check whether the fastest response standard in your queue would have caught the delay sooner.
3. Confirm the insurance authorization rule sent any related question straight to whoever owns verification, not to a front desk coordinator.
4. Check that facility and clinical requests reached different owners, and that licensing reminders arrived well ahead of any renewal deadline.
5. Fix any gap the replay exposes right away, since a slow referral intake is the failure most likely to cost you a referring relationship.