Extend phone and email coverage for European outbound

Give a global outbound team usable mobiles and work emails for EMEA and French/EU decision makers where US-centric sources run thin.

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_role_search/, POST /person_contacts_lookup/phone_numbers/ · People search API reference

What it costs: 15 credits per mobile found · 5 credits per email 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

3 inputs → Mobile numbers + Work emails + Person enrichment + People search → 4 fields sample data

01 · Inputs

target countries

linkedin.com/in/lee-sampler

Title

VP Revenue Operations

Company

Example Inc.

02 · Forager

Mobile numbers + Work emails + Person enrichment + People search POST /person_role_search/

Match found

03 · Outputs

Lee SamplerVP Revenue Operations · Example Inc.

work email: lee@example.com
phone number: +1 (312) 555-0107
person location: Chicago, IL
role title: VP Revenue Operations
name: Lee Sampler
company: Example Inc.

4 fields in the responseexample data

Steps

Build EMEA persona lists with POST /person_role_search/ (person_locations, role_title)
Get work_email via /person_contacts_lookup/work_emails/ and drop unverified addresses
Add direct mobiles from POST /person_contacts_lookup/phone_numbers/ for phone-first markets
Apply the team's regional consent and do-not-call rules before sequencing
Track bounce and connect rate by country

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. Build EMEA persona lists with POST /person_role_search/
# (person_locations, role_title)
r1 = requests.post(f"{BASE}/person_role_search/", headers=HEADERS, json=body)

# 2. Get work_email via /person_contacts_lookup/work_emails/ and drop
# unverified addresses

# 3. Add direct mobiles from POST /person_contacts_lookup/phone_numbers/ for
# phone-first markets
r2 = requests.post(f"{BASE}/person_contacts_lookup/phone_numbers/", headers=HEADERS, json=body)

# 4. Apply the team's regional consent and do-not-call rules before
# sequencing

# 5. Track bounce and connect rate by country

# 1. POST /person_role_search/
curl -X POST \
  https://api-v2.forager.ai/api/{account_id}/datastorage/person_role_search/ \
  -H "X-API-KEY: $FORAGER_KEY" \
  -H "Content-Type: application/json" \
  -d @request.json

# 2. 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: People search 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
target countries	`work_email`
persona titles	`phone_number`
account list	`person location`
	`role_title`

Questions about this recipe

Which B2B data sources have good phone coverage in Europe?

This recipe uses Forager Mobile numbers, Work emails, Person enrichment and People search. Mobile numbers: Direct mobile numbers for a person, from a LinkedIn URL or a Forager person ID, validated before they reach you. Give a global outbound team usable mobiles and work emails for EMEA and French/EU decision makers where US-centric sources run thin.

What does it cost to extend phone and email coverage for European outbound?

Mobile numbers: 15 credits per mobile number found, and a mobile number lookup that finds nothing costs 0 credits. Work emails: 5 credits per work email found, and a work email lookup that finds nothing costs 0 credits. Person enrichment: 1 credit per request, charged whether or not data comes back. People search: people search 1 credit per request and people search: role details 1 credit per request, charged whether or not data comes back. Growth's 8,250 monthly credits cover 550 mobiles, 1,650 emails 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 account list, persona titles and target countries. You get back person location, phone_number, role_title and work_email, as JSON. You also need a Forager API key, which comes with a free account.

How do I lower bounce rates on EMEA outbound lists?

Build EMEA persona lists with POST /person_role_search/ (person_locations, role_title). Track bounce and connect rate by country.

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 outbound team expands into EMEA or France and sees high bounces and missing phones on European lists. European outbound runs with lower bounce rates and fewer hours spent hunting numbers.

Which Forager products does this recipe use?

Mobile numbers, work emails, person enrichment and people search. Mobile numbers: direct mobile numbers for a person, from a LinkedIn URL or a Forager person ID, validated before they reach you. Work emails: verified work email addresses for a person at their current employer.

How accurate is Forager data?

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.

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: build EMEA persona lists with POST /person_role_search/ (person_locations, role_title), get work_email via /person_contacts_lookup/work_emails/ and drop unverified addresses, add direct mobiles from POST /person_contacts_lookup/phone_numbers/ for phone-first markets, apply the team's regional consent and do-not-call rules before sequencing and track bounce and connect rate by country.

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.

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.

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.
Roger
- AI SDRs
AI outbound sales rep.
HubSpot
- CRM add-ons
Selected use case: enriching contact and company records with people, company and job-posting data.
Airscale
- Waterfall enrichment
Selected use case: a Forager step in its mobile number waterfall.
Jeeva AI
- AI SDRs
Agentic platform of AI digital workers for sales teams.

Extend phone and email coverage for European outbound

How the data flows

Steps

Inputs and outputs

Questions about this recipe

Which B2B data sources have good phone coverage in Europe?

What does it cost to extend phone and email coverage for European outbound?

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

How do I lower bounce rates on EMEA outbound lists?

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 accurate is Forager data?

Which tools can run this workflow?

How many steps is this workflow?

Is there a contract or minimum commitment?

Can we show Forager data inside our product?

More recipes for AI SDRs

Power an AI SDR's email and phone waterfall from a chat prompt

Source a role-tagged buying committee for every target account

Qualify PLG sign-ups and route enterprise accounts to sales

Enrich leads before an AI agent writes personalized campaign copy

Give an AI SDR a verified mobile before it dials

Build an AI SDR's daily call list from hiring signals

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