Context-led B2B cold calling: how to prepare a relevant call

A B2B cold call does not begin when someone dials a number. It begins when the team decides why that company made it onto the list, which signal needs checking and whether the telephone is an appropriate channel in that case.

Without this work, the call depends on speed, improvisation and pressure. With context, it can be shorter: the caller identifies themselves, explains why they are calling, checks whether they have reached the right person and asks a question that helps both sides decide whether it is worth continuing.

This guide is operational and does not replace legal validation. The applicable rules vary according to the recipient, the source and nature of the data, the purpose, the existing relationship and how the call is conducted. Validate the specific case before starting a campaign.

Editorial image: Ada, Makers’ virtual persona, in a photorealistic composition created for this edition.

A cold call does not mean an indiscriminate call

“Cold” describes the absence of a previous sales conversation. It should not mean an absence of selection, relevance or limits.

A context-led call starts with six elements recorded before the first ring:

1. selected company: it belongs to the defined segment and territory;
2. verifiable signal: a current business fact supports the hypothesis;
3. data source: the team knows where the number came from and the purpose for which it is using it;
4. likely role: there is a proportionate reason to seek that department or responsibility;
5. useful question: the call aims to validate something, rather than recite a presentation;
6. exit rule: the team knows when to end, suppress the contact or refrain from contacting them again.

If one of these fields is empty, postponing the call is usually better than filling the gap with an assumption.

The initial go/no-go check: deciding whether the call should happen

Before preparing what to say, carry out a short review of the list.

1. Confirm the type of recipient

A general number published by a legal entity should not be treated in the same way as a professional’s personal number. A contact being publicly available does not, on its own, settle the lawfulness of using it, the individual’s expectations or the suitability of the purpose.

Record whether the number is:

• the company’s switchboard or general line;
• a line for a role or department;
• a named professional contact;
• a personal contact or one of uncertain nature.

When its nature is uncertain, do not assume. Return to the source or choose another approach.

2. Check objection lists and internal suppression

Portuguese Law No. 41/2004, as amended, distinguishes subscribers who are natural persons from those who are legal entities and establishes obligations concerning unsolicited communications. Article 13-B includes consulting the national list of legal entities that have objected.

In addition to the applicable external checks, always consult the internal suppression list. A new import, a different spreadsheet or a change of operator does not cancel a request to stop.

3. Exclude inappropriate signals

Do not turn information about health, family, opinions, alleged financial circumstances, technical vulnerabilities or anything the person would not reasonably expect to hear in a sales call into a sales argument.

The context should concern business activity: a published offering, the region served, a visible process, a contact channel, an announced expansion or another proportionate, verifiable fact.

4. Define the purpose of the call

“Introduce the company” is too vague. Choose a purpose that can be fulfilled in a short conversation:

• confirm who manages a particular process;
• check whether an observable problem exists;
• understand whether it is worth sending an example;
• obtain permission for a second step;
• conclude that there is no relevance and close the conversation.

A context sheet that fits on one screen

The operator does not need a lengthy report. They need a small, verifiable sheet:

Do not turn the sheet into a script for pretending familiarity. Its purpose is to prevent a generic call and make the reason for contact auditable.

An opening that asks for time without demanding attention

The first few seconds should answer three questions for the person receiving the call: who is calling, from which company and why.

A simple structure:

Good morning, this is [NAME] from [COMPANY]. I am calling because we noticed [BUSINESS SIGNAL] and wanted to check who manages [PROCESS]. Have I caught you at a bad time?

If the person says they cannot talk, do not turn a request for permission into a tactic for continuing. Ask whether they would prefer to end the call, point you towards the right department or receive a summary through an appropriate channel — only where that step is permitted and wanted.

Avoid openings such as:

• “I will not take much of your time” before explaining the reason;
• “We have an unmissable opportunity” without context;
• “I have been following your work” when you only found a name;
• “I want to speak to the decision-maker” without saying which process you mean;
• “It is a quick call” followed by a long presentation.

The relevance statement: fact, hypothesis and limit

After introducing yourself, connect the signal to a hypothesis without presenting something you do not yet know as certain.

I saw that the company has started serving [REGION]. In similar operations, local enquiries tend to reach the sales team through several different channels. I wanted to understand whether that is an issue for you or whether it is not a priority.

The statement works because it contains:

• a fact that can be confirmed;
• a hypothesis presented as a hypothesis;
• a question that allows the other person to correct your interpretation;
• an explicit way out if the subject is not relevant.

Ask two questions, rather than conducting an interrogation

A first call rarely needs a full discovery conversation. Two well-chosen questions are enough to decide the next step.

