Patient engagement

Stay in touch without anyone remembering to

Appointment reminders, visit and billing updates on WhatsApp and SMS, and a portal where patients can see their own history.

Book a demo See the platform

Patient communication fails in the same way everywhere: it depends on a person remembering. The reminder goes out when the desk is quiet and does not when it is busy, which is exactly when it matters. OlivHealth sends from events rather than from intentions — the appointment being booked is what schedules the reminder, so the message goes out whether or not anyone had time.

Reminders depend on someone being free

Messages are triggered by what happened in the system — an appointment booked, a visit completed — and sent on a schedule, not by hand.

Nobody knows if the message arrived

Delivery is confirmed by the provider’s delivery report rather than by the send being accepted, so "sent" means it actually reached the phone.

Patients call the desk to ask what they paid

A patient portal lets them see their own visits and bills, which takes a whole category of phone calls off the front desk.

A duplicate message goes out twice

Notifications are recorded once per event, so a retry or a double-save cannot send the same patient the same message twice.

Appointment reminders

Scheduled WhatsApp and SMS reminders ahead of the visit, configured per hospital rather than per staff member.

Event-driven notifications

Messages are raised by real events in the system, so communication reflects what actually happened to the patient.

Delivery confirmation

Each send is reconciled against the provider’s delivery report, with retries and backoff, so failures are visible.

Patient portal

Patients sign in to see their visits, appointments and bills, and to keep their own contact details current.

Per-hospital templates

Each unit binds its own templates and channels, so branches can speak in their own voice and language.

Consent-aware

Contact details are captured with consent, which is what the DPDP Act expects before you message anyone.

ABDM — included as standard

Go live ABDM-enabled from day one

Every practice we onboard goes live ABDM-enabled — create and verify a patient’s ABHA at registration, and let their records follow them across the health system on their consent. It’s part of onboarding, not a separate project or an extra module to buy.

Best fit for

High no-show practicesFollow-up heavy specialtiesMulti-branch groupsPatient-facing clinics

Frequently asked questions

Do I need my own WhatsApp Business account?

Yes, messaging runs through your own registered channel and templates. Promotional messaging in India needs DLT registration and approved templates, and getting that in place is part of onboarding.

What does the patient portal actually show?

Their profile, appointments, visits and bills, plus the ability to update their own contact details. It is a patient-facing view of their own record, not a second inbox for your staff to watch.

Will a system error stop a patient being registered or billed?

No. Notifications are raised after the clinical or billing action has been saved and never block it, so a messaging outage cannot break the business workflow.

Can I see what was sent to a patient?

Yes. Each notification and its delivery outcome is recorded, so you can check what went out and whether it landed.

See it on your own workflow

A quick, no-pressure walkthrough over WhatsApp or a call.

Book a demo →