Saleshandy Verify Emails
Overview
Converts a lead list (from saleshandy-find-leads or supplied directly)
into verified, sendable contacts — checking DNC suppression and respecting
credit costs along the way. See reference.md for credit-cost and batching
details.
Workflow
- Get the lead list:
lead_id[]from a priorsage_search, orlinkedin_url[]/full_name_with_company[]if supplied directly. - Ask the user: email only, or email + phone? Map "email" / no preference
→
reveal_phone: false; "phone" / "email and phone" →true. If ambiguous AND the batch is large, confirm before burning phone credits (7x more expensive — seereference.md). - If the user already has known emails/domains (not going through a
reveal), check them against DNC first via
search_dnc_item(type="email")before doing anything else — no point verifying or enrolling a suppressed contact. - Call
enrich_contactswith up to 100 IDs per call (hard cap — seereference.mdfor how to handle more). - Poll
get_enrichment_statusuntilcompleted, then callget_enrichment_result. - Report: how many revealed successfully, how many failed/had no email found, and flag any that matched a DNC list.
- If a revealed contact looks like a hard bounce risk (Saleshandy reports
it as unverifiable), recommend excluding it rather than enrolling it,
since bounces hurt account health (see
saleshandy-account-healththresholds).
Handoff
End by asking whether to proceed to saleshandy-build-sequence (or
add_leads_to_sequence into an existing one) with the verified list —
restate the mandatory gate: always ask the user which sequence AND which
step; never default or infer either, even if only one active sequence
exists.