LinkedIn Phone Number Search: How to Find a Prospect's Number in 2026

You have a LinkedIn URL. You need a phone number. LinkedIn does not show phones publicly, so a LinkedIn phone number search always resolves outside the platform: you take the identity the profile gives you, then match it against phone data held elsewhere.

This guide covers both directions, profile to number and number back to profile, the 5 workflows that work in 2026, what each one really returns, and what it costs per match.

How a LinkedIn phone number search actually works

Every tool on this page does the same three things, and understanding them tells you why hit rates differ so much.

1. Identity resolution. The profile gives a first name, last name, current company and job title. That tuple is the key. It is not the phone number, and no amount of scraping the page will produce one that is not printed on it.
2. Matching. The key is looked up against phone data assembled from other places: company directories, registries, public filings, data partners. The match is probabilistic, which is why the same profile can return a number from one provider and nothing from another.
3. Verification. A matched number is checked for line type and reachability before it is handed back. Skipping this step is how lists end up 30% dead on arrival.

The consequence is worth stating plainly: a LinkedIn phone number search is an enrichment problem, not a scraping problem. The tools that behave like scrapers put your own LinkedIn session at risk for data the profile never held in the first place. The tools that behave like enrichment providers run the lookup on their own infrastructure, with your account out of the loop entirely.

It also explains the ceiling. Nobody holds every mobile number in existence, so nobody returns 100%. A provider quoting 90% is quoting coverage on the slice of profiles it does hold, not on the list you are about to run.

The 5 LinkedIn URL → phone workflows

1. Dedicated phone finder via LinkedIn URL

Tools like Derrick and Wiza take an URL and return a verified phone number. Hit rate 35-60% depending on region (US best, APAC weakest).

Pros: fastest, no ban risk on your account, works at bulk.
Cons: cost per match ($0.20-1.50).

2. LinkedIn Sales Navigator + cross-source

If the prospect exposed contact info on Sales Nav, you might see it. Combine with email finder cross-source to bypass.

Pros: leverages Sales Nav data you may already have.
Cons: requires Sales Nav subscription.

3. Chrome extension scraping

Chrome extensions of this kind scrape directly on profile pages.

Pros: free-tier often available.
Cons: cookie-based, ban risk on your account if abused (>50/day manual).

4. Manual research (Google + website + footer)

For high-value prospects: take the name, search Google + company website + look at footer signatures in their posts.

Pros: free, zero ban risk.
Cons: doesn't scale, 5-10 min per lead.

5. Direct ask (LinkedIn DM)

Simply ask: "What's the best number to reach you?" - works on warm connections, 8-15% reply rate.

Pros: 100% accurate when answered, builds rapport.
Cons: requires existing connection or strong context.

What LinkedIn itself exposes, and what it hides

Before paying for anything, it is worth knowing exactly what the platform gives you for free, because most guides skip it and most people over-estimate it.

The Contact Info panel

Every profile has a Contact info link under the headline. A member can put a phone number there, and some do. Visibility is set by the member and keyed to connection degree, which is why the same profile looks different to two people looking at it on the same day.

• 1st-degree connections: roughly 5% of members expose a number.
• 2nd and 3rd degree: closer to 0.5%.
• Logged out or out of network: effectively zero.

So the free path works, on about one profile in twenty, and only for people who already accepted your connection request. That is a fine reason to check it first on a shortlist of ten prospects. It is not a reason to build a calling list around it.

The "discover me by phone number" setting

LinkedIn has a privacy setting with a name that misleads people into thinking the platform offers a reverse lookup. It does not. The setting controls whether a member can be surfaced to someone who already has their number and uploads it from a phone contact list. It never turns a number you found somewhere into a profile on demand, and it is off for a large share of accounts.

Sales Navigator

Sales Navigator improves your targeting, not your contact data. It gives you far better filters for building the list of profiles worth calling, and it surfaces contact info the member chose to publish, on the same terms as everywhere else. The number itself still has to come from outside.

The honest summary: LinkedIn is the best identity graph in B2B and a poor phone directory. Use it for the first job and resolve the second one elsewhere.

Hit rate by tool - what's real in 2026

Read the last column with the first. Derrick returns a number on 50-60% of US profiles for roughly a fifth of what the same match costs on the premium tier, which is what decides the budget once you run thousands of rows rather than dozens.

Two caveats on any table of this kind, including this one. Hit rates move by region and by seniority: a VP at a 5000-person US company resolves far more often than an individual contributor at a 20-person shop in southern Europe. And a match that is never dialled is worth nothing, which is why phone number validation belongs in the workflow before the call list, not after the first wasted hour.

Free methods: Google operators for a LinkedIn phone number search

Before spending a credit, there is a free tier that costs only time. It will not scale, but on a named account worth six figures it is often the fastest route to a direct line.

Search operators worth typing

• site:linkedin.com/in "Firstname Lastname" "Company" confirms you have the right profile and the exact spelling the databases will key on.
• "Firstname Lastname" "Company" ("mobile" OR "direct" OR "cell") surfaces conference bios, press releases and speaker pages, which is where senior people publish a direct line without thinking of it as publishing.
• site:company.com ("Firstname" OR "Lastname") ("tel" OR "phone") catches team pages, investor-relations pages and PDF one-pagers still sitting in the index.
• filetype:pdf "Company" "Firstname Lastname" is the one most people forget. Annual reports, tender documents and event programmes leak direct numbers constantly.

