[ Enrichment ]

Run waterfall email enrichment

Use provider fallbacks to improve email coverage while keeping match status and review state visible per row.

Use this playbook

Overview

Use provider fallbacks to improve email coverage while keeping match status and review state visible per row. This workflow is useful when a single provider leaves too many rows unresolved or when you want to preserve the source behind each match for review. Cockpit keeps the waterfall output in the spreadsheet so the team can trust and audit the result.

Use provider fallbacks to improve email coverage while keeping match status and review state visible per row.

How it works

1

Import or select rows

Start with names, company domains, or LinkedIn URLs

2

Run an email enrichment waterfall

Waterfall Email Result

3

Review and filter results

Approved rows ready

4

Export or hand off rows

Clean dataset prepared

Step-by-step process

  1. 1

    Start with spreadsheet rows

    Start with names, company domains, or LinkedIn URLs. Keep the original input columns visible so the team can check where each result came from and whether the row has enough context to match.

  2. 2

    Run an email enrichment waterfall

    Choose the enrichment providers and fallback order, then run the waterfall on selected rows. Cockpit writes the waterfall result back into the sheet as reviewable columns instead of hiding the provider chain behind one opaque answer.

  3. 3

    Review the output

    Filter by status, confidence, missing values, fit, or approval state before moving the data downstream. Rows with uncertain matches are easier to isolate when the source provider is visible.

  4. 4

    Prepare the handoff

    Keep only the useful fields, then use CSV export or another destination that matches the next workflow. The handoff should include the email, the provider source, and any review flags you want to preserve.

Key outputs

Waterfall Email Result

Waterfall

The main output of this workflow. It gives each row a waterfall email result that can be reviewed, filtered, and exported.

  • Work email
  • Provider source
  • Match status

Review Status

Workflow

A simple status field for deciding whether the row is ready, needs review, or should be skipped.

  • Ready
  • Needs review
  • Skip

Why a waterfall is better than one enrichment attempt

Email enrichment often fails for simple reasons: a provider does not have enough data, the row needs a different identifier, or the match is ambiguous enough that it should not be trusted without review. A waterfall helps because it lets you try more than one provider in a defined order instead of stopping after the first miss.

The practical advantage is coverage. If the first provider does not return a usable result, the next one gets a chance to do better. That can lift the total number of rows you can work with while still keeping the source of the match visible in the sheet.

  • Use the strongest provider first if you care most about quality.
  • Use fallback providers to recover rows the first pass could not fill.
  • Keep review flags so uncertain matches do not flow downstream by mistake.

This workflow is especially useful when a list includes mixed inputs. Some rows may have a name and domain, while others only have a LinkedIn URL or a partial company record. A waterfall gives you a structured way to handle those differences without building separate workflows for each source type.

Question to askWhy it matters
Which provider should go first?That determines whether you optimize for accuracy or coverage.
What counts as a good match?That keeps uncertain rows from being treated as final.
What do you export?That decides whether the next tool gets a clean field set or too much noise.

When the waterfall is set up well, the output is easy to audit. You can see which rows matched, which source produced the result, and which rows still need another pass. That transparency is what makes the workflow useful for teams that care about quality as much as coverage.

To get started

  • Start with names, company domains, or LinkedIn URLs
  • Choose the enrichment providers and fallback order
  • Run the waterfall on selected rows

When to use this

  • One provider does not cover enough rows
  • You want fewer manual retries
  • You need source and confidence visibility before export

Integrations

Email enrichment
Waterfall enrichment
CSV import
CSV export

What you can swap

This playbook follows the workflow shown in the video, but the exact source, enrichment, prompt, and handoff can be changed to match your team.

  • Input source
  • Column configuration
  • Provider or AI prompt
  • Export destination

Common questions

Can I run this on an existing spreadsheet?

Yes. Import or open existing rows, add the relevant Cockpit columns, then run the workflow on selected rows or the full sheet.

Can I review results before exporting?

Yes. Results stay visible in the spreadsheet so you can filter, edit, rerun, or approve rows before handoff.

Can I reuse the workflow later?

Yes. Treat the columns and prompts as a repeatable playbook for the next list, campaign, or account segment.

More Enrichment playbooks