Notification Routing and Delivery
The governed last mile. Every event, provably delivered.
Herald takes any event the platform raises and routes it to the people, services and systems that need to know. Destinations are reusable notification targets that are owned, shared and versioned, so nobody retypes addresses. Policies add quiet hours, throttling and digests, silences pause noise with a written reason, and a per-attempt delivery ledger lets you prove who was told and when.
After an incident, few teams can show who was told, when, and whether the message arrived. Herald routes platform events to reusable, versioned destinations under policies with quiet hours, throttling, and digests, and keeps a tamper-evident record of every delivery attempt, so you can prove it.
- Reuse targets — email, SMS, webhook, and 150+ messaging and incident services — instead of retyping addresses
- Bundle recipients into policies with quiet hours, throttling, de-duplication, and digests
- Apply time-capped silences with a written reason
- Keep a tamper-evident, per-attempt delivery ledger
- Retry failures automatically and alert the owner on a pattern
What you get
What Herald gives your team.
Reusable notification targets
Email, SMS, webhooks and more than 150 chat, push and incident services, each owned, shared, versioned and searchable.
Confirmed addresses
New email and SMS destinations are confirmed with a 6-digit code before use, and lose confirmation if the address changes.
Notification policies
Bundle people, teams, destinations and agent tasks with delivery windows, severity floors, deduplication, throttling and digests.
Time-limited silences
Quiet an organization or one policy for up to 14 days, with a written reason and early revoke.
Delivery ledger
Every attempt records outcome, timing and attempt number with a masked destination and tamper-evident rows.
Retry and health alerts
Failed deliveries retry automatically, and a destination's owner is alerted on a pattern. In-app alerts name the organization they are about and reach its owners, parents included.
How it works
- 1
Create notification targets
Add email, SMS, webhook or one of 150+ chat, push and incident services as a shared target. New email and SMS addresses are confirmed with a 6-digit code.
- 2
Bundle them into policies
Group people, teams, destinations and agent tasks into a versioned policy with delivery windows, a severity floor, deduplication, throttling and digests.
- 3
Bind events and quiet noise
A subscription binds a whole policy as one recipient. Pause noise with a silence of up to 14 days that carries a written reason and can be revoked early.
- 4
Prove delivery
The Deliveries page filters every attempt by channel, status or policy, opens its timeline, and replays failures. The ledger also records recipients held back, and why.
Ask AI about Herald
Every Herald page has an Ask AI button. It opens a chat that already has the page, its rows, and your selection. Try asking:
- Which notification policies on this page have a severity floor or quiet hours set?
- Which of my destinations are not confirmed yet?
- Show failed deliveries from the last day and which destination each went to.
How teams use it
- Show an auditor who was paged for an incident and when delivery succeeded.
- Stop a noisy event from flooding a team with digests and silences.
- Change who gets paged only after an approved change request.
Frequently asked questions
See Herald in action
Join the early-access list, or talk to our team about your environment.
Talk to us