SaaS Cold Call Script Templates and the Two Federal Rules

TL;DR: A SaaS cold call script is six beats rather than a monologue. The beats are a permission opener, a specific reason you dialed this company, a problem hypothesis you are willing to be wrong about, one discovery question, a value bridge built from the answer, and a next step you say out loud. Two federal rules decide what those beats may claim, and they run on different axes, which is where most SaaS cold call script advice goes wrong. The FTC Telemarketing Sales Rule at 16 CFR 310 exempts business-to-business sales calls from the bulk of the rule, but the exemption explicitly keeps the misrepresentation provisions, so every price, contract limit, integration claim, cancellation term, and named partner in your script stays regulated. The FCC rule at 47 CFR 64.1200 does not ask whether your prospect is a business, because it keys off the line, and a call placed to a cellular number using an autodialer or an artificial or prerecorded voice needs prior express consent, in writing when the call is telemarketing. That is the trap for teams selling to founders who answer on a mobile. Write the script to the stricter half of each pair, dial it live, and change one beat at a time so the recordings tell you something.

Why most cold call scripts fail before the first word

Your script is probably not the reason the quarter is behind. Look one step earlier in the funnel.

Say a rep loads two hundred SaaS prospects, blocks two hours, and finishes with four conversations. The script ran four times. Whatever is clumsy about those four conversations is a rounding error next to the hundred and ninety six dials that never reached a human being. Rewriting the opener does nothing to that number. It is the wrong lever on the wrong variable.

So separate the four things that actually produce a booked meeting, because they fail independently and they are fixed by different people. The list decides who picks up and whether they have the problem at all. The connect rate decides how many times the script gets to run. The script decides what happens in the ninety seconds after hello. The follow-up decides what happens to the conversations that do not end in a calendar invite.

Most teams only ever touch the third one. That is not because it matters most. It is because it is the only one of the four that feels like writing, and writing feels like progress on a day when nobody is picking up.

Here is the failure mode a manager can actually see on a recording. The rep opens well. The buyer says something unexpected at second twenty, usually a version of “we already looked at this.” The rep keeps reading. Four more lines of a script written for a buyer who has never heard of the category get delivered to a buyer who evaluated three competitors last quarter. The call ends politely. The disposition says not interested. Nothing in the CRM explains what went wrong.

A script that cannot survive the buyer changing direction is not a script. It is a monologue with a greeting attached.

The SaaS cold call script template that adapts

Treat the script as six beats with a job each. The words move. The jobs do not. A rep who knows the job of the beat can improvise the sentence and still land the call where it needs to go, which is the whole point.

Cold call permission opener

You interrupted someone. Say so, and ask for a small, specific amount of time rather than a vague one.

“Hi [name], it’s [rep] at [company]. I know I’m interrupting. Can I have thirty seconds to tell you why I called, and then you can tell me to go away?”

Thirty seconds is a real number and the buyer can hold you to it. “A few minutes” is not, and asking for it signals you plan to talk for five. The permission ask also does something mechanical: it forces a yes or no, which gets the buyer talking inside the first ten seconds instead of listening to a pitch in silence.

Cold call reason for reaching out

Name the specific thing about this company that put them on your list today. Not the industry. The company.

“You posted two SDR roles last month and your careers page lists a fourth AE opening. I called because teams that add reps that fast usually hit a reporting problem before they hit a headcount problem.”

If you cannot name the trigger, you do not have a reason, you have a list. Say that honestly instead of inventing one. “I’m calling companies in your space, and I’ll be straight that I don’t know whether this applies to you” outperforms a fabricated personalization, because the buyer can tell the difference and you just spent your credibility on a detail they know is wrong.

SaaS problem statement

State the problem as a hypothesis you might lose, not a fact you have established.

“My guess is that when a rep leaves, their call history leaves with them, so whoever picks up the account starts from nothing. Is that close, or do you already have that solved?”

“Is that close” is the load-bearing phrase. It gives the buyer permission to correct you, and a correction is worth more than an agreement, because a correction tells you what they actually think the problem is.

Cold call discovery question

One question. Then stop talking.

“When a deal goes quiet for three weeks, how does anyone on your team find out?”

Ask about a state transition rather than an opinion. “How do you handle follow-up” gets you a process description that may or may not be real. “How does anyone find out” gets you the gap, because the honest answer is usually that nobody finds out until the forecast call.

SaaS value bridge

Connect their answer to your product in one sentence. Use their words, not your feature names.

