Why Your PMS Does Not Tell You Who to Call Today (And What Phoenix Does Instead)

By Raman Soni, Head of Performance Marketing at ICG.

Your Practice Management Software is a remarkable piece of technology. It books appointments, raises invoices, stores clinical records, manages inventory, and produces monthly revenue reports. It does virtually everything except the most important thing: tell your counsellor who to call at 9am tomorrow.

angryturtle/13-weekly-tasks.png" alt="Angryturtle Weekly Tasks — prioritised action queue per listing, week by week" loading="lazy" decoding="async" style="width:100%;height:auto;display:block;">

That gap, between "the system that recorded what happened" and "the person who needs to act on it today", is where clinic revenue quietly disappears.

What a PMS was designed to do

Practice management software is a system of record. It captures transactions, appointments, clinical data, and financial information with high fidelity. HealthPro360 and the other practice management systems on the market all do this well.

What they were not designed to do: surface the patients who are about to churn, identify the packages nearing expiry that need a renewal call, flag the first-time visitor who has not returned in 45 days, or tell your team which of those 850 active patients represents the most urgent revenue opportunity today.

That is not a criticism of PMS software. It is a description of what a different kind of system needs to do, one that reads from the PMS and translates data into action.

The revenue that is sitting in your database right now

In a typical multi-centre clinic group with 500 active patients per centre, the PMS holds:

• 60-90 patients who have not visited in 45+ days (Visit Frequency drift)

• 15-25 patients with outstanding balances over ₹500 (Amount Due)

• 8-15 patients whose packages are 80%+ used with no renewal conversation started (Package Near Complete)

• 20-30 patients who visited once, paid under ₹10K, and never returned (First-Visit Low Conversion)

• 10-20 patients with packages past their renewal window (Package Renewal Lapsed)

At an average package value of ₹15,000-₹40,000, this is ₹15-50 lakh of recoverable revenue sitting in the PMS, unconverted, because nobody has a systematic process to work it.

Phoenix is that process.

How Phoenix works

Phoenix connects to your PMS via API on a daily sync. It reads patient records, appointment history, package data, invoice data, and sales accruals. It runs a signal engine that checks every active patient against 9 criteria. Any patient that triggers a signal gets sorted into one of three buckets:

Prevent Loss: Patients at risk of churning if not contacted in the next 5-7 days. The 45-day-inactive patient is here. The patient with ₹500+ outstanding who has not been followed up is here. This is the urgent queue.

Maintain and Engage: Patients who are active and should stay that way with regular outreach. Birthday touchpoints, mid-package check-ins, post-treatment follow-ups. This is the retention queue.

Grow Revenue: Closeable revenue opportunities. The patient on session 11 of 12 who has not had a renewal conversation. The first-timer who should be cross-sold. The patient who last purchased a product 90 days ago. This is the revenue queue.

Each patient in each queue shows: what the signal is, how many days since last contact, the revenue at stake, and what to say on the call.

Phoenix Prevent Loss action queue - patient list with signal type, inactivity days, and suggested outreach for 266 patients" loading="lazy" class="w-full h-auto rounded border border-slate-200" />

What this changes for a centre counsellor

Before Phoenix: the counsellor starts the day by scrolling the PMS for "who hasn't been in a while", an imprecise, time-consuming, and inconsistent process. The patients who get called are the ones the counsellor remembers, not the ones with the highest urgency.

After Phoenix: the counsellor opens the platform and sees a ranked list of patients to contact, with the reason and the talking points already drafted. The process is the same every day. No patient falls through the cracks because nobody remembered to check.

The 7-stage workflow

Every patient Phoenix surfaces moves through seven stages: Uncontacted → Tried Contact → In Conversation → Follow-up Scheduled → Converted → Lost Patient → Not Interested. Every call, WhatsApp, and in-person touchpoint is logged. The queue automatically deprioritises patients in active conversation and resurfaces those who have not responded after a configurable window.

What Phoenix is not

Phoenix does not replace your PMS. It does not book appointments, raise invoices, or store clinical notes. It reads from your existing system and adds the action layer. Your team keeps using HealthPro360 or its existing PMS for everything they use it for today. Phoenix is the morning brief that tells them what to do first.

Multi-centre deployment

Phoenix supports multi-centre rollouts with per-centre targets, configurable signal thresholds (what counts as "at risk" may be different for a dermatology centre vs a dental centre), and user roles for centre managers, counsellors, and HO admins. Currently deployed with a multi-centre hair and skin chain.

See the full Phoenix platform.