Where the number usually turns out to be

In practice the free win comes from four places, roughly in order of yield: press releases with a media contact block, the company's own team or contact page, an event or webinar registration page, and email signatures quoted inside a public thread or a forum post.

Set expectations honestly. This works on roughly 10-30% of prospects, skews heavily towards founders, executives and anyone with a public-facing role, and takes 5 to 10 minutes each. That is a good trade on twenty accounts and an impossible one on two thousand.

Reverse LinkedIn phone number search: from a number back to a profile

The other direction comes up constantly and is far less well served: you have a number, an inbound call or a line on an old list, and you want to know who it belongs to and whether they are worth calling back.

Three things actually work, and one thing does not.

• Search the number as a string. Put it in quotes in Google, with and without the country code, with and without spaces. Numbers published on a team page or in a press release are indexed as text and come straight back.
• Resolve the identity first, then the profile. If the number is attached to a record you already hold, take the name and company and find the LinkedIn profile from those. This is the reliable path, and it is why a clean CRM beats a clever lookup.
• Check the company switchboard range. Direct dials are usually allocated in blocks. A number one or two digits away from a known company line tells you the employer even when it does not tell you the person, which is often enough to decide whether to call back.

What does not work is asking LinkedIn to do it. The platform has no public reverse phone lookup, and the setting described earlier only matches numbers already in a contact list you upload from your own phone. Consumer reverse-lookup directories are a different market with a different purpose: they index residential and personal listings for people trying to identify unknown callers, and they are a poor fit for identifying a B2B decision maker.

Cascade for max coverage

Best ROI workflow:

1. Bulk run primary tool (Derrick or Lusha) - covers 50-60%
2. For the nulls, run a 2nd cheaper tool - picks up another 10-15%
3. For high-priority remaining: manual research + LinkedIn DM

The order matters more than the tools. Run the cheapest broad pass first, keep the nulls in their own column, and only spend expensive credits and human minutes on rows that survived. Teams that invert this pay premium rates on the 55% any provider would have returned anyway. The same logic drives the wider B2B phone workflow, where the phone is one field among several rather than the only one you chase.

Running a LinkedIn phone number search at scale: Sheets, API and MCP

One profile is a browser tab. Two thousand profiles is a pipeline, and the right surface depends on where your list already lives.

A list you already hold: Google Sheets

Paste the LinkedIn URLs in a column, open the Derrick sidebar and point Phone Finder at it. Results land in the adjacent column, so there is no export and re-import step and no CSV round trip. Phone Finder is a paid feature at 150 credits per phone found, billed per result found rather than per row attempted, which is roughly €0.30 a match on the Standard plan.

A question asked inside an AI client: MCP

Derrick ships an MCP server, so Claude, ChatGPT or any MCP client can run the lookup as part of a conversation. This is the right door when the phone number is one step in a larger question ("who runs revenue at these fifteen accounts, and how do I reach them") rather than a column to fill.

An automated workflow or a CRM: the REST API

When enrichment has to fire on a trigger, a new lead in the CRM or a form submission, call the REST API directly and write the result back where your reps already work. No spreadsheet in the loop and no human waiting on a batch.

Working online without a spreadsheet: the web app

A Derrick web app is arriving shortly for teams that would rather run lists in a browser than in a tableur. Same data, same credit model, no Sheets required.

Pick the door by the use case, not by habit. A list to enrich goes to Sheets, a question asked in a chat goes to MCP, a triggered workflow goes to the API.

The lower-risk path is to stop scraping the profile for the number at all and resolve it from the identity instead. That is what the Phone Finder feature does from Google Sheets, without a browser session on your account.

Avoiding ban risk

If you scrape via extension or DM at scale, you risk LinkedIn restrictions. Mitigations:

• Stay under 50 manual actions/day on your account
• Use cookie-based extensions sparingly
• Prefer API-based lookups: the request runs on the vendor's infrastructure, so your LinkedIn account is never in the loop. Derrick exposes its Phone Finder through a REST API and an MCP server
• Don't connect tools that automate beyond 100 LinkedIn requests/day

The asymmetry is what people underestimate. A restricted account costs you the identity graph you built over years, and it is the input to every workflow above. The credits you save by scraping are the cheapest part of the stack; the account is the expensive part. Once the numbers are in hand, the call script decides what they are worth.

Key takeaways

• From a LinkedIn URL to a phone number: 5 workflows ranging from 10% (manual) to 70% (premium API).
• LinkedIn itself exposes a number on roughly 5% of 1st-degree profiles and 0.5% beyond, so the platform is an identity source, not a phone directory.
• Cascade 2 tools is the best ROI - primary tool covers 50-60%, fallback gets 10-15% more.
• Derrick has the lowest cost per match on this list, around €0.30 on the Standard plan, at a 50-60% US hit rate.
• Cognism and Lusha reach 55-70% but cost $1-1.50 per match, so the extra coverage is paid 3 to 5 times over on every number.
• The reverse direction has no native LinkedIn answer: resolve the identity from your own records, or search the number as an indexed string.
• For high-value targets: combine tool match + LinkedIn DM ask - accuracy near 100% on the ones who answer.