“So it surfaces in the forecast call, three weeks late. The reason I called is that we put that in front of the manager the day it goes quiet instead of at the end of the month.”

If the buyer said nothing useful in the discovery beat, you do not get a value bridge. Go back to the hypothesis and try a different one, or close the call out cleanly. Bridging to a problem the buyer never confirmed is how a cold call turns into a pitch, and it is also where the accuracy rules below start to matter.

Cold call meeting ask

Name the next step, its length, and what happens in it. Then be quiet.

“Twenty minutes on Thursday. I’ll show you the manager view and you tell me whether it would have caught the last deal that went quiet. If it wouldn’t, we stop there.”

The escape hatch is not weakness. It lowers the cost of saying yes, and it commits you to a standard the buyer can hold you to, which is the only reason a cold prospect agrees to a second call.

Two federal rules that govern what your script can claim

Most script advice treats compliance as a separate article for the legal team. That is a mistake, because two federal rules land directly on sentences a rep says, and they do not work the way sales teams assume. They are not two versions of the same rule. They run on different axes, and knowing which axis you are on changes what your script may claim and how you are allowed to dial.

None of what follows is legal advice. It is a reading of the current rule text, and the exact citations are in the Sources section at the end so you can check it against your own counsel.

What the business to business exemption drops from your cold call script

The FTC’s Telemarketing Sales Rule at 16 CFR 310 contains an exemption for telephone calls between a telemarketer and a business made to induce the business to buy goods or services. In plain terms, a B2B SaaS cold call sits outside most of the rule. The national do-not-call registry provisions, the calling-hour restrictions, and the rest of the rule’s machinery are not the operative constraint on a straightforward business sales call.

Two carve-outs sit inside that exemption and both matter. The first is a narrow category rule: calls made to induce the retail sale of nondurable office or cleaning supplies do not get the exemption. If you sell software, that one is not about you. The second is not narrow at all.

What the exemption keeps in your cold call script

The exemption explicitly does not apply to the rule’s misrepresentation provisions. Read that again, because it is the single most useful line in the rule for anyone writing sales copy for the phone.

The provisions that survive prohibit misrepresenting, directly or by implication, the total cost to purchase, receive, or use what you are selling; any material restriction, limitation, or condition on purchasing or using it; any material aspect of its performance, efficacy, nature, or central characteristics; any material aspect of your refund, cancellation, exchange, or repurchase policy; and your affiliation with, endorsement by, or sponsorship by any person or government entity. A separate surviving provision prohibits making a false or misleading statement to induce any person to pay for goods or services.

So the part of the Telemarketing Sales Rule a SaaS rep cannot escape is the accuracy of the pitch itself. Not the dialing. The words.

That turns a vague coaching note into a checklist you can run against a script line by line. Every one of these is a sentence reps say on cold calls, and every one lands on a surviving provision:

• “It’s forty nine a seat” when the real figure excludes a platform fee, a minimum seat count, or the annual commitment that unlocks that rate. That is total cost.
• “You can cancel anytime” when the contract is annual. That is cancellation terms.
• “It syncs bidirectionally with your CRM” when the sync is one-way, or one-way for the object the buyer just asked about. That is central characteristics.
• “We’re a Salesforce partner” when you appear in a directory rather than holding the partnership being implied. That is affiliation and endorsement.
• “Teams see a thirty percent lift” with no study behind the number. That is performance and efficacy, and the implication rule means a confident delivery does not save it.

Note the phrase “directly or by implication.” A rep who never states a falsehood but lets a buyer walk away believing the annual contract is month to month is inside the thing the rule describes. That is a coaching standard as much as a legal one, and it is checkable on a recording.

What the cell phone rule means for a SaaS cold call

Now the second axis, and this is the one that catches SaaS teams.

The FCC’s rule at 47 CFR 64.1200 restricts initiating a call using an automatic telephone dialing system or an artificial or prerecorded voice to any number assigned to a cellular telephone service, a paging service, specialized mobile radio, other radio common carrier service, or any service where the called party is charged for the call. The exceptions are a call made for emergency purposes or one made with the prior express consent of the called party. Where the call includes or introduces an advertisement or constitutes telemarketing, the consent has to be prior express written consent.

Read what that rule keys off. The line. Not the subscriber.

There is no business-to-business exemption in it. The FTC exempted the B2B relationship; the FCC restricted by the type of number dialed, and those are different regulators writing different rules on different axes. The exemption you relied on in the paragraph above does nothing for you here, because it never touched this rule.

