Voicify "Competitor A or Competitor B" in Dental AI: The Battlecard Trigger Map

A Voicify dental AI battlecard library that has grown into 18+ slot-aware artifacts — from the discovery brief at first qualified meeting, through the demo script when sales engineering is engaged, through the pilot scorecard at parallel-pilot kickoff, into the win-loss debrief at close, and through the CSM B-slot defense plan post-sale — is genuinely useful only if the rep can pick the right artifact for the right deal moment without reading nine pages first. That decision tree is the battlecard trigger map. The map takes three inputs — deal stage, slot tag, the most recent field signal — and outputs one artifact and one activation cue. This post is the field-facing version of that map, plus the swap protocol when a slot flips mid-deal and the quarterly refresh mechanism that keeps the map honest.

Why a Trigger Map Sits Above the Battlecard Library

A library of 18+ Voicify "Competitor A or Competitor B" artifacts has two failure modes if shipped without an index. The first is rep paralysis — the new AE opens the enablement folder, sees four artifacts that look applicable to a discovery call, picks one, and the choice is no better than random. The second is rep regression — the senior AE who learned the system in Q1 keeps grabbing whichever artifact muscle-memory tells them to grab, and the slot-aware variants the team built in Q2 collect dust. Both failure modes have the same root cause: no enforcement layer between the library and the deal. The trigger map is that layer. It is a decision tree, not a deeper artifact. It does not replace any of the existing battlecards. It tells the rep which one to deploy and what cue should make them deploy it.

The map also produces a measurement surface. If the map says the objection handling card should fire when an A-slot buyer raises horizontal-platform pricing in week two of evaluation, RevOps can measure how often the card was actually deployed on deals matching that signal and how those deals advanced compared to deals where the cue was missed. Without the map, the library is unfalsifiable — reps say they used the artifacts, managers cannot tell, and the quarterly refresh has no signal to read. The map is the connective tissue that turns a content library into an enforceable sales system.

The Three Inputs: Stage, Slot, Signal

The map takes exactly three inputs. More than three produces a decision tree no rep will read in a hallway between meetings. Fewer than three under-specifies the deal moment and the map fires the wrong card.

Stage is the standard pipeline stage: prospecting, discovery, demo, pilot, close, post-sale. The map treats demo and pilot as separate because the artifacts that fire are genuinely different — demo is rep + SE, pilot is rep + buyer running their own evaluation, and the slot weighting works differently in each.

Slot is the A-or-B tag the discovery brief assigned. A-slot means the buyer is comparing Voicify against a horizontal voice-AI platform — broad industry coverage with dental as one vertical of many. B-slot means the buyer is comparing Voicify against a dental-pure AI receptionist — narrow feature surface, lighter PMS integration depth, faster setup wizard. Unknown-slot at first qualified meeting is a valid state and the map handles it explicitly.

Signal is the most recent field event that should change the artifact selection — a competitor demo scheduled, a new executive in the room, a slot flip detected mid-evaluation, a pricing question that escalates beyond the AE's ceiling, a clinical-safety concern raised by a hygienist. The signal is what flips the map from "default artifact for this stage and slot" into "the artifact for this stage, this slot, and this moment specifically."

The Trigger Matrix: Stage × Slot → Artifact

The default matrix below assumes no late-breaking signal — it is the artifact the rep deploys for the standard progression of a deal in each stage and slot. The signal column comes next.

Three columns, six rows, sixteen unique artifact pointers. The unknown-slot column never persists past discovery — if the rep advances to demo without a slot tag, the map says stop and return to discovery. Demoing into an unknown slot is the single most common deal-killer in the system; the slot decides whether the SE leads with PMS write-back depth (A-slot) or with after-hours coverage uptime (B-slot), and the wrong opening loses the SE the room before the live demo even starts.

The Signal Column: Mid-Deal Triggers That Override the Default

The default matrix is a starting point. The signal column is where the map earns its keep. Five signals override the default artifact for the current stage and slot, and the rep is expected to swap within 24 hours of detection.

Each signal is observable in CRM or in a call note. RevOps wires the slot-flip signal to the CRM field directly; the other four are flagged by the rep in weekly forecast review, and the manager confirms the override fired. The map is not aspirational — it is enforced at the forecast call.

Slot-Flip Triggers and the Hot-Handoff Protocol

