V · Underneath the front door
The five leaks
The phone is one leak. There are four more behind it.
Mercury answers the calls you would have missed. That is the top of the system and the only part a patient ever hears. Underneath it, the platform works the leaks that never ring at all: the slot that evaporated, the plan left unfinished, the patient who quietly stopped coming, the referrer who never heard back. Every one of them is a visit that was already yours. The measure is visits per day, set with you at the start, and each pillar is scored against it.
-
01
Referral capture
Gets the patient in
The leak
A referral that reaches voicemail rarely calls back. Before a system records it, nobody even knows what was missed.
What the software does
Mercury answers every line in three languages and ends every call in a logged outcome. A web door lets a patient start at eleven at night. Missing insurance fields are flagged before they can become a denial.
What your desk does
Verifies each intake and clears it. Nothing reaches the record until it is cleared.
-
02
No-show backfill
Keeps the slot
The leak
A cancelled afternoon slot evaporates. In most practices the no-show rate is not even measurable, so nobody can argue about it either way.
What the software does
Reminders before the visit, and a standing waitlist that offers the freed slot the same day. The consent packet carries the cancellation policy that makes the rule enforceable.
What your desk does
Works the waitlist the moment a slot frees, instead of discovering the hole that afternoon.
-
03
Plan completion
The largest of the five
The leak
A patient who stops mid-plan leaves no event behind. The chart simply stays open, so nothing triggers a call and the loss stays invisible.
What the software does
Flags anyone falling behind their plan before they disappear: visits used against visits authorized, a script about to expire, a follow-up overdue.
What your desk does
Works the flagged list every day, in the patient's language, and logs what came of each call.
-
04
Reactivation
Pays first
The leak
Past patients who could be contacted about their own care, and never are, because nobody ever owned re-engagement.
What the software does
Finds and sizes the pool, then runs the invitation in batches on a schedule instead of in a burst.
What your desk does
Books the responses. This is treatment communication to your own patients, inside healthcare marketing rules, with no advertising.
-
05
Physician loop
The one that compounds
The leak
Referring doctors never hear back, so referrals never grow. Report-back means a person typing an email per patient per milestone, which is exactly why it never happens.
What the software does
Sends the evaluation summary and progress notes back to the referring physician automatically, drawn from the note your clinician already signed.
What your desk does
Nothing extra. The signed note is the source, and the release in your consent packet is the permission.
Adoption is not requested. It is operated.
- The platform keeps scorequeues, flags, alerts, audit log
- We read the score and chase ita measured daily cadence, not a monthly call
- Your staff work the flagged listverify, call, reschedule, treat, document, sign
- Every outcome is loggedand the score updates on its own
Every step is measured from the audit log, not from what anyone says they did. Nothing in the loop depends on someone remembering, and nothing that drops stays invisible.
A platform you hand over gets ignored. A system somebody operates cannot be.