Patient Journey Pipelines: Surgical vs Non-Surgical

A clinic that does both surgery and sessions often runs one pipeline for everything. Then the dashboard says consult conversion is 25% and nobody knows if that is good or terrible.

It might be both. The laser patient who did not book a second session and the knee patient still deciding with his son in Pune are not the same kind of "not converted". They need different stages, different follow-ups and different numbers.

What is a patient journey pipeline?

It is the set of stages every patient moves through inside your CRM, with an owner and a next date at every step. The base pipeline I use has seven stages:

1. New enquiry
2. Contacted
3. Booked
4. Confirmed
5. Arrived
6. Decided
7. Treatment started

Every patient sits in exactly one stage. Every next step has an owner and a date. If it is not in the CRM, it did not happen.

The first five stages work the same for surgery and for sessions. The split happens at "decided", because what a decision looks like, and how long it takes, is completely different.

How is a surgical pipeline different?

Surgical decisions take longer and involve more people. Some patients go ahead straight away because they must. Others put it off for a long time. And in India, the decision is usually a family decision.

So after "arrived", a surgical pipeline needs extra stages that reflect the real steps:

• Tests ordered, with a date and a review slot already booked.
• Family session, in person or on a video call, booked before the patient leaves.
• Financing or insurance, where the coordinator handles EMI applications or the TPA desk handles pre-authorisation.
• Surgery date booked.
• Surgery done.
• Post-op reviews, for example at three months, six months and a year after a joint replacement.

Consult conversion is also measured differently. For medically necessary surgery, measure how many of the patients you advised surgery for actually went ahead, over a longer window, not how many decided on the day.

How is a non-surgical pipeline different?

Here, the decision is usually faster, but the risk moves to the middle. A skin, hair or physiotherapy plan with six sessions only works if the patient completes six sessions.

So after "treatment started", a non-surgical pipeline tracks the plan itself:

• All sessions booked, on the day the patient says yes.
• Session tracking: session 1, 2, 3 and so on, with progress photos taken with consent.
• Missed session: an automatic flag, and a warm call within a day.
• Phase milestones, if your method has three to five named phases.
• Completion review with the doctor.
• Maintenance or long-term plan.

Surgical vs non-surgical pipelines side by side

What does this look like in rupees?

Example, non-surgical: say a skin clinic sells a six-session plan at ₹60,000, paid in milestones. Twenty patients start in a month. If half stop after two sessions, the clinic collects far less than the plans it sold, and ten patients go home with half a result and tell people it did not work. A pipeline that books every session upfront and calls every missed visit within a day protects both the revenue and the reputation.

Example, surgical: say a knee unit sees 40 patients a month for whom surgery is advised, and 12 book a date on the day. If the pipeline tracks the other 28 through tests, family sessions and financing, with a coordinator following up on a fixed cadence, even a few more going ahead each month is a significant amount of revenue, because each case is high value.

How do you build both in one CRM?

Keep one CRM, with two pipelines that share the first five stages. A patient moves into the surgical or non-surgical pipeline at "decided", based on the plan the doctor recommends.

Then set the automations for each one:

• Surgical: test reminders, a booked review slot for results, family session invites, financing document checklists, pre-surgery instructions approved by the doctor, a call from the doctor on the evening after surgery, and review reminders.
• Non-surgical: session reminders before every visit, a missed-session alert to the coordinator, progress check-ins, and a completion review invite.

We set up both pipelines for clinics as part of our CRM, WhatsApp and AI work. If your problem is earlier, at the consultation or the coordinator handover, start with our conversion systems instead. Specialities with long surgical decisions, like orthopaedics, usually benefit most from the extra stages.

What mistakes break a pipeline?

• One pipeline for everything. Your numbers blend two very different journeys and tell you nothing.
• Stages with no owner. "Family session pending" with no name and no date is just a polite way of losing the patient.
• Skipping the arrival tick. If the front desk does not mark patients as arrived, the CRM cannot spot no-shows or count show rate.
• Closing the record at surgery or at the last session. The pipeline should end in long-term care, not in a payment. That is where reviews, related care and referrals come from.
• Too many stages. If your team cannot name every stage from memory, you have built a pipeline for software, not for people. Add a stage only when it reflects a real step with a real owner.

The short version

• Both pipelines share the first stages: enquiry, contacted, booked, confirmed, arrived.
• Surgical pipelines add tests, family sessions, financing or TPA, a surgery date and post-op reviews.
• Non-surgical pipelines add upfront session booking, session tracking, missed-visit calls and a completion review.
• Measure surgical success by advised patients who went ahead, and non-surgical success by plan completion.
• One CRM, two pipelines, each with its own automations and owners.