> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Find Work Email

> Decide whether work-email lookup is the right next step, then use the maintained waterfall to pilot and execute.

[Human guide: work with your agent →](https://deepline.com/docs/human/plays/task-find-work-email.md)

> [!NOTE]
>
> Choose the work-email input route and define the result you will accept.

Use this task page to decide whether work-email lookup is the right next step
for a person or a CSV. It does not establish that an address is deliverable.
the maintained Play's live contract defines its provider route, result rule,
and Deepline-credit price.

## Check input readiness

Separate people with missing or ambiguous identity fields before a full run, and
keep those rows in the pilot to observe their no-result behavior. The canonical
guide selects the supported input path for the data you have.

## Ask an agent

```text theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
/deepline-gtm Find work emails for leads.csv. Run five representative rows first, keep no-result states, and show the result fields and Deepline-credit usage before scaling.
```

## Run the maintained Play

[Email waterfall](https://deepline.com/docs/plays/email-waterfall.md) owns the executable single-record
and CSV-pilot procedures, input selection, live-contract inspection, and
result interpretation. Use that page before running a batch.

## Next steps

* [Prebuilt Plays](https://deepline.com/docs/plays/tasks-overview.md): compare a prebuilt Play with a custom
  Play.
* [Data lifecycle](https://deepline.com/docs/data-lifecycle.md): decide when a CSV pilot should move into
  the Database or a CRM.

## Verify this task

Confirm person identity and required fields before the maintained pilot. Keep unsupported or missing results explicit.

Ask your agent to explain a failed check before repeating work or expanding the scope.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.