AI prompts for running Hunter from your AI assistant

I'm {{your_role}} at {{your_company}} moving new customers into onboarding.

Pull my Hunter list {{list_name_or_url}} — recently signed accounts. Draft the handoff sequence the templates model: the sales rep introduces the CSM ([[CSM name]]) with the customer's primary goal restated, then a welcome laying out a Week 1/2/3 plan, then a "confirming what we agreed on" note that lists the sales commitments and invites correction before kickoff — end on a specific kickoff-call slot. Scaffolded and concrete, role-based sign-offs.

Verify addresses and build it in Hunter for my review.

Grounded in Hunter's customer-success-handoff templates: continuity + expectation-setting; the trust move is explicitly restating the primary goal and commitments; concrete scheduling CTAs with proposed slots. Real subject: "{{first_name}}: confirming what we agreed on."

Ensure the copy is real, human, and avoids any AI tell-tale signs, including em-dashes, staccato sentences, and unnatural language like: carry, shipped, ask etc.

I'm {{your_role}} at {{your_company}}. Pull my Hunter list {{list_name_or_url}} — customers in their first 90 days.

Build the cadence the templates already form: at 30 days, ask if the workflow they set up in onboarding is working; at 60, nudge a deeper second-phase feature most teams move to; at 90, ask whether the outcome they were aiming for is showing up, before the renewal window.

Each email is one specific observation plus one open question — the softest ask in the library, no upsell. Add trigger-based variants for a usage milestone or an account signal (usage drop, unactivated feature, nearing a limit).

Verify addresses, then build it in Hunter for my review.

Grounded in Hunter's check-in templates: the 30/60/90 series escalates setup → depth → outcome and is a natural sequence; trigger variants ("You just hit [[milestone]]", "Noticed something in your account"). Softest CTA set — often just "Any questions or feedback so far?"

Ensure the copy is real, human, and avoids any AI tell-tale signs, including em-dashes, staccato sentences, and unnatural language like: carry, shipped, ask etc.

I'm {{your_role}} at {{your_company}}. Pull my Hunter list {{list_name_or_url}} — customers renewing around {{renewal_window}}.

State the renewal date up front, then run a 3-touch sequence: a consultative opener that recaps what they've achieved and asks two quick "what's worked / what to add" questions, then one concrete reason to commit ({{incentive_eg_multi_year_discount}}), then a dated reminder with the renewal link.

Where I flag a rough patch this year in {{known_issues}}, front-load a "before we talk renewal" note that names it honestly and asks for 20 minutes — and for silent accounts, add the senior-signed personal variant. Verify addresses and build it in Hunter for my review.

Grounded in Hunter's renewal templates: date stated up front; transactional (reminder + self-serve link) vs consultative (diagnostic questions before terms) modes; a deliberate escalation variant signed by a senior role. Real lines: "Before we talk renewal, {{first_name}}", "I'd rather get this right than rush into a renewal conversation."

Ensure the copy is real, human, and avoids any AI tell-tale signs, including em-dashes, staccato sentences, and unnatural language like: carry, shipped, ask etc.

I'm {{your_role}} at {{your_company}} and we sell {{product}}.

Pull my Hunter list {{list_name_or_url}} — existing customers to expand. For each, open on a concrete usage observation, then name the ceiling or need it points to, then the plan or feature that solves it with a light pricing softener — pick the trigger that fits from {{expansion_context}} (new feature on their plan, an adjacent product, more seats for a grown team, or a usage limit reached).

Close on a single permission-style question, not a hard sell. Use {{first_name}}/{{company}} as merge fields and leave [[current plan]], [[higher plan]], [[specific capability]] as author fill-ins.

Draft a 2-touch sequence, verify addresses, and build it in Hunter for my review.

Grounded in Hunter's upsell templates: 4-beat arc (observed signal → name the need → plan/feature + pricing softener → permission question). Real CTAs: "Want me to walk you through it?", "Would it make sense to move your team to a plan built for this size?"

Ensure the copy is real, human, and avoids any AI tell-tale signs, including em-dashes, staccato sentences, and unnatural language like: carry, shipped, ask etc.

I'm going to {{event_name}} and this is the exhibitor list: {{company_list}}. For each company, run a Domain Search and pull one contact in {{job_titles}} with a verified email address. I want meetings in the calendar before I arrive, so draft a two-line note per contact that mentions the event and asks for 15 minutes there.

Save my Discover search for {{ideal_customer_profile}} in Hunter under the name {{search_name}}. Whenever I ask you to run it from now on, rerun the saved search, check the results against my Hunter company list {{list_name}}, and show me only the companies that aren't in it yet. New companies enter my market every month, and this way I catch them without rebuilding the filters each time.

I want to test {{subject_line_or_body}} on my list {{list_name}}, and only that one variable. Draft two versions that differ in nothing else, create two sequences in Hunter, and split my verified contacts evenly between them, at least 50 per side, or tell me the list is too small for the result to mean anything. Leave both for my review. Once the sends finish, I'll come back and ask you to compare them by reply rate.

This email earned replies and I don't want to rebuild it from memory next quarter: {{paste_email}}. Save it in Hunter as a message template named {{template_name}}, with the personalization spots left as placeholders a sequence can fill from custom attributes. Confirm it's saved, so the next campaign starts from something already proven instead of a blank page.

Before we start, pull my Hunter account details: the plan I'm on, what I've used this month, and what's left. Then estimate what the job I'm about to hand you will use, based on {{rough_job_description}}, and tell me whether it fits. If it doesn't, suggest where to trim: fewer companies, fewer contacts per company, or verification only for the contacts that make the shortlist.

Here are the companies I'm considering: {{company_list}}. For each one, check how many email addresses Hunter has on file before I spend anything on contacts. Rank the list by coverage and split it in two: companies where Domain Search will carry the work, and companies where I'll be researching by hand. If more than a third sit in the second group, say so plainly, because that changes whether this segment deserves a quarter of my time.

Nothing gets sent this month. Build the three lists the Outreach Planner calls for in Q1 Month 1: my target audience via Hunter Discover ({{industry}}, {{location}}, {{employee_range}}), competitor switchers via the technology filter for {{competitor_technology}}, and companies hiring in {{department}}, which you'll research on the open web before Hunter finds the people. For each company, pull 1-2 contacts in {{job_titles}}, verify every address, and keep each list to 50-100 leads. Save the three groups to their own Hunter Leads lists named for the quarter and give me the totals, so January is ready before the holidays start.

These are deals I lost {{timeframe}} ago and want another run at: {{contact_list}}. Before I write a word, verify each contact's email with Hunter. Where the address is still valid, keep them on the list. Where it comes back invalid, the person has probably moved on, so run a Domain Search on the company and find whoever now holds {{job_title}}, with a verified address. Return the two groups separately, because the email to a brand-new person in the seat needs a completely different opening.