For most B2B categories that distinction is academic, because you are dialing a desk line at a company with a receptionist. For SaaS it is the daily reality. The founder of a twelve-person startup, the head of revenue at a remote-first company, the technical evaluator who has never had a desk phone: those contacts are mobile numbers, and a purchased list will not reliably tell you which ones.

Two practical consequences fall out of the rule text, and they are the ones to build into the operating process:

• A live, manually dialed conversation is a different thing from an automated one. The restriction attaches to calls placed using an automatic telephone dialing system or an artificial or prerecorded voice. A rep having a real conversation is not the conduct the paragraph describes.
• A prerecorded voicemail is an artificial or prerecorded voice. That is the plain reading, and it is where a productivity feature collides with the rule. Dropping a recorded message onto a cold prospect’s cell number as a prospecting step is squarely in the territory the rule is written about, and because the message is selling something, the written-consent standard is the one in play.

The operating instruction is to build to the stricter half of each pair. Treat every unverified number as though it may be a mobile, keep cold first touches live and manually dialed, and reserve prerecorded voicemail for contacts who gave you written consent, which in practice means existing customers and inbound hand-raisers rather than a cold list. If you want the do-not-call side of this in more depth, we wrote about scrubbing cold calling lists against do-not-call data separately.

Running the script at volume with a power dialer

Go back to the four variables. The script is beat three. The connect rate is beat two, and it decides how many times beat three gets to exist. This is the part a tool actually changes, and it is worth being precise about what it changes rather than calling it productivity.

Kixie’s PowerDialer uses multi-line dialing with AI Human Voice Detection, which distinguishes a live person from a recording and connects the rep to the live person. That is a narrow description on purpose, and it is the right one, because the thing it removes is specific: the rep stops listening to ring tones and voicemail greetings, and the time between one conversation ending and the next beginning collapses. The script does not get better. It gets more repetitions, which is the only way anyone finds out whether it is any good.

It also removes the pause that nobody puts on a dashboard. After a rejection, a rep has a reason that looks like work to go read the next account’s website for four minutes. Ten of those in a call block is forty minutes of avoidance that looks like research. When the system advances the list, that decision stops being the rep’s to make.

ConnectionBoost works on the same variable from the other direction, combining local presence dialing, progressive caller ID, and number reputation monitoring to help teams manage outbound number reputation and pickup rates. Kixie’s phone number reputation tools monitor outbound numbers and support remediation when inaccurate “Spam Risk” or “Scam Likely” labels appear. This is worth understanding as a script problem, not just a telecom one: a number carrying a spam label means the buyer never hears the opener at all, and no rewrite of beat one can reach a phone that does not ring.

Calls, texts, outcomes, and recordings log to the CRM automatically. That matters for the script work specifically, because automatic call recording with playback inside the CRM is what turns script changes from opinion into evidence. Without the recording you have a disposition field and a rep’s memory of a call from Tuesday. With it, a manager can hear where the buyer changed direction and whether the rep adjusted.

Kixie also ships Voicemail Drop, which pre-records a message and leaves it automatically, and this is where the previous section binds. The feature is genuinely useful for the contacts where you have consent, and it is the wrong tool for a cold mobile number. The capability existing does not make the call permissible. That is a process decision your team makes before the list is loaded, not a setting.

On the list side, Kixie supports checks against the National Do Not Call Registry and your internal suppression lists. Kixie’s own published position is worth repeating rather than paraphrasing: customers remain responsible for their calling practices and legal review. That is accurate, and any vendor telling you otherwise is making a claim about your liability that is not theirs to make.

One honest boundary. Kixie is a sales engagement platform for business calling and texting, built around multi-line power dialing with CRM logging. It is not a predictive dialer that over-dials a queue against agent availability, and a contact center running a hundred-seat predictive floor is a different category with a different shortlist.

SaaS cold call script examples by scenario

Same six beats. What changes is the problem hypothesis and the size of the ask, because the person on the other end has a different job.

Cold call script for decision makers

“I know I’m interrupting, give me thirty seconds. You’ve added four reps since July. My guess is your reporting still tells you what closed but not why the ones that didn’t died. If I’m wrong, say so and I’ll leave you alone.”

An executive buys a consequence, not a feature. Lead with the number they are accountable for and keep the ask small. Do not pitch the product to this person. Pitch the twenty minutes.

Cold call script for technical evaluators

“You’re the one who’d have to own the integration, so I’ll skip the pitch. We write call activity back to Salesforce at the activity and opportunity level. Where does your current setup break when a rep calls from a mobile?”

