The customer reference call is the most leveraged thirty minutes in a Voicify "Competitor A or Competitor B" dental AI deal. It is also the artifact reps most often improvise. A horizontal voice-AI prospect hears a single-location practice and concludes the platform does not scale. A dental-pure competitor's prospect hears an enterprise DSO and concludes the platform is too heavy for their three-location group. Both calls are technically successful — the customer said nice things, the rep sent the follow-up email — and both deals slip in the procurement window for reasons the rep traces back to pricing when the real failure was the reference selection on day forty-two. The customer reference call playbook prevents that pattern by publishing slot-aware reference matching, a tight talk-track for the rep, an intel-capture template for the post-call write-up, and a rotation cadence that keeps the reference pool credible across the year.

TL;DR

Match the reference to the slot. Stay silent for thirty minutes. Capture two artifacts. The Voicify A-or-B customer reference call playbook publishes a slot-to-reference matrix — A-slot prospects (horizontal voice-AI competitor) hear from mid-market dental groups whose ops directors can name workflows a horizontal platform could not handle; B-slot prospects (dental-pure competitor) hear from single-location or small-group practices whose office managers can describe the side-by-side evaluation in concrete terms. The rep opens with the prospect's two discovery criteria framed as questions to the reference, stays silent for the middle thirty minutes, and captures two artifacts: the reference's value phrase and the prospect's new objection. References cap at four calls per quarter; rotation is governed by the quarterly refresh meeting and sourced from strong pilot scorecards. The call threads the mutual action plan as a dated milestone and feeds the field intel capture for battlecard refresh.

Why Reference Selection Decides the Call Before It Starts

The reference call is not where credibility gets built. It is where credibility gets confirmed or contradicted. The prospect has already read the website, watched the demo, talked to two reps, and surfaced two or three evaluation criteria during discovery. They join the reference call to hear a customer answer one question — "is what I have been told true at scale, in a practice that looks like mine, against the alternative I am also evaluating?" — and the answer to that question is mostly determined by which customer is on the line, not by what they say.

This is why reference selection is the rep's most leveraged decision in the procurement window and why the playbook publishes the slot-to-reference mapping in advance. The mapping reads from the slot decision artifact and the segment field on the discovery brief, and the rep does not improvise the match under deadline pressure with one hour notice from a procurement team that suddenly wants a reference call before end of week.

The Slot-to-Reference Matrix

Four slot-and-segment intersections cover the bulk of A-or-B reference traffic. Each intersection publishes the customer profile a reference must match, the named reference pool (three deep), and the value emphasis the rep should brief the reference on before the call.

Prospect slotProspect segmentReference profile requiredValue emphasis
A-slot (vs horizontal voice-AI)Single-location to 3 locationsSmall dental group whose office manager can name two workflows a generalist platform could not handle without custom buildDental-specific intent classification depth, time saved on insurance verification, no integration custom work
A-slot (vs horizontal voice-AI)Mid-market 4 to 25 locationsMid-market group whose ops director can describe the buy-versus-build math the horizontal platform forcedTotal cost of ownership including custom build avoided, multi-location rollout speed, dental-specific reporting
B-slot (vs dental-pure competitor)Single-location to 3 locationsPractice that evaluated both side-by-side or migrated from the B-competitor, office manager availableTwo or three concrete evaluation criteria where Voicify won, ideally referencing the B-competitor by capability not name
B-slot (vs dental-pure competitor)DSO 26+ locationsDSO operations VP whose deployment has hit the 12-month mark and produced reportable outcome dataMulti-location consistency, brand-voice configuration at the location level, security and IT diligence the B-competitor could not match

The matrix publishes the right reference for the right deal. It does not publish the right script — that comes from the talk-track in the next section. A rep who pulls a DSO reference for a single-location prospect because the DSO is more impressive is misreading the prospect's actual question, and the deal slips for reasons the rep blames on pricing.

The Three Things the Rep Does on the Call

Reference calls fail when the rep does more than three things. The playbook caps the rep's role at exactly three:

  1. Open with the prospect's two discovery criteria, framed as questions to the reference. Pull the two criteria from the discovery brief verbatim. "Sarah, you mentioned in our last call that after-hours coverage and the front-desk team's adoption curve were your two biggest evaluation criteria. Mark, can you walk Sarah through what after-hours coverage actually looked like in your first thirty days, and then describe what adoption felt like for your front-desk team?" Naming the criteria primes the reference to address them and keeps the call from drifting into a feature tour the prospect did not ask for.
  2. Stay silent for the middle thirty minutes. The reference is more credible than the rep on every dimension a prospect cares about — implementation reality, team adoption, ROI math, the answer to "would you buy it again." A rep who interjects to clarify, expand, or correct reminds the prospect they are watching a sales motion. The strongest reference calls have the rep speak less than 90 seconds in the middle half-hour.
  3. Close with two questions for the prospect, not the reference. "Sarah, what did you hear that confirmed what you were already thinking, and what did you hear that raised a new question?" The new-question answer is the field intel — it is the objection the discovery brief did not surface, and it goes into the post-call capture template.

The Post-Call Intel Capture

Two artifacts get logged within 4 business hours of every reference call. Both go to the field intel capture and feed the next quarterly refresh.

Reference Rotation and Pool Health

A customer reference burns out at roughly four calls per quarter. Past that, the office manager starts declining requests, the rep starts skipping the reference for the next ten deals because the request friction is too high, and the platform loses a credible voice it cannot easily rebuild. The rotation cadence solves this by enforcing three pool-health rules.

How the Reference Call Connects to the Cluster

The reference call is a node in the A-or-B cluster, not a standalone artifact. It sits between the pilot scorecard (which sources the pool) and the mutual action plan (which threads it as a dated milestone with a participant list and a follow-up step). The discovery brief supplies the two criteria the rep opens with. The field intel capture consumes the post-call artifacts. The battlecard governance SOP ingests the new objections at the quarterly refresh. The win-loss debrief tags any loss following a reference call as reference-selection failure, reference-execution failure, or deal-level failure, and the quarterly refresh reads the tagging to decide whether the pool needs widening or the rep needs coaching.

The reference call is the moment the prospect stops listening to the rep and starts listening to someone like themselves. The playbook's job is to make sure that someone is the right someone, briefed on the right criteria, on a call where the rep mostly listens. Everything else in the procurement window depends on what the prospect hears in that thirty minutes.