Skip to main content
Human guide: work with your agent → Use the maintained email route, then interpret its validation evidence before using a returned address. Your goal is an inspected result, not a delivery promise.

​
1. Choose the input route

For a CSV containing names and company domains, follow the executable email waterfall guide. For a verified LinkedIn URL, inspect prebuilt/person-linkedin-to-email and its current contract.
Read the live result fields and any required column mappings. A preflight check does not call an email provider.

​
2. Define the acceptance rule

Decide what your next task requires. The Play’s validation outcome is one piece of evidence. Identity, current employment, delivery, and permission to contact someone are separate questions. Do not assume every route includes an extra ZeroBounce call or a fixed pattern price. Provider steps and applicable charges come from the actual route.

​
3. Run and inspect a representative pilot

Use the pilot procedure. Save the run ID and inspect its retained result and row outcomes. Compare the email, source, validation state, and attempt outcomes. Keep misses separate from rejected candidates and provider failures. An earlier candidate must not override a later rejection in your review.
Each accepted row satisfies the selected identity and validation rule. Unresolved rows remain visible. Recorded usage reflects the work that ran.
If an additional validation action is required, inspect its schema and cost. Author that action explicitly in a checked Play. Do not assume a natural-language request changes an existing prebuilt implementation.

​
Continue

Use waterfall evaluation to compare accepted coverage. Ask your agent to explain the actual validation outcome before adding more paid attempts.