Ona Health
Notifications

Alerts that respect the room.

Role-aware notifications across in-app, email, SMS, and push — tuned so the right person sees the right alert, without pagers going off in the middle of a consult.

  • Per-event email toggles
  • In-app unread counts
  • Per-user defaults
  • Workspace-level controls

Too many notifications, and people turn them off. Too few, and important things slip. The calm middle is a small set of alerts tuned to what you actually want to hear about — on the channel you actually read.

Ona's notifications today focus on the basics: per-event email preferences for organization, meetings, chat, and patient updates — with in-app unread counts for messages already in your workspace.

Notifications
Per-clinician notification preferences grouped by category, with autosave and clear descriptions.

01 · Why it matters

When alerts are noise, the one that mattered gets missed.

A short, honest list of what Ona emails you about — and a tidy switch per event.

Every clinic we've seen with paging-app chaos has the same pattern: staff quietly silence everything, and the one alert that really mattered gets missed. It's not a discipline problem — it's a design problem.

We start with a small, well-scoped set of events and let each clinician decide which ones they want by email. Anything inside the app already has unread counts. Fancier routing — quiet hours, escalation, on-call, Slack & Teams — is on the roadmap rather than pretending to exist.

02 · What you get

A simple, honest notification surface.

Per-event email toggles

Turn each email type on or off for your account — new chat messages, patient questionnaires completed, consents received, booking-page appointments, and more.

Grouped by category

Settings live under clear headings: Organization, Meetings, Chat, and Patient updates. No hunting through a single long list.

In-app unread counts

New chat messages show an unread count in the sidebar so you don't need an email for things you're already looking at in the app.

Defaults per workspace

Admins set sensible organization-wide defaults; clinicians and staff adjust their own preferences without stepping on each other.

Autosave as you toggle

Flip a switch and it's saved. A small inline indicator confirms so you're never unsure whether it stuck.

Small set, tuned on the way

We'd rather ship the notifications that actually help than a pile you end up silencing. More event types land as the product grows.

03 · How it works

Event happens, a tidy email follows.

  1. Event fires

    A patient books, completes a questionnaire, signs a consent, sends a message — any of the supported events.
  2. Preferences decide

    Each user's preference says whether they want an email for this event type. No preference means the workspace default.
  3. Delivered once, linked back

    The email links directly to the record in the app — the booking, the patient, the message — so one click drops you where the work is.
  4. In-app counters update

    Chat rooms show unread counts in the workspace so you don't need the email for context you're already seeing.

I turned off what I didn't want to hear about and kept what I did. Nothing clever — and finally my inbox feels honest.

Dr. Raghav MehtaMedical Director · Monarch Primary Care

04 · In practice

Sensible defaults for common roles.

Clinicians

The patient-update emails, not the rest.

Keep questionnaires-completed and consent-received on; quiet the broader organization emails you don't need.

Front desk

Stay on top of meetings and booking-page activity.

Booking-page appointments email the desk so scheduling stays visible without a dashboard refresh every hour.

New teammates

Organization welcome emails stay on.

When someone joins the workspace, org-level emails make the arrival visible. Toggle off once onboarded.

Focused clinicians

In-app only.

Prefer to live in the app? Turn email toggles off; keep the unread counts inside the workspace as your signal.

FAQ

Common questions.

What channels are supported?
Email today, plus in-app unread counts for chat. SMS and push notifications are on the roadmap.
Do you support Slack or Teams?
Not today. Routing specific events into Slack or Teams is something we'd like to build — tell us the events and channels that'd matter for your team.
Are there quiet hours or escalation rules?
Not today. Clinicians can turn individual email types off; richer scheduling (quiet hours, on-call rotation, escalation to a second person) is on the roadmap.
Can admins set defaults for the team?
Yes — workspace-level defaults for notifications, with each user able to override for their own account.
Does every event send an email?
Only the ones we've explicitly wired up and documented in settings. We'd rather add events deliberately than spam inboxes by default.
Ready when you are

Turn down the noise — without missing what matters.

Bring your current notification frustrations to a 15-minute walkthrough; we'll show you what we send and what's on the way.