Built for hospital patient journeys
Know what happened after every patient enquiry.
From the first call to appointment, consultation, procedure and follow-up, PulseOS gives your team one connected operational view.
Works alongside your existing calling and hospital systems.
Hospital performance
Last 30 days · all branches · all services
- 143
- Enquiries
- 91
- Appointments booked
- 72
- Visits attended
- 68
- Consultations
- 14
- Procedures done
Patient Journey Performance
% of enquiries reaching each stageLargest drop-off: Enquiries → Appointments booked (-36pp of enquiries)
| Source | Enq. | Visits | Consults | Done |
|---|---|---|---|---|
| 52 | 31 | 24 | 6 | |
| Meta | 38 | 17 | 12 | 2 |
| Website | 21 | 13 | 11 | 3 |
| Phone | 32 | 24 | 21 | 3 |
- Cataract52 → 14
- Oculoplasty31 → 8
- Laser vision correction27 → 7
- Squint19 → 5
Patient Journey · Cataract enquiry
Google → call → appointment
Appointment confirmed
Tomorrow · 10:30 AM
Waiting
8 min
Screens use synthetic demo data. No real patient or hospital information.
The lead is only the beginning
Your marketing report says 42 enquiries. What happened to them?
Most reports stop here. The patient's story doesn't.
- 42Enquiries
- 27Appointments booked
- 21Visits attended
- 18Consultations completed
- 9Procedures advised
- 6Procedures scheduled
- 4Procedures done
- Enquiries42
- Appointments booked27
- Visits attended21
- Consultations completed18
- Procedures advised9
- Procedures scheduled6
- Procedures done4
Example journey data (synthetic). Not a customer result.
The journey
Follow one patient. See the whole journey.
Do what your team would do. Watch the timeline and the owner's numbers respond. Synthetic patient.
The enquiry arrives. Google, Cataract. It lands on a journey with a source and an assigned team member, not in a spreadsheet.
PRIYA
Cataract enquiry · Source: Google · Today 10:12 AM
Today
- Lead created10:12 AM
Google · Cataract · Assigned to Shivani
What the owner sees
Hospital funnel · example data
- Enquiries+143
- Appointments booked27
- Visits attended21
- Consultations completed18
- Procedures advised9
- Procedures scheduled6
- Procedures done4
Step 1 of 5
The old way
If your follow-up system looks like this, you already know the problem.
| Name | Phone | Day 1 | Day 2 | Feedback Day 1 | Follow-up Date | Final Feedback |
|---|---|---|---|---|---|---|
| Savitha M. | 98xxx 10234 | Called | Called | No response | — | No response |
| Ravi K. | 90xxx 55871 | Called | — | Call tomorrow | 07 Oct | Booked |
| Pooja N. | 97xxx 22418 | Called | Called | Interested | 08 Oct | Visited |
| Imran S. | 99xxx 70352 | Called | — | No response | — | — |
| Latha R. | 88xxx 41096 | Called | Called | Call tomorrow | 09 Oct | Booked |
Fictional rows. Day 1 here, Day 2 there, a separate sheet for follow-ups.
PulseOS · one journey
Priya · Cataract- Enquiry · Google10:12
Cataract · assigned to Shivani
- Call connected10:20
No response → call tomorrow 11:00 AM
- Call connectedNext day
Interested → appointment booked
- VisitedTue 10:30
Consultation completed
- Procedure advisedTue 11:05
Next action: coordinator follow-up
- No Day 1.
- No Day 2.
- No separate follow-up sheet.
Just one chronological patient journey and the next action.
For the owner
Stop asking, “what happened to this lead?”
See where enquiries become appointments, consultations and procedures.
Hospital performance
Last 30 days · all branches · all services
- 143
- Enquiries
- 91
- Appointments booked
- 72
- Visits attended
- 68
- Consultations
- 14
- Procedures done
Patient Journey Performance
% of enquiries reaching each stageLargest drop-off: Enquiries → Appointments booked (-36pp of enquiries)
| Source | Enq. | Visits | Consults | Done |
|---|---|---|---|---|
| 52 | 31 | 24 | 6 | |
| Meta | 38 | 17 | 12 | 2 |
| Website | 21 | 13 | 11 | 3 |
| Phone | 32 | 24 | 21 | 3 |
- Cataract52 → 14
- Oculoplasty31 → 8
- Laser vision correction27 → 7
- Squint19 → 5
Age group
- 18–3024
- 31–4538
- 46–6046
- 60+35
Area
- Whitefield33
- Jayanagar28
- HSR Layout24
- Hebbal19
Gender
- Female78
- Male65
- Shivani48 enquiriesUp to date
- Deepa41 enquiries2 overdue
- Arun35 enquiriesUp to date
Illustrative numbers on synthetic data.
Which source brings patients who actually visit?
Source → visit → consultation → procedure, side by side.
Where are patients dropping off?
The funnel names the largest drop and the stage it happens at.
Which services turn into procedures?
Enquiries and procedures advised, service by service.
Who is your hospital actually reaching?
Patterns by age group, area and the fields your hospital chooses to record.
One journey. A different view for every team.
See the hospital journey without chasing updates.
From the source of an enquiry to the procedure that followed, on one screen.
- Source → procedure, not just source → lead
- Services that turn into procedures
- Follow-ups that are overdue, and who owns them
| Source | Enq. | Visits | Consults | Done |
|---|---|---|---|---|
| 52 | 31 | 24 | 6 | |
| Meta | 38 | 17 | 12 | 2 |
| Website | 21 | 13 | 11 | 3 |
| Phone | 32 | 24 | 21 | 3 |
- Cataract52 → 14
- Oculoplasty31 → 8
- Laser vision correction27 → 7
- Squint19 → 5
Age group
- 18–3024
- 31–4538
- 46–6046
- 60+35
Area
- Whitefield33
- Jayanagar28
- HSR Layout24
- Hebbal19
Gender
- Female78
- Male65
One action, not three screens
Book the appointment while you're still on the call.
Set the next action to Book appointment, pick the date and time, confirm with the patient, save. The call, the appointment and the follow-up land on the same journey.
Appointment confirmed
Tue · 10:30 AM
Reminder planned
Goes out when your messaging provider is connected
Front desk updated
Tomorrow's queue already shows Priya
Outcome
Patient interested
Feedback
Asked about surgery and timings
Next action
Book appointment
Date
Tue, 10 Oct
Time
10:30 AM
Configure
Your workflow shouldn't be hard-coded.
Choose what you collect, where it appears and what's required. Try the switches.
Settings · CRM fields
Show on Add Lead
- Patient TypeNew / existing patientON
- AreaLocality of the patientON
- Date of BirthUsed for age groupOFF
- GenderUsed in who-is-enquiringOFF
Add Lead
What your front desk sees
Phone *
Name
Service
Source
Patient Type
Area
Services
- Cataract
- Oculoplasty
- Squint
- Laser vision correction
Lead sources
- Meta
- Website
- Walk-in
- Referral
Clinic hours
- Mon–Sat 9:00–18:00
- Sun closed
An enquiry is not a registration form.
Collect what matters at the right moment. Your front desk shouldn't fill 15 fields just to save a phone enquiry.
First enquiry
- Phone
- Name
- New / existing
- Service
- Source
Later, when needed
- UID
- Address
- PIN
- Area
- Service-specific details
Where PulseOS fits
PulseOS connects the space between acquisition and clinical care.
Patient arrival
- Meta
- Website
- Phone
- Walk-in
- Referral
PulseOS
- Enquiry
- Patient
- Calls
- Follow-ups
- Appointment
- Visit
- Consultation
- Treatment journey
- Analytics
Your existing stack
- Calling / IVR
- EMR / HMIS
- Billing
- Clinical systems
Clinical charting, prescriptions and billing stay where they belong.
Calling / IVR
Great at
Receiving and routing calls.
PulseOS adds
What happened after the call.
General CRM
Great at
Leads and sales tasks.
PulseOS adds
The hospital-specific patient workflow.
EMR / HMIS
Great at
Clinical and hospital records.
PulseOS adds
The operational patient journey around care.
Designed to fit the systems your hospital already uses.
- Integration-ready
Calling
Manual Log Call, Runo
Log a call by hand today. Call records and missed-call callbacks arrive when your hospital connects its calling provider.
- Integration-ready
Messaging
WhatsApp Business
Confirmations and reminders are planned in PulseOS and sent when your WhatsApp account is connected.
- Integration-ready
Website
Website enquiry form
A protected intake endpoint creates the patient and journey when your website posts to it.
- Integration-ready
Ads
Google Ads, Meta Ads
Read-only spend and campaign reporting. Provider conversions are never counted as PulseOS outcomes.
- On request
EMR / HMIS
Your existing system
PulseOS works alongside your EMR. Integration depends on what your system supports.
- Works today
Walk-in & referral
Add Lead
Enter walk-ins and referrals in seconds with the source attached.
Integration-ready means the capability is built; your hospital connects its own account. Nothing is connected on your behalf.
Beyond leads
A lead count tells you who enquired. PulseOS tells you what happened next.
A typical marketing report
- Google40 leads
- Instagram32 leads
- Website18 leads
Which of them actually came? The report can't say.
PulseOS
Google
- 40
- Enquiries
- 24
- Appointments
- 18
- Consultations
- 6
- Procedures done
Instagram
- 32
- Enquiries
- 12
- Appointments
- 7
- Consultations
- 1
- Procedures done
Website
- 18
- Enquiries
- 11
- Appointments
- 9
- Consultations
- 3
- Procedures done
Same enquiries, very different outcomes.
Illustrative data. Not customer results.
Built for hospital operations
Built around how Indian hospitals actually follow up.
Phone-first enquiries, WhatsApp, walk-ins, referrals and campaigns. A front desk, a coordinator, a doctor and an owner who all need the same patient story.
- One patient. Multiple journeys.
- Role-based workflows for owner, front desk, coordinator and doctor.
- Hospital-configurable intake.
- Source-to-procedure visibility.
- Built around real front-desk workflows.
Role-based access
Each role sees what it is allowed to. Permissions are enforced on the server, not just hidden on screen.
Separate hospital data
Every hospital's workspace is kept apart, and access always comes from the signed-in session.
Secure sessions
Passwords are stored as one-way hashes. Sign-in uses secure, server-managed session cookies.
Protected credentials
Provider keys live on the server and are never shown back in the browser. Sensitive changes are logged.
Reminders matter
Published healthcare research has repeatedly found that reminders improve attendance.
One systematic review and meta-analysis found patients who received digital (text-message) notifications were 23% more likely to attend clinic and 25% less likely to no-show than those who received none.
Independent research, not a PulseOS result. Source: Robotham et al., “Using digital notifications to improve attendance in clinic: systematic review and meta-analysis”, BMJ Open, 2016.
Questions hospital owners ask.
Do we have to replace our EMR or HMIS?
No. PulseOS handles the patient engagement and operational journey around your clinical systems. Prescriptions, investigations, clinical notes and billing stay where they are.
Does it work with WhatsApp and our calling provider?
You can log every call and enquiry by hand from day one. WhatsApp confirmations and reminders, and call records from a calling provider, switch on when your hospital connects its own accounts.
Can we change what the front desk has to fill in?
Yes. Choose which fields appear on Add Lead, which are required and which can be used as filters. Services, lead sources and clinic hours are yours to set.
Who can see what?
Owners and admins see performance. Coordinators see their follow-ups and journeys. Front desk sees the day's patient flow. Doctors see their planner. This is enforced on the server.
Is PulseOS a clinical record system?
No, and it does not try to be. It is the operational layer: enquiry, call, follow-up, appointment, visit, consultation outcome and treatment follow-up.
See what happens after the enquiry.
Walk us through how your hospital handles enquiries, follow-ups and appointments. We'll show you how PulseOS fits.