Score mobile numbers by connect likelihood before dialing
Give a phone-intent or scoring layer a supply of mobiles it can rank, so reps dial the numbers most likely to be answered first.
- Free API key
- No credit card
- Run your sample
A selection of teams that run this job on Forager · plus other sales-tech platforms
Uses POST /person_contacts_lookup/phone_numbers/, POST /person_detail_lookup/ · Mobile numbers API reference
What it costs: 15 credits per mobile found. A mobile or email lookup that returns nothing costs 0 credits. Enrichment and search are charged per request: credit pricing.
- Mobile numbers
- Person enrichment
- API
- Embedded in a platform
- Sales tech
How the data flows
POST /person_contacts_lookup/phone_numbers/ - phone number
- +1 (416) 555-0186
- connect score
- true
- role title
- VP Revenue Operations
- name
- Kim Exemplar
- work email
- kim@example.com
- company
- Example Inc.
Steps
- Retrieve candidate numbers per contact from
POST /person_contacts_lookup/phone_numbers/(Gold and Silver) - Attach person context from
POST /person_detail_lookup/(role_title,role_is_current, location) as scoring features - Score each number using the platform's own model (line type, recency, call outcomes)
- Order the dial list by score and suppress low-score numbers
- Log connects per number to retrain scoring
import json, os, requests BASE = "https://api-v2.forager.ai/api/{account_id}/datastorage" HEADERS = {"X-API-KEY": os.environ["FORAGER_KEY"]} body = json.load(open("request.json")) # request fields: see the API reference # 1. Retrieve candidate numbers per contact from POST # /person_contacts_lookup/phone_numbers/ (Gold and Silver) r1 = requests.post(f"{BASE}/person_contacts_lookup/phone_numbers/", headers=HEADERS, json=body) # 2. Attach person context from POST /person_detail_lookup/ (role_title, # role_is_current, location) as scoring features r2 = requests.post(f"{BASE}/person_detail_lookup/", headers=HEADERS, json=body) # 3. Score each number using the platform's own model (line type, recency, # call outcomes) # 4. Order the dial list by score and suppress low-score numbers # 5. Log connects per number to retrain scoring
# 1. POST /person_contacts_lookup/phone_numbers/ curl -X POST \ https://api-v2.forager.ai/api/{account_id}/datastorage/person_contacts_lookup/phone_numbers/ \ -H "X-API-KEY: $FORAGER_KEY" \ -H "Content-Type: application/json" \ -d @request.json # 2. POST /person_detail_lookup/ curl -X POST \ https://api-v2.forager.ai/api/{account_id}/datastorage/person_detail_lookup/ \ -H "X-API-KEY: $FORAGER_KEY" \ -H "Content-Type: application/json" \ -d @request.json
Run it yourself: Mobile numbers API reference
- Free API key
- No credit card
- Run your sample
Inputs and outputs
| Inputs | Outputs |
|---|---|
| call list | phone_number |
| LinkedIn identifiers | connect score |
| historic call outcomes | dial order |
role_title |
Questions about this recipe
How can I tell which phone numbers in my list are most likely to be answered?
Retrieve candidate numbers per contact from POST /person_contacts_lookup/phone_numbers/ (Gold and Silver). Order the dial list by score and suppress low-score numbers.
What does it cost to score mobile numbers by connect likelihood before dialing?
Mobile numbers: 15 credits per mobile number found, and a mobile number lookup that finds nothing costs 0 credits. Person enrichment: 1 credit per request, charged whether or not data comes back. Growth's 8,250 monthly credits cover 550 mobiles or 8,250 person enrichments, or a mix. Self-serve plans are Starter, Growth, Pro and Scale. See plans and prices
What do I need to run this recipe, and what comes back?
You send call list, historic call outcomes and LinkedIn identifiers. You get back connect score, dial order, phone_number and role_title, as JSON. You also need a Forager API key, which comes with a free account.
What is a good cold-call connect rate and how do teams improve it?
Give a phone-intent or scoring layer a supply of mobiles it can rank, so reps dial the numbers most likely to be answered first. Reps reach far more live conversations per hundred dials.
Can I test mobile numbers for free?
Yes. Create a free account at app.forager.ai: it comes with $5 in free credits and an API key, and there is no credit card to sign up. Run it on records you already know, or book a demo and send us a list: we run it and show you what we find.
When should I run this workflow?
When a rep or agency loads a cold-call list and wants connect rate above the baseline before burning dials. Reps reach far more live conversations per hundred dials.
Which Forager products does this recipe use?
Mobile numbers and person enrichment. Mobile numbers: direct mobile numbers for a person, from a LinkedIn URL or a Forager person ID, validated before they reach you. Person enrichment: a full professional profile for a person from a LinkedIn URL, email or phone: experience, education, skills and contact channels.
How do I know the data is right?
Forager ranked #1 of 10 in Clay's 2026 test of mobile data providers, by quality score: Clay's measure of how likely a dialled number reaches the right person. The test that counts is your own: send a list of profiles you care about. We run it and show you what we find, number by number, so you can measure hit rate and connect rate yourself.
How to rank phone numbers before cold calling?
Retrieve candidate numbers per contact from POST /person_contacts_lookup/phone_numbers/ (Gold and Silver). Order the dial list by score and suppress low-score numbers.
Which tools can run this workflow?
Native in Clay and Zapier, partner-built in Deepline and Cargo and called through the API from Make, n8n and your own code. Or call the endpoints in the steps above from your own code with one API key.
How many steps is this workflow?
5 steps: retrieve candidate numbers per contact from POST /person_contacts_lookup/phone_numbers/ (Gold and Silver), attach person context from POST /person_detail_lookup/ (role_title, role_is_current, location) as scoring features, score each number using the platform's own model (line type, recency, call outcomes), order the dial list by score and suppress low-score numbers and log connects per number to retrain scoring.
Do I need a subscription?
Not to test: a free account comes with $5 in credits. To keep using Forager, choose a monthly or yearly plan. Monthly plans cancel anytime and unused credits roll over; yearly plans grant all credits upfront and cost 10% less. Larger volumes are agreed with our team.
Written answers are not available right now. The matching pages above still help, or book a demo and ask the team.
- $5 free credits
- No credit card
- Run your sample
A selection of teams that run this job on Forager · plus other sales-tech platformsA selection of teams using Forager
-
Clay - GTM workflow builders
Selected use case: Forager mobile numbers, emails and people data inside Clay tables.
-
Juicebox - AI candidate sourcing
Selected use case: Forager data behind its PeopleGPT search and sourcing agents.
-
Nooks - Power & parallel dialers
Selected use case: mobile numbers inside their dialer.
-
Amplemarket - AI SDRs
Selected use case: mobile numbers inside its contact waterfall.
-
HubSpot - CRM add-ons
Selected use case: enriching contact and company records with people, company and job-posting data.
-
BetterContact - Waterfall enrichment
Selected use case: a Forager step in its waterfall for mobile numbers.
-
Klenty - Power & parallel dialers
Sales engagement and AI dialer platform.
-
Orbital - Lead databases
Selected use case: contact lookups in its enrichment waterfall, for teams selling to local businesses.
More recipes for power & parallel dialers
-
Feed a parallel dialer with direct mobile numbers
-
Enrich mobiles just in time at dial time instead of bulk refreshes
-
Pair mobile numbers with best-time-to-call scheduling
-
Add a mobile-number slot to a multi-provider enrichment waterfall
-
Detect CRM contacts who changed jobs and alert on moved champions
-
Back a sales-intelligence database with an additional mobile source
