A B2B cold calling script your team can actually use

Before writing the opener, define the target company, the relevant contact, one problem your service addresses, and the purpose of the meeting. Add disqualifiers and a list of claims callers are allowed to make.

For the IT example: the target might be a multi-location business; the contact is responsible for operations; the issue is coordinating support across locations; the next step is a brief discussion of the current support model. Do not assume the business has outages or unhappy staff simply because it fits the company profile.

Give the caller an approved response when they do not know an answer: “I do not want to guess. That is something our specialist can cover if a conversation makes sense.” An honest limit is better than an invented technical explanation.

“Hi Jordan, this is Alex with Example IT. This is a cold call. We help businesses coordinate IT support across multiple locations. Is that something you look after, or does it sit with someone else?”

This identifies the caller, acknowledges the interruption, gives a business reason, and checks responsibility. It does not imply a referral, pretend to be returning a call, or promise a result you have not established.

If they are the right person, continue with a question such as: “How are you handling support across the locations today?” If the role is wrong, ask whether there is a more appropriate contact without pressuring someone to disclose information they do not want to share.

Keep the opener short enough that the prospect can answer. Do not stack a company history, several features, and three questions into the first turn.

The caller’s job is not to conduct a full discovery call. It is to learn enough to establish relevance. Use a small number of questions and follow the answer rather than treating the script as a checklist.

• “Is your current arrangement working well, or is anything difficult to coordinate?”
• “When you review providers, what usually prompts that conversation?”
• “If a review became relevant, who else would need to be involved?”

Do not force a meeting when the prospect describes no relevant need. Record their actual answer, including timing. “No current problem; reviews providers in September” is more useful than marking every polite person as interested.

A branch should help the caller understand the situation, not trap the prospect into agreeing. Review patterns in objections by segment; a consistently irrelevant message needs changing, not louder delivery.

“You mentioned that coordinating requests across locations is taking time. Would a short conversation with our specialist about your current setup be useful? We can cover how you handle requests now and whether another approach is worth considering.”

If they agree, confirm the purpose, length, attendees, time zone, and destination for the invitation. Use your actual meeting length rather than promising a “quick five minutes” for a 30-minute appointment.

Log what the prospect said, not what the caller hoped they meant. The qualified meeting checklist shows what the receiving salesperson should get.

Review clarity, relevance, listening, honesty, and the quality of the next step. If you review recordings, follow applicable recording and consent rules. Use the same evaluation criteria across callers and avoid making a major change from one unusual conversation.

Test a specific hypothesis: for example, whether the opener names the buyer’s responsibility clearly enough. Keep the target segment and qualification definition stable while comparing the change. This is operational testing, not proof that a particular sentence caused an outcome.

The FTC’s B2B telemarketing protections address misrepresentations. Train callers on your claims and suppression process as well as their delivery. For staffing decisions, use the hiring scorecard; for volume decisions, use a conservative results model.