MSP cold calling scripts and objection handling

MSP cold calling scripts that sound human: openers, discovery questions, a four-step objection framework and responses to the objections MSP sellers hear most.

Guide

What makes a good MSP cold call?

A good MSP cold call earns thirty seconds with a specific reason for calling, spends most of its time asking about the prospect’s business rather than pitching, handles objections by getting curious instead of arguing, and asks for one small next step — usually a short discovery conversation or a no-obligation assessment.

Every script on this page is written to be adapted, not read. Prospects can hear a script being read in the first sentence, and the moment they do, they stop listening. Use these as structure: learn the shape of each one, then say it in your own words.

One rule runs through all of it. You are not trying to sell managed services on a cold call. You are trying to find out whether there is a problem worth a second conversation, and to earn that conversation.

Openers

How should you open an MSP cold call?

Say who you are, give a specific reason for calling that is about them rather than you, and ask a permission question. A relevant reason — a new office, a hiring push, an industry change, a mutual connection — earns more attention than a generic introduction ever will.

The trigger opener.

“Hi Sarah, it’s James from Northgate IT. I saw you’re hiring for three roles in the Leeds office — I work with a few firms your size who’ve found that growth is when the IT gets messy. I’m not calling to sell you anything today. Have you got two minutes for me to ask how you’re handling it, and you can tell me if it’s not relevant?”

It works because it is specific, it names a real situation, and it gives the prospect an easy way out, which paradoxically makes them more likely to stay.

The honest cold opener.

“Hi Tom, this is Priya at Brightline. This is a cold call — do you want to hang up now, or give me thirty seconds and then decide?” Most people, surprised by the honesty, say go on. Then: “We look after IT for accountancy practices around Bristol. The conversation I usually end up having is about what happens when something breaks during a deadline week. Is that something you’ve had to think about?”

Use this only if it suits your voice. Said nervously, it sounds like a trick; said plainly, it disarms.

The referral opener.

“Hi Mark, Dan from Keystone. Helen at Carter & Price suggested I call — we sorted out their backups last year and she thought you might be dealing with something similar. Is now a bad time?” If you have a genuine connection, lead with it. Never invent one.

Discovery

What questions should you ask on an MSP cold call?

Ask about how IT is handled today, what happened the last time something went wrong, what is changing in the business, and who makes technology decisions. Short, open questions that let the prospect talk will tell you more in two minutes than any pitch, and they decide whether a second conversation is worth having.

Questions that open people up.

Pick three or four, not all of them. Listen more than you speak, and follow the answer rather than the list.

  • “Who looks after IT for you at the moment?”
  • “When something goes wrong, what happens — who do people call?”
  • “What was the last IT problem that actually cost you time?”
  • “If your server or email went down tomorrow, how long before you’d be back?”
  • “What’s changing in the business this year — people, offices, systems?”
  • “Has cyber insurance or a client asked you questions about security lately?”
  • “Who else would be involved if you decided to change how IT is handled?”

Listen for the real problem.

Prospects rarely say “we need managed services”. They say “the internet drops sometimes”, “our guy is hard to get hold of”, or “we had a scare with an email last month”. Those are the openings. Write down their exact words — you will use them again in the follow-up and, if you get that far, in the proposal.

Framework

How should you handle objections on an MSP cold call?

Treat every objection as information, not resistance. Acknowledge it so the prospect feels heard, ask one question to find out what is really behind it, respond to that real concern briefly, and then ask for a small next step. Arguing with an objection almost always ends the call.

Four steps: acknowledge, ask, answer, advance.

This is the shape behind every response in the next section. Learn the shape and you can handle objections you have never heard before.

  • Acknowledge. Agree with what is reasonable in it: “That makes sense.” Never “but”.
  • Ask. One question that uncovers the reason behind the objection.
  • Answer. Respond to the real reason in a sentence or two. No speeches.
  • Advance. Ask for something small: fifteen minutes, an assessment, permission to send one specific thing.

Common objections

What are the most common MSP objections, and how do you respond?

The objections MSP sellers hear most are “we already have an IT guy”, “it’s too expensive”, “we’re happy with our provider”, “just send me an email” and “we don’t need it, nothing breaks”. Each usually means something more specific, and the response should address that.

ObjectionWhat it often meansResponse direction
“We already have an IT guy.”Loyalty, or fear of offending someone they likeRespect the relationship; ask what happens when he is unavailable
“It’s too expensive.”They are comparing against what they pay now for break-fix, or have no price yetAsk what they spend today, including downtime; compare like with like
“We’re happy with our provider.”Things are fine, or switching feels like too much workAgree; offer a second opinion rather than a replacement
“Just send me some information.”A polite way to end the callAgree, then ask one question so what you send is relevant
“We don’t need it — nothing breaks.”They have been lucky, or problems are absorbed quietly by staffAsk about backups and recovery rather than breakages
“Now isn’t a good time.”Literally busy, or a brush-offOffer a specific later time, and keep it
A quick reference. The sample responses below show each one in full.

Responses

What do good objection responses sound like?

They sound like a conversation, not a rebuttal. Each response below follows acknowledge, ask, answer, advance, and each is written to be adapted to your own words rather than memorised. The goal is never to win the argument; it is to earn the next conversation.

