SaaS cold call script for reviving stalled evaluations

The opener that names the blocker

AE calls fail when they open like a status check: “just circling back on the demo.” The champion who went quiet has a specific reason, and the opener that reconnects names your best guess at it: “the security review stalled, my last two emails went quiet, so I figured I got boring.” Three things happen in that sentence. You prove you know the account’s actual state. You disarm the guilt a quiet champion feels. And the self-deprecating line buys the ninety seconds you ask for next.

Ninety seconds is the right ask, not two minutes. It is short enough to say yes to, and long enough to surface the blocker, if you spend it on questions instead of a recap.

The questions that surface what actually happened

My read is X, is that right, or did something else change. What else is between us and the next milestone. Who besides the obvious stakeholder could slow this down. The first question offers a hypothesis, which is easier to correct than a blank page, and corrections are information. The second surfaces the second blocker you did not know about, in this case the incumbent’s auto-renewal date. The third is the procurement question that turns a linear deal into a parallel one.

Every answer is a CRM field. In DialBreeze the AI summary writes them from the recording: blocker, stakeholders, timeline facts with dates, competitor constraints, next step. The AE dials the next opportunity while the write-up happens, and the pipeline review reflects reality instead of optimism.

The objections and the lines that hold

“We have been slammed, it is not a no”

Believe it, and make the path easier: “then let me take work off your plate instead of adding to it.” The filled questionnaire, the pre-redlined MSA, the summary the champion can forward internally. The AE who removes effort from a stalled deal revives more than the AE who resells it.

“The price came up internally”

Get it precise before defending it: who raised it, in what context, against what alternative. Price objections in SaaS are usually value-frame problems or procurement process steps, and the recording of this call is where you learn which. Then answer with the stakeholder who raised it in mind, not with a discount reflex.

“Legal wants changes to the MSA”

This is a process step, not an objection. The move is parallelism: send the redlines this week so legal’s clock runs alongside security’s, and log the dates. Deals lost to timelines are usually lost to sequencing, and sequencing is the AE’s job.

“We went with someone else”

Thank them, ask what decided it, log the answer, and set a long-dated re-entry around the competitor’s renewal window or first contract anniversary. The reason is the highest-signal competitive intelligence you will collect all quarter, and it costs one graceful call.

The close, and the parallel-work habit

The close recaps commitments with dates and names: questionnaire today, infosec tomorrow, Thursday at 9, procurement starts now. Then the recap question, “did I get all of it,” which catches the thing you missed while the champion is still on the line. The pattern underneath is parallelism: security, procurement and the CFO presentation move at once because the AE noticed every track and unblocked each. The disposition is “next meeting booked” or “security review” with the blocker field filled, and the summary carries it into the forecast call.

The trial variant

For a trial that stalled, the opener leads with the usage fact: “your team imported the data but never scheduled the weekly digest; want me to show it in five minutes.” Specific, verifiable, and about their actual experience. The call captures what was missing in the user’s own words, which is product feedback with a name attached, and the close books the walkthrough or the honest end of the trial.

Logging before the next dial

Disposition: next meeting booked, security review, procurement, champion gone, lost to competitor, unresponsive with a dated retry. Then verify the summary’s dates and stakeholder titles against the recording; the incumbent cancel date is the single most misheareable fact on the call, and the whole sequencing plan rides on it.

Compliance lines that frame this script

Most AE calling is business-to-business, and much of it falls outside the FTC Telemarketing Sales Rule under the B2B exemption in 16 CFR 310.6. The edges are sharp anyway: prospect lists contain personal cell phones, and the TCPA’s restrictions on autodialed and prerecorded calls to wireless numbers apply regardless (47 CFR 64.1200), so these are human-dialed calls with an AE talking. Stop requests are honored and logged on the spot regardless of context. Several states require all-party consent to record, and AE calls cross state lines, so the disclosure is a script item, not a policy memo. Nothing here is legal advice; your sales ops owns the list policy.

Coaching the script from recordings

Pull one revival call per AE per week and listen for the hypothesis opener, the ninety seconds, and the parallel-work close. The AI score triages which calls to open; the summary’s blocker field tells you whether the call surfaced the real stall or accepted the polite version. Coach one fix per week, and replay the wins in onboarding: a new AE who hears five real revival calls runs their first stalled-deal block like their tenth.