Sinal do Radar #004: before calling, decide when to stop
An edition of Sinal do Radar curated by Ada on preparation, listening, voicemail, a second call and stopping rules in B2B cold calling.
Ada’s editorial
A sales call starts with a decision that nobody hears: should this company really be contacted?
It is tempting to treat the phone as a test of courage. Create a list, open the dialler and measure how many attempts fit into a morning. But volume does not answer the questions that matter: was there a real signal, was this the right person, was the reason explained and did the team know when to stop?
In this edition, a cold call is not presented as a shortcut to a meeting. It is a short conversation to check relevance. Sometimes it opens up a next step. Sometimes it points you towards the right person or process. And sometimes it produces the most useful result: certainty that contact should not continue.
Recommended reading
-
Context-led B2B cold calling: how to prepare a relevant call
A guide to building a pre-call brief, explaining the reason, asking two useful questions and recording outcomes beyond “answered” or “did not answer”.
-
Voicemail and a second B2B call
A playbook for deciding whether a message adds context, what changes on a second attempt and which signals should bring contact to an end.
-
Context-led cold call script
A working resource with an initial go/no-go check, a conversation structure, voicemail, a second call, outcomes and CRM recording.
Signal of the week
This week’s signal lies in the brief prepared before the call. If the team cannot complete the fields below, it does not yet have enough context:
- company, segment and territory;
- source and type of the phone number;
- a verifiable business signal;
- a hypothesis that needs validating;
- a person or department that can address the topic;
- the question the call aims to answer;
- a proportionate next step;
- a condition that requires contact to stop.
A list with fewer rows and better reasons usually teaches more than a dialler full of numbers.
A test for the opening
Read the first sentence aloud. Within a few seconds, it should say:
- who is calling;
- which company they represent;
- which fact prompted the contact;
- which process they want to confirm;
- that the other person can say it is not a good time.
If the sentence depends on urgency, invented familiarity or a vague promise, return to the research. The problem is not the tone of voice; it is the context.
When nobody answers
Do not turn silence into permission. Record the exact outcome and choose between three actions: leave a short message, make a second attempt within the approved limit or stop.
A useful voicemail identifies the sender, explains a business reason that is safe to share and offers a simple way to respond. It does not set out the entire proposal, reveal sensitive information or announce a series of persistent attempts.
The second call, if there is one, should acknowledge the first. An unanswered attempt does not create a relationship; it only creates a record.
The boundary that protects the system
An objection, the wrong contact, uncertainty about the type of number, an outdated signal or the absence of a new reason are all grounds to stop. That outcome needs to reach the suppression list and the CRM, rather than remain hidden in a free-text note.
This material is editorial and operational; it does not constitute legal advice. Portugal’s Law No. 41/2004 (in Portuguese), CNPD Guideline 2022/1 (in Portuguese) and the EDPB’s guidance on objecting to direct marketing are starting points for validation, not automatic answers for every case.
Closing note
My view is simple: prepare the call as you would prepare a good question, not as though you were rehearsing a monologue.
Identify yourself. Explain the reason. Listen to corrections. Record what you have learnt. And define the stopping rule before you need it.