All features

Notifications & Push

Timely alerts for staff and patients across channels.

5

staff alert types

3

platforms (iOS · Android · Web)

2

audiences (staff + patients)

Notifications & Push

Overview

Two push stacks, one platform: patients get native mobile alerts through FCM when reminders and campaigns fire, while staff receive in-app notifications plus optional browser push for sessions, lab results, and inventory — all logged per device.

In-app and push notificationsAppointment and result alertsConfigurable notification rulesReduces missed visits and delays

Two audiences, one engine

Illustrative — delivery mix varies by clinic setup

Staff alerts
New session
Session request
Cancellation
Low stock
Lab result
↓
In-appBrowser push
Patient alerts
Appointment reminder
Follow-up campaign
Dual-send backup
↓
FCM mobile app

Real-world use cases

1

Cut no-shows with mobile reminders

Appointment reminders reach the patient app instantly — no WhatsApp number required when push is the primary channel.

2

Front desk stays in sync

New session requests and cancellations pop up in the browser while staff work in other tabs — no constant dashboard refresh.

3

Dual-send for critical follow-ups

Send WhatsApp first, then push as backup on the same reminder rule — patients who miss chat still get the alert on their phone.

4

Trace every delivery

Support checks PushNotificationLog status and FCM message IDs instead of guessing whether a patient actually received the alert.

What you get

Native patient app push (FCM)

iOS and Android tokens registered per clinic and approved patient profile, with automatic re-registration on app reopen.

Staff browser Web Push

Five alert types — sessions, requests, cancellations, low stock, lab results — with per-user preference gates.

Shared reminder engine

Push is a first-class channel alongside WhatsApp, SMS, and Telegram in the same admin workspace.

Per-device delivery logs

Every send creates a log row with PENDING → SENT or FAILED status and provider error details.

Safe device lifecycle

Unregister soft-deactivates tokens; duplicate devices dedupe on send so one phone never gets spammed.

Multi-profile households

One device token registers for all approved profiles the patient user manages in a clinic.

How it works

  1. 1

    Enable the push channel

    Create a Push Notification channel (FCM) in the messaging workspace — same place you manage WhatsApp.

  2. 2

    Patients opt in via the app

    On login with an approved profile, the app registers the device token automatically after permission is granted.

  3. 3

    Reminders and events deliver

    The reminder cron sends to registered devices; staff events trigger in-app + browser push based on user preferences.

Need implementation details, APIs, or workflows?

Read the full documentation
Talk to us on WhatsApp

Related modules

Roles & Permissions

Fine-grained access so every role sees only what they need.

Ready to run your clinic on one platform?

See how Smart Clinic unifies EHR, ERP, growth tools, and AI — book a demo tailored to your specialty and size.

Get a free demoBack to home