OMNIA Notifications is the hub that serves every product: it receives an event, resolves who to notify, with which template and through which channel, and retries until delivery is confirmed. The producer only reports what happened; the Hub decides the rest.
01 What it does
Every source system fires business events: a policy that gets issued, a claim that moves forward, a payment that comes due. None of them knows (or needs to know) who to notify, with what message, or through which channel. That responsibility lives in a single place: OMNIA Notifications.
The producer sends only the event and its business data, never a recipient or a template. If the producer retries the send, the Hub automatically discards the duplicate before touching any channel: reliable delivery, no duplicates.
The Hub walks the client → site → contact hierarchy to find who the message belongs to, with precedence rules and a fallback contact when data is missing at the source.
If a channel fails, the Hub retries with growing backoff and, if needed, falls back to a backup channel. The whole journey lives in a single state model, from received to delivered and certified.
02 Channels
Each channel is interchangeable from the event's point of view: the Hub picks the right one based on the template, the contact's preference, and the product's rules, not on what each team happens to know how to build.
Templates with declared variables, delivered via SMTP with automatic retry on a transient bounce.
Business messages over WhatsApp Business, with the same contact resolution as every other channel.
For short, urgent alerts when email or WhatsApp aren't enough or don't apply.
Certified mail with proof of delivery and a deadline watcher that escalates the case if certification doesn't arrive on time.
Push notifications to the client's or policyholder's app, with the same event and the same template resolved for the channel.
The same event contract can trigger an AI voice agent as a contact channel: same recipient resolution, same status trail.
03 How it works
The producer never decides these three things. Every event goes through the same journey, no matter which product it comes from or which channel it ends up using.
The source system publishes the business fact. The Hub identifies it, automatically discards duplicates, and transforms it into its own data model before deciding anything.
It resolves the recipient by walking client → site → contact, and in parallel picks the template based on the combination of event × channel × source system × product. No one else in the organization needs to know this rule.
It sends through the chosen channel, retries on failure, falls back to a backup channel if needed, and certifies delivery when the case requires it. The entire path, from received to delivered, certified, and completed, is traced end to end.
04 Built to be trusted
A hub that serves every product can't afford to lose messages or improvise template changes. Every piece of the design answers to that.
Retrying the publication of an event never duplicates a notification that was already sent: reliable delivery, always.
What fails gets retried with judgment; what can't be processed stays isolated and traceable, never lost.
Changing a message goes through approval and lands in an audit log, not a silent deployment.
Business and system health metrics, not just logs, to watch the hub operate in real time.
If your product already lives in the OMNIA ecosystem, you don't need to build your own email, SMS, or certified-mail delivery: the Hub already knows how.