# Omni-channel alerts

Canonical page: https://docs.ovok.com/signals/with-ovok/omni-channel-alerts

Signals sends alert events. Omni-channel alerts in Ovok tells the people your rule names, over the channels it names.

## Who does what [#who-does-what]

| | Signals | Ovok |
| --- | --- | --- |
| Sends the alert events | Yes, as it always does, to your webhooks and to Ovok | No |
| Holds your [rule](/signals/with-ovok/routing-rules) | No | Yes, with the project |
| Runs the rule on each event | No | Yes |
| Finds the people the rule names | No: it never holds names or addresses | Yes, from the project's FHIR records |
| Sends the email or push | No | Yes, through your email provider and push provider |
| Stores the alert | Yes | No: only a short-lived marker per send, so a retry never tells anyone twice |

Omni-channel alerts is part of Ovok. It does not change what Signals sends. To deliver alerts over a channel of your own, take Signals' [alert webhooks](/signals/standalone/webhooks/alert-triggered) directly.

## How an event reaches people [#how-an-event-reaches-people]

1. Signals sends an alert event, for example [`alert.triggered`](/signals/standalone/webhooks/alert-triggered), to the project's Ovok subscription.
2. Ovok runs your rule on the event. The rule answers who to tell and over which channels.
3. Ovok resolves each recipient group the rule names (`practitioner`, `caregiver`, `relatedPerson`, `sharedWith`) to people in the patient's project, and tells each of them over each channel the rule names.
4. A person with no email address, or no registered device, is skipped for that channel. If a provider fails, Ovok answers so that Signals retries, and only the sends that failed go out again.

A rule that fails tells nobody of that event, and the failure is logged.

## Recipients [#recipients]

| Recipient | Who | From |
| --- | --- | --- |
| `practitioner` | The patient's general practitioners, and the practitioners they share their record with | `Patient.generalPractitioner`, and accepted [record shares](/invitations/share-with-practitioner) |
| `caregiver` | The patient's care team | Members of active `CareTeam` resources whose `subject` is the patient |
| `relatedPerson` | Family members and emergency contacts | `RelatedPerson` resources of the patient not marked inactive |
| `sharedWith` | The people the patient shares their readings with | Accepted [shares with carers](/invitations/share-with-a-carer) and with other patients |

Email goes to the first email address in the person's `telecom`. Push goes to the devices the person registered after signing in.

## What a message says [#what-a-message-says]

The email carries the patient's name, when the alert fired, the event and a link to it. Practitioners get `ALERT_NOTIFICATION`, everyone else `PATIENT_ALERT_NOTIFICATION`; map both in [Email templates](/email-templates/template-catalogue). No reading or value is ever included. A push shows no patient name or value on the lock screen, and its `data` is `{ type: 'ovok.alert', alertId, patientId, event }`.

## Turn it on [#turn-it-on]

The project needs a Signals tenant of its own. Switch on [OMNICHANNEL_ALERTS_ENABLED](/settings-and-features/settings/omnichannel-alerts-enabled), which subscribes Ovok to the tenant's alert events. Then save a [rule](/signals/with-ovok/routing-rules) and map the email templates. The [guide](/guides/omni-channel-alerts) walks through it.

## Related [#related]

- [Rule](/signals/with-ovok/routing-rules)
- [Omni-channel alerts guide](/guides/omni-channel-alerts)
- [Signals alert webhooks](/signals/standalone/webhooks/alert-triggered)
