Every enrich call
per work email and per phone found by an additional source, charged only on a match
1 in 2
missing work emails and phone numbers filled, across all waterfall accounts, September 2026
0 credits
when a source finds nothing
How it runs
Pay on match
Admin Control
Reveal a missing phone or email in any table. The credit cost shows before you confirm, with the source marked on the result.
Runs automatically on eligible Enrich Contacts requests. Providers that return results in the background are collected through the enrich job endpoint.
Ask the assistant to enrich a list. The waterfall runs through the Lusha MCP server and results come back in the chat, including from providers that respond in the background.
n8n, Make, Clay, or something you built on the API. The setting is account level, so it applies without configuring each tool.
Eliminate the manual one-by-one lookup. Turn static, thin CSV lists into fully enriched prospecting files by processing hundreds of contacts in seconds via Lusha’s bulk API.
A filter tells you who could buy. A signal tells you who is changing right now. This Skill starts from the signal, finds the companies or people it fired on, dates each event, and returns the buyer with a direct dial.
A reusable Claude Skill that starts from what already worked. Give it 5 or more of your best customers, or 5 or more of your best buyers, and it returns the companies or people that match the same profile, keeps your existing accounts out of the results, and finds a verified contact at each new […]
Waterfall enrichment checks several data sources in sequence. If the first source has no match for a field, the next one is tried, until a confirmed value comes back or the sources run out. It raises coverage above any single provider without stitching vendors together yourself. Lusha’s version runs its own verified data first, then the providers you enabled, and charges only on a match.
Read the full guide to how waterfall enrichment works and what a miss should cost.
Lusha checks its own data first. If a work email or phone is still missing, it tries the additional providers you enabled, in Lusha’s order, and stops at the first confirmed match.
Lusha data costs 1 credit per work email and 5 per phone. A match from an additional provider costs 2 per work email and 8 per phone. A provider that returns nothing costs nothing.
Nothing, in Lusha’s waterfall. Credits are charged only when an additional source returns a confirmed email or phone. Some vendors charge per attempt, so check whether a provider bills on the query or the match.
It runs on Pro plans and above through Lusha Workspace, API, and the MCP server, and an admin turns it on. Check the pricing page for current plan coverage.
A vetted set of providers, each under Lusha’s Supplementary Terms. Admins see the full list under Account Settings → Waterfall and can turn each one on or off. Lusha sets the query order.
Work email and phone. It does not fill firmographics, job titles or other profile fields.
No. It completes records Lusha already holds. Use prospecting search to find contacts you do not have.
Yes, when paired with partial profiles. Pass includePartialProfiles on a Search API request to surface contacts held with no contact details, then waterfall fills the missing email or phone.
No. It returns values on the enrich response and your integration decides what to write.
Yes. A request through the Lusha MCP server runs the same waterfall, on the same account setting and credit balance, as a direct API call.
A waterfall of waterfalls (FullEnrich is the common example) has no database of its own and queries 20 or more third parties per contact. Lusha’s waterfall starts from its own 515M+ verified contacts and uses additional providers only to fill a missing field, so the first and cheapest answer comes from data Lusha can stand behind.
Lusha data first, the providers you enable second, credits only on a confirmed match.
