Customer lifecycle AI prompts

I'm {{your_role}} at {{your_company}}. Pull my Hunter list {{list_name_or_url}} — customers who churned or lapsed.

Draft a 2–3 touch win-back that acknowledges the lapse without guilt and leads with one concrete thing that changed — a shipped fix to the exact issue they raised ({{known_issue}}), a targeted comeback offer ([[targeted offer]]), or a no-pitch diagnostic question about why they left — then a low-key "last note from me, the door's open" close. Re-verify addresses first, since lapsed contacts move. Build it in Hunter for my review.

Grounded in Hunter's win-back templates: acknowledge lapse → one concrete change or no-pitch question → soft/no CTA (two of six have no hard ask). Real subjects: "We fixed [[specific issue]], {{first_name}}", "Last note from me about [[your product]]."

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 I want trials to convert.

Pull my Hunter list {{list_name_or_url}} — people inside a {{product}} trial. Draft the lifecycle sequence mapped to trial stage: a welcome naming the single first action and the time it takes, a "set up [[key feature]] in 5 minutes" activation nudge, a one-week-in check with a stage-relevant tip, an expiry email that shows upgrading preserves their work, and — if they never logged in — a "what got in the way?" note asking for one line. Mix hard-link CTAs (upgrade/get-started) with low-friction reply asks by stage.

Verify addresses and build it in Hunter for my review.

Grounded in Hunter's free-trial templates: stage-mapped (welcome → activation → mid-trial → expiry → post-expiry); CTA splits between "Upgrade now: [[link]]. Takes about 2 minutes." and "even a one-line reply helps." Real line: "It's the one action that makes everything else click."

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}} — prospects at the demo stage.

For each, draft the email their {{demo_stage}} needs: a "what to expect" preview with agenda and duration, a confirmation with the full logistics block (date, time, timezone, link) and two prep questions, a "next steps from your demo" recap that restates the challenge and names the best-fit use case, or a gracious no-show reschedule offering two slots. Logistics-led, soft CTA.

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

Grounded in Hunter's demo-request templates: pre/post-booking logistics; soft, logistical CTAs ("here's how to get started", "Would [[day]] or [[day]] work?") — two carry no hard ask. Real subject: "Confirmed: [[your product]] demo on [[date]]."

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}} 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.