CEDX Bookings · Workplace
Three hundred twenty appointments in 30 days — 83% show rate, 22 no-shows, $36K of idle and no-show waste. Behind the booking page sits the whole operation: services, deposits, risk scores and the hosts' capacity.
A no-show is usually discovered when the host sits alone in the meeting. Here it is predicted: 14 upcoming appointments at risk 80 or above, and one confirmed demo with no deposit at risk 88.
Runs on demo data. Clients, hosts and pages named on screen belong to the demo workspace.
What it is
Every service lists duration, buffer, hosts and — where it applies — price and deposit. The trial wrap-up runs 30 minutes with a 15-minute buffer at $340; six services hold a deposit. Capacity is designed here, not inherited.
Every page carries views, bookings, conversion and show rate. The implementation-kickoff page converts 34.1% of 367 views and shows at 95%; the hiring screen converts 26.9% and shows at 78% — and the overview flags it.
The appointments table is the ledger: 139 upcoming, 106 held, 22 missed, 53 cancelled or rescheduled. Service, host, status and minutes per row — from a 15-minute executive brief to a 120-minute onboarding workshop.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/bookings.
01 — Overview
Capacity utilisation 50%, waste $36K, and the alerts that follow: sales calendars bleeding idle hours Tuesday to Thursday, recruiting screens under 80% show, a paid review pending without its deposit.
02 — Appointments
A QBR at 60 minutes sits next to a 15-minute campus interview; a no-show trial wrap-up stays on the record as a no-show. The diary does not forget what the slot cost.
03 — Services
Twenty-four active services with their buffers and hosts — partner intro at 90 minutes with one host, the onboarding workshop at 120 with two. The four priced types show their prices in the table.
04 — Booking pages
Every public page shows its funnel: views to booked to held. The migration-plan page converts 33.4% and shows at 90%; the paused feature-lab page kept its 91% show rate on the record.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Owns the demo and QBR slots. The Tuesday-to-Thursday idle-hours alert is their calendar, and the deposits on high-risk VIP demos are their chase list.
high risk soon · 14
Runs the hiring screen and panel interviews. The 78% show rate on hiring screens triggered the confirm-gate tightening on the do-this-next queue.
hiring screens · 78% show
Works the priority-support page — 30-minute slots, 94 booked in 30 days, 94% show. The queue and the calendar are finally the same thing.
support page · 94% showThe 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
A host's availability becomes a booking page with its own slug, service lengths and buffers.
The client picks a slot; the funnel counts the view, the booking and, later, whether they showed.
High-value services hold a deposit — six of them do — and high-risk bookings get double-confirmed before the day.
Show rates, waste and risk land on the overview: which pages convert, which hosts idle, which slots never happen.
One record
A booking is not a standalone event. It is the same client, calendar and conversation the rest of the estate holds.
The appointment lands on the host's calendar with load scores and conflicts already known.
CEDX MeetThe held appointment becomes a scored meeting — attendance, notes and ROI follow it.
CEDX CRMThe demo request and the QBR sit on the same account record the pipeline reads.
CEDX MailConfirmations and the double-confirm chase run through the shared inbox on the same thread.
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 services, your hosts
Bookings with the rest of it
Questions
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/bookings. It runs on demo data — the clients, hosts and pages belong to a demo workspace, not to a customer.
A per-appointment figure on upcoming bookings — 14 sit at 80 or above in the demo view. The alert that names the pattern is specific: a confirmed demo with no deposit at risk 88. The do-this-next queue answers with deposit chases and double-confirms.
Idle hours plus no-show hours across host calendars — $36K in the demo workspace, with the worst host-days tabled by dollar cost. The root cause is printed: Tuesday to Thursday on the sales calendars.
Six services in the demo catalog carry a deposit hold — the flag is on the service row next to duration and buffer. The alert for the paid review pending without its deposit shows what happens when one slips through.
Its own funnel: views, bookings, conversion and show rate — 2,358 bookings came through 42 pages in 30 days at 21.1% average conversion. The best page converts 34.1% and shows at 95%; the hiring screen's 78% show rate triggered a confirm-gate fix.
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 count last month's no-shows on your own calendar.