Capture & Ingest
Records land in CEDX Knowledge Base already linked to the canonical customer, employee, or vendor ID.
Knowledge Base measures itself the way a sceptic would: every article carries views, avoided contacts, deflection rate and helpful votes; the searches that found nothing are a queue of their own.
"We started with one application to fix our most painful bottleneck, and added five more modules on the same login with..."
| Ticket / Incident ID | Customer & ARR Tier | Assigned Queue & Pod | SLA Breach Clock | Root-Cause Context | Resolution Score |
|---|---|---|---|---|---|
| INC-49201 · API Webhook LagCEDX Knowledge Base · Record #1040 | Meridian Corp · $420K ARR | Tier-3 Platform Pod | 18m remaining | ● Linked to PR #4812 | 98% Confidence |
| TCK-88310 · Billing Seat SyncCEDX Knowledge Base · Record #1041 | Harbor Retail · $640K ARR | Enterprise Billing Ops | 1h 42m remaining | ● Auto-Resolved via Books | 100% Verified |
| INC-49209 · SSO SAML RotationCEDX Knowledge Base · Record #1042 | Atlas Logistics · $285K ARR | Identity & Access Queue | 44m remaining | ● Cert Runbook Attached | 95% Confidence |
| TCK-88344 · Field Dispatch RMACEDX Knowledge Base · Record #1043 | Cedar Foods · $310K ARR | Field Service Dispatch | 3h 15m remaining | ● Parts Reserved in WMS | 94% Confidence |
The Deflection screen prints its formula under the funnel: avoided ÷ (avoided + contacted). A number with its working shown is a number you can argue with. That is the point.
Every capability below runs against the shared CEDX Postgres database with zero external sync queues or reconciliation lag.
The article list reads like a ledger: views, avoided contacts, deflect %, helpful %, status and author on every row. The password-reset article deflects 46% on 14K views; a data-residency article deflects 26% and is flagged for work in the same table.
Categories are managed, not just nested: 697 articles summed across 36 of them, with a 43% mean deflection and an owner on every row. Billing & plans deflects 52% on 64K views; the search category sits at 22%, visibly below the line.
918K article views in 30 days become 71K estimated contact intents, 29K avoided tickets and 42K still-contacted, and the screen says how: intent contacts are readers who would have opened a ticket without self-serve.
Every figure below is directly inspectable in the running CEDX Knowledge Base application workspace with zero synthetic projections.
Click any screen below to inspect how CEDX Knowledge Base moves from initial intake to verified cross-estate completion.
Forty per cent deflection with the dials behind it: 229 published, 28 in review, 45 draft, 18 archived. The alerts are root-caused: one no-hit cluster has 286 misses and a suggested title; 46 published articles are not indexed, so self-serve fails before it starts.
Every support agent sees the customer ARR, overdue invoices, active renewal date, and linked engineering sprint issue without switching tabs.
Records land in CEDX Knowledge Base 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.
Works the do-this-next list: 54 published articles without owners, 42 articles to write straight off the no-hit board.
Reads the 71 open no-hit queries as the voice of the queue. These are the exact strings customers typed and found nothing for.
Runs the index audit. Forty-six published articles are not indexed, which means self-serve loses before the first keystroke.
CEDX Knowledge Base 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.
Desk's knowledge screen is the agent-side view of the same idea: macros and articles with uses-30d and the same stale flags.
The chat bot's containment, 40% on its floor, is only as good as the articles it answers from. That library is this one.
Ask AI (⌘J) sits on every screen here. Grounded answers cite their sources; this is the kind of source they cite.
Votes and no-hits are two spellings of the same signal. Feedback counts the first; this page counts the second.
"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 (ServiceNow CSM + Zendesk Enterprise + Intercom + PagerDuty) against running CEDX Knowledge Base natively on the unified CEDX estate.
Explore the live CEDX Knowledge Base workspace on canonical demo data at /app/knowledge-base, or book a 30-minute architecture session to map your first entity rollout.
Instant browser access to CEDX Knowledge Base pre-loaded with canonical demo records and connected across the 132-application CEDX estate.