![\"29693\"](\"https:\/\/news.swordfish.ai\/wp-content\/webp-express\/webp-images\/uploads\/2026\/01\/how-to-find-candidates-phone-numbers-93d512e7.png.webp\")
<\/p>\n<\/p>\n
Byline:<\/strong> Ben Argeband, Founder & CEO of Swordfish.AI<\/p>\n When I’m accountable for time-to-fill and candidate experience across a team, phone is a precision channel. It only helps if we can prove we’re contacting the right person, keep messages respectful, and stop immediately on opt-out.<\/p>\n If you’re asking how to find candidate phone number<\/strong> reliably, the repeatable part is identity resolution before enrichment. That prevents wrong-person outreach, reduces complaints, and improves reply rates without adding more volume.<\/p>\n This is for recruiters and sourcers who need a practical playbook for finding candidate phone numbers and reaching out responsibly. It fits teams that:<\/p>\n Finding phone numbers is not the outcome. The outcome is faster, higher-quality conversations with the right people while protecting candidate trust. In practice, teams are trying to:<\/p>\n Treat phone as permission-based even when the data is legally sourced: lead with identity, purpose, and an exit.<\/p>\n If someone asks how you got their number, answer once in plain language, then offer opt-out again and stop if requested.<\/p>\n Rules vary by region and channel. Follow your internal policy and local requirements for calling\/texting, and stop immediately on opt-out.<\/p>\n Use this sourcing workflow<\/strong> to find candidates phone numbers with fewer wrong numbers and faster first conversations: identity → enrich → verify → rank → outreach<\/strong>. Each step exists to protect candidate experience while improving placement speed.<\/p>\n 1) Identity (resolve the right person)<\/strong><\/p>\n Input:<\/strong> name, current company, title, location, and a stable profile URL. Output:<\/strong> one confirmed person record you can defend if challenged.<\/p>\n Many teams anchor identity on LinkedIn sourcing<\/strong> because employer and role signals are consistent. Using LinkedIn sourcing as the identity anchor reduces false matches, which reduces wrong-number texts and protects candidate experience.<\/p>\n 2) Enrich (append contact channels)<\/strong><\/p>\n Input:<\/strong> a confirmed identity record. Output:<\/strong> phone and email attached to that identity.<\/p>\n Write the number back to your ATS\/CRM with source URL, date captured, and suppression status so the team doesn’t re-contact opted-out candidates.<\/p>\n 3) Verify (reduce wrong numbers and wasted touches)<\/strong><\/p>\n Input:<\/strong> enriched phone data. Output:<\/strong> a number you’re comfortable using for SMS\/call outreach.<\/p>\n Minimum standard: confirm country\/area alignment, mobile classification where available, and at least one corroborating identity signal before outreach. If you need a deeper walkthrough of enrichment and validation approaches, see candidate phone number lookup<\/a>.<\/p>\n 4) Rank (prioritize who to call\/text first)<\/strong><\/p>\n Input:<\/strong> verified contact data plus role fit. Output:<\/strong> a prioritized list that matches effort to expected return.<\/p>\n Some teams use ranked mobile numbers by answer probability<\/strong> to decide who gets a call versus SMS-first. Use SMS-first when you need consent-forward outreach and the candidate is likely in meetings; use call after you’ve sent context and you need a same-week conversation. The business outcome is more conversations per hour of sourcing, which improves time-to-submit on scarce profiles.<\/p>\n 5) Outreach (3-touch candidate reach plan)<\/strong><\/p>\n Input:<\/strong> a prioritized list and a clear reason for outreach. Output:<\/strong> a scheduled conversation or a clean “no,” without repeated pings.<\/p>\n Use the 3-touch candidate reach plan<\/strong> over 3–5 business days: (1) SMS with opt-out, (2) email with role context, (3) one call or voicemail referencing the prior messages. This reduces surprise calls and increases replies from passive candidates who need a clear reason to engage.<\/p>\n FIELD NOTE:<\/strong> SMS-first with opt-out typically produces cleaner engagement than call-first because the candidate can respond on their schedule and you’ve established intent before a live conversation.<\/p>\n Use this weighted checklist to decide whether a candidate should enter phone\/SMS outreach today. The weights reflect common failure points that slow placement speed: poor identity match, unverified contact data, and weak relevance. Total possible weight: 100.<\/p>\n Operating rule:<\/strong> If you score below 70\/100, fix identity, relevance, or verification before you send SMS or place a call.<\/p>\n Use the templates below as written, then personalize the one line that proves relevance. Recommended spacing for the 3-touch plan: Day 1 SMS, Day 2 email, Day 4 call\/voicemail.<\/p>\n These recruiting outreach templates reduce back-and-forth and improve reply-to-meeting conversion because the next step is explicit.<\/p>\n When they respond, confirm the best channel and ask if texting is okay going forward. If they reply STOP, confirm suppression and do not re-add later.<\/p>\n Template 1: SMS (first touch, passive candidate)<\/strong><\/p>\n Hi {FirstName} — I’m {YourName}, a recruiter with {Company}. I’m reaching out because your background in {SpecificSkill\/Domain} looks aligned with a {RoleTitle} role I’m hiring for. Open to a quick 10-min chat this week? Reply YES and I’ll send times. If you’d rather not get texts from me, reply STOP.<\/p>\n Template 2: Email (second touch, adds detail)<\/strong><\/p>\n Subject: {RoleTitle} — quick question<\/p>\n Hi {FirstName},<\/p>\n I’m {YourName} with {Company}. I’m hiring for a {RoleTitle} and reached out because of your work in {SpecificSignal: tech stack \/ domain \/ scope}.<\/p>\n If you’re open to it, I’d like to ask two questions: (1) are you open to a change in the next {Timeframe}? (2) what range would you need to consider it?<\/p>\n If now isn’t a fit, reply “not interested” and I’ll close the loop.<\/p>\n Template 3: Voicemail (third touch, references prior messages)<\/strong><\/p>\n Hi {FirstName}, this is {YourName} with {Company}. I sent a quick text and email about a {RoleTitle} role because of your experience in {SpecificSkill}. If you’re open to a brief chat, you can call me back at {CallbackNumber}. If you’d prefer I stop reaching out, just reply STOP to my text and I’ll update my records. Thanks.<\/p>\n Template 4: SMS (silver medalist re-engagement)<\/strong><\/p>\n Hi {FirstName} — {YourName} here. We spoke earlier about {OldRole\/Team}. I’m hiring again for {NewRoleTitle} with {KeyConstraint: comp\/location\/stack}. Want me to send details? Reply YES and I’ll share a 3-bullet summary. Reply STOP to opt out.<\/p>\n Template 5: Agency recruiting (candidate-first framing)<\/strong><\/p>\n Hi {FirstName} — I’m {YourName}. I support a few teams hiring for {RoleFamily}. Based on your {SpecificSkill}, I may have a role that matches your priorities (comp\/location\/remote). If you tell me your top 2 must-haves, I’ll only send roles that match. Reply STOP to opt out.<\/p>\n Why this workflow works operationally:<\/strong> identity resolution reduces wrong-person outreach; enrichment increases reachable candidates; verification reduces wasted dials; ranking focuses effort on the best-fit prospects; structured outreach improves reply-to-meeting conversion. Those are the levers that affect placement speed.<\/p>\n What to log for auditability:<\/strong> source profile URL, date\/time of enrichment, verification notes (at a high level), and opt-out status. This keeps your team consistent and prevents repeat-contact incidents.<\/p>\n Suppression discipline:<\/strong> If a candidate opts out in SMS, suppress them from calls and emails as well.<\/p>\n Quality expectations:<\/strong> If connect rates are low, don’t assume candidates don’t answer. Assume your identity and verification steps are leaking. Teams that use ranked mobile numbers by answer probability<\/strong> typically waste fewer touches because they prioritize the most reachable prospects first.<\/p>\n How do I find a candidate phone number if I only have a LinkedIn profile?<\/strong><\/p>\n Confirm identity signals (name, company, title, location). Then enrich from that identity and verify the number before outreach. This reduces wrong-person contact and improves reply-to-meeting conversion.<\/p>\n Is it acceptable to text passive candidates?<\/strong><\/p>\n It can be if you provide context, keep it brief, and include opt-out language. SMS-first often improves candidate experience because it’s asynchronous.<\/p>\n What’s the safest order: call, text, or email?<\/strong><\/p>\n For most roles: SMS (with opt-out) → email (details) → one call\/voicemail referencing the prior messages.<\/p>\n How many times should I try before I stop?<\/strong><\/p>\n Use a defined 3-touch plan over 3–5 business days, then stop unless the candidate re-engages.<\/p>\n How do I avoid contacting the wrong person?<\/strong><\/p>\n Make identity resolution a gate before saving a number: company + title + location consistency. If you can’t confirm, don’t outreach by phone.<\/p>\n How do I manage opt-outs across tools?<\/strong><\/p>\n Create one suppression field in your ATS\/CRM and enforce it in every sequence tool so SMS opt-outs suppress calls and emails too.<\/p>\n Day 1:<\/strong> Standardize the workflow (identity → enrich → verify → rank → outreach) and add a suppression field that every recruiter can see.<\/p>\n Days 2–3:<\/strong> Implement the 3-touch candidate reach plan and require the Weighted Checklist score before SMS\/call outreach.<\/p>\n Week 2:<\/strong> Review wrong-number rate, connect rate, and reply-to-meeting conversion. Fix the step that’s leaking before increasing volume.<\/p>\n Week 3–4:<\/strong> Document your minimum verification standard and opt-out handling so agency recruiting partners and internal teams follow the same rules.<\/p>\n If you need a compliance baseline for contact data collection and outreach, use contact data compliance<\/a>.<\/p>\n Ben Argeband<\/span><\/a> is the Founder and CEO of Swordfish.ai and Heartbeat.ai. With deep expertise in data and SaaS, he has built two successful platforms trusted by over 50,000 sales and recruitment professionals. Ben’s mission is to help teams find direct contact information for hard-to-reach professionals and decision-makers, providing the shortest route to their next win. Connect with Ben on <\/span>LinkedIn<\/span><\/a>.<\/span><\/p>\n<\/span>Who this is for<\/span><\/h2>\n
\n
<\/span>What recruiters are trying to accomplish<\/span><\/h2>\n
\n
<\/span>Ethical use of phone numbers<\/span><\/h2>\n
\n
<\/span>Sourcing workflow<\/span><\/h2>\n
<\/span>Checklist: Diagnostic Table<\/span><\/h2>\n
\n\n\n
\n \nSymptom<\/th>\n Likely root cause<\/th>\n What to change (next 24 hours)<\/th>\n Metric to watch<\/th>\n<\/tr>\n<\/thead>\n \n SMS delivered, no replies<\/td>\n Message lacks context or reads like bulk outreach<\/td>\n Add 1 line proving relevance (specific skill + why now) and include opt-out<\/td>\n Reply rate per 50 sends<\/td>\n<\/tr>\n \n High “wrong number” rate<\/td>\n Weak identity resolution before enrichment<\/td>\n Require company + title match before saving a number; re-check location<\/td>\n Wrong-number rate<\/td>\n<\/tr>\n \n Calls go to voicemail repeatedly<\/td>\n Calling at low-answer times or using non-mobile numbers<\/td>\n Shift to SMS-first; call only after SMS\/email context<\/td>\n Connect rate<\/td>\n<\/tr>\n \n Candidate replies: “How did you get my number?”<\/td>\n No transparency or consent framing<\/td>\n Use a short explanation and offer opt-out immediately<\/td>\n Negative reply rate<\/td>\n<\/tr>\n \n Candidate opts out, then gets contacted again<\/td>\n Opt-out not synced across ATS\/CRM and sequences<\/td>\n Create a single suppression field and enforce it in every tool<\/td>\n Repeat-contact incidents<\/td>\n<\/tr>\n \n Strong candidates respond but don’t schedule<\/td>\n Too much back-and-forth, unclear next step<\/td>\n Offer two time windows and confirm interview format in the first reply<\/td>\n Reply-to-meeting conversion<\/td>\n<\/tr>\n \n Low response on hard-to-reach roles<\/td>\n Value prop not specific to the constraint<\/td>\n Lead with the one constraint that matters (comp band, location flexibility, tech stack)<\/td>\n Qualified reply rate<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n <\/span>Decision Tree: Weighted Checklist<\/span><\/h2>\n
\n
<\/span>Outreach templates<\/span><\/h2>\n
<\/span>Troubleshooting Table: Outreach Templates<\/span><\/h2>\n
<\/span>Evidence and trust notes<\/span><\/h2>\n
<\/span>FAQs<\/span><\/h2>\n
<\/span>Next steps<\/span><\/h2>\n
<\/span>About the Author<\/b><\/span><\/h2>\n