How to Tell if a Number Is Mobile or VoIP (Recruiter Routing Guide)

Last updated: August 28, 2026

Ben Argeband, Founder & CEO of Heartbeat.ai — Decision-based; no telecom deep dive.

Who this is for

Recruiters who need to decide whether SMS is appropriate, avoid wasted dials, and keep outreach compliant. If you’re trying to reach a real person faster without texting a shared office line, this is the routing playbook.

Quick answer

Core answer

Classify the line type, validate it against behavior, then route: mobile numbers can support SMS in the right circumstances; VoIP and landline numbers usually call for a call or email first. Number porting makes any of this probabilistic, not certain.

Key insight

Line type changes expectations and reachability, but it’s a routing input, not a guarantee. Treat it as a starting hypothesis you confirm with outcomes.

Best for

Recruiters deciding whether SMS is appropriate for a given number and trying to avoid wasted dials.

Compliance & safety

This method is for legitimate recruiting outreach only. Always respect candidate privacy, opt-out requests, and applicable data and telemarketing laws. Heartbeat does not provide legal counsel, and nothing here should be treated as a substitute for advice from qualified counsel on TCPA or state-level requirements.

• 60-second tells (practical)
  • A personal voicemail greeting with a name usually behaves like a personal line.
  • IVR menus (“press 1…”) usually behave like a business system, often VoIP.
  • A front desk or staff member answering is a shared-line signal — don’t treat it like a personal mobile.
  • A “wrong person” response means the number was reassigned or shared. Suppress and refresh it.
  • If detection says mobile but you consistently hit an IVR, suspect number porting or business routing.

• SMS red flags (pause texting)
  • Any IVR or operator greeting on the number.
  • Staff replies or a shared-inbox tone (“Scheduling,” “Front Desk,” “Team”).
  • Wrong-party indicators or identity uncertainty.
  • Any opt-out request — suppress immediately.

Framework: detect, validate, route, refresh

• Detect: identify the likely line type — mobile, VoIP, or landline.
• Validate: confirm the number behaves the way you’d expect (connects, answers, accepts SMS, or bounces).
• Route: choose the first channel and fallback sequence based on risk and speed to connect.
• Refresh: re-check periodically, because number porting and reassignment change outcomes over time.

Line type isn’t trivia in recruiting — it’s a workflow control that determines whether you call, email, or carefully text. The trade-off is time: classifying and validating a number takes a minute or two up front, but it stops your team from burning attempts on the wrong channel repeatedly.

Step-by-step method

Step 1: Detect the likely line type

Bucket the number as mobile, VoIP, or landline. You’re aiming for a first-route decision, not certainty.

VoIP, in plain language, means calls route over the internet instead of a cellular network or traditional copper line. In recruiting contexts, VoIP often signals a business phone system or shared routing, but not always — some clinicians use VoIP as a personal line.

Line type describes how a number is provisioned and how it typically behaves: mobile (cellular), VoIP (internet-based calling), or landline (traditional fixed line). In recruiting operations, it’s a proxy for reachability and channel fit, not a legal classification.

If your team uses a line type lookup tool, treat the result as a starting point rather than a final answer.

Step 2: Validate with behavior

Detection tools can be wrong because of number porting and reassignment. Validate using what actually happens when you try to reach the person.

Porting happens when a phone number is transferred from one provider or service type to another while keeping the same digits. It can change whether SMS works, who answers, and how calls route — sometimes without any visible signal in a database lookup.

Suspect porting or business routing when detection indicates mobile but you repeatedly hit an IVR or operator greeting; when different attempts produce inconsistent outcomes, such as a personal voicemail one day and a front desk the next; or when SMS delivers but replies come from staff or a generic shared inbox.

• Call behavior: personal greeting versus IVR versus generic mailbox.
• Wrong-party signals: staff answering, a clinic operator, or a direct “you have the wrong number.”
• SMS behavior: only test SMS when you have consent where required and you’ve included opt-out language.