Useful questions:

• “How do you currently route enquiries that arrive through [CHANNEL]?”
• “What happens when a contact is not assigned an owner straight away?”
• “Is the priority to generate more demand or to organise existing demand better?”
• “Who manages this day to day?”
• “Would it make sense to see an example applied to a similar operation?”

Avoid asking for internal data, sensitive volumes, budgets or system access before there is enough context. The call should reduce uncertainty, rather than collect everything for which the CRM has a field.

Four valid ways to end the call

A useful cold call has more than “meeting booked” as a possible outcome.

1. There is relevance

Confirm a small next step: send a specific example, arrange a short conversation with an agenda or involve the person responsible.

2. This is not the right person

Ask for guidance on the department, rather than unnecessary personal details:

I understand. Which team normally manages [PROCESS]?

If they do not refer you, thank them and end the call.

3. It is not a priority

Record the reason in factual language. Do not try to turn every objection into another presentation.

Thank you for being clear. I will leave it there.

4. There is an objection or a request to stop

Confirm that you will respect the request, end the call and update suppression. The EDPB explains that, for direct marketing, an objection must lead to an end to processing for that purpose.

When nobody answers

“No answer” is still not permission to keep trying. Record the exact outcome: unanswered, voicemail available, switchboard unable to refer, invalid contact or callback requested.

If leaving voicemail is part of the approved policy, keep it short and make your identity clear:

Good morning, I am [NAME] from [COMPANY]. I called about [BUSINESS REASON]. It is not urgent. If you handle this subject, you can reach me through [CHANNEL]; if it is not relevant, there is no need to reply.

Do not disclose sensitive personal or business details on a system that others may hear. Do not create artificial urgency or say that you will “keep trying” as an implied threat.

The Voicemail and second B2B call guide explores the decision between leaving a message, trying a second time or stopping.

A second call needs a new or still-valid reason

Another attempt should not erase what happened before. Check:

• whether a voicemail was left and what was said;
• whether the time and channel comply with internal policy;
• whether a new signal has appeared or the original reason remains current;
• whether there is any objection, request to postpone or indication of a wrong contact;
• whether the second attempt adds value or merely increases activity.

An honest opening could be:

Good morning, this is [NAME] from [COMPANY]. I tried calling on [DATE] about [SUBJECT] and left a brief message. I just wanted to check whether this is the right department; if it is not, I will leave it there.

Do not imply continuity where there has been no conversation. An unanswered call does not create a relationship.

What to record in the CRM

The record should allow another person to understand the context without hearing the entire call:

• date, time, operator and number used;
• source and nature of the contact;
• company, role and signal that prompted the call;
• standardised outcome;
• question answered and useful context;
• objection or restriction stated;
• next step, owner and date;
• deadline or stopping rule.

Use factual notes. Avoid labels such as “difficult”, “hostile” or “lacks vision”. “Asked not to be contacted again” is precise and actionable; “difficult prospect” is not.

Metrics that help improve selection

Measure the quality of the system, not just activity:

• percentage of valid numbers;
• contacts with the right department;
• conversations in which the signal was confirmed;
• calls that produced an agreed next step;
• reasons for a poor fit;
• objections and suppressions processed;
• meetings that actually took place;
• learning by segment, territory and signal.

More calls with falling relevance do not mean greater productivity. They mean more noise, measured precisely.

Review before starting

Before dialling the first number, confirm:

• the segment, company and signal have been checked;
• the source and nature of the number are recorded;
• the recipient and purpose have passed the applicable validation;
• objection and suppression lists have been checked;
• the operator knows how to identify themselves and explain the reason;
• there are no more than two priority questions;
• the next step is proportionate;
• voicemail and a second attempt have defined rules;
• objections can be recorded and propagated without delay;
• recording is disabled, unless a specifically validated and communicated process applies.

Sources for validation

Before putting sales calls into operation, check the process against:

• Portuguese Law No. 41/2004, as amended, particularly Articles 13-A and 13-B;
• CNPD Guideline 2022/1, which addresses electronic direct marketing communications and includes telephone calls;
• the EDPB’s guidance on individuals’ rights, including objections to direct marketing;
• ANACOM’s information on calling line identification.

These sources do not replace an assessment of the campaign, recipients, data and internal processes. Use them to formulate controls and seek appropriate validation.

Turn preparation into a useful conversation

The Context-led cold call script brings together the initial go/no-go check, preparation sheet, opening, questions, exits, voicemail, second call and post-contact record in a single working document.

The aim is not to help the team speak faster. It is to help them know why they are calling, what they need to learn and when they should stop.