---
name: contact-finder
description: Use when the user wants the right person to contact at a target company (a recruiter, a hiring manager, or an engineer on the team) before outreach. Finds one primary contact and one or two alternates, verifies current employment from a dated public source, finds a public email only when it can be verified, and checks the user hasn't already contacted them.
metadata:
  id: contact-finder
  version: "1.0.0"
  author: BotPlaza
---

# Contact Finder

> Drafts only: nothing is submitted, applied for, or sent without your explicit OK.

## What it does

Finds the one person at a company most likely to read your note, and proves they still work there. You get a primary contact and a couple of alternates, each with a dated source, a confidence level for their email, and one real detail you can mention. People you've already contacted are filtered out.

## When to use

- "Who should I email at Anthropic about research internships?", "find a recruiter for this role", "get me three contacts for these companies".
- Pair it with Outreach Note Writer, which drafts the message.

## Requires

Web search and web access to company team pages, LinkedIn profiles visible on the public web, conference and paper pages, and GitHub. Optional: an email connector (to check sent mail for earlier contact) and a contact-enrichment tool.

## Schedule

On demand, or in batches after each Role Scout run.

## Inputs

| Setting | Default | Notes |
|---|---|---|
| `company` | required | |
| `role_or_team` | required | The team the user wants to reach. |
| `prefer` | recruiter, then team engineer or manager | At startups, founders are fine. |
| `alternates` | 2 | |
| `email_policy` | verified only | `verified only`, or `allow pattern` with the user's approval. |

## Steps

1. **Find candidates:** first a recruiter who hires for that team or level, then an engineer or manager on the team.
2. **Verify employment** from at least one dated source, such as a profile showing "Present", the company team page, or a recent talk or post. Record the source and the date checked.
3. **Find an email** only from a public source: the company site, a paper, a GitHub profile, or a verified enrichment result. Mark it VERIFIED, or PATTERN (a guess based on the company's format, not verified).
4. **Check for prior contact** in the user's sent mail and outreach logs. Skip anyone already contacted.
5. **Note one real detail** per person (a talk, a paper, a launch they worked on) that could personalize the note.
6. **Write the list** and hand it to the outreach step. Status stays HELD until the user approves drafts.

## Output format

```markdown
# Contacts at {Company} for {team} · {date}
| | Name | Title | Source (checked) | Email | Detail |
|---|---|---|---|---|---|
| Primary | {name} | {title} | [{source}]({url}) ({date}) | {email} (VERIFIED) | {detail} |
| Alt 1 | ... |
```

## Edge cases

- **No verifiable email:** say so and suggest a professional networking connection request or the company's careers contact.
- **The person left the company:** drop them and find a replacement.
- **The company is tiny:** a founder is fine as the primary contact.

## Boundaries

- Research only: never send, connect, follow, or message anyone.
- Never present a guessed email as verified.
- Public professional information only. No personal phone numbers, home addresses, or family details.