Step 3: Route outreach based on line type and risk

Route your first attempt to maximize connectability while minimizing compliance risk. For a likely mobile number, call first when urgency is high; SMS is optional when appropriate and you can honor opt-out immediately. For a likely VoIP number, call and email first, and treat SMS as higher risk until the clinician confirms the line is personal. For a likely landline, call during business hours, expect gatekeepers, and use email to confirm the best direct contact.

If line type is still unknown after two attempts — one call plus one email — stop guessing with SMS and move to confirmation-first outreach instead.

Step 4: Refresh and suppress

Numbers decay. Build a refresh loop and suppression rules so your team doesn’t keep hammering stale or shared lines. Refresh the line type classification when outcomes contradict detection — for example, a “mobile” number that always hits an IVR. Suppress numbers that generate repeated wrong-party responses or any explicit opt-out. Log outcomes by line type so routing rules improve over time instead of staying static.

Diagnostic table

Heartbeat.ai ops note: when you have multiple numbers on file for the same clinician, prioritize the one most likely to connect first; Heartbeat.ai can support routing with ranked mobile numbers by answer probability.

Weighted checklist

Use this to decide whether a number is safe to text now versus one that needs a call or email first. Score it, then follow the decision.

• +3 Candidate explicitly provided the number or confirmed it in writing.
• +2 Detection indicates a mobile number.
• +1 Call reaches a personal greeting, not an IVR.
• -2 Detection indicates VoIP or landline.
• -2 Any shared-line indicator — IVR, operator, front desk, group voicemail.
• -3 Any explicit opt-out or wrong-party indicator.

A score of 4 or higher means SMS can be appropriate if you include opt-out language and have consent where required. A score of 1 to 3 means call first, then consider SMS only after confirmation. A score of 0 or below means route through email or call via the office; don’t text until identity and appropriateness are confirmed.

Outreach templates

Template 1: Voicemail (mobile-leaning)

Voicemail: “Hi Dr. [Last Name] — this is [Name] with [Org]. I’m calling about a [role] opportunity in [city]. If this is the best number, call me at [number]. If not, email me at [email] and I’ll update my records.”

Template 2: First SMS (only when appropriate)

SMS: “Hi Dr. [Last Name] — [Name] with [Org]. Are you open to a quick call about a [role] option in [city]? Reply YES/NO. To opt out, reply STOP.”

Reminder: only text when you have consent where required and the line appears personal. Always honor opt-out requests promptly.

Template 3: Email opener (VoIP/landline-safe)

Subject: “Confirming best contact for [role] in [city]”

Email: “Dr. [Last Name], I’m recruiting for a [role] role in [city]. Can you confirm the best number to reach you directly? If you prefer not to be contacted, let me know and I’ll mark an opt-out.”

Common pitfalls

• Assuming line type is a guarantee: porting and reassignment mean you need outcomes-based validation, not just a database label.
• Texting shared lines: VoIP and office systems can be monitored by staff. Confirm personal ownership before sending SMS.
• Ignoring opt-out: if someone opts out, suppress immediately across every channel and system you use.
• Over-dialing the wrong route: if a number behaves like a clinic system, stop treating it like a personal mobile and switch to email plus office-hour calling.
• Not tagging outcomes: without logging by line type, you can’t coach reps or improve your routing rules over time.

How to improve results

Improvement comes from measuring outcomes by line type and adjusting routing rules accordingly. Track each attempt with the detected line type, the channel used, the outcome, and whether the clinician confirmed the number is personal.

Measurement instructions

• Connect rate = connected calls divided by total dials.
• Answer rate = human answers divided by connected calls.
• Deliverability rate = delivered emails divided by sent emails.
• Bounce rate = bounced emails divided by sent emails.
• Reply rate = replies divided by delivered emails.

What to log on every attempt:

• Detected line type — mobile, VoIP, landline, or unknown.
• Channel used — call, email, or SMS.
• Outcome — connected, answered, voicemail, IVR, wrong-party, opt-out, or reply.
• Next action — retry window, switch channel, suppress, or refresh.