This person has been sold to badly and can detect a vague integration claim in one question. Be specific and be accurate. If the sync is one-way for a given object, say which, both because it builds credibility with the only person who will check and because the central-characteristics rule above is the one you are standing on.

Cold call script after a trigger event

“I saw the funding announcement, congratulations. Calling because the quarter after a raise is usually when the pipeline reporting that worked at eight reps stops working at twenty. Is that on your list yet, or is it still hiring?”

The trigger buys attention. It does not buy a meeting. Spend it fast and move to the hypothesis, and give the buyer a way to say “still hiring,” which tells you to call back in six weeks instead of marking them closed.

Cold call script for small business prospects

“You’ll probably be the one using this, so I won’t route you to a demo team. Most owners doing their own outbound tell me the admin after the call is what kills the call block. Is that true for you, or are you not making many calls right now?”

At this size the buyer, the user, and the budget are one person, so the authority questions are wasted and the price question arrives early. Answer it straight when it does. This is also the call most likely to be a mobile number, which is the operating reason it stays live and manually dialed.

Cold call script for enterprise prospects

“I’m not expecting this to be a quick decision. I’m trying to work out whether it’s worth either of our time. If you were to replace the dialer your team uses, who else would have to be in the room, and what would they need to see?”

Enterprise first calls are mapping exercises. The goal is to find out who else must agree and what the security and procurement path looks like, not to establish value in one pass. A rep who books a demo here without identifying the other stakeholders has created a meeting, not a deal.

Cold call script for a no response follow up

“It’s [rep] again. I’ve tried you twice and I don’t want to be the person who calls forever. If the reporting thing isn’t a priority, tell me and I’ll close it out. If it’s just timing, give me a month and I’ll come back then.”

Make the close-out explicit and mean it. A clean no is worth more than a sixth attempt into silence, and asking for it tends to produce the honest answer you have been guessing at for three weeks.

SaaS cold call objection responses

Treat an objection as information about which of four things is actually blocking the deal: the problem, the money, the authority, or the timing. The responses below all do the same work, which is to find out which one you are holding before you answer it.

Cold call response to not interested

“Fair enough. Before I go, is it that the problem isn’t real for you, or that you’ve already got it handled?”

“Not interested” at second fifteen is a reflex, not a verdict. One clarifying question is reasonable. A second one is not, and pushing past a real no is the fastest way to make sure the next rep from your company never gets a hearing.

Cold call response to send me an email

“I will. So I send something useful rather than a brochure, what’s the one thing it would need to answer for you to reply to it?”

This is usually a polite exit. Asking what the email should contain either converts it into a real piece of discovery or confirms it was an exit, and both outcomes are better than sending a generic deck into a dead thread.

Cold call response to we already use another tool

“Good, that means the problem is real. What does it not do that you’ve had to work around?”

Never criticize the incumbent. The buyer chose it, and attacking it makes them defend the decision instead of describing the gap. The workaround question is the one that finds the gap, because every tool has one and people enjoy complaining about it.

Cold call response to no budget

“Understood. Is there no budget for this kind of thing at all this year, or is it allocated and you’d have to move something?”

Those are different situations with different next steps and reps collapse them constantly. No budget at all means a calendar follow-up. Allocated elsewhere means there is a competing priority worth hearing about. Do not respond to either by discounting on a first call.

Cold call response to not a priority

“That’s honest, thank you. What is on the list ahead of it? I’d rather know whether to call you in a quarter or not at all.”

This is the objection most likely to be true. The useful move is to find out what the priority is, because it either reveals a problem you solve from a different angle or tells you the realistic timeline.

Cold call response to bad timing

“No problem. Is there a date when it stops being bad timing, or is that a nice way of saying no? Either answer is fine.”

Naming the possibility that it is a soft no makes it easier for the buyer to give you the real answer. A vague “call me in a few months” that nobody wrote down is how a pipeline fills with records nobody will ever work.

How to test a script instead of guessing

Script changes get argued about in team meetings because nobody has the evidence to settle them. Fix that first and most of the argument goes away.

Change one beat at a time. If you rewrite the opener and the discovery question in the same week, you will have no idea which one moved the number, and you will keep both out of superstition.

Measure the beat, not the quarter. Each beat has its own observable outcome: the opener is working if the buyer is still on the line at second thirty, the hypothesis is working if the buyer corrects you instead of agreeing flatly, the discovery question is working if the rep is silent for the next fifteen seconds, and the ask is working if the objection you get is about timing rather than relevance. Revenue will not tell you any of that. The recording will.

Give it enough calls to mean something. A script change evaluated over twenty dials and four conversations is a coin flip with a narrative attached. Wait for the sample, which is another argument for the connect rate work, since a team having three times the conversations reaches a real answer three times sooner.

Then codify what the top performer is already doing. On most teams the best rep has quietly stopped following the official script, and nobody wrote down what they do instead. Pull five of their recordings, write down the beats, and make that the script. That is a faster path to a better script than any rewrite, and it has the advantage of being known to work on your buyers rather than someone else’s.

Cold call script FAQs

How long should a SaaS cold call be?

Long enough to find out whether a real problem exists, which is usually two to four minutes when it is going well and under forty seconds when it is not. Length is an output, not a target. A rep optimizing for call duration will keep bad calls alive, which costs more than the call that ends early.

Should you ask for permission at the start of a cold call?

Usually yes, with a specific number attached. “Can I have thirty seconds” gives the buyer a decision they can hold you to and gets them speaking inside the first ten seconds. The version that fails is the open-ended one, because “do you have a few minutes” invites a no and promises a longer call than you intend to make.

What is the goal of a first SaaS cold call?

To find out whether a relevant problem exists and agree on a next action. That next action can be a discovery meeting, a referral to the person who actually owns the problem, a specific piece of information you send, or an explicit close-out. A clean disqualification is a successful call, because it returns the rep’s time to the list.

Can you leave a prerecorded voicemail for a cold SaaS prospect?

Treat it as off limits for cold outreach. A prerecorded message is an artificial or prerecorded voice, and the FCC rule at 47 CFR 64.1200 restricts those calls to cellular and similar numbers absent prior express consent, in writing where the call is telemarketing. Since you often cannot tell whether a list number is a mobile, the workable rule is to use prerecorded voicemail only where you hold written consent and to keep cold first touches live. Your counsel should confirm this against how your team dials.

Sources

• 16 CFR 310.6, Exemptions, Federal Trade Commission Telemarketing Sales Rule, via eCFR. Paragraph (b)(7) exempts telephone calls between a telemarketer and any business to induce the purchase of goods or services by the business, provided that the exemption does not apply to the requirements of sections 310.3(a)(2) and (a)(4), or to calls to induce the retail sale of nondurable office or cleaning supplies. Basis for the statement that a business-to-business SaaS sales call sits outside most of the rule while the misrepresentation provisions continue to apply. Reviewed November 8, 2026.
• 16 CFR 310.3, Deceptive telemarketing acts or practices, Federal Trade Commission Telemarketing Sales Rule, via eCFR. Paragraph (a)(2) prohibits misrepresenting, directly or by implication, total costs and quantity, any material restriction, limitation or condition, any material aspect of performance, efficacy, nature or central characteristics, any material aspect of refund, cancellation, exchange or repurchase policies, and affiliation with or endorsement or sponsorship by any person or government entity. Paragraph (a)(4) prohibits making a false or misleading statement to induce any person to pay for goods or services. Basis for the script accuracy checklist. Reviewed November 8, 2026.
• 47 CFR 64.1200, Delivery restrictions, Federal Communications Commission, via eCFR. Paragraph (a)(1) prohibits initiating a call, other than a call for emergency purposes or made with the prior express consent of the called party, using an automatic telephone dialing system or an artificial or prerecorded voice, to numbers including those assigned to a paging service, cellular telephone service, specialized mobile radio service, other radio common carrier service, or any service for which the called party is charged for the call. Paragraph (a)(2) requires prior express written consent where such a call includes or introduces an advertisement or constitutes telemarketing. Basis for the statement that the rule keys off the line rather than the subscriber’s status as a business. Reviewed November 8, 2026.
• Kixie PowerDialer feature page. Basis for the description of multi-line outbound dialing, AI Human Voice Detection distinguishing a live person from a recording, and automatic logging of calls, texts, outcomes and recordings to the CRM. Reviewed November 8, 2026.
• Kixie ConnectionBoost feature page. Basis for the description of local presence dialing, progressive caller ID, outbound number reputation monitoring, and remediation support when inaccurate “Spam Risk” or “Scam Likely” labels appear, and for Kixie’s statement that customers remain responsible for their calling practices and legal review. Reviewed November 8, 2026.
• Kixie Voicemail Drop feature page. Basis for the description of pre-recording a message and leaving it automatically in a prospect’s voicemail. Reviewed November 8, 2026.

Sources verified by the Kixie Research Team on November 8, 2026.