To set up a phone waterfall, start from LinkedIn profile URLs, enable the phone providers you want to test, and order them by credits per number found on a sample of your own list. Validate every number before it reaches a dialer, record which provider found it, and check do-not-call rules for the countries you call.
Phone data behaves differently from email. Numbers rarely appear on public pages, they change when people move jobs or carriers, and there's no silent way to confirm a number belongs to the person the way an email verifier checks a mailbox. That makes provider choice, ordering and validation more important than they are for email. This guide is the setup walkthrough; for the general theory of cascades see how waterfall enrichment works, and for a comparison of standalone phone tools see the best phone number enrichment tools.
What input does a phone waterfall need?
Databar's phone waterfall takes one input: a LinkedIn profile URL. Every provider in the chain looks the person up by that URL, which removes the ambiguity of matching on a name and company.
If your list doesn't have LinkedIn URLs yet, add them first. A reverse email lookup can return a LinkedIn URL from a work email, which is covered in reverse email lookup. Check that the URLs point at personal profiles (linkedin.com/in/...) rather than company pages, and remove duplicates so the same person isn't looked up twice.
Which providers are in Databar's phone waterfall?
These are the providers listed in the Databar catalog in September 2026, with the credits each charges when it returns a number. Prices and provider lists change, so confirm them in the setup sidebar before a large run.
Provider | Credits per number found | What the catalog says it returns |
|---|---|---|
8 | Phone numbers by LinkedIn URL (Databar's in-house enrichment) | |
10 | Mobile number from a LinkedIn profile | |
16 | Contact details from Upcell's database | |
Limadata | 16 | Mobile and direct-dial numbers |
21 | Mobile numbers linked to the profile | |
Pubrio | 21 | Phone numbers with verification status |
22 | Mobile and direct numbers | |
32 | Phone number by LinkedIn profile | |
Forager | 36 | Mobile number from a LinkedIn profile |
48 | Phone numbers by social link |
The spread is wide: the most expensive provider costs six times the cheapest per number. That spread is the whole reason ordering matters more for phones than for emails. Two catalog phone validators sit alongside the chain: Databar Labs phone verification (1.5 credits) and Trestle (2.5 credits).
How do you set up the phone waterfall in a table?
Load your list into a Databar table from a CSV or your CRM, with the LinkedIn URL in its own column.
Add the waterfall. Click Enrich, choose Add a new Enrichment, switch to the Waterfalls tab and pick the phone waterfall.
Configure providers. Expand Waterfall setup, click provider cards to switch them on or off, and drag them into order. Providers run top to bottom and the chain stops at the first number returned.
Map the input to your LinkedIn URL column.
Run a sample of 100 to 200 rows that look like the full list, then review before running everything.
Validate the results. Add a phone verification enrichment (Trestle or Databar Labs) on the phone column, and set a run condition so it only runs on rows where a number was found.
The waterfall enrichments page shows the feature, and the setup steps are in the Databar docs.
What order should phone providers go in?
Order by expected credits per number found: the provider's price divided by the share of your rows it resolves. Hit rates for phone data vary a lot by country, seniority and company size, so the only numbers worth using are ones measured on your own list.
An illustration with made-up hit rates: a 10-credit provider that finds numbers for 25% of your sample costs 40 credits per number found. A 32-credit provider that finds 50% costs 64 credits per number. The cheaper one goes first, and the expensive one only runs on the rows it missed. Now flip the numbers: if the 10-credit provider found only 10%, it would cost 100 credits per number found, and it should move below the 32-credit one or be switched off.
A routine that works:
Pick a 200-row sample from the segment you're about to call.
Run your candidate providers as single enrichments on that sample, so each one's standalone hit rate is visible.
Validate every number returned, and count only valid, active numbers as hits.
Divide each provider's credits by its valid-hit rate and sort ascending. That's your starting order.
Switch off providers that add very few numbers the earlier ones didn't already find.
Re-test when you move to a new country or segment, and at least every quarter.
Counting only validated numbers matters because the cheapest number is useless if it's disconnected. A provider with a slightly higher price and a much better valid rate usually wins.
How do you validate phone numbers before calling?
Validation doesn't prove a number belongs to your prospect, but it removes numbers that can't connect and tells you what kind of line you're dialing. Trestle's enrichment on Databar returns whether the number is valid, an activity score for spotting disconnected numbers, the line type (mobile, landline or VoIP), the carrier, whether it's prepaid, and the country. Databar Labs verification checks validity, country and area, and the carrier.
Use the output to route numbers, not just to filter them:
Invalid or inactive: drop from the call list and, if the contact matters, try the next provider in the chain on just those rows.
Mobile: check your local rules on calling mobiles before these go into a dialer.
Landline or VoIP: often an office line; worth calling, but expect a switchboard sometimes.
More on the Trestle integration in stop dialing dead numbers.
What does a phone waterfall cost?
Billing follows the same rules as every Databar waterfall. Only the provider that returns a number is charged. Providers that look up the row and find nothing cost nothing. The chain stops at the first number returned, so later providers never run for that row. Validation is a separate enrichment, charged per number you validate.
One consequence: a number that a provider returns and that later fails validation has still been paid for. If you then want to try the next provider on that row, filter the table to the invalid rows and run the remaining providers on just that selection.
To estimate a budget, multiply your sample's credits per valid number by the number of contacts you need to call. Databar's Build plan includes 5,000 credits for $99 a month and Scale includes 50,000 credits for $495 a month (pricing).
Should you find emails before phone numbers?
For most outbound teams, yes. In Databar's catalog the email waterfall providers charge 3 to 22 credits per result and the phone providers 8 to 48, so run the email waterfall on the full list and the phone waterfall only on the accounts your reps will actually call: top-tier accounts, people who opened or replied, or a segment where calling works. We cover the email side in how to set up an email waterfall.
A run condition makes this automatic: run the phone waterfall only when a tier column says "call" or when an engagement flag is set.
What compliance checks apply to enriched phone numbers?
Phone outreach is more regulated than email, and the rules depend on where the person is. This isn't legal advice, but the checks to build into the workflow are the same everywhere:
Do-not-call registries. Many countries run one, such as the US National Do Not Call Registry and the UK's Telephone Preference Service. Screen numbers against the registries that apply to your calling before they reach a dialer.
Mobile numbers. Rules for calling or texting mobiles, especially with autodialers or prerecorded messages, are stricter in several jurisdictions. Line type from validation helps you apply them.
EU and UK contacts. Have a documented lawful basis for processing, honor objections immediately, and keep the source provider on each record so you can answer a data subject request.
Keeping the provider name and validation result in the table gives you that audit trail by default.
Can you run the phone waterfall from the API or an AI agent?
Yes. The phone waterfall runs through the REST API (identifier phone_getter, input linkedin), the Python SDK, the CLI and the Databar MCP server, with the same provider selection and billing. That's useful for enriching a lead the moment it's routed to a rep, or for letting an agent pull a number only after it has qualified the account.
FAQ
Why start a phone waterfall from a LinkedIn URL?
It identifies one person exactly, so every provider in the chain is looking up the same individual. Name-and-company matching can return a different person with the same name, which is costly when every lookup is priced like a phone lookup.
How many providers should a phone waterfall have?
Test more providers than you would for email, because individual phone hit rates tend to be lower and vary more by region. Then keep only the ones whose credits per valid number stay below what a reachable contact is worth to you.
Do I pay when no provider finds a number?
No. Lookups that return nothing aren't charged. You pay for the provider that returns a number, plus any validation you run on it.
Can I tell whether a number is a mobile or a landline?
Run a validation step. Trestle returns the line type (mobile, landline or VoIP) along with an activity score and carrier.
Where can I compare phone data tools outside Databar?
Our phone number lookup tools guide compares standalone tools, including how to test a vendor's direct-dial quality before you buy.
Build a phone waterfall on your list
Databar puts ten phone providers, two phone validators and 160+ data providers in total behind one table, API and MCP server. Start free with a 14-day trial that includes 100 credits to test provider order on a sample, or book a founder demo and we'll set up the waterfall on your list with you.
Recent articles
See all
