MSP cold call script for SMB IT discovery calls

What the discovery call is for

An MSP grows one business at a time. The first call is not trying to sell a managed services agreement. It is trying to find a small business with an unmanaged stack, a person who is tired of being the default IT department, and a specific fear about downtime or data. Those three together are a live opportunity, and the assessment is how you get in the door.

That means the call is mostly questions about their setup, not statements about your services. A dentist office manager will give you three minutes to talk about their server. They will give you ten seconds to talk about your monitoring stack.

Before you dial: list and territory

Load the SMB list as a CSV with company, industry, contact where you have one, phone and any stack notes from prior contact. Chamber lists, association rosters and referral partners all work. Group by industry so a rep works one vertical per block, because the pain language of a dental office differs from a machine shop and the script should flex with it.

Screen the internal do-not-call list before the block. Most calls to businesses sit outside the FTC Telemarketing Sales Rule under the business-to-business exemption in 16 CFR 310.6(b)(7), but the exemption is narrow, and many small business owners answer on personal cell phones, where the FCC restrictions on autodialed and prerecorded calls to wireless numbers under 47 CFR 64.1200(a)(1) still apply.

The opening: the who-handles-it question

“Quick question for whoever handles your computer issues. Is that you, or is there an office manager I should ask for?”

This opening works because it is a routing question, not a pitch. Whoever answers can respond to it, and the answer tells you whether you are talking to the decision maker, the delegated victim of their own IT, or a gatekeeper with a name for you. Get the name and log it even when the call goes nowhere.

The talk track, in order

The script runs routing, current support, downtime consequence, assessment close. Three habits make it work.

First, ask about consequences, not equipment. “If the server went down tomorrow morning, what happens to the schedule” produces the fear that funds the fix. Technical questions get technical answers; consequence questions get budget conversations.

Second, quantify what you hear. Twice this month, six staff, paper schedules. Numbers repeated back to the owner sound like the problem being taken seriously, because they are.

Third, close on the assessment, never the contract. A flat-fee, engineer-led assessment with a written findings list is a small decision. A managed services agreement is a big one, and nobody makes a big decision on a first cold call.

Objections you will hear

“We have a guy.” Ask what happens when the guy is on vacation when something breaks. You are not replacing him on this call; you are applying to be the backup.

“We already have an IT company.” Log it and stop. A business under contract is not a prospect until renewal season, and the disposition tells you when to check back.

“Everything is fine.” Ask when the backups were last restored. Most businesses do not know, and the honest answer opens the assessment conversation.

“Just send me an email.” Agree, send it in five minutes while the conversation is fresh, and disposition for a two-day callback. Email alone converts nothing; email plus a dated callback converts some.

“We cannot afford monthly fees.” Say the assessment is a flat fee with no contract attached. Price objections to services nobody has scoped yet are usually risk objections in disguise.

Dispositions in MSP terms

• Assessment booked with the day and window.
• No IT person with the contact name for a later pass.
• Has an MSP with a long callback.
• In-house IT with the admin’s name.
• Callback requested with the date.
• Left voicemail with the recorded drop.
• Do not call on any stop request, logged the same day.

What the AI summary captures

DialBreeze records and transcribes connected calls, then writes structured fields. For MSP discovery the useful ones are the stack in their words, user count, backup status, who handles IT today, who signs, the pain with a date, and the agreed next step. Check server ages and any incident details against the recording before the engineer’s report references them, because an assessment built on a misheard detail starts the relationship with an error.

Compliance lines that matter

The business-to-business exemption under 16 CFR 310.6(b)(7) covers most calls to businesses, but it is not unlimited, and it is not a wireless-number exemption. Keep solicitation calls inside 8 a.m. to 9 p.m. local time at the called party’s location under 16 CFR 310.4(c). Honor every stop request. Several states require all parties to consent before a call is recorded, so use a short disclosure. One MSP-specific care point: discovery calls surface patient, client and financial data, and anything you say on a recorded call about handling that data should match your contracts. DialBreeze applies your internal DNC list, quiet hours and attempt caps. It does not decide whether a number may be called. This page is not legal advice.

Practice it before the real list

Run five sandbox calls where you never mention your service tiers and never quote monthly pricing. Then run five where the prospect insists everything is fine. The second set teaches the backup-question move, which is the single line that turns a polite call into an assessment.