Follow-up AI prompts

These follow-up email prompts include invoice chasing, proposal nurture, meeting recaps, event and webinar follow-up, reviving cold threads, breakups, and routing. Works in ChatGPT, Claude, or any AI assistant with the Hunter MCP connector.

Categories
10 prompts
Job-search follow-up sequence

I'm {{your_name}}, following up on job applications and interviews.

Pull my Hunter list {{list_name_or_url}} — recruiters and hiring managers I'm waiting on.

For each, pick the right note: an application follow-up (reference the role + submission date → prove fit against one requirement → deferential status ask), a post-interview thank-you (reference a specific conversation moment → reaffirm fit → mostly passive close), a competing-offer nudge where I flag {{competing_offer_deadline}}, or a graceful post-rejection "keep me in mind."

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

Grounded in Hunter's job-application, interview, and candidate-side recruitment-follow-up templates: reference the specific application or interview → prove attention and fit → soft ask. Real subjects: "Noticed the [[job title]] repost: is my application still active?", "[[Job title]] panel: thank you, {{first_name}}."

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.

Sales cadence follow-up sequence

I'm {{your_role}} at {{your_company}} following up on cold or warm sales threads.

Pull my Hunter list {{list_name_or_url}}.

For each, build a multi-touch cadence that de-escalates: a post-touch nurture that shares a resource, a value-tease ("reply YES and I'll send my suggestions"), an objection-reframe built around a client story, and a low-risk offer with a soft deadline — ending, if still silent, in a breakup.

One ask per email, soft and reply-oriented; only the final offer carries any urgency. Verify addresses, then build it in Hunter for my review.

Grounded in Hunter's sales-follow-up templates (the section's largest cluster, ~35): reference prior touch → restate value/resource/proof → low-friction ask. Real lines: "Just bubbling our conversation back to the top of your inbox.", the numbered "send one number: 1 … 2 … 3 …" reply mechanic.

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.

Wrong-person routing sequence

I'm {{your_role}} at {{your_company}} and I may have the wrong contact.

Pull my Hunter list {{list_name_or_url}}.

For each, keep it very short: a one-line reason for reaching out, then ask whether they're the right person and, if not, who is and the best way to reach them.

Polite, single, gatekeeper-friendly ask — no pitch. Verify addresses, then build it in Hunter for my review.

Grounded in Hunter's sales-follow-up and seo routing templates: brief follow-up → "is it you? if not, point me to the right person." Real subjects: "Appropriate person", "Relevant person", "Better fit".

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.

Breakup / permission-to-close sequence

I'm {{your_role}} at {{your_company}} and it's time to close the file on non-responders.

Pull my Hunter list {{list_name_or_url}}.

For each, draft a single graceful last touch: acknowledge the silence without guilt ("usually this means you're busy or it's not a priority"), optionally dangle one low-risk offer, and ask permission to close or hand control back ("what do you recommend as a next step?").

Leave the door genuinely open, no passive-aggression. Verify addresses, then build it in Hunter for my review.

Grounded in Hunter's breakup templates (across no-response and sales-follow-up): concede the silence → low-risk out → control-ceding close. Real subjects: "Permission to close your file?", "Closing your file", "Goodbye {{first_name}}", "Thanks from [[company]]."

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.

No-response re-engagement sequence

I'm {{your_role}} at {{your_company}} and these contacts went quiet on an earlier email.

Pull my Hunter list {{list_name_or_url}}.

For each, don't re-pitch — pivot on a single new element per touch: a different angle, a peer proof point ("[[case study company]] had the same problem"), a trigger event you noticed, a smaller ask, or a fresh insight.

Keep it low-pressure with explicit "no pressure" language, one soft opt-out-framed question each. Verify addresses, then build it in Hunter for my review.

Grounded in Hunter's no-response (and value-nudge sales-follow-up) templates: reference the unanswered email → introduce ONE new element → low-pressure close. Real lines: "I know that's a bigger commitment, so here's a smaller version:", subject "[[Case study company]] had the same problem."

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.

Webinar follow-up sequence

I ran {{webinar_name}} at {{your_company}}.

Pull my Hunter list {{list_name_or_url}} — registrants.

