| Greetmate
Referral management software will show you every referral that arrived this week. It will not call any of them back. The gap between a record appearing in a queue and a patient appearing on the schedule is where specialty groups lose patients they already earned. The fax came through, the record got created, the dashboard lit up, and nobody had a free ten minutes before the patient booked with someone else.
Most groups cannot say how large the gap is. In a study of 103,737 specialty appointment scheduling attempts across 34 clinics, only 34.8% ended in a documented completed appointment, and 38.9% had no documented status at all (FY2016 data). Separately, 29% of patients aged 65 and older referred to a specialist are never scheduled to be seen.
This article follows one referral from the sending practice to a booked appointment and names the five places it stalls on the phone. Each stall point comes with a follow-up workflow you can build: when the first attempt goes out, how many attempts follow, on which channel, who gets escalated to, and what gets logged.
Table of Contents
Key Takeaways:
Referral management software receives inbound referrals from fax, portal, and HIE feeds, turns them into structured records, places them in a work queue, tracks status, and reports on volume. It shows a practice which referrals exist and where each one stands. It does not contact the patient. A person still has to make that call.
That is the honest boundary, and it matters because every page-one result for this category uses the same operative verb: track. Tracking is real work. A referral management system in healthcare replaces a fax tray with a searchable list, standardizes fields across sites, and gives a coordinator one place to work from. Revenue cycle systems do their own real work on the claim and eligibility side. None of that is in dispute here.
What no dashboard does is dial. It will not decide that a referral entered at 9:14 a.m. needs an outbound attempt by 10:00, send the SMS between voice attempts, or escalate a case that has been sitting in "auth pending" for nine days.
Scope, stated plainly. This article is about the call-and-follow-up layer wrapped around referrals. Your referral management platform, your EHR, and your RCM system keep doing what they do. The follow-up layer sits alongside them and writes back into them. Anyone telling you one category solves all of it is selling you a category.
The two terms get used interchangeably and they describe different failures.
Referral leakage is the referred patient who never converts into a visit at your practice. A physician sent them to you. The referral reached your queue. The appointment never happened. For a specialty group receiving inbound referrals, this is the hole that costs you volume you already won.
Patient leakage is care leaving your network or your panel and going somewhere else: the patient who was supposed to come back to your group for imaging, therapy, or a follow-up procedure and went elsewhere instead. That is a network-integrity problem, and it is what health systems usually mean when they talk about how to reduce patient leakage.
Both are measured the same way, in booked and completed appointments, never in referral counts. A queue with 41 referrals in it tells you nothing about your referral conversion rate.
Specialty scheduling attempts by documented outcome (34 clinics, FY2016)
That middle bar is the one worth staring at. Nearly four in ten scheduling attempts had no recorded outcome. You cannot manage what nobody wrote down.
We covered the inbound-call version of this problem in The Hidden Cost of Intake Leakage in Healthcare Practices, which deliberately left referral leakage out of scope. This is that missing piece.
A referral arrives Monday morning by fax or portal. It lands in the queue. The coordinator works the queue in whatever order the day allows, between walk-ins, insurance questions, and a provider who needs something scanned. By Thursday the referral is still open, and the patient, who was told on Monday to expect a call, has already phoned two other specialists.
Nobody did anything wrong here. One person was handed forty tasks and a phone.
The fix is timing. In one program, a referral team covering roughly 90% of operational hours contacted 80% of referred patients within nine minutes of referral entry and left only 7.4% of referrals unresolved: 3.7% unreachable after repeated attempts and 3.7% still on hold. Nine minutes is a high bar, but the principle underneath it is simple. Contact is triggered by the referral arriving, not by somebody getting to it.
Workflow design
The scheduling advantage here is real and it is boring: whoever calls first usually wins the appointment. We wrote about why in The First Practice To Respond Usually Wins.
The referral is incomplete. It is missing an insurance detail, a chart note, or the imaging the provider wants to see before booking. Your coordinator calls the sending office and gets voicemail. The sending office calls back an hour later and gets your voicemail, because your coordinator is on another call. Repeat for two days.
This is the least dramatic and most common way a referral dies. Both desks are working. Neither is available at the same moment as the other.
The design answer is to stop treating referring-provider calls as generic inbound. Give them a dedicated path that captures the request in a structured way (who is calling, which patient, which referral, what is missing) and routes that detail straight into the coordinator's queue as a task with a name attached to it. The information gets captured as data instead of as a thirty-second audio file at the bottom of a mailbox.
Cub Larkin at Inclusive Therapy Group described using webhooks to connect Greetmate to their other systems so calls get routed and followed up on based on what the call actually was, "rather than leaving our team with unorganized voicemail backlogs." The deployment handled 836 calls, 68% of them arriving after hours, helped 501 callers immediately, and eliminated 217 callbacks, which recovered roughly 69.5 staff hours.
Workflow design
This is the highest-volume stall. The coordinator calls, the patient does not pick up, a voicemail may or may not get left, and the record stays open forever in a state that nobody revisits. In the FY2016 specialty scheduling data, 18% of referrals required multiple scheduling attempts, 6% of referred patients could not be contacted, and 12% declined for reasons that were never recorded.
A designed cadence beats a hopeful one. In a multi-center outbound program of 548,089 calls, 12.1% resulted in a booked appointment (14.6% adjusted), 25.7% never reached the patient, and 42.9% reached someone who declined. The protocol was up to three attempts, spread across different days and different times of day, with a voicemail left on the first attempt.
Two things stand out. First, a quarter of attempts never reached anyone, which is why attempt count and time-of-day variation matter more than call quality. Second, the program could report all of that, because the cadence was defined in advance and every outcome had a place to land.
Workflow design
The multi-touch pattern is the same one that works for dormant-patient outreach. We broke that cadence down in The patient recall system most practices don't actually run.
Reduce front-desk call volume and improve patient communication.
Go live in hours with done-for-you setup.
The patient wants the appointment and the referral is clean, but the case parks behind a prior authorization with no owner and no clock on it. Weeks pass, and the patient assumes they were forgotten, because from where they sit, they were.
The scale of the problem is documented. In the 2025 AMA Prior Authorization Physician Survey of 1,000 physicians, 95% said prior authorization delays access to care and 79% reported patients abandoning treatment because of authorization problems, with physicians and staff spending about 13 hours a week on prior authorizations.
Scope. Greetmate does not perform prior authorizations, submit them, or make any determination about coverage. That work belongs to your staff and your payer processes. What is described below is the communication and escalation layer around the wait.
Workflow design
The patient message is not complicated. It says the practice is still working on it and will call when it clears. That single message is often the difference between a patient who waits and a patient who goes somewhere else.
You did everything right. You reached the patient on the second attempt, booked them for the following Tuesday, and they came in. The referring office heard nothing.
Everyone treats loop-back as a clinical courtesy. For a specialty group it is also a volume decision. A referring physician who never learns what happened to the patient they sent you has no reason to believe you handled it well, and the next referral goes to whoever last gave them an answer. Clinical loop closure and the consult note stay with your clinical team and your EHR. The operational confirmation (we got them, we booked them, here is when) is a separate, cheap message that keeps referral volume coming.
Workflow design
That monthly summary is also a relationship tool. Handing a referring office a one-page view of what happened to the patients they sent you is a better conversation than a lunch.
Ask most specialty groups these three questions and the answers come back as estimates:
Two more separate a managed referral coordinator workflow from a busy one: reach rate by referring practice, and average time from referral entry to first contact attempt.
The reason these are hard is structural, not a staffing failure. In that FY2016 specialty dataset, 38.9% of scheduling attempts carried no documented status. If attempts are not captured in a reportable field, no amount of effort produces a report. Patient referral tracking that stops at the intake record cannot tell you why a referral did not convert.
When the follow-up layer runs the cadence, every attempt is a logged event by default. Leadership can read what happened instead of asking how it is going.
Greetmate is healthcare voice and SMS AI infrastructure, delivered as a tech-enabled service. For referral work, that means four concrete things.
The workflow is scoped and tested before go-live. We map your referral path as it actually runs, including where referrals arrive, who touches them, and what blocks them, then build the cadence to match. Attempt counts, timing windows, escalation owners, and terminal states are decided with you and tested against real scenarios before a single patient hears anything.
Somebody guides the rollout. Onboarding, routing design, QA, staff training, and the first weeks of refinement are our job. Basic deployments can go live quickly; referral workflows with authorization logic and multi-site routing take longer and get the attention they need.
It connects to the systems you already run. Greetmate integrates with dozens of leading EHRs for scheduling, notes, medications, and lab results, plus calendars, forms, inboxes, CRMs, and your referral management platform through webhooks and APIs. Your coordinator keeps working where they already work. The no-code workflow builder is where the routing, triage paths, and intake capture get built.
Leadership can see what came in and what it produced: referrals received, patients reached, appointments booked, reach rate by referring practice, time to first contact, and the aged cases that need a human today.
Greetmate is HIPAA-ready, with a BAA available. For groups running the same referral process across five, ten, or twenty sites, the workflow is defined once and deployed consistently. That is the multi-location standardization piece, and it is usually what makes the reporting comparable across sites for the first time.
On commercials: this is an initial engagement of at least three months, because a referral cadence needs a few cycles of real volume before the numbers mean anything. Pricing starts at $999–$2,500 per month for the base, plus $0.18 per minute above an included allowance set per customer, so the base figure is a starting point and not the all-in cost.
Referral management software receives inbound referrals from fax, portal, and HIE feeds, converts them into structured records, puts them in a work queue, tracks status, and reports on volume. It tells you which referrals exist and where each one stands. Contacting the patient is a separate job that still requires a phone call.
Referral leakage is a patient who was referred to your practice and never became a visit: the referral arrived and the appointment never happened. Patient leakage is care leaving your network or panel to another provider. Both are measured in booked appointments. Referral leakage is the one an inbound specialty group controls most directly.
Almost always on the phone, at one of five points: no same-day callback after the referral arrives, voicemail tag between two front desks over missing information, a single contact attempt with no cadence behind it, an authorization that ages with no owner, and no confirmation back to the sending provider. None of these are effort problems.
As close to referral entry as the day allows. One referral team that reached 80% of referred patients within nine minutes of referral entry left only 7.4% of referrals unresolved. The practical target for most groups is a first attempt within the hour, triggered by the referral arriving instead of by a batch review.
A defensible protocol used across 548,089 outbound calls was up to three attempts on different days and at different times of day, with a voicemail left on the first attempt. Add an SMS between voice attempts. Then close the record to a defined state. Unreachable is an answer; open forever is not.
Neither. Your referral platform still receives, digitizes, and tracks. Your coordinator still owns the relationships, the exceptions, and the judgment calls. What changes is that the routine dialing, the SMS touches, the aging escalations, and the logging run on a schedule, so the coordinator works the cases that need a person.
Greetmate is built for healthcare use and a BAA is available. Workflows are designed with your team to control what information is spoken, captured, and written back, and to which systems. Any integration into your EHR or referral platform is configured during implementation with those boundaries defined in advance rather than assumed.
A referral sitting in your queue is demand a physician already sent you. There is no acquisition cost left to spend. Recovering it takes a phone call at the right hour, two more if the first goes unanswered, a text in between, and a note back to the office that sent them. That is the entire program.
The reason it does not happen is not indifference. It is that one person cannot answer the phone and work forty referrals in the same eight hours, and no dashboard has ever dialed a number. Build the follow-up layer around the referral system you already have, and the three numbers that matter (received, reached, booked) become something you read instead of something you estimate.
Handle patient calls around the clock — including after-hours and overflow — so your front desk can focus on in-office care.
Automate appointment scheduling, patient follow-ups, and reactivation outreach through workflow-driven voice communication.
Connect with your existing EHR, scheduling tools, and operational systems for seamless, end-to-end patient communication.
See Greetmate in Action.
Healthcare voice AI infrastructure — live in hours.
If you receive inbound referrals and cannot say how many of them got booked last month, that is the conversation to have. Schedule a demo and we will map your referral path, name the stall points, and show you what the follow-up workflow would look like in your practice.
Find helpful articles in our blog that are all about business, customer service and AI technology.
Eight people call during one twenty-minute chairside block and one person can answer one of them. Here are the four moments a dental group's phones break, what belongs with a person at each, and an escalation rule set mapped to the ADA's own emergency, urgent and routine tiers.
Every practice management system prints the overdue list. Almost nobody works it consistently. Here's how to segment it, set a cadence, land the booking in the schedule, and report on what it produced.
