CEDX Conversations · Sales & CRM
Five channels, one inbox. Every thread knows who is waiting on whom, for how long, and what it risks — so “I'll get back to them” becomes a queue you can clear, measured in hours.
The top signal in the demo inbox: a buyer compared pricing against an alternative in their last message. The recommended move is not “reply soon” — it is: send the differentiation one-pager before the next call.
Runs on demo data. The workspace named in the chrome is the demo tenant, not a customer.
What it is
93 threads where the buyer spoke last, sorted by hours waiting — 13.4 at the top — with priority, channel, deal and owner. VIP waits are flagged in the subject line, and the first-response SLA is named when it is at risk.
When a deal's conversations spread across people and channels without coordination, the risk table scores it: the top deal cluster shows 4 open threads across 3 channels at risk 96. The fix is to multi-thread deliberately, not to hope.
Each channel reports threads, open, needs-reply, reply rate, SLA rate and median wait: SMS answers in 1.7 hours at 72% SLA; meetings wait 4.9 hours at 52%. You fix the channel that is actually broken.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/conversations.
01 — Overview
195 open threads of 320, 93 needing reply, 136 at next-step risk. The cadence-health ring scores the book at 30 and itemises why: next-step risk, multi-thread, needs reply — each a number you can click into.
02 — Inbox
The ranked stream leads with what changed: an alternative mentioned in the last message, two new stakeholders touching one deal's threads, a VIP waiting 8 hours on a meeting reply. Underneath, the needs-reply queue carries wait in hours.
03 — Threads
The ledger: subject, channel, touches, status, owner and last activity. Security questionnaire, SSO requirements, MSA markup — the subjects read like a real quarter, and statuses run open, waiting, snoozed, won and lost.
04 — Channels
Email, meeting, call, social and SMS, each with reply rate, SLA rate and median wait. The blended 59% SLA conceals a 72% SMS desk and a 45% social channel — which is why the table exists.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Clears the needs-reply queue by wait time. The 13.4-hour thread at the top is the first call of the day, not the one they remembered.
wait · 13.4h
Works the routed signals: a reply gone quiet, a new stakeholder to acknowledge, a one-pager to send before the next call.
signals · 10
Reads the cadence-health ring and the channel table. A 45% SLA on one channel is a staffing decision, made on evidence.
SLA · 59%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
The ranked stream leads the inbox: what changed overnight, weighted, with the move attached. The queue comes second.
Needs-reply sorts by hours waiting. The 13-hour thread at the top outranks the one you happen to like.
New stakeholders get acknowledged and added — the stakeholder-surge signal exists because single-threaded deals die quietly.
Weekly, per channel: reply rate, SLA, median wait. Fix the broken one; leave the rest alone.
One record
A conversation is not a separate silo — it is the living edge of the same account and deal record.
Every touch lands on the account: last touch, health, idle days all move because a thread moved.
CEDX OutboundA reply auto-pauses the sequence and arrives here — the handoff between cadence and conversation is automatic.
CEDX PipelineA thread that books a meeting moves the card; a thread gone quiet is why the card ages.
CEDX DeskWhen the conversation is support, not sales, it continues as a ticket against the same account.
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 SLAs
Conversations with the rest of it
Questions
Yes. Every screenshot is a capture of the running build at /app/conversations, on demo data. The demo workspace is named in the chrome.
Any thread where the buyer spoke last. The queue shows 93 of them with wait in hours, priority and owner — and a VIP flag where the contact's seniority makes the wait expensive.
A deal whose conversations spread across people and channels without coordination. The risk table scores it — 4 open threads across 3 channels at 96 — and the recommended move is to acknowledge and add the new stakeholders, not to bypass them.
The captures show call as a channel with its own reply and SLA rates. What call capture and recording involve for your jurisdiction is a setup and counsel conversation; we are not claiming it on this page.
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 how many of your own buyers spoke last — and for how long.