For each, curate rather than dump: never "here's the 45-minute recording," always the one part that matters — a 5-minute highlight clip, a single actionable takeaway, a timestamped section, or a peer's result. Serve attendees and no-shows differently ("here's what you missed").

Mostly soft or no CTA; one touch can carry a real day-specific meeting ask. Verify addresses, then build it in Hunter for my review.

Grounded in Hunter's webinar templates: anchor to the webinar → deliver ONE piece of value → light ask. Real lines: "Instead of sending the full 45-minute recording, here's the 5-minute clip that got the strongest reaction.", subject "Clipped the best part of [[webinar name]] for you."

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.

Post-event follow-up sequence

I'm {{your_role}} at {{your_company}} and I met people at {{event_name}}.

Pull my Hunter list {{list_name_or_url}} — contacts from the event.

For each, run on proof-of-attention: cite something they personally said or asked, deliver the thing you promised (an answer, a resource, a link), and make a light ask — a call, or a standing "let's compare notes," or no ask at all where staying in touch is the point. Verify addresses, then build it in Hunter for my review.

Grounded in Hunter's event templates: reference-the-meeting → recall one specific shared moment → light ask. Real subject: "You asked about [[specific question]] at [[event name]]", and one with "No specific ask here. I just wanted to stay connected."

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.

Meeting recap & next-steps sequence

I'm {{your_role}} at {{your_company}}.

Pull my Hunter list {{list_name_or_url}} — people I've just met with.

For each, send a crisp recap: the decision or direction agreed, owner/action/deadline lines for each next step, the one still-open item flagged, and a soft "let me know if I missed anything" correction check.

For internal team recaps, open "Hi team" and drop the first-name merge; for client-facing ones, personalise and close on a dated forward commitment or a check-in question. Verify addresses, then build it in Hunter for my review.

Grounded in Hunter's meeting templates: anchor to the meeting → decisions + owner/action/deadline → surface the open item → "Let me know if I missed anything." Real line: "Wanted to capture what we discussed while it's fresh."

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.

Proposal follow-up sequence

I'm {{your_role}} at {{your_company}}, chasing sent proposals.

Pull my Hunter list {{list_name_or_url}} — contacts with an open proposal.

Rather than repeat one nudge, rotate the six real angles: a plain check-in, a "do you have a decision timeline?" permission-to-plan ask, a value-add ("here's a similar project's result"), a scarcity/capacity update, a multi-thread to a secondary contact ({{secondary_contact}}), and a graceful "closing the loop" breakup.

Reference the proposal by {{project_name}} in every subject, one soft opt-in ask each. Verify addresses, then build it in Hunter for my review.

Grounded in Hunter's business-proposal templates: reference the proposal → one reason to re-engage → soft offer of a call or help. Real lines: subject "Closing the loop on the [[project name]] proposal", "No rush on my end, but it would help me plan if I had a rough sense of when your team expects to make a call."

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.

Invoice / payment-reminder sequence

I'm {{your_role}} at {{your_company}}, chasing unpaid invoices.

Pull my Hunter list {{list_name_or_url}} — contacts with an invoice outstanding.

For each, use the details in {{invoice_number_amount_due_date}} to build the escalation ladder the templates form: a plain due-date reminder, a days-overdue nudge that re-attaches the invoice, an empathetic payment-plan offer where I flag {{payment_plan_ok}}, a work-paused notice, and a final notice naming the contractual consequence.

Front-load the invoice number in every subject for thread-matching, and keep the CTA firm and singular — a closed question asking for a confirmed payment date (this is the one place follow-ups get hard, not soft). Verify addresses, then build it in Hunter for my review.

Grounded in Hunter's invoice templates: name invoice + amount + status → reference/consequence → "Could you confirm a payment date?" Real lines: "I understand that cash flow can be unpredictable.", subject "Invoice [[invoice number]]: final notice before next steps."

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.

Run every prompt on this page from your AI assistant.

Connect Hunter to Claude, ChatGPT, or Perplexity. Every prompt below runs on your Hunter account and returns verified contacts with provenance attached, so your assistant knows where each one came from and how confident it should be before acting.