Playbook
Use Apollo as the default high-recall people/company prospector.- Keep
include_similar_titles=trueunless the user explicitly asks for strict title matching. - For broad discovery, start with
person_seniorities+q_keywordsand only tighten after you inspect totals. - Prefer keyword-style constraints in
q_keywordsandq_organization_nameover overly narrow exact strings. - Use low
per_pagefor pilot checks, then scale once payload shape and match quality are confirmed. - For changed-company email recovery specifically, do not force Apollo first; prefer the scenario default order from the GTM meta skill.
- Detect redacted/obfuscated last names early (for example:
S****,K.,-,N/A,redacted, masked punctuation-heavy strings). - Treat
last_name_obfuscatedfromapollo_people_searchas non-authoritative for name-based email finding. - Do not pass obfuscated last names into
leadmagic_email_finderor pattern generators. - Required bridge step:
apollo_people_search->apollo_people_match(by Apolloid) -> useperson.last_namefor name-dependent flows. - If last name is obfuscated, do not rely on
first.last/first.lastInitial/firstInitial.lastInitialpatterns as primary candidates. - Prefer fallback order: direct provider email fields and enrichment lookups first (Apollo/person enrichment/LinkedIn-based enrichment), then emit pattern candidates only when confidence is acceptable.
- Persist deterministic flags for downstream branching, for example
last_name_obfuscated=trueandname_quality=low|medium|high. - Keep recall-first behavior: obfuscation checks should gate pattern generation quality, not force strict matching globally.