The pre-call discovery brief picks the slot. The battlecard library frames the conversation. The demo is the moment the slot decision either pays off or unravels. Most dental AI reps walking into a live product demo carry one walkthrough and run it identically against every prospect — which means an A-slot Voicify-displacement deal sees the same eight minutes of platform-breadth proof as a B-slot Voicify-defense deal, and neither buyer gets the slot-specific proof they actually need. The slot-tagged demo script fixes that. Twenty-two minutes, four acts, eleven beats, and three trap doors named in advance so the rep can avoid them in the moment.
TL;DR
Twenty-two minutes. Four acts. Eleven beats. Two slot variants. The Voicify A-or-B demo script runs the same opening setup and core voice flow in both slots, then forks at minute eleven into slot-specific proof — A-slot proves migration safety, parity, and cutover; B-slot proves PMS depth, platform breadth, and multi-channel coverage. Three trap doors (integrations rabbit hole, admin-screen detour, AI-tech monologue) get named in the script so reps recognize them mid-call. The minute-twenty-two close seeds the post-call note, verifies or flips the slot tag, and hands the deal to the proposal-stage queue with slot context attached.
Why a Universal Demo Script Costs You Twelve Minutes
The universal demo problem is mechanical, not strategic. A dental AI walkthrough has roughly thirty proof beats across the platform — call answering, message routing, appointment booking, intake collection, PMS write-back, after-hours coverage, multilingual handling, owner-line escalation, and so on. A twenty-two-minute demo can fit eleven of them. Picking which eleven depends on the slot. An A-slot prospect already has a Voicify-trained office manager and a working integration; they do not need a demo of basic call answering, because they have been operating that for ten months. They need the migration mechanics and the parity verification. A B-slot prospect, on the other hand, has been pitched depth-versus-breadth by a dental-pure competitor; they need the multi-channel proof and the platform story.
The universal demo splits the difference. It runs four minutes on basics that an A-slot prospect already has, three minutes on migration that a B-slot prospect does not care about, and ends with five rushed minutes of slot-relevant proof when the prospect's attention has already drifted. Twelve minutes of misallocation per demo, across an entire sales team, across a quarter — the demo conversion gap between teams running slot-tagged scripts and teams running universal scripts is meaningfully wider than most enablement leads expect. The script below removes the universal-demo tax by structuring the first two acts as shared and forking acts three and four by slot.
The Four-Act Structure
Both slots share Acts 1 and 2. The fork happens at the start of Act 3, minute eleven. Act 4 is shared again but with slot-specific close language.
| Act | Minutes | Beats | Slot variant? |
|---|---|---|---|
| Act 1: Setup | 0:00 – 4:00 | Greeting, scene-set, screenshare, account context recap | Shared (with slot-tag in greeting) |
| Act 2: Core Voice Flow | 4:00 – 11:00 | Inbound call live demo, intent classification, appointment intake, PMS write-back | Shared (PMS write-back uses prospect's named PMS) |
| Act 3: Slot-Specific Proof | 11:00 – 19:00 | A-slot: migration, parity, cutover. B-slot: PMS depth, multi-channel, breadth | Forked |
| Act 4: Handoff | 19:00 – 22:00 | Three-line summary, slot verify or flip, follow-up commitment | Shared (close language varies by slot) |
Act 3 Beats by Slot
A-Slot (Voicify Displacement)
The A-slot Act 3 has three beats and runs eight minutes. The prospect is currently on Voicify or has run a Voicify pilot recently. The job-to-be-done is to make migration feel safe, prove parity on the features they already rely on, and outline a cutover timeline that does not disrupt operations.
- Beat A1 — Migration safety (3 min). Walk the migration workflow: data export from Voicify, mapping into the new system, the rollback path. Name Voicify here because the workflow cannot be discussed abstractly. Show the rollback toggle on screen — the visible rollback option does more for migration-anxiety than any verbal reassurance.
- Beat A2 — Parity checklist (3 min). Run the four-or-five features the discovery brief flagged as “currently relied on.” Demo each in the new system, in the same order the prospect described them. The point is not to wow the prospect with new capability; it is to retire the question “will I lose anything?”
- Beat A3 — Cutover timeline (2 min). Pull up the cutover template — two weeks parallel, one week shadow, full switchover with a thirty-day Voicify-rollback safety window. The shadow week is the line item that lands the deal more often than any other element of the cutover.
B-Slot (Voicify Defense vs Dental-Pure Challenger)
The B-slot Act 3 has three beats and also runs eight minutes. The prospect is in market for an AI receptionist, has been pitched by a dental-pure competitor, and is weighing depth versus breadth. The job-to-be-done is to prove that the platform's PMS integration is at parity with the dental-pure competitor on the integration depth that matters, and that the platform breadth offers material multi-channel coverage the dental-pure competitor cannot.
- Beat B1 — PMS depth (3 min). Demo the PMS write-back live, including the two or three operations the dental-pure competitor has positioned as their depth advantage (procedure code mapping, treatment plan acknowledgment, hygienist column logic, depending on the named competitor). The discovery brief's opponent-expected field tells the rep which operations to feature.
- Beat B2 — Multi-channel coverage (3 min). SMS, web chat, and voice all from the same intent classifier and the same patient record. A dental-pure voice-only competitor cannot demo this in three minutes because they do not have the surfaces. The proof is the unified inbox view of a patient who started on chat and ended on voice, not a feature list.
- Beat B3 — Platform breadth (2 min). One example from outside dental — an aesthetic clinic or specialty practice — that shows the same platform handling a different vertical's intake. This is the proof that the platform is a real platform and not just a dental-skinned vertical product. Two minutes, one screen, one outcome metric.
The mechanics behind why these slots get assigned in the first place are in our slot decision framework; the fields that drive the assignment are in the discovery brief.
The Three Trap Doors
Three demo failure modes are common enough in dental AI walkthroughs that the script names them as trap doors. The point of naming them is not to prevent them — they will still happen — but to give the rep a recognition trigger so the demo can be recovered.
- Trap 1 — The integrations rabbit hole. The prospect names a niche scheduling tool, the rep opens the integrations admin panel, and the next four minutes are spent toggling and filter-searching. Recovery move: “Let me grab the answer for you after the call — I want to keep your time focused on what you came to see.”
- Trap 2 — The admin-screen detour. A prospect asks how a configuration is set, and the rep navigates to a backend admin screen to demonstrate. The buyer now sees UI complexity that no office manager will ever touch. Recovery move: do not open admin screens during the demo. Verbal answer plus “we set this up for you during onboarding.”
- Trap 3 — The AI-tech monologue. A curious buyer asks how the voice model works. The rep spends four minutes on transcription accuracy, intent classification confidence scoring, and ASR architecture. The slot-specific proof beats get cut to recover the clock. Recovery move: forty-five seconds on the topic, then “happy to send our technical brief after — let me show you the part of this that matters for your office today.”
The Twenty-Two-Minute Close and the Handoff
The Act 4 close is a three-line summary. Line one names the slot back to the buyer in operational language (“Based on what we covered, this is a Voicify-replacement conversation, so the next step is a parallel-run scope” or “You're evaluating us against a dental-only voice tool, so the next step is a sandboxed integration test”). Line two names the two strongest proof beats from this specific call — usually one A-slot beat or one B-slot beat plus one shared-beat moment that landed. Line three commits to a follow-up artifact with a date attached. The summary is also the seed text for the post-call note, which is the input that the win-loss debrief reads at deal close.
The slot tag from the discovery brief is verified at this moment. If the demo revealed a slot mismatch — A-slot brief, B-slot reality, or the reverse — the rep logs the slot flip with a one-line reason. The naming rules for the slot flip language match the rest of the system; see our naming rules note for the specifics. The verified slot tag follows the deal record forward into the proposal stage so the proposal template inherits the slot context rather than starting blank. That is the integration point that turns a slot-tagged demo into a slot-tagged cycle.