Find Work Phone
/find-work-phoneTurn a LinkedIn profile URL into that person's work or office phone number, the company line rather than their personal mobile.
Overview
Find Work Phone takes a LinkedIn profile URL and returns that person's work or office phone number, using the SyncGTM MCP find_work_phone tool. It gives you the company line you reach them on at their desk, not the personal mobile that find_mobile_number returns. Each lookup costs 12 credits whether or not a number comes back, so the skill qualifies, deduplicates and caps the list before it spends anything.
What it does
- 1
Takes one required input: linkedin_url, the full LinkedIn profile URL. No URL, no lookup.
- 2
Accepts three optional parameters that cost nothing extra — first_name, last_name and organization_name — which raise the hit rate on sparse profiles and disambiguate common names.
- 3
Returns three fields: work_phone in international format (the documented example is +14155550100), status, and the linkedin_url you passed. One call resolves one person.
- 4
Does not return a personal mobile, a work email or a company record. Use find_mobile_number, find_work_email or enrich_organization for those.
- 5
Has no batch parameter and no limit parameter. A list of 10 people is 10 separate calls.
- 6
Costs 12 credits per lookup, charged on empty results too, which makes it one of the two most expensive tools in the catalogue.
How to use it
- 1
Download the skill file — it saves as find-work-phone.zip.
- 2
In Claude, open Settings → Capabilities → Skills and upload the .zip (or unzip the find-work-phone/ folder into .claude/skills/ for Claude Code).
- 3
Connect the SyncGTM MCP server with browser sign-in, no API key needed, then run check_credits to confirm your balance covers 12 credits per name on the list.
- 4
Run /find-work-phone and paste your rows with one LinkedIn URL each, plus first name, last name and company wherever you have them.
- 5
Tune the one setting that matters: the batch cap. The tool has no limit parameter, so you enforce it in the prompt — say "stop after 8 lookups and report credits used" so a long export cannot drain the balance.
Use cases
Cold call blitz
Give SDRs an office number for every account on the day's dial list. Reps call the company line and ask for the contact by name when no direct number is published.
Reviving stalled deals
Pull the desk line for a champion who has gone quiet on email. A call to the office often lands where a fifth follow-up does not.
Mobile-free outreach
Some regions and internal policies restrict calling personal mobiles. Pull the business line so outbound stays on a company-owned number.
Enterprise multithreading
Add office numbers for two or three extra stakeholders on a stalled enterprise opportunity. AEs can then call around the blocker instead of waiting on one contact.
GTM workflow examples
Monday dial list from a 12-name CRM export
- 1Run `check_credits` (free) to confirm the balance and set a hard cap for the run.
- 2Run `check_job_change` (2 credits each, takes `profile_url`) on all 12 contacts — 24 credits spent, 3 have moved companies, leaving 9 live contacts.
- 3Run `scrape_phones_from_website` (0.5 credits each) on the 9 company domains — 4.5 credits spent, and 4 accounts publish a usable switchboard number.
- 4Run `find_work_phone` (12 credits each) on the 5 profiles still missing a number, passing first_name, last_name and organization_name on every call — 60 credits, charged on empties as well as hits.
- 5Run `check_credits` again and log the closing balance against the opening one.
Outcome: A 9-row call sheet built for 88.5 credits — 4 rows carrying the switchboard number the site already published, 5 rows sent to the paid lookup — against the 144 credits `find_work_phone` on all 12 names blind would have cost.
Multithread a stalled enterprise opportunity
- 1Run `find_people_within_company` (1.5 credits, flat per call) on the account domain with `max_profiles: 25` and a `job_title` array like ["VP Sales", "CRO", "Head of Revenue Operations"] — the cost does not rise with the cap, so ask for the wider list in one call.
- 2Shortlist 4 VP-and-above stakeholders, then run `enrich_person` (1 credit each, 4 credits) to fill in first name, last name and company for each.
- 3Run `find_work_phone` (12 credits each, 48 credits) on those 4 profiles, passing all four parameters so common names resolve correctly.
- 4Run `find_work_email` (1 credit each, 4 credits) on the same 4 profiles so any empty phone row still has a written channel — chain `verify_email` (0.3 credits) separately if deliverability matters.
Outcome: Four named stakeholders at the stalled account for 57.5 credits, each row carrying an office line, a work email address, or both.
Call the new exec inside their first 90 days
- 1Run `newly_hired_executives` (0.5 credits per profile) once per account across 10 target accounts with `max_results: 5` and the default `seniority_levels` of ["Director", "Vice President", "CXO", "Owner / Partner"] — up to 50 profiles, 25 credits, each with start date and previous role.
- 2Run `enrich_organization` (2 credits each, 20 credits) on the 10 account domains to confirm headcount and industry and to capture the exact company name for organization_name.
- 3Run `scrape_phones_from_website` (0.5 credits each, 5 credits) on the same 10 domains — the accounts that publish a main line are resolved at that price.
- 4Run `find_work_phone` (12 credits each) only for the new hires at the 6 accounts whose site published nothing, passing first_name, last_name and organization_name — 72 credits.
Outcome: A first-90-days call list across 10 accounts for 122 credits, with the 12-credit lookup spent on only the 6 accounts the 0.5-credit scrape could not cover.
Prompts
Paste any of these into Claude once the skill is installed and the SyncGTM MCP is connected.
Find the work phone for https://www.linkedin.com/in/janedoe. Pass first name Jane, last name Doe and organization name Acme Corp to improve the match, and tell me the credits it cost.Check my SyncGTM credits, then find work phones for the 8 LinkedIn URLs I paste below. Stop at 8 lookups, do not retry empty results, and report total credits used.Run scrape_phones_from_website on acme.com first. Only if no number comes back, run find_work_phone on https://www.linkedin.com/in/janedoe. Cap the run at 1 lookup.Run check_job_change on these 10 LinkedIn URLs first. Skip anyone who has changed jobs, then find work phones for the rest — maximum 6 lookups, and report credits spent.I need the office line, not the mobile, for https://www.linkedin.com/in/janedoe at Acme Corp. Use find_work_phone, show the status field, and stop after this one lookup.Best practices
Say "work phone" or "office line" in the prompt. Without it your client may reach for find_mobile_number, which costs the same 12 credits and returns a different number.
Try scrape_phones_from_website first at 0.5 credits. It often returns the same switchboard number for a fraction of the cost, though it gives you a front desk rather than the person's own desk.
Run check_credits before every batch. At 12 credits a call, 20 people is 240 credits, and this is one of the two most expensive tools on the server.
Never retry an empty result. An empty means the number could not be found — not that the company has no line — and the retry bills another 12 credits against the same providers.
Pass first_name, last_name and organization_name on every call. They are free, they raise the hit rate on sparse profiles, and they stop a common name matching the wrong person.
Do not chain validate_whatsapp onto the output. It takes a mobile number, so an office line is the wrong input.