Plan a multi-touch sequence that doesn't harass
#chatgpt
#prompt
Design an outreach sequence for this prospect segment: for each touch give the channel, the day offset, the job that touch does (labeled 'Job:'), and a two-line sketch of its content — not full copy. Constraints: every touch must carry something new (no 'bumping'); mix channels only where the segment plausibly lives; the sequence ends with a clean breakup, not a fade-out. Then, under 'Kill criteria', state the reply signals that should immediately end or redirect the sequence. Ground everything in the segment description — where it's too vague to choose a channel or angle, say so explicitly. Segment: {{segment}} Product: {{product}} Assets we have: {{assets}}
Fill in: Who the segment is (role, company type, where they hang out), your product, and the content assets you can use.
Known limits: A sequence plan is a hypothesis — without reply-rate data per touch it cannot be optimized, only reasoned about.
Run evidence
Sandbox run 2026-08-19 · openai/gpt-5-mini
Input fixture
SEGMENT: Heads of Customer Support / Support Ops at US 3PL and freight
companies, 200-1000 employees, Zendesk stack, hiring seasonal agents for Q4 (hiring
signal = in-market). Active on LinkedIn; industry Slack (SupportDriven) membership
common; conference: Support Driven Expo in October.
PRODUCT: Relay — Zendesk ticket auto-triage for peak season.
ASSETS: 6-min recorded demo; Coastway Logistics case study (3x December volume, 2
fewer temps); free 'peak season staffing calculator' web tool; founder available for
15-min teardowns of a prospect's public help center.
Model output (unedited)
Sequence (target = Heads of Customer Support / Support Ops at US 3PL/freight, 200–1000 employees, using Zendesk and hiring seasonal agents for Q4)
Notes before the sequence
- Channels used: LinkedIn (connection + InMail/messages), email, SupportDriven Slack (DM or thread) — chosen because the segment is active on LinkedIn and commonly members of SupportDriven Slack. Use Slack touches only when the prospect’s membership is confirmed; if unknown, substitute the Slack touch with a LinkedIn message.
- Conference tie-ins reference Support Driven Expo (October). Do not assume the prospect will be there unless their profile or public event RSVP indicates attendance; where that’s unknown I specify the alternate copy.
- Every touch adds something new (tool, stat, demo, personalized insight, founder teardown, event ask). No bumping.
- Sequence length: 21 days, ends with an explicit breakup.
Touch 1
- Channel: LinkedIn connection request
- Day offset: 0
- Job: Get permission & establish relevance
- Sketch: Quick note: saw you run support for a 3PL on Zendesk and are hiring for Q4 — we help Ops teams avoid hiring extra temps with ticket auto-triage. Low-friction ask to connect.
Touch 2
- Channel: Email
- Day offset: 2
- Job: Deliver immediate utility and start a data-driven conversation
- Sketch: Link to the free “peak season staffing calculator” and one-line on how it models temp hires vs triage automation; CTA: try the calculator and ping back a number you don’t like.
Touch 3
- Channel: SupportDriven Slack DM (if confirmed member) — otherwise LinkedIn message
- Day offset: 5
- Job: Provide targeted social proof and prompt a lightweight reply
- Sketch: One-paragraph highlight from Coastway Logistics case study (3x December volume handled, while using 2 fewer temps) and a quick question: “Is your December the same shape as this?” (easy yes/no).
Touch 4
- Channel: Email
- Day offset: 9
- Job: Show product in-action (low time cost)
- Sketch: 6‑minute recorded demo link with two-line TL;DR: how Relay auto-triages Zendesk to deflect repetitive tickets and reduce temp headcount; CTA: 6 mins to see if it maps to your spike.
Touch 5
- Channel: LinkedIn message (or Slack DM if active and previously engaged)
- Day offset: 12
- Job: Personalize with a quick, public-help-center observation to build credibility
- Sketch: Two tactical observations from their public help center or Zendesk-facing pages (e.g., repetitive ticket type, missing automation) and one suggested quick win; soft CTA: “Want a free 15‑min teardown to flesh these out?”
Touch 6
- Channel: Email (Founder outreach)
- Day offset: 15
- Job: High-value conversion ask (low-commitment, high-signal)
- Sketch: Founder offering a free 15‑minute teardown of their public help center — promise: 2–3 tactical fixes + estimated impact on ticket volume/temp hires; calendly link / offered time slots.
Touch 7
- Channel: LinkedIn message (or SupportDriven Slack if they engage there) — conditional
- Day offset: 18
- Job: Event tie-in / next-step urgency (or virtual alternative)
- Sketch: If profile/event shows they’re attending Support Driven Expo: quick “We’ll be at Support Driven Expo in Oct — 15 mins to compare notes?” If attendance unknown: “If you’re not going, happy to meet virtually that week — still offering teardown.”
Touch 8 (Breakup)
- Channel: Email (final)
- Day offset: 21
- Job: Clean breakup with a clear, low-effort keep-in-touch option
- Sketch: Short note: last outreach for now; recap one line of value (Coastway result + calculator link), invite to book teardown anytime, and ask to reply with “not interested” or a referral if so.
Kill criteria (immediately end or redirect the sequence)
- Positive interest / booking signals (end sequence and hand off to AE/SDR):
- Prospect replies asking to schedule a demo, teardown, or meeting.
- Prospect asks for pricing, pilot details, or a procurement next step.
- Prospect asks for the demo/case study/calculator (send immediately and hand off).
- Explicit negative signals (stop outreach; add appropriate tag/CRM note):
- “Not interested,” “Don’t contact me,” unsubscribe, or asks to be removed from lists.
- Prospect confirms they’re not hiring for Q4 / not in-market for seasonal staffing.
- Prospect says they already have an equivalent solution in production and are locked into it for the season (unless they ask to revisit).
- Redirect signals (stop sequence and move to long‑term nurture):
- Prospect says “we’ll revisit after Q4 / next budget cycle” — pause sequence and set a timed nurture reminder for the stated time.
- Prospect refers you to another person — end current cadence and start a new, targeted sequence to the referred contact.
- Administrative / compliance:
- Engagement indicates corporate vendor-block or procurement do-not-contact list — stop immediately and note in CRM.
If any reply requests an asset or meeting, the sequence should not continue the predefined touches — instead, immediately fulfill the request and hand off to the appropriate rep.
Editorial review (independent AI agents)
-
Accuracy —
pass
(editorial-accuracy/google/gemini-2.5-flash)
-
Safety —
pass
(editorial-safety/anthropic/claude-haiku-4.5)
-
Usefulness —
pass
(editorial-usefulness/openai/gpt-5-nano)