Refresh triggers: detection says mobile but outcomes look like IVR or operator; any wrong-party response; or repeated no-connect patterns that contradict the expected line type.

A simple weekly ops review helps: compare connect rate and answer rate for numbers detected as mobile versus VoIP versus landline, compare reply rate for call-first versus SMS-after-confirmation sequences where SMS was actually appropriate, and track wrong-party and opt-out rates by source so you can refresh and suppress aggressively when they spike.

Routing worksheet

Use this decision tree to route outreach without overthinking each call:

• Step A: Detect line type. Mobile number → go to Step B. VoIP or landline → go to Step C. Unknown → go to Step D.
• Step B: Mobile route. Call first. If appropriate and permitted, send one SMS with opt-out language. If no response, email to confirm best contact and preference.
• Step C: VoIP/landline route. Call during business hours and expect gatekeepers. Email to confirm direct contact and preference. Only send SMS after the clinician confirms it’s their personal number.
• Step D: Unknown route. One call attempt plus one email. Classify based on behavior, then follow Step B or C. Refresh the record if outcomes conflict.

Legal and ethical use

Recruiting outreach needs to be compliant and respectful. TCPA rules around SMS have been shifting: businesses generally need prior express written consent before sending marketing text messages, and opt-out requests must be honored promptly once received. Build your workflow around permission, transparency, and fast suppression rather than assuming a number’s line type settles the question.

• Consent: a personal number is not automatic permission to text. Get consent where required and keep messages relevant to the recipient.
• Opt-out: make opting out easy and honor it immediately across every system you use.
• Minimize exposure: avoid sending sensitive details to numbers that may be shared, which is common with VoIP and office lines.
• Document your process: keep logs of outreach attempts and opt-out handling in case a record is ever challenged.

Rules in this area continue to evolve, and requirements can vary by state, so review current FCC guidance and consult qualified counsel before finalizing your SMS policy.

FCC TCPA overview

Evidence and trust notes

This page is written for recruiting operators. We treat line type as probabilistic because number porting and reassignment are common, and outcomes matter more than labels.

• How we think about data quality, verification, and suppression: Heartbeat trust methodology.
• More provider contact data workflows: provider contact data resources.
• Regulatory baseline for unwanted calls and texts: FCC guidance on stopping unwanted robocalls and texts.
• TCPA overview: FCC TCPA overview.

FAQs

Is a VoIP number always a business line?

No. Some clinicians use VoIP personally, and some practices route calls through VoIP systems. Treat VoIP as a higher shared-line risk until the clinician confirms it’s personal.

Can a mobile number be non-textable?

Yes. Some mobile numbers can’t receive texts due to settings, service issues, or how the number was provisioned after number porting. Validate with outcomes and don’t assume.

What should I do if line type says “mobile” but I keep hitting an IVR?

Assume the number is ported or being routed through a business system. Reclassify it operationally as business-routed and switch to call and email first.

When is it appropriate to send an SMS?

When you have consent where required or a legitimate outreach rationale, the number appears personal, and your message includes clear identification and opt-out handling. If it’s VoIP, landline, or shared, confirm first.

How does line type affect recruiter metrics?

It changes your connect rate and answer rate on calls, and it changes whether SMS is even a reasonable channel. Track outcomes by line type so you can route smarter and reduce wasted attempts.

Next steps

• If you’re standardizing routing across your team, document your rule for how to tell if a number is mobile or VoIP so reps don’t improvise under pressure.
• To align your team on which number to try first — office line, direct dial, or mobile — see: office line vs direct dial vs mobile: recruiter routing.
• If you need a deeper workflow for confirming whether a clinician number is usable for outreach, use: number usability check for clinician outreach.
• If you want to operationalize this routing inside your sourcing workflow, start free search & preview data.

About the Author

Ben Argeband 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 LinkedIn.