"How did you get my number?" is not a cue to speak faster. It is a direct question about trust, privacy and whether the person wants the conversation to continue.
Answer it before doing anything else. If the source is defensible, say what it is. If the data is wrong, admit it and fix it.
First, hear the question behind the question
The buyer may be curious, surprised, worried about a personal mobile number, angry about repeated calls or testing whether the caller is legitimate. Tone and wording matter.
Do not assume every person is inviting an objection response. A firm "Remove this number" is an instruction. A calmer "Where did you find me?" may only need a transparent answer.
Listen for whether the concern is the source, the number type, the frequency or the company's identity. Answer the issue the person raised. A long explanation of data practices does not help somebody who is simply saying, "This is my private line."
Use a four-part response
The response should include the source, selection reason, boundary and choice:
We use [specific source or approved source category] for business contact information. I selected you because [role and account reason]. I understand you may not want a call here. Would you like me to explain the business reason in twenty seconds, use another channel or remove the number?
Do not bury the source beneath a company speech. Answer the question in the first sentence.
Script for a public business number
I found the number on [company directory, professional profile or other specific public source]. I called because your role appears to own [business issue]. If I have the wrong person or this is not a suitable number, I will correct it.
Only say public when you can identify the public source. "It was somewhere online" sounds like the caller found the number taped under a bus seat.
Script for a third-party business data source
Follow the client's approved disclosure language and the provider agreement:
The contact was provided through a third-party business data source we use for B2B outreach. I selected your account because [verified reason] and your role appeared relevant. If this number should not be used, I can record that now.
If the person requests the provider name, removal process or more detail, do not improvise. Use the documented answer or escalation path.
Script for an accidental personal number
When the person says the number is personal and the campaign did not intend to call it, stop selling:
I am sorry. We had this recorded as a business contact number. I will mark it for removal and end the call. Thank you for correcting it.
Then apply the suppression and investigate the record. An apology followed by a pitch is not an apology.
Script when the buyer sounds concerned but stays open
Fair question. We identified [Account] because [verified event or fit], and your role appeared connected to [issue]. The contact came from [source]. I can give you the reason for the call briefly, and you can decide whether we continue.
If the buyer agrees, use one plain problem statement and one question. Do not treat permission for twenty seconds as permission for the keynote address.
If the buyer declines but does not request removal, follow the approved campaign disposition. Do not use the softer ending as permission to hunt for another mobile number. The route may be a public business channel, a timed follow-up or a clean close.
Know the three paths after the answer
Continue: The person accepts the explanation and wants to hear the business reason. Ask one relevant question.
Redirect: The number or contact is wrong, but the person offers a business channel or correct owner. Confirm the correction without pressing for more private information.
Stop: The person requests removal, sounds unsafe, identifies a personal number that should not be used or the source cannot be explained. End the call and trigger the process.
The broader objection handling guide explains how to clarify meaning without turning a boundary into a debate.
Do not use these responses
Avoid "I have my ways," "It is all public," "Marketing gave it to me" and "Before I answer, let me tell you why I called." Each response makes the caller sound evasive.
Never invent a referral or say the buyer submitted a form unless the record proves it. A caller who cannot see the source should not guess which story feels safest.
Build the answer before the campaign
Every list should have a documented origin, permitted use, relevant market, review process, suppression workflow and approved explanation. Callers need to know which source category applies to the record in front of them.
Rules vary. The FTC explains that most US business-to-business calls are exempt from its Telemarketing Sales Rule, with exceptions, while other federal and state rules may still apply. Canadian B2B calls are exempt from National DNCL rules but remain subject to other Unsolicited Telecommunications Rules. UK live B2B marketing calls have screening, identification and objection requirements described by the ICO.
This guide is operational guidance, not legal advice. Get qualified advice for each jurisdiction, call type, number type and technology used.
CallTeam field card: contact-source response
Keep this beside the dialer:
- Pause and acknowledge the question.
- Name the real source or approved source category.
- Explain the account and role reason.
- Offer continue, redirect or remove.
- Record the outcome immediately.
If step two is impossible, do not freestyle. Stop and escalate the data issue.
How CallTeam handles contact-source questions in live outreach
CallTeam verifies the approved data source, market rules, suppression process and exact caller response before a campaign starts. Human callers answer the question plainly, give the buyer control and decide whether the conversation can responsibly continue. If relevance is confirmed, sales receives the business context, source concern and agreed meeting purpose. Wrong numbers are corrected, unsupported records are removed and opt-outs are suppressed. We do not move a questionable contact to another channel to pretend the restriction disappeared.
CallTeam field observation: In real calls, the question often becomes sharper when the opening was vague. A direct source answer plus a clear business reason can settle the concern quickly. Dodging it usually turns simple curiosity into distrust.
Record facts and honor the choice
The CRM note should capture the source category, concern, correction, new business channel if volunteered, opt-out status and action taken. A removal must feed the suppression process, not sit inside free-text notes waiting for the next caller to miss it.
CallTeam builds governed lists, prepares the approved response, makes the human calls and books qualified meetings when buyers choose to continue. Want CallTeam to run the campaign? Book a B2B strategy call to define the audience, data controls and live conversation path.