VesonixOne · Notification Engine

One event.
Every channel.
Automatically.

Route the right message to the right people — across Email, Microsoft Teams, and in-app — triggered by workflow transitions, new records, or deadline reminders. Runs entirely inside your own infrastructure.

Book a Demo → See it dispatch

Delivery
channels

Recipient
strategies

Hardcoded
recipients

↻

Purchase Order #2847 — Approved

Email · Teams · In-App — 3 recipients resolved

just now

⏰

Contract #0091 — Expiry in 2 days

Deadline reminder · Email + In-App sent

3 min

＋

Invoice #1034 — Record created

Teams channel + In-App — 2 users notified

8 min

✉ Email 3

⧆ Teams 3

○ In-App 3

Watch an event
reach every channel

A workflow transition, a new record, or a deadline approaching — each fires the engine. It resolves who should be notified, renders each channel’s message, and dispatches all three simultaneously. No manual intervention.

Notification routing runs entirely inside your infrastructure. No message data leaves your servers.

Notification Capabilities

One engine. Every message your business sends.

✉

Reach Anyone, Any Way

Email, Microsoft Teams, and in-app notifications — all sent from a single event setup, at the same time. One configuration covers every channel.

⊙

The Right Message, The Right Person

Define recipients by role, workflow stage, or assigned field. The engine identifies the right people at the time of sending — no fixed lists to maintain.

►

Approve Without Logging In

Action buttons embedded in the notification email let recipients approve, reject, or act on a record with one click — without opening the application.

⏰

No Action Falls Through the Cracks

Set reminders to fire before a deadline, after a record is created, or when nothing has been done for a set number of days. The engine runs the follow-ups — you don't have to.

↻

Alerts Sent When It Matters

Notify on status changes, new record creation, or approaching deadlines. Each scenario pulls the right details into the message automatically — no manual setup per case.

◗

See Every Message, Every Status

Every notification sent is logged by channel — delivered, failed, or pending — with the full recipient list and any error detail. Nothing is sent without a record of it.

Why Notification Engine

Notifications that route themselves.

✓

Recipients Set by Rules, Not Lists

Recipient rules resolve automatically at the time of sending. Add someone to a role and every relevant notification reaches them — without updating a single list.

✉

One Setup, Three Channels

Set up one notification event and it goes out across email, Teams, and in-app at once. No separate configurations for each channel to manage.

►

Act from Your Inbox

Approvers complete workflow actions directly from the email notification. Secure, time-limited links mean no login required and no security compromise.

⏰

Follow-Ups That Never Slip

Deadline reminders run on their own every day. Once sent, the engine prevents duplicates — the same reminder won't fire again until the configured window resets.

◗

Full Visibility on Every Message

Every delivery — success or failure — is logged with the recipient, channel, and any error detail. You always know exactly what was sent, when, and to whom.

↻

Fits Into How You Already Work

Connect notification events to your existing workflow stages. When a record moves to the next step, the notification fires automatically — no extra development required.

Common Questions

Questions people actually ask.

Click any question to read the answer.

Is there a notification system that alerts the right person automatically?

Notification Engine

Yes — Notification Engine routes one triggering event to the right person across Email, Microsoft Teams, and in-app notifications, based on your workflow rules.

Can recipients act on a notification without logging into the application?

Notification Engine

Yes — action buttons embedded directly in the notification email let recipients approve, reject, or act on a record with one click, without opening the application.

How does the system decide who to notify for a given event?

Notification Engine

Recipients are defined by role, workflow stage, or assigned field, and the engine resolves the right people at the moment of sending — there's no fixed list to maintain as people or roles change.

What happens if no one acts on something that needs a response?

Notification Engine

Reminders can be set to fire before a deadline, after a record is created, or when nothing has happened for a set number of days — the engine runs the follow-ups automatically, so nothing falls through the cracks.

Can we see whether a notification actually reached someone?

Notification Engine

Yes — every notification sent is logged by channel as delivered, failed, or pending, along with the full recipient list and any error detail, so nothing goes out without a record of it.

Do we need to set up each channel separately for every type of alert?

Notification Engine

No — one configuration covers Email, Microsoft Teams, and in-app notifications at the same time, so a single event setup reaches every channel instead of configuring each one separately.

One event.Every channel.Automatically.

One engine. Every message your business sends.

Notifications that route themselves.

Questions people actually ask.

Part of a connected on-premise suite.

One event.
Every channel.
Automatically.