The slot-flip override is the most-fired signal in the map by volume. The brief assigns the slot at first qualified meeting, but buyers do not always cooperate. The clean case is a buyer who consistently introduces horizontal-platform comparisons (A-slot signal) even though the rep tagged them B-slot in the brief because their stated incumbent was a dental-pure receptionist. The clean response is to swap to the A-slot variant of whichever artifact is in flight, log the flip with reason code, and update the slot tag in CRM so downstream artifacts fire correctly. The slot-flip log is one of three inputs into the quarterly refresh — the others are the win-loss debrief themes and the CSM field intel capture — and consistent flip patterns in a vertical or geography are what tell enablement the discovery brief's slot signals need re-tuning.

The hot-handoff protocol applies when the flip happens between role transitions — SDR-to-AE, AE-to-SE, AE-to-CSM. The protocol is simple: the inbound role inherits the slot tag, the slot-flip log, and the signal note from the outbound role, and confirms the slot at the first meeting with the buyer before deploying the next artifact. If the inbound role disagrees with the inherited slot, they re-tag and re-log; they do not silently swap. Silent slot swaps are the single largest source of artifact misfires across the system.

How the Trigger Map Updates: The Quarterly Refresh Loop

The map is a living document. It updates on the same cadence as the underlying library, driven by the quarterly refresh meeting. Three update types are in scope. First, a new artifact joins the library — for example, an executive briefing one-pager or a pricing escalation path — and the map gets a new row or column with the activation cue spelled out. Second, an existing activation cue produces consistent misfires — the artifact fires on the matching signal but does not change deal outcome. The map either retunes the cue (more specific signal definition) or retires the activation. Third, a new slot signal emerges in the field that the three-input model does not capture — most commonly a third competitor archetype that does not fit cleanly into A or B. The refresh meeting decides whether to extend the slot taxonomy (rare, painful) or treat the new archetype as a signal-driven override within the existing A or B framing.

The refresh meeting reviews the activation log — RevOps' record of which artifacts fired on which deal signals — against the win-loss outcomes for those deals. Activations that correlate with stage advancement stay. Activations that fire often but do not move deals get retuned. The map's authority depends on this loop: a map that is never measured against deal outcomes becomes wishful sales theater within two quarters.

Failure Modes: When the Map Fires the Wrong Card

Three failure modes recur. The first is over-reliance on stage and under-reliance on signal — the rep deploys the default artifact for the stage without checking whether a signal has fired since the last touch. This shows up as a flat-feeling deal that should have escalated and a rep who reports "I sent the brief, I sent the demo script, I do not know why we lost." The cure is forecast-call enforcement: the manager asks "what signal fired since last week, and which override did you deploy?" If the answer is no signal and the default artifact, the manager either accepts that or pushes the rep to re-read the recent call notes for signals they missed.

The second failure mode is reverse — the rep over-deploys overrides on noise. Every buyer question is treated as a signal, every executive name-drop fires a one-pager, and the deal collapses into artifact fatigue on the buyer side. The cure is the activation log: if the rep fired the executive override on three deals and only one of those deals actually had a new executive in the committee, the manager retunes the rep's signal threshold in the next 1:1.

The third failure mode is silent slot drift — the rep tags A-slot at discovery, the buyer behaves like a B-slot deal for the next three weeks, and the rep never updates the tag. The artifacts that fire are A-weighted; the buyer is evaluating B-weighted criteria; the deal loses on weighting alignment, not on capability. The cure is the slot-flip log itself — the rep is expected to log the flip the moment they see it, and the manager is expected to confirm at the next forecast call. Drift without logging is a coaching issue, not a system issue.

What the Trigger Map Is Not

The map is not a battlecard. It does not contain a single proof point, talk track, or trap-setter. It contains pointers to other artifacts and the conditions under which those artifacts should fire. A rep who tries to deploy the map directly to a buyer has misunderstood what the map is for — the map is the internal sales-enablement operating layer that decides which buyer-facing or rep-facing artifact gets used. It is also not a replacement for rep judgment. The map handles the standard cases — stage × slot × five named signals — and explicitly defers to rep judgment outside that boundary. The boundary is what reps consult the map for; outside the boundary, the rep escalates to a manager or runs the play they think the deal needs and logs the decision. Maps that pretend to cover every case turn into rule-following ceremonies and reps stop reading them. The map exists to cover the cases that come up every week, not the cases that come up once a quarter.