playbook-name-to-other-prospects

Build an other_prospects variable that names up to two other senior colleagues at the recipient's company, then slot it into a sentence like "If this sits with {{other_prospects}} instead, happy to talk to them." The referral CTA must be its own sentence that disappears entirely when the variable is empty.

Exclude the recipient before any model call by matching on normalized first and last name plus LinkedIn profile URL. Normalize hard — lowercase, strip accents and punctuation, compare first+last only — so nicknames, middle initials, and credential suffixes still match.

Yes. The playbook ships both a Clay table build (columns for domain lookup, exclusion formula, AI judge, and still-there check) and a Clay CLI workflow with equivalent code nodes. The exclusion runs as a formula before the paid AI column.

Provider job titles go stale, so a candidate list alone is unreliable. The playbook requires a still-there web check on each kept name plus the domain before the variable ships, and a headline-contradiction rule in the judge prompt drops self-reported titles that do not match reality.

One name is a valid answer. The phrase is assembled in code so a single name renders cleanly without a dangling "or", and the copy sentence must still read naturally with one name.

Do not use it when you want the buying committee as separate leads — the people named in this variable must never be emailed unless they are in the list on their own merits. It exists only to give the reader an easy referral instead of a yes or no.