Overview
Most messaging is reactive. The proactive engine flips it: store and EMR events trigger outbound sends — order updates, reminders, results — with quiet-hours windows, automatic retries on failure, failure alerts, and an on-demand 'fire' API for your own systems.
- Triggered by store, EMR, or your own system events
- Quiet-hours windows so messages never arrive at 3am
- Automatic retries when a send fails
- Failure alerts so nothing slips silently
- On-demand 'fire' API to trigger sends from your code
- Every send rate-limited and logged for audit
How it works
1
An event happens
An order ships, a result is ready, or your system calls the fire API — each becomes a queued proactive send.
2
The engine decides when
Sends respect each customer's quiet hours and your rate limits, holding messages until the right window.
3
Delivery, retried and logged
Failed sends retry automatically, raise an alert if they keep failing, and every attempt lands in the audit log.