Capture & Ingest
Records land in CEDX Mail already linked to the canonical customer, employee, or vendor ID.
Support@, sales@, billing@, hello@ and noreply@ land in one place, with a needs-reply queue instead of an unread count, a wait time on every thread, and a delivery score on every sending domain.
"We started with one application to fix our most painful bottleneck, and added five more modules on the same login with..."
| Workspace Artifact / Room | Connected Estate Object | Collaborators & ACL | Live Telemetry / Edits | DLP & Retention Policy | Sync Latency |
|---|---|---|---|---|---|
| FY26 Board Pack & Financial ModelCEDX Mail · Record #1040 | Live Query -> CEDX Books GL | CFO + Audit Committee (8) | 42 Live Cell Bindings | ● Strict Boardroom ACL | 0.008s Live |
| Meridian Deal Desk War RoomCEDX Mail · Record #1041 | Bound to CRM Opportunity #409 | AE + Legal + RevOps (11) | Redline v3 Signed in Sign | ● 7-Yr Contract Retention | 0.011s Live |
| Q4 Product Architecture SpecCEDX Mail · Record #1042 | Linked to 18 Sprints Issues | Core Systems Group (34) | Whiteboard + Docs Synced | ● Internal Engineering | 0.009s Live |
| Global All-Hands BroadcastCEDX Mail · Record #1043 | 418 Attendees in CEDX Meet | Executive Leadership | Live Transcript Indexed | ● Auto-Published to Intranet | HD Zero-Jitter |
The most honest numbers on this page are the ones the software prints on itself: 77 threads need reply, median wait 4.1 hours. A mailbox that can see its own backlog is one you can manage.
Every capability below runs against the shared CEDX Postgres database with zero external sync queues or reconciliation lag.
The inbox opens on the 77 threads that owe someone an answer, sorted so the worst wait, 17.4 hours on a billing thread, sits at the top. Every row carries its mailbox, priority, wait and assignee, so triage is a sort, not a scroll.
Labels are inventory, not decoration: 20 built-in system labels and 28 the team defined, each with its thread count, unread count and health. Q3 nurture holds 210 threads; the 13 low-activity labels are flagged stale so the taxonomy gets pruned instead of fossilising.
320 threads across inbox, sent, archive, spam and starred. Each row shows message count, folder, mailbox and who has it, so “where did that customer thread go” is a filter away, not a forward-and-pray.
Every figure below is directly inspectable in the running CEDX Mail application workspace with zero synthetic projections.
Click any screen below to inspect how CEDX Mail moves from initial intake to verified cross-estate completion.
Unread 104, needs reply 77, queue depth 78 failed-and-retry, delivery score 63, median wait 4.1h. The alerts arrive root-caused: one sending domain at score 5 with bounce 6.2% and an IP reputation of 48, 27 outbound messages needing retry, a nurture sequence losing people at step 3.
A number in CEDX Sheets or Slides is never a dead copy-paste: it is a live, permission-checked reference to CEDX Books, CRM, or People.
Records land in CEDX Mail already linked to the canonical customer, employee, or vendor ID.
Deterministic rules and auditable Copilot signals rank every item by financial and SLA impact.
Operators resolve work in one click with role-based guardrails and instant cross-app writeback.
Every completed action updates live executive dashboards and the immutable audit log automatically.
Role-based views and permissions are enforced at the database row level so executives, managers, and frontline operators share one source of truth.
Lives in the needs-reply queue. Owns the median wait and the 17-hour tail, and assigns before the morning standup instead of after it.
Watches the per-domain scores and the send queue. When a domain drops to 5 with bounce at 6.2%, that is their page, not a surprise in a weekly report.
Works sales@ and the VIP flags. The demo request waiting 15 hours is pipeline, and the queue treats it that way.
CEDX Mail is not an isolated point tool. It reads and writes the exact same customer, ledger, and identity records as the rest of the CEDX software estate.
The support@ queue in these captures is the same work Desk drives: refunds, password resets, portal errors. One conversation, two doors.
When a thread stops being a thread, it escalates to a channel without losing the record of how it started.
The demo requests sitting in the inbox land as events, with the organiser's load score already known.
Ask AI (⌘J) sits on every one of these screens, grounded in the same record.
"We started with one application to fix our most painful bottleneck, and added five more modules on the same login without a single migration project."
"Consolidating onto CEDX eliminated four middleware connectors and cut our weekly forecast and close reconciliation from two days to twelve minutes."
"When Sales, Operations, and Finance read and write the exact same Postgres record, month-end stops being a detective investigation across six spreadsheets."
Drag the seat slider to compare your current stitched stack (Google Workspace Enterprise + Slack Grid + Notion + Loom + Box) against running CEDX Mail natively on the unified CEDX estate.
Explore the live CEDX Mail workspace on canonical demo data at /app/mail, or book a 30-minute architecture session to map your first entity rollout.
Instant browser access to CEDX Mail pre-loaded with canonical demo records and connected across the 132-application CEDX estate.