Messaging Channels
Mobile push, web push, in-app, inbox, email, SMS, WhatsApp, RCS, on-site and webhooks, with no margin on delivery.
DeliverExplore Channels
Deliver
The rules that make the platform safe to hand to a marketer.
Frequency caps, quiet hours, suppression, send-rate throttling, a blast-radius ceiling and a delivery log that explains every miss.
One customer, one day
u_5f2a · Asia/Kolkata · Tue 22 Sep · caps: push 1 / day, all channels 3 / day, 6 / week
today2 / 3
combined week4 / 6
delivered held: deferred or capped suppressed transactional
Blast-radius ceiling · organisation
projected 1.2M sends > ceiling 1.0M: refused to activate
Delivery log
every miss has a reason- 02:40pushdeferredquiet hours 22:00–08:00 · delivered 08:00
- 14:30smssuppressedunsubscribed 12 Sep via reply STOP
- 16:00pushcappedpush 1 / day reached · queued to 09:00 tomorrow
Overview
One misconfigured rule can send four million pushes at three in the morning. Edverix evaluates every send against per-channel and cross-channel caps, minimum gaps, quiet hours in the customer's own timezone and suppression lists, then against an organisation-wide ceiling. Every attempt, delivered or not, is logged with its reason.
Only on Edverix
- Blast-radius ceilingOnly on Edverix
A maximum send volume for the organisation. Anything projected to exceed it refuses to activate; a running campaign that breaches it halts itself.
- Organisation-level notification policyOnly on Edverix
A workspace admin sets rules for their whole team, overriding individual preferences. Essential for B2B products.
- Simulation before activationOnly on Edverix
Replay any campaign over thirty days of real events: who would have received it, how many times, and where a cap would have stopped it.
Capabilities
Everything in Governance
12 capabilities in 3 groups, organised the way the product is.
Frequency and timing
Caps per channel and combined
Daily, weekly, monthly and lifetime ceilings evaluated in each customer's timezone, with a cross-channel limit on top.
Minimum gap between messages
Nobody gets two things fifteen minutes apart unless you say so.
Quiet hours
Per day of week, in local time, with an explicit choice to skip or defer to the morning.
Queue rather than drop
A send blocked by a cap is held and delivered later, not silently lost.
Send-time and best-channel optimisation
Per-person best hour and channel learned from their own history, exposed as journey nodes you can see.
Protection
Suppression lists
Unsubscribes, hard bounces, complaints and national do-not-call registries, enforced on every send.
Send-rate throttling
Protects your checkout, support desk and infrastructure from the spike your campaign just created.
Blast-radius ceilingOnly on Edverix
A maximum send volume for the organisation. Anything projected to exceed it refuses to activate; a running campaign that breaches it halts itself.
Organisation-level notification policyOnly on Edverix
A workspace admin sets rules for their whole team, overriding individual preferences. Essential for B2B products.
Proof
Simulation before activationOnly on Edverix
Replay any campaign over thirty days of real events: who would have received it, how many times, and where a cap would have stopped it.
Per-message delivery logOnly on Edverix
Every attempted send with its outcome and reason: suppressed, capped, outside quiet hours, token expired, provider rejected.
Delivery forensics in plain languageOnly on Edverix
Ask why a specific person did not receive a specific message and get an answer, not a ticket.
FAQ
Questions about Governance
Do transactional messages respect caps?
No, by design. Transactional sends use a separate endpoint that bypasses caps and quiet hours, and are labelled as such in the delivery log.
What happens when the blast-radius ceiling is hit?
The campaign pauses, the owner and approvers are notified, and it resumes only when someone with the right permission raises the ceiling or confirms the volume.
Get started
See Governance on your own data.
Send your first event in an hour, simulate your first journey against real history, and keep every byte of it in a database you can query.
- No credit card for the Developer plan
- Bring your own providers
- Export everything, any time