“We already have an IT guy.”

“That’s good to hear — plenty of the firms we work with started out with one person they trusted. Can I ask what happens when he’s on holiday, or ill, or dealing with another client when you need him?”

If there is a pause, there is an opening: “We often work alongside someone like that rather than replacing them — they keep the relationship, and we cover monitoring, backups and the out-of-hours side. Would it be worth fifteen minutes to see whether that would take some pressure off him?”

“It’s too expensive.”

“Fair — nobody wants another monthly bill. Out of interest, what are you spending on IT now, including the call-outs and the time your team loses when things go wrong?”

Most prospects do not know, and that is the point: “Most people we speak to haven’t added it up, because break-fix costs arrive in bits. Our assessment does that sum for you, and if it shows you’re better off as you are, we’ll tell you. Would that be useful?”

“We’re happy with our current provider.”

“That’s great, honestly — I’m not going to try to talk you out of a provider you’re happy with. When did they last walk you through a review of your security and backups?”

Then offer a second opinion, not a switch: “Some businesses like a fresh pair of eyes once in a while, the way you would with an accountant. If we ran a short assessment and it confirmed you’re in good shape, that’s a good outcome too. Want to keep that in your back pocket?”

“Just send me some information.”

“Happy to. So I send you something useful rather than a brochure, what’s the one IT thing you’d most like to be less worried about?” Whatever they say becomes the subject line of your follow-up email, and a reason to call back: “I’ll send that over today and give you a quick ring on Thursday to see if it raised any questions — does morning or afternoon suit better?”

“We don’t need it — nothing ever breaks.”

“That’s a good place to be. Can I ask a different question, then — if you lost your files tomorrow to ransomware or a failed drive, how confident are you that you could get them back, and how long would it take?” Recovery is a question most businesses have never tested. If they are not sure, offer to check: “A backup that hasn’t been tested is a guess. We can test yours as part of a short assessment.”

“Now isn’t a good time.”

“No problem — I’ve caught you in the middle of something. Would Tuesday at ten or Wednesday after lunch be better for five minutes?” Offer two specific times. If they pick one, put it in the calendar while you are on the phone and call exactly then. Keeping a small promise is the first evidence that you keep larger ones.

The ask

How do you ask for the meeting on a cold call?

Ask for something small, specific and useful to the prospect. A fifteen-minute discovery call or a no-obligation assessment works better than “a meeting to tell you about our services”, because it offers them something — a clearer picture of their own risk — whether or not they ever buy.

Offer the assessment as the next step.

“Based on what you’ve said about the backups and the new office, the most useful next step is probably a short assessment — we look at security, backups and the network and give you a scored summary. There’s no charge and no obligation. If it shows you’re in good shape, you’ve lost an hour. Shall we find a time?”

Assessment-led selling continues after the call. The break-fix conversion guide covers how to turn the assessment into the proposal.

Voicemail and follow-up.

Leave short voicemails with one reason and your number said twice: “Hi Sarah, James at Northgate IT, about the IT side of your new Leeds office. 0113 496 0000 — that’s 0113 496 0000. I’ll also send a short email.” Then send an email of three sentences that repeats the reason and asks one question. Plan a sequence of several touches over a couple of weeks, spaced out, and stop when they ask you to.

Know the rules where you call.

Calling rules differ by country and region: do-not-call registers, business-to-business exemptions, and what you must say about recording. If you record calls, find out whether the jurisdictions involved require one party’s consent or everyone’s, and say so at the start of the call where required.

Tools

How can software help with cold calling?

By putting the right words in front of the caller at the right moment and learning from every call afterwards. Scripts and rebuttals your team agreed on can appear on screen when an objection is raised, and recorded calls can be graded and coached so the next call is better than the last.

How MADDOX supports it.

Call scripts are authored in MADDOX, with required lines, hints, compliance statements and your own objection-and-rebuttal pairs. The AI Softphone — a separate application that places the calls — reads them, and its live coaching shows your rebuttal beside the live transcript when an objection is raised.

Afterwards, objections are tracked as records on the deal rather than buried in notes, and call grading feeds one-to-ones, so coaching is built on what was actually said. Recording consent is tracked per contact.

Questions

The things people actually ask.

Does cold calling still work for MSPs?

It can, when calls are researched, specific and aimed at a small next step rather than a pitch. Many MSPs combine calling with email and referrals rather than relying on any one channel.

Should I read a script word for word?

No. Learn the structure of each script and say it in your own words. Prospects recognise a read script within a sentence and disengage. Scripts are most useful for the opener, the key questions and objection responses.

What is the best response to “we already have an IT guy”?

Respect the relationship and ask what happens when that person is unavailable. Position your MSP as support alongside them, covering monitoring, backups and out-of-hours work, rather than as a replacement.

What should the goal of an MSP cold call be?

A small, specific next step: usually a fifteen-minute discovery conversation or a no-obligation assessment. Trying to sell managed services on the first call usually ends it.

Put your rebuttals on screen during the call.

Ask for an invitation and we will show you scripts authored in MADDOX, objections tracked on the deal, and calls graded afterwards.