Who evaluates mobile numbers at spreadsheet/agentic GTM workflow builders, and what they are judged on
Product manager who owns the enrichment feature: judged on what users see when they open a record
Engineering lead integrating the API: judged on response time and errors they can route on
Partnerships or data lead managing vendors: judged on cost per valid result
A selection of GTM workflow builders using Forager for mobile numbers · plus other sales-tech platformsA selection of teams using Forager
Nooks
Power & parallel dialers
Selected use case: mobile numbers inside their dialer.
Amplemarket
AI SDRs
Selected use case: mobile numbers inside its contact waterfall.
Clay
GTM workflow builders
Selected use case: Forager mobile numbers, emails and people data inside Clay tables.
Airscale
Waterfall enrichment
Selected use case: a Forager step in its mobile number waterfall.
Bitscale
GTM workflow builders
Selected use case: Forager in its contact waterfall for mobile numbers.
Orbital
Lead databases
Selected use case: contact lookups in its enrichment waterfall, for teams selling to local businesses.
BetterContact
Waterfall enrichment
Selected use case: a Forager step in its waterfall for mobile numbers.
Freckle
GTM workflow builders
Selected use case: Forager as a selectable mobile number provider in its waterfalls.
“Forager's great for accuracy, the numbers we get from them are consistently the highest grade for accuracy and confidence. They've earned our trust when connect rates matter most.”
OrbitalAaron JosephHead of BizOps
800M+people
65M+companies
How to test it
Test mobile numbers on your own sample
Pull a sample. Take profiles your users looked up last week.
Run it. Use a self-serve key, or book a demo and send us the list.
Measure what your users feel. Connect rate for mobiles, bounces for emails, and whether the right person answers.
How do GTM workflow builders use Forager mobile numbers?
⌄
Give GTM engineers a mobile, email and person provider they can drop into any table, workflow or waterfall step, billed in platform credits. Direct mobile numbers for a person, from a LinkedIn URL or a Forager person ID, validated before they reach you. This page walks through 3 workflows with the exact steps.
What do mobile numbers cost for GTM workflow builders?
⌄
Mobile numbers: 15 credits per mobile number found, and a mobile number lookup that finds nothing costs 0 credits. That is $0.20 per mobile number on Starter month to month and $0.15 on Pro with yearly billing. Self-serve plans are Starter, Growth, Pro and Scale. See plans and prices
Why do GTM workflow builders add mobile numbers?
⌄
Give your workflow users a contact step that connects. Products like yours are judged on connect rate and cost per valid result, which is why the cost that counts is per result that reaches the right person. Run your own sample to see what mobile numbers returns for your users before you build on it.
How do I add mobile number provider to GTM workflow builder?
⌄
Expose person_detail_lookup, work_emails, personal_emails, phone_numbers and organization_search as native actions with field mapping. Let users chain the actions as waterfall steps after or before other providers.
What do I send, and what comes back?
⌄
You send LinkedIn URL, LinkedIn identifier and LinkedIn identifiers. You get back phone_number, role_title, work_email and organization, from POST /person_contacts_lookup/phone_numbers/, as JSON.
Can we show Forager data inside our product?
⌄
Yes, under platform terms. Self-serve plans cover internal use by your own team. Showing Forager contacts to your users, or passing records on, is licensed separately: talk to sales about volume and which fields your users need to see.
Am I charged when no mobile number is found?
⌄
No. A mobile number lookup that finds nothing costs 0 credits, so you pay for mobile numbers we find. Search, enrichment and reverse lookups are the exception: they are charged per request.
Is there a free way to try Forager?
⌄
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.
How can an insurtech find and contact independent insurance agency owners?
⌄
Find agencies with POST /organization_search/ (industries = insurance, employees_end small, locations). Identify principals/owners and agency managers with POST /person_role_search/.
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 is a mobile number lookup API different from a contact database?
⌄
A contact database sells access to a list, often by seat or by export. A lookup API answers one person at a time inside your product or workflow: you send the LinkedIn URL or email you already hold and get back a mobile number in one JSON response. With Forager a mobile number lookup that finds nothing costs 0 credits, so you pay for numbers, not for searches.
Does Forager integrate with the tools we already use?
⌄
Native in Clay and Zapier, partner-built in Deepline and Cargo and called through the API from Make, n8n and your own code. Everything else connects through the REST API with one API key.
Written answers are not available right now. The matching pages above still help, or book a demo and ask the team.
