Skip to main content

Choose which enrichment providers run first with a custom waterfall

Decide the order in which lemlist tries email and phone data providers, including your own connected accounts like Lusha or Apollo, and turn off the ones you don't need.

By default, lemlist tries the providers you connected with your own account first, then shuffles its built-in providers at every enrichment. A custom waterfall lets your team set the order yourself for email and phone enrichment: choose which providers run, put the one that works best for your market first, and turn off the ones that don't deliver results for your use case.


Limitations

  • Your team can have one custom waterfall for email and one for phone. You cannot create more than one waterfall per type.

  • You cannot create different waterfalls by country or region. Geographic conditions are not supported.

  • A custom waterfall applies to all enrichments for your team. You cannot set a different provider order per campaign or per user.


How enrichment order works

Without a custom waterfall

Enrichment uses the Default email waterfall and Default phone waterfall. In Data management → Enrichment, both show All providers and Shuffled.

  • Any provider you connect externally is always tried first.

  • Built-in providers are shuffled automatically at every enrichment.

[SCREENSHOT: Screenshot_2026-09-30_at_09_11_33.png | alt: Edit waterfall window for the Default email waterfall, with built-in providers such as Prospeo, Dropcontact and Findymail all marked Shuffled]

In the Default phone waterfall, built-in providers are grouped in two tiers:

  • Tier 1: Premium, tried first among this group, in random order.

  • Tier 2: Standard, tried next if Tier 1 finds nothing, in random order.

[SCREENSHOT: Screenshot_2026-09-30_at_09_11_45.png | alt: Edit waterfall window for the Default phone waterfall, with providers grouped into Tier 1 Premium and Tier 2 Standard, all marked Shuffled]

With a custom waterfall

  • lemlist runs the enabled providers in the order you set, for all enrichments on your team. It replaces the default order.

  • Providers you connected with your own account can be placed anywhere in the order, not only first.

  • Email and phone are independent. You can create a waterfall for email, for phone, or for both. A type without a custom waterfall keeps its default waterfall.


Core lesson

Phase 1: Open your enrichment waterfalls

  1. Go to Settings → Data management → Enrichment.
    In Settings, under Team settings, click Data management, then open the Enrichment tab. This is where your team's email and phone waterfalls are listed.

    ✅ Verify: you see the Default email waterfall and Default phone waterfall cards, and the Custom waterfall button in the top-right corner.

[SCREENSHOT: Screenshot_2026-09-30_at_09_09_19.png | alt: Enrichment tab in Data management settings showing the Default email waterfall and Default phone waterfall, both set to All providers and Shuffled]

Phase 2: Create a waterfall for email or phone

  1. Click Custom waterfall.

  2. Under Configure your waterfall, choose the type and name.
    In Waterfall type, select Email waterfall or Phone waterfall. Enter a name in Waterfall name. To control both types, create one waterfall for each.

Phase 3: Set the order and choose which providers run

  1. Under Waterfall order, drag and drop providers to set the order.
    The provider at the top runs first. Put the provider that performs best for your market at the top. The list includes lemlist's built-in providers and the providers you connected with your own account (bring your own provider, BYOP).

  2. Enable or disable individual providers.
    Disabled providers are skipped during enrichment.

  3. Click Save.

    ✅ Verify: your custom waterfall appears in the Enrichment tab, with your providers in the order you set and only the ones you want enabled.


Your own providers in the waterfall

  • Providers you connected with your own account (for example Lusha or Apollo) appear in the waterfall list alongside lemlist's built-in providers.

  • In a default waterfall, they are always tried first. In a custom waterfall, you can place them anywhere in the order.

  • If you connect a new provider after your custom waterfall already exists, it appears in the list disabled. Enable it and move it to the position you want.

  • If you disconnect a provider, it disappears from the waterfall.


Go back to the default order

Delete your custom waterfall. Your team goes back to the default waterfall for that type.


Manage waterfalls via API and MCP

Custom waterfalls are also available through the lemlist API and the lemlist MCP. See Find and use the lemlist API and lemlist MCP: full tools reference.


Practical example

Your team knows Dropcontact finds the most emails for your market, but in the Default email waterfall it is shuffled with the other built-in providers. You go to Settings → Data management → Enrichment, click Custom waterfall, and select Email waterfall. Under Waterfall order, you drag Dropcontact to the top, keep the providers that still find results for you below it, disable the ones that don't, and click Save. From then on, every email enrichment on your team tries Dropcontact first. Phone enrichment keeps the Default phone waterfall until you create a phone waterfall too.


Troubleshooting & pitfalls

Issue: A provider you just connected is never used

Root cause: You connected it after your custom waterfall was created, so it was added disabled.

  • Go to Settings → Data management → Enrichment and open your custom waterfall.

  • Enable the provider and drag it to the position you want.

  • Click Save.

Issue: A provider disappeared from your waterfall

Root cause: The provider was disconnected.

Issue: Phone (or email) enrichment still uses a random order

Root cause: Email and phone waterfalls are independent, and there is no custom waterfall for that type. The Default email waterfall or Default phone waterfall still shows Shuffled.

  • Go to Settings → Data management → Enrichment.

  • Click Custom waterfall and create one for the missing type.


If your case is different

Did this answer your question?