Feed a parallel dialer with direct mobile numbers

Fill the number waterfall behind a power or parallel dialer so SDRs spend sessions talking to buyers, not hunting numbers.

Get a free API key + $5 Get a sample run

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/ · Mobile numbers API reference

What it costs: 15 credits per mobile found. A mobile or email lookup that returns nothing costs 0 credits.

Mobile numbers
API
Waterfall slot
Sales tech

How the data flows

2 inputs → Mobile numbers → 4 fields sample data

01 · Inputs

Your list

contacts.csv · 1,200 rows

LinkedIn URL

linkedin.com/in/jane-example

02 · Forager

Mobile numbers POST /person_contacts_lookup/phone_numbers/

Match found Pay per field · Empty result: 0 credits

03 · Outputs

Jane ExampleVP Revenue Operations · Example Inc.

phone number: +1 (415) 555-0142
provider attribution: forager
name: Jane Example
title: VP Revenue Operations
work email: jane@example.com
company: Example Inc.

3 fields in the responseexample data

Steps

Dialer collects contacts without a mobile from the queued session list
Call POST /person_contacts_lookup/phone_numbers/ per contact with linkedin_public_identifier; Gold first for quality, Silver for maximum reach
Write phone_number into the dialer contact with source = provider for audit
Rank contacts in the session so those with a found mobile are dialed first
Feed dispositions (connected, wrong number) back into provider order

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. Dialer collects contacts without a mobile from the queued session list

# 2. Call POST /person_contacts_lookup/phone_numbers/ per contact with
# linkedin_public_identifier; Gold first for quality, Silver for maximum
# reach
r1 = requests.post(f"{BASE}/person_contacts_lookup/phone_numbers/", headers=HEADERS, json=body)

# 3. Write phone_number into the dialer contact with source = provider for
# audit

# 4. Rank contacts in the session so those with a found mobile are dialed
# first

# 5. Feed dispositions (connected, wrong number) back into provider order

# 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

Generated from the recipe stepsRequest fields: API reference

Run it yourself: Mobile numbers API reference

Get a free API key + $5 Get a sample run

Free API key
No credit card
Run your sample

Inputs and outputs

Inputs	Outputs
dialer session contact list	`phone_number`
LinkedIn identifier per contact	`tier`
	`dial rank`
	`provider attribution`

Questions about this recipe

What data source do parallel dialers use to find prospects' mobile numbers?

You send dialer session contact list and LinkedIn identifier per contact. You get back phone_number, tier, dial rank and provider attribution. SDRs on the dialer reach more live conversations per hour and book more meetings per rep.

What does it cost to feed a parallel dialer with direct mobile numbers?

Mobile numbers: 15 credits per mobile number found, and a mobile number lookup that finds nothing costs 0 credits. Growth's 8,250 monthly credits cover 550 mobiles, 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 dialer session contact list and LinkedIn identifier per contact. You get back dial rank, phone_number, provider attribution and tier, as JSON. You also need a Forager API key, which comes with a free account.

How can a dialer platform raise its live connect rate?

Dialer collects contacts without a mobile from the queued session list. Write phone_number into the dialer contact with source = provider for audit.

Is there a free way to try Forager on this workflow?

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?

An SDR team loads a call list into the dialer and contacts are missing a direct mobile. SDRs on the dialer reach more live conversations per hour and book more meetings per rep.

Which Forager products does this recipe use?

Mobile numbers. Mobile numbers: direct mobile numbers for a person, from a LinkedIn URL or a Forager person ID, validated before they reach you.

How do you check data quality?

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 do parallel dialers find direct dials?

Dialer collects contacts without a mobile from the queued session list. Call POST /person_contacts_lookup/phone_numbers/ per contact with linkedin_public_identifier; Gold first for quality, Silver for maximum reach.

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: dialer collects contacts without a mobile from the queued session list, call POST /person_contacts_lookup/phone_numbers/ per contact with linkedin_public_identifier; Gold first for quality, Silver for maximum reach, write phone_number into the dialer contact with source = provider for audit, rank contacts in the session so those with a found mobile are dialed first and feed dispositions (connected, wrong number) back into provider order.

Is there a contract or minimum commitment?

No contract to start: 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.

A selection of teams that run this job on Forager · plus other sales-tech platforms

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.
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.
Cortex Intelligence
- ABM & intent
GTM intelligence platform for account research and outbound.

Feed a parallel dialer with direct mobile numbers

How the data flows

Steps

Inputs and outputs

Questions about this recipe

What data source do parallel dialers use to find prospects' mobile numbers?

What does it cost to feed a parallel dialer with direct mobile numbers?

What do I need to run this recipe, and what comes back?

How can a dialer platform raise its live connect rate?

Is there a free way to try Forager on this workflow?

When should I run this workflow?

Which Forager products does this recipe use?

How do you check data quality?

How do parallel dialers find direct dials?

Which tools can run this workflow?

How many steps is this workflow?

Is there a contract or minimum commitment?

More recipes for power & parallel dialers

Score mobile numbers by connect likelihood before dialing

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

Back a sales-intelligence database with an additional mobile source

Offer mobile and email enrichment as native actions in a GTM workflow builder

Put people, company and job data your users can act on inside your product