Importance is not urgency. Your inbox finally knows it.
A two-axis engine scores importance AND urgencyindependently, and learns each sender's pattern from your behavior. Most “AI priority inboxes” collapse everything to one number. We don't.
> the inbox that thinks.
Opens lie. Replies don't. RadMail knows what got a reply, and drafts the follow-up you promised the day it's due.
A faithful simulation of the live triage engine reading a raw inbox. Scripted re-enactment, not a live model call — the engine itself is live in a test bed on two real businesses.
RadMail tracks every commitment in your threads — both what you owe and what you are owed — drafts the reply the day it's due, and watches for the reply so it never nags you about what's already done.
Money, banking, and strangers? Always a human. Forever.
Pick a request — or type your own — and watch auto-send draft it or hard-stop.
no request selected — auto-send is watching.
Apple opens a copy of every message, so a logged open means nothing. RadMail tells you which sends actually earned a reply because it reads your inbound mail too — the reply lands in the same mailbox it sent from.
SPF, DKIM, and DMARC come handled — a per-tenant wizard walks you from none → quarantine → reject, but only once your reports come back clean.
RadMail scores every email on two independent axes importance and urgency— never one blended number. A high-importance, low-urgency contract and a loud newsletter are never confused.
[ engine LIVE today in a test bed on two real businesses ]
sample data — illustrative scores, not a customer metric
why surfaced:known high-value buyer, asks a question, money on the line, replies fast — you answer this sender within the hour 9/10.
A two-axis engine scores importance AND urgencyindependently, and learns each sender's pattern from your behavior. Most “AI priority inboxes” collapse everything to one number. We don't.
A “Right Now”hero lane surfaces the highest-importance mail that actually needs you now — each item tagged with a plain-English “why surfaced.”The AI's judgment is auditable, not a black box.
It reads what they want, gathers the facts with deterministic code (not the model guessing), and drafts a complete answer. The facts are code, so the proposal is solid enough to one-click. Human-confirm, always.
Rules first, the model only when needed — with a self-learning loop that folds your fixes back in overnight. Plus one-click 4D (Do / Defer / Delegate / Delete) with an AI pre-pick.
The engine is live today in a test bed on two real businesses. Join the waitlist to shape what ships.
We're onboarding design partners first. Waitlist members shape the roadmap, the regimes, and the pricing — and lock founding terms.
Every tenant's mail is isolated at the row from day one. The Gmail / Outlook overlay ships after launch — waitlist members get it first.
Designed dark-mode-first — where most branded email inverts to unreadable.
14-template librarytransactional lifecycle outreach
4 need you · 11 handled · ranked by the importance engine
The Priority Digest: a single rendered summary of what needs you, in priority order. The daily proof the inbound brain is working for you.
Compliance is a pluggable per-organization regime, assembled from PolicyPacks. We sign a BAA and process your data on BAA-covered, encrypted, audited infrastructure — compliance is a shared responsibility, and RadMail is a tool that supports your program, not a compliance guarantee.
RadMail is not a compliance certification; it is a tool that supports your program under a shared-responsibility model. The WSLCB cannabis PolicyPack is live in a test bed today; the SOC 2, HIPAA, and FedRAMP/CUI packs are architecture and roadmap.
WSLCB pack live today; the rest are architecture, stated on the record.
SOC 2-aligned controls today, audit planned. On FedRAMP/CUI: a target design only, no authorization held, and we do not handle CUI in production today. For HIPAA tenants, regulated sends are draft/ingest-only and human-reviewed — we do not auto-send regulated mail until SES-prod is in place.
Shared responsibility, stated plainly:RadMail signs a BAA and becomes your Business Associate. It then processes on BAA-covered, encrypted, audited infrastructure. The architecture is the premium lever — never a badge we'd claim we don't hold.
› Talk regimes with usWaitlist members shape it.
Four tiers — Starter, Pro, Business, Enterprise. Prices land later. Join early access, help set them, and lock founding terms.
one team, inbox under control
The inbound brain for one team. It tells you what matters now.
join early access>it acts, then proves it landed
Adds autonomous follow-through and reply-correlation — it writes the email, then proves it landed.
join early access>multi-mailbox, growing ops
Multi-mailbox ops on a SOC 2-aligned controls floor.
join early access>regulated, isolated, integrated
Regulated regimes, region-locked isolation, and a signed BAA.
talk to us>| capability | Starter | Pro | Business | Enterprise |
|---|---|---|---|---|
| Inbound brain + importance engine | [] | [] | [] | [] |
| Autonomous follow-through | [] | [] | [] | [] |
| Reply-correlation | [] | [] | [] | [] |
| Regulated regimes + BAA | [] | [] | [] | [] |
| SOC 2-aligned controls floor | [] | [] | [] | [] |
[ pricing :: TBD — early-access partners lock founding rates ]
The engine is live today in a test bed on two real businesses. Early-access partners set the numbers and lock founding rates before public pricing posts.
On the regulated tiers we sign a BAA and process on BAA-covered, audited infrastructure. Compliance is a shared responsibility— a tool, not a guarantee.
join the waitlist for early-access pricing — no card, no commitment