CEDX Notify · Platform
Email, push, SMS, in-app and webhook from one console. The demo fleet's sample is blunt about it: 380 deliveries, 104 delivered, 116 failed hard or soft, 103 still in flight — and 31 recipients past the fatigue line, whom the system will not keep pushing.
The status that earns trust is not Delivered — it is Suppressed: the message the system chose not to send because the recipient has had enough. It sits in the table like any other row.
Runs on demo data. Northline Systems in the captures is the software's demo workspace, not a customer.
What it is
The delivery log carries channel, status, campaign, attempt number and send date on every row — including the failures. Bounced, Suppressed and Failed are statuses with counts on the tabs, not exceptions buried in a log export.
Sixty-four campaigns, 36 active, and 30 marked AI-optimized — timing, channel or variant chosen by the system and labelled as such on the row. Sent, delivered and failed are columns per campaign, so the busiest webhook campaign's 3,800 failures sit next to its 78,000 sends.
Forty-eight templates, 33 live, each with channel, category, version, 30-day sends, CTR and failure rate. A transactional SMS at version 5 with 31,000 sends and 1.1% failure is a different object from a marketing push at 4.2% — and both rows say so.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/notify.
01 — Overview
The health ring reads 38 — delivered 104, failed or bounced 116, in flight 103, fatigue 31 — and the Do this next panel ranks the response: run the failure-risk board (102 rows at 55% or higher fail probability), throttle the fatigue cohort, fail over the degraded push pool.
02 — Deliveries
Four hundred eighty-character truth: a webhook delivery clicked on attempt one, an in-app message bounced on attempt four, a survey push suppressed. Recipient, campaign and status per row, searchable.
03 — Campaigns
Sixty-four campaigns with status, AI flags, channels, sent, delivered and failed. The difference between an active churn-save at 2,073 failures and a completed re-engagement at 722 is the operating picture this table exists to give.
04 — Templates
Every template with its version, channel, category and 30-day performance. Failure rates run 0.2% to 4.8% across the live set — the 1.7% average on the header is computed from rows you can inspect.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Owns channel health: the push pool at 39, the SMS route at 42, and the failover the console recommends before the failure rate becomes a complaint.
failure-risk board · 102
Owns the 64 campaigns and the AI flags on 30 of them — and respects the fatigue cohort, because the throttle is the product working, not failing.
fatigue cohort · 31
Owns templates and versions: 48 in the library, 9 drafts not shipping, and the failure rate on every live version.
avg fail · 1.7%The shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
A template ships at a version — v5, not a mystery edit — with its channel and category declared.
The campaign delivers across channels, attempts counted per row, failures named as they happen.
Fatigue and quiet hours intervene: 31 recipients are past the line, and Suppressed rows are the system keeping its word.
CTR, failure and fatigue feed the next send — 30 campaigns now run AI-chosen timing, channel or variant, labelled on the row.
One record
Notify is how the other products reach people — and the fatigue rules are how the estate avoids shouting.
Dunning paths and alert relays in Workflow end as deliveries here — the automation decides what, Notify decides whether now.
CEDX EventsStream alerts — lag, schema breaks, dead letters — are the signals that become the messages this console delivers.
CEDX JourneysLifecycle campaigns are the message layer of journeys; the fatigue cap applies across both, so a journey cannot out-shout the fleet rules.
CEDX AuditSends, suppressions and preference changes are events worth a trail — and Audit keeps the trail.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your channels, your templates
Notify with the rest of it
Questions
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/notify. It runs on demo data — the sample log is labelled a sample on the screen itself.
A score per recipient; at 70 or above the system throttles. Thirty-one profiles are past the line in the demo fleet, quiet hours are annotated on the timeline, and messages held back this way appear in the log as Suppressed — visible, not silently dropped.
Scores deliveries and campaigns by fail probability — 102 rows at 55% or higher in the demo — so degraded channels are found before recipients find them. The Overview ranks running that board as the top recommended action.
Each channel pool carries a health score and failure rate: the weakest push pool reads 39 at 4.5% failure, the best email pool 61 at 1.7%. Failover is a recommended action on the same screen, not a console command you have to know.
In three labelled places: timing, channel and variant selection, chipped on the campaign rows that use them — 30 of 64 in the demo. Everything a template says is still a versioned template a person shipped.
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
Live build, demo data, no card. Then ask what your own messaging stack does about a recipient who has had enough.