A campaign with reply detection and stop conditions
Automation 12 min
0/21
Business problem
Automatic campaigns without control are a disaster: sending to a person who already replied ('this is your 4th email to someone mid-conversation'), sending to bounces (burns the domain), no unsubscribe (complaints → spam). Stop conditions aren't an option — they're the condition for the domain and reputation surviving.
Proven method
A campaign in 6 elements:
- CAMPAIGN TRIGGERS: what brings a lead into the campaign (score ≥ 70, priority HIGH, tag 'for campaign', manual add),
- SEQUENCES: an email sequence (5-7 from the Cold Email module: value, new value, case, angle, close) with 3-4 day gaps,
- FOLLOW-UPS: automatic, but each with new value (never a 'reminder'),
- TIMING: sending on the days and hours with the highest open (Tue-Wed morning), rotation by time zones,
- REPLY DETECTION: the system detects a reply (at the gateway, without opening) → STOP the sequence → a human alert,
- BOUNCE HANDLING: a hard bounce → the lead is removed, marked, NOT retried; a soft one → retry once;
- UNSUBSCRIBE: every email has an unsubscribe link → an unsubscribe immediately removes from the campaign (not 'mark and send again'),
- STOP CONDITIONS: reply / bounce / unsubscribe / an OUT_OF_OFFICE reply (pause) / a CRM status change (e.g. an open deal) — each stops the sequence. Workflow: Lead enters campaign → Email #1 → Wait → Reply? YES → Stop + alert; NO → Follow-up → ... → Stop conditions always checked.
Market example
- BAD
- Manual, inconsistent execution or chaotic automation lacking data validation.
- GOOD
- The 'e-commerce customer service' campaign: 500 leads enter (trigger: score ≥ 70). Email #1 on Tuesday 9:00. On Thursday: reply detection — 12 replies (STOP for those leads + an alert 'new conversation'), 8 hard bounces (removed, not retried), 1 unsubscribe (removed). The rest: Email #2 on Friday (new value — a case study). After 3 emails: 40 replies, 30 bounces, 15 unsubscribes, 415 in the sequence. All stop conditions work automatically — a clean domain, and the salesperson gets only replies and alerts.
Ready-to-use prompt
You are a campaign architect. Context: My campaign: [PRODUCT + EMAIL SEQUENCE]. List: [FROM WHERE, NUMBER]. Email tool: [INSTANTLY/SMARTLEAD/OTHER]. CRM: [CRM]. Task: Design the automatic campaign: 1. Campaign triggers: what brings a lead in (thresholds, tags, sources) 2. A sequence: a plan of 5-7 emails (when, what value in each) 3. Timing: send days/hours + time zones 4. Reply detection: how to configure (what happens after a reply — STOP + alert) 5. Bounce handling: hard vs soft (what I do with each) 6. Unsubscribe: how to configure (immediate removal) 7. Stop conditions: the full list + what happens after each (workflow) 8. Monitoring: what I check daily in the campaign Format: 8 sections.
Model rekomendowany: Claude 3.5 Sonnet / GPT-4o Copy and paste into ChatGPT, Claude or Perplexity
ALTERNATYWNE SCENARIUSZE
Variations & alternative scenarios
Small-scale version: manual campaign adds + basic stop conditions.
Full version: CRM triggers + reply detection + bounces + reports.
Practical exercise
Draw your campaign workflow (Lead enters → Email #1 → Wait → Reply? → STOP/follow-up). List 6 stop conditions and what you do after each. Set the send timing (days/hours).
Zapisano w przeglądarce