$5 free Limited time. Sign up to activate. Get your $5 →

Pair mobile numbers with best-time-to-call scheduling

Combine a direct mobile with timezone and role context so reps call each prospect when they are most likely to pick up.

  • Free API key
  • No credit card
  • Run your sample

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

  • Clay
  • Juicebox
  • Nooks
  • Amplemarket
  • Airscale
  • HubSpot
  • Bitscale
  • Klenty

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.

How the data flows

2 inputs → Mobile numbers + Person enrichment → 3 fields sample data
01 · Inputs
Your list
contacts.csv · 1,200 rows
LinkedIn URL
linkedin.com/in/lee-sampler
02 · Forager
Mobile numbers + Person enrichment POST /person_contacts_lookup/phone_numbers/
Match found
03 · Outputs
Lee SamplerVP Revenue Operations · Example Inc.
phone number
+1 (312) 555-0107
person location/timezone
Chicago, IL
name
Lee Sampler
title
VP Revenue Operations
work email
lee@example.com
company
Example Inc.
3 fields in the responseexample data

Steps

  1. Find mobiles with POST /person_contacts_lookup/phone_numbers/
  2. Pull person location and role_title from POST /person_detail_lookup/ to derive timezone and seniority
  3. Apply the platform's best-time model to each contact
  4. Build a time-slotted call plan and push it to the rep's dialer
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. Find mobiles with POST /person_contacts_lookup/phone_numbers/
r1 = requests.post(f"{BASE}/person_contacts_lookup/phone_numbers/", headers=HEADERS, json=body)

# 2. Pull person location and role_title from POST /person_detail_lookup/ to
# derive timezone and seniority
r2 = requests.post(f"{BASE}/person_detail_lookup/", headers=HEADERS, json=body)

# 3. Apply the platform's best-time model to each contact

# 4. Build a time-slotted call plan and push it to the rep's dialer
Generated from the recipe stepsRequest fields: API reference

Run it yourself: Mobile numbers API reference

  • Free API key
  • No credit card
  • Run your sample

Inputs and outputs

InputsOutputs
prospect listphone_number
LinkedIn identifiersperson location/timezone
recommended call window

Questions about this recipe

What is the best time to cold call a B2B decision maker?

This recipe uses Forager 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. Combine a direct mobile with timezone and role context so reps call each prospect when they are most likely to pick up.

What does it cost to pair mobile numbers with best-time-to-call scheduling?

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 LinkedIn identifiers and prospect list. You get back person location/timezone, phone_number and recommended call window, as JSON. You also need a Forager API key, which comes with a free account.

Which tools tell reps when to call each prospect?

Use it when a rep plans tomorrow's call block across several timezones. Reps get more connects from the same dial volume.

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?

When a rep plans tomorrow's call block across several timezones. Reps get more connects from the same dial volume.

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 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.

What is the best time to call B2B prospects tool?

This recipe uses Forager 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. Combine a direct mobile with timezone and role context so reps call each prospect when they are most likely to pick up.

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?

4 steps: find mobiles with POST /person_contacts_lookup/phone_numbers/, pull person location and role_title from POST /person_detail_lookup/ to derive timezone and seniority, apply the platform's best-time model to each contact and build a time-slotted call plan and push it to the rep's dialer.

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.

  • Airscale
    • Waterfall enrichment

    Selected use case: a Forager step in its mobile number waterfall.

  • HubSpot
    • CRM add-ons

    Selected use case: enriching contact and company records with people, company and job-posting data.

  • Bitscale
    • GTM workflow builders

    Selected use case: Forager in its contact waterfall for mobile numbers.

  • Klenty
    • Power & parallel dialers

    Sales engagement and AI dialer platform.

Start building

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

Send us a list. We run it, show you what we find, then talk volume and terms.

  • $5 free credits
  • No credit card
  • Run your sample
Platforms and teams that build on Forager
  • Clay
  • Juicebox
  • Nooks
  • Andela
  • HubSpot
  • SeekOut