Capture & Ingest
Records land in CEDX Feedback already linked to the canonical customer, employee, or vendor ID.
Feedback turns a suggestion box into a scored backlog: every post carries the voter's plan and ARR, duplicates cluster with merge confidence, themes score votes against effort, and shipped posts close the loop with the people who asked.
"When Sales, Operations, and Finance read and write the exact same Postgres record, month-end stops being a detective i..."
| Ticket / Incident ID | Customer & ARR Tier | Assigned Queue & Pod | SLA Breach Clock | Root-Cause Context | Resolution Score |
|---|---|---|---|---|---|
| INC-49201 · API Webhook LagCEDX Feedback · Record #1040 | Meridian Corp · $420K ARR | Tier-3 Platform Pod | 18m remaining | ● Linked to PR #4812 | 98% Confidence |
| TCK-88310 · Billing Seat SyncCEDX Feedback · Record #1041 | Harbor Retail · $640K ARR | Enterprise Billing Ops | 1h 42m remaining | ● Auto-Resolved via Books | 100% Verified |
| INC-49209 · SSO SAML RotationCEDX Feedback · Record #1042 | Atlas Logistics · $285K ARR | Identity & Access Queue | 44m remaining | ● Cert Runbook Attached | 95% Confidence |
| TCK-88344 · Field Dispatch RMACEDX Feedback · Record #1043 | Cedar Foods · $310K ARR | Field Service Dispatch | 3h 15m remaining | ● Parts Reserved in WMS | 94% Confidence |
The theme table quietly settles roadmap arguments: a $22K theme with XS effort scores 102.6 while a $420K theme at XL scores 74.1. Small and certain beats big and expensive, with the arithmetic showing.
Every capability below runs against the shared CEDX Postgres database with zero external sync queues or reconciliation lag.
Three hundred twenty posts with theme, status, plan, votes, ARR and a 30-day vote sparkline per row. A CSV-export request, submitted again, shows 109 votes and $4.13M of account value behind it, which is why “again” matters.
Themes aggregate posts, votes, accounts and ARR next to effort. Dark mode leads at 102.6 on ten posts and XS effort; offline sync (28 posts, 412 votes, $420K, XL effort) sits fourth at 74.1. The score is the argument, printed.
The overview scores board health at 82 and lists its dials: 14 unthemed posts, 28 duplicate clusters, 19 stale reviews, 21 days average age. The merge alert names its threshold, confidence ≥0.7, so dedup is a decision, not a vibe.
Every figure below is directly inspectable in the running CEDX Feedback application workspace with zero synthetic projections.
Click any screen below to inspect how CEDX Feedback moves from initial intake to verified cross-estate completion.
Posts by status read like a pipeline: 68 new, 54 in review, 42 planned, 38 building, 52 shipped, 66 declined. The intake chart carries the board's own history as markers: a relaunch, a new sales board, a merge-backlog spike.
Every support agent sees the customer ARR, overdue invoices, active renewal date, and linked engineering sprint issue without switching tabs.
Records land in CEDX Feedback 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.
Owns close-the-loop: the 61% of voters told their request shipped, and the 39% who heard nothing. The tablet at the exit is the same gesture, offline.
Lives in the theme table: 36 themes, and the standing question of why a $22K XS theme outranks a $420K XL one.
Merges the 28 duplicate clusters at confidence ≥0.7 and clears the 14 unthemed posts that arrive every week.
CEDX Feedback 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.
Support tickets are unsolicited feedback. Desk's subjects and this board's posts often say the same thing in different clothes.
The 24 on-roadmap posts link somewhere. Roadmap is where the commitment gets a date and a swimlane.
“The docs were wrong” is a feedback post too. The help centre's no-hit list is the other ear, counting searches instead of votes.
Ask AI (⌘J) sits on every Feedback screen, versioned and traced by the Copilot console behind it.
"When Sales, Operations, and Finance read and write the exact same Postgres record, month-end stops being a detective investigation across six spreadsheets."
"Our operators actually enjoy opening the workspace. Every screen is fast, legible, and grounded in live production data with zero synthetic clutter."
"Having identity, least-privilege access, audit trails, and business applications on one kernel cut our security review and provisioning time by 82%."
Drag the seat slider to compare your current stitched stack (ServiceNow CSM + Zendesk Enterprise + Intercom + PagerDuty) against running CEDX Feedback natively on the unified CEDX estate.
Explore the live CEDX Feedback workspace on canonical demo data at /app/feedback, or book a 30-minute architecture session to map your first entity rollout.
Instant browser access to CEDX Feedback pre-loaded with canonical demo records and connected across the 132-application CEDX estate.