# Cold Email Sequence with Hot-Reply List > **Version 1.1.0 · Last updated 2026-10-22 · Difficulty: Advanced · Setup time: 60–120 minutes** Your clone sends a personalized 4-touch cold email sequence to every new eligible lead in your CRM, stops the moment someone replies, bounces or opts out, and emails you a daily hot list of the people who want to talk. You answer the warm replies yourself. --- ## 1. Overview and value Most outbound programs die after the first email. Touches 2, 3 and 4 get forgotten, replies get buried, and someone who said "not now" gets the same email again a week later. The leads were paid for (in money or effort) and most of them never get a real sequence. The Cold Email Sequence use case fixes that. Twice every weekday your clone: - picks up **new eligible leads** from your CRM (from Clone-Lead-Generation-Skill, a sheet import or leads already in the CRM), - checks each one against your **safety filters** (no customers, no open deals, no other reps' contacts, no opted-out people), - writes and sends **personalized emails** from your inbox, following a 4-touch schedule, - reads every reply, **classifies it** and takes the right action (stop, pause, unsubscribe, follow up later), - updates the **CRM** with the sequence step, status and last-touch date, - sends you a **daily hot list** of interested replies so you can respond personally. **What you get:** | Benefit | What it looks like | |---|---| | Every lead gets the full sequence | 4 well-timed touches, not 1 forgotten email | | No embarrassing mistakes | Stops instantly on reply, bounce or opt-out; never emails customers or open deals | | Warm replies don't get lost | One daily email listing everyone who said yes, with context and a suggested next step | | A clean CRM | Step, status and last-touch date on every lead, opt-outs flagged | | Safe sending | Daily cap, warm-up ramp, opt-out line and business-hours sending built in | > | Area | What works | > |---|---| > | CRM | **Salesforce** (SalesforceLeadOperator, SalesforceContactOperator, SalesforceAccountOperator, SalesforceOpportunityOperator, SalesforceActivityOperator) or **HubSpot** (HubspotContactOperator, HubspotCompanyOperator, HubspotDealOperator, HubspotEngagementOperator). HubSpot has no separate Lead object in this stack: leads are contacts with lifecycle stage "Lead" and a lead source property | > | Email (sending inbox) | **Gmail** (GoogleGmailOperator) or **Outlook** (Outlook email operator) | > | Lead supply | **Clone-Lead-Generation-Skill** (finds NEW leads), a list import via **GoogleSheets-Operator** or **Microsoft_Excel**, or leads already in your CRM | > | Suppression list | A sheet (GoogleSheets-Operator or Microsoft_Excel) or the CRM do-not-email flag | > | Hot reply alerts (optional) | **Slack** or **Microsoft Teams** (delivery only) | > | Personalization | Light web research by the clone | ## 2. Who it's for - **SDRs / BDRs and account executives** who own outbound and want consistent follow-up without manual chasing. - **Founders and small sales teams** with more leads than time. - **Marketing teams** running outbound to lead lists or event attendees. - **RevOps** teams who want one documented, compliant outbound process with clean CRM data. It is built for **new prospects only**. Existing customers, open opportunities and contacts owned by another rep are excluded on purpose. ## 3. How it works ``` ┌───────────────────────────────────────────────────────────────────┐ │ New leads land in your CRM (Clone-Lead-Generation-Skill, sheet │ │ import or existing records), about {DAILY_LEAD_VOLUME} per day │ └───────────────────────────────┬───────────────────────────────────┘ │ Every weekday at {RUN_TIMES} (scheduled task) │ ▼ ┌───────────────────────────────────────────────────────────────────┐ │ "Cold Email Sequence" skill │ │ │ │ 1. Check the inbox first ──► replies, bounces, opt-outs, OOO │ │ 2. Classify each reply ──► stop / pause / suppress / hot │ │ 3. Update the CRM ──► step · status · last touch │ │ 4. Find due follow-ups ──► touches 2, 3, 4 that are due │ │ 5. Find new leads ──► {LEAD_CRITERIA}, then filter: │ │ (no customers, open deals, other reps' leads, │ │ suppressed or do-not-email contacts) │ │ 6. Write personalized emails (value prop + light research) │ │ 7. Send within today's cap and the lead's business hours │ │ ({DAILY_CAP}, warm-up ramp, follow-ups first) │ │ 8. Morning run: send the HOT LIST ──► {HOT_LIST_RECIPIENTS} │ └───────────────────────────────┬───────────────────────────────────┘ │ ▼ ┌───────────────────────────────────────────────────────────────────┐ │ You: read the hot list → reply personally to interested leads → │ │ book the meeting. The clone never auto-replies to a hot lead. │ └───────────────────────────────────────────────────────────────────┘ ``` ### The 4 touches Timing is set by `{SEQUENCE_TIMING}` (default: day 0, day 3, day 7, day 14, counted in business days or calendar days, your choice). Touches 2 to 4 are sent as replies in the same email thread. | Touch | Default day | Purpose | |---|---|---| | 1. Intro + relevance | Day 0 | Who you are, why them, one clear reason it matters to their role or company, a light ask | | 2. Value / proof | Day 3 | A concrete result or example (from `{PROOF_POINTS}`), restate the `{CTA}` | | 3. Different angle / resource | Day 7 | A new angle (a different pain point or use case) or a useful resource, no pressure | | 4. Polite breakup | Day 14 | "I'll stop here", leave the door open, make it easy to say "not now" or "wrong person" | Example templates (the clone personalizes each one; `{{double braces}}` are filled per lead): ``` Touch 1 Subject: {{company}} and {PRODUCT_NAME} Hi {{first_name}}, {{personal_line}} (one true, specific line about their company or role) We help {{role}}s like you {VALUE_PROP}. Worth a 20-minute call to see if it fits? You can pick a time here: {BOOKING_URL} {SENDER_NAME} Touch 2 (reply in same thread) Hi {{first_name}}, a quick example: {PROOF_POINTS}. If that's relevant for {{company}}, {CTA}. Touch 3 (reply in same thread) Hi {{first_name}}, a different angle: many {{role}}s tell us {{second_pain_point}}. This short {{resource_name}} explains how others handle it: {{resource_link}} Touch 4 (reply in same thread) Hi {{first_name}}, I don't want to clutter your inbox, so this is my last note. If the timing is wrong, or someone else owns this, just let me know and I'll follow up accordingly. Either way, all the best. Every email footer: {SENDER_NAME}, {COMPANY_NAME}, {COMPANY_ADDRESS}, and {OPT_OUT_LINE} ``` ## 4. What the clone does with leads and replies **Every run, in this order:** 1. **Reads the inbox first**, so nobody gets another email after they have already replied. 2. **Stops immediately** when a lead replies, bounces or opts out. Any reply (except a pure out-of-office) ends the sequence for that lead. 3. **Classifies replies** and acts: | Reply type | What the clone does | |---|---| | **Interested** (wants a call, asks a question, says yes) | Stops the sequence, status "Interested", puts it on the hot list. **Never auto-replies.** | | **Not now** ("check back next quarter") | Stops, status "Not now", creates a follow-up task for the owner in `{NOT_NOW_DELAY}` | | **Not interested** | Stops, status "Not interested", never sequences them again | | **Out of office** | Pauses (does not count as a reply), resumes the day after the return date (or in 7 days if none is given) | | **Unsubscribe / remove me** | Stops, adds the address to `{SUPPRESSION_LIST}`, sets do-not-email in the CRM in the same run | | **Wrong person / referral** | Stops, puts it on the hot list with the referred name. Never emails the referred person automatically. | | **Bounce** | Stops, status "Bounced", flags the email address as invalid | | **Unclear** | Pauses and lists it on the hot list as "Needs review" | 4. **Sends due follow-ups first, then new touch 1 emails**, up to today's cap, inside the lead's business hours (`{SEND_WINDOW}`). 5. **Updates the CRM** after every send: `{SEQUENCE_STEP_FIELD}`, `{SEQUENCE_STATUS_FIELD}`, `{LAST_TOUCH_FIELD}`, plus a logged email activity. **What it never does:** - Never emails existing customers, contacts on open opportunities, or leads owned by someone outside `{SEQUENCE_OWNERS}`. - Never emails anyone on `{SUPPRESSION_LIST}` or flagged do-not-email. - Never invents facts (no made-up mutual connections, fake results or false "following up on our call" subjects). - Never replies to an interested lead, negotiates, quotes prices or books meetings on your behalf. - Never goes over the daily cap, and never sends outside the send window. - Never sends anything until you have approved the templates **and** the first batch. ## 5. Setup walkthrough The quickest path: download **CLONE-INSTRUCTIONS.md** and give it to your clone. It will check what's connected, ask for your settings, show you a plan, and set up what it can after you approve. The steps below are what happens, so you know what to expect. **Step 1: Check requirements (10 min)** Open **REQUIREMENTS.md** and run through the pre-flight checklist. You need Gmail or Outlook for the sending inbox, Salesforce or HubSpot operators with limited write access, and the ability to create scheduled tasks. Ask IT to confirm SPF, DKIM and DMARC are set up for the sending domain. **Step 2: Hand the instructions to your clone (2 min)** Paste or upload CLONE-INSTRUCTIONS.md into a chat with your clone and say: *"Please set up this use case for me. Show me a plan before changing anything."* **Step 3: Review the discovery table (5 min)** The clone reports which skills/operators and connections it already has and which are missing. **Step 4: Answer the setup questions (15–20 min)** See the table in section 6. The value proposition, proof points and lead criteria take the most thought, so prepare them first. **Step 5: Approve the templates (10 min)** The clone drafts the 4 templates from your answers. Edit until you'd be happy to send them yourself. **Step 6: Approve the plan (2 min)** The clone lists exactly what it will attach, create and schedule. Say "yes" only when it looks right. **Step 7: Do your part (15–30 min)** Things only you (or your admins) can do: - Sign in (OAuth) to the sending inbox and the CRM. - Create the three CRM custom fields (or agree to use activities/tasks instead). - Set up the suppression list and share it with the clone. - Confirm sending-domain authentication with IT. **Step 8: Save the skill (5–10 min)** If the clone can't create custom skills directly, it gives you the full skill text in a copy-paste block with exact steps. **Read it before you save it.** **Step 9: Run the test plan (20 min)** Run the whole sequence against test leads that are your own addresses (never real prospects), then reply, unsubscribe and send an out-of-office to check every branch. **Step 10: Approve the first real batch, then go live** The first real run is in review mode: the clone prepares the emails and shows them to you without sending. Once you say "approved", it switches to live sending on the warm-up ramp. ## 6. Placeholders to decide Setup values use `{CURLY_CAPS}`. Per-lead merge fields in templates use `{{double_braces}}` and are filled automatically. | Placeholder | What it means | Example | |---|---|---| | `{CLONE_NAME}` | Your clone's name | "Ava" | | `{SENDER_INBOX}` | The inbox the emails are sent from | you@go.yourcompany.com | | `{SENDER_NAME}` | Name and title in the signature | Jordan Lee, Account Executive | | `{COMPANY_NAME}` | Your company name as it should appear | YourCompany | | `{YOUR_COMPANY_DOMAINS}` | Your own domains (never sequenced) | yourcompany.com, go.yourcompany.com | | `{PRODUCT_NAME}` | What you're selling | "YourCompany Scheduler" | | `{VALUE_PROP}` | One-sentence value proposition | "cut no-show rates by automating reminders" | | `{PROOF_POINTS}` | Results you're allowed to cite | "a 40-person clinic cut no-shows by 30% in 2 months" | | `{CTA}` | The single ask | "book a 20-minute call" | | `{BOOKING_URL}` | Your booking link | yourcompany.com/meet/jordan | | `{LEAD_CRITERIA}` | Which leads are eligible | Lead status = New AND lead source in (Webinar, List import) | | `{DAILY_LEAD_VOLUME}` | New leads expected per day | 15 | | `{SEQUENCE_OWNERS}` | Lead owners whose leads may be sequenced | Jordan Lee (or "unassigned + me") | | `{CUSTOMER_DEFINITION}` | How your CRM marks a current customer | Account Type = Customer | | `{SEQUENCE_TIMING}` | Days for touches 1 to 4 | Day 0, 3, 7, 14 (business days) | | `{DAILY_CAP}` | Max emails per day after warm-up (all touches) | 40 | | `{WARMUP_PLAN}` | Ramp to the cap | Week 1: 10/day, week 2: 20, week 3: 30, then 40 | | `{SEND_WINDOW}` | Allowed sending hours in the lead's time zone | 8:00–17:00, Mon–Fri | | `{DEFAULT_TIME_ZONE}` | Used when the lead's time zone is unknown | America/Chicago | | `{RUN_TIMES}` | When the skill runs | 8:30 AM and 1:30 PM your time, Mon–Fri | | `{HOT_LIST_RECIPIENTS}` | Who gets the daily hot list | you@yourcompany.com | | `{NOT_NOW_DELAY}` | When to follow up on "not now" | 90 days (or the date they gave) | | `{SUPPRESSION_LIST}` | Where opted-out and blocked addresses live | "Do Not Email" spreadsheet, or a CRM list | | `{COMPANY_ADDRESS}` | Physical mailing address for the footer | 100 Main St, Suite 200, Springfield, ST 00000 | | `{OPT_OUT_LINE}` | Opt-out sentence in every email | "Not relevant? Reply 'unsubscribe' and I won't email again." | | `{EU_POLICY}` | What to do with EU/UK leads | "Skip unless lead source is documented as legitimate interest" | | `{SEQUENCE_STEP_FIELD}` | CRM field: current touch (0–4) | "Sequence Step" | | `{SEQUENCE_STATUS_FIELD}` | CRM field: sequence status | "Sequence Status" (Active, Paused, Interested, …) | | `{LAST_TOUCH_FIELD}` | CRM field: date of last email | "Last Sequence Touch" | Tip: with a 4-touch sequence, each new lead costs up to 4 sends. At 10 new leads a day you'll reach about 30–40 sends a day once all touches overlap. Set `{DAILY_LEAD_VOLUME}` and `{DAILY_CAP}` together. ## 7. What to expect day to day - **Morning run ({RUN_TIMES}, first time):** the clone processes overnight replies, sends due follow-ups and new intros, then emails the **hot list** to `{HOT_LIST_RECIPIENTS}`: interested replies, referrals and "needs review" items, each with the original message, lead details and a suggested next step. It also includes a short run report (sent, paused, stopped, skipped and why, cap usage, source status). - **Afternoon run:** same processing. It only emails you if there are new hot replies or a problem (for example, the CRM was unavailable). - **Your part:** 5–15 minutes a day. Reply personally to hot leads from your own inbox, ideally the same day. - **First weeks:** sending volume follows the warm-up ramp, so results build gradually. That's on purpose. - **Weekends and holidays:** nothing is sent unless you change the schedule. ## 8. Customizing **Templates and tone.** Ask the clone to edit the templates, e.g. "Make touch 1 shorter", "Use a more casual tone", or "Add a P.S. with our case study". Any template change goes back through your approval. **Timing and length.** Change `{SEQUENCE_TIMING}` (e.g. day 0, 2, 5, 10) or drop to 3 touches. Don't go above 5. **Lead criteria.** Narrow `{LEAD_CRITERIA}` by industry, title, company size or region. Different segments can get different value propositions and templates. **Hot list delivery.** Add a chat alert (Slack or Teams) for each interested reply, or send the hot list to a team alias. **Research depth.** Turn light research off (templates only, faster) or on (one specific line per lead from the company website or a research operator). ## 9. Known gotchas - **Test the full sequence on yourself first.** Use your own addresses (a work and a personal one) as test leads and go through all 4 touches with a shortened timing. You'll catch broken merge fields, threading problems and awkward wording before a prospect does. - **Check formatting in real inboxes.** Look at the test emails in Gmail and Outlook, on desktop and phone. Plain text, short paragraphs and no images or heavy HTML look more personal and land in the inbox more often. - **Don't re-sequence existing customers.** Imported lists often contain current customers or people already in a deal. The skill checks for customer accounts, open opportunities and other owners, but only if your CRM data is accurate. Fix duplicates and missing company domains first. - **Lead source quality varies.** Imported or scraped data can be stale or wrong. Watch bounce and reply rates per lead source and drop sources that perform badly. - **Respect sending limits.** Your email provider has daily limits, and cold outreach should stay far below them. Keep the warm-up ramp and the daily cap. Sudden volume spikes get mailboxes flagged. - **Bounces hurt your sender reputation.** More than about 2–3% bounces is a warning sign. Use clean, recent lists, and let the clone skip obviously invalid or role addresses (info@, sales@) before they enter the sequence. - **Authenticate your domain.** SPF, DKIM and DMARC must be set up for the sending domain. Many teams use a secondary sending domain (e.g. go.yourcompany.com) to protect the main domain. The clone can't change DNS; IT has to do this. - **Replies can arrive in other places.** People reply from a different address, forward the email to a colleague who replies, or start a new thread. The skill checks the sender's domain and the subject, but some replies will land in "Needs review". Skim your inbox too. - **Out-of-office replies are not real replies.** The skill pauses on OOO instead of stopping, but unusual auto-replies (ticket systems, "this mailbox is not monitored") can be misread. Check the run report's "auto-reply" section in the first weeks. - **Use exact skill/operator names** as they appear in your skill catalog. Names can differ between workspaces; the clone checks them during discovery. - **Read every instruction before saving it into a skill.** You're responsible for what your clone sends. Have someone check the compliance rules (opt-out, address, EU leads) against your company's policies. ## 10. FAQ **Does this work with my CRM?** It works with **Salesforce** and **HubSpot**, the CRMs with operators on the platform today. The clone needs read access and permission to update a few lead or contact fields. See the mapping in REQUIREMENTS.md. **Whose inbox do the emails come from?** From `{SENDER_INBOX}`: usually your own mailbox or a dedicated sales mailbox on a secondary domain, connected to the clone through sign-in. Replies go back to that inbox, which the clone reads. **Does it track opens and clicks?** No. Open and click tracking adds tracking pixels and rewritten links that hurt deliverability, and opens are unreliable anyway. The sequence is driven by replies. **Will it reply to interested prospects for me?** No, on purpose. Interested replies go on the hot list and you respond personally. That's where deals are won or lost. **Is this legal?** Cold B2B email is allowed in many places if you follow the rules: honest sender and subject lines, a physical address, a working opt-out that you honor promptly, and (for EU/UK contacts) a lawful basis such as documented legitimate interest. Rules differ by country. This use case builds in the basics, but it isn't legal advice: check with whoever handles compliance at your company. **What if a lead is in the CRM as a contact, not a lead?** By default only leads matching `{LEAD_CRITERIA}` are sequenced. You can include contacts, but the customer and open-deal checks matter even more then. **Can several reps use it?** Yes, but set it up once per sender (each with their own inbox, owner filter and cap). Never let two clones sequence the same leads. **How much time does it take once running?** 5–15 minutes a day to answer hot replies, plus a weekly look at the run reports. ## 11. Troubleshooting | Symptom | Likely cause | Fix | |---|---|---| | No emails sent | Still in review mode, cap reached, outside send window, or no eligible leads | Check the run report; approve the first batch; check `{LEAD_CRITERIA}` | | No hot list email | Scheduled task paused or wrong time zone | Ask the clone to list its scheduled tasks; check `{RUN_TIMES}` | | A customer was emailed | Duplicate record, missing company domain, or wrong `{CUSTOMER_DEFINITION}` | Apologize personally, add them to `{SUPPRESSION_LIST}`, fix the CRM data and the rule | | Follow-ups start a new thread | Original message not found, or subject changed | Check the sending inbox's Sent folder is readable; keep follow-up subjects as "Re:" | | Lead got a follow-up after replying | Reply came from another address or a new thread | Mark that lead stopped; add the alternate address to the CRM record | | Many bounces | Stale or low-quality list | Pause the source, clean the list, check reputation | | Emails land in spam | Missing SPF/DKIM/DMARC, volume too fast, links/images | Fix authentication, slow the ramp, use plain text | | "CRM: unavailable" in report | Connection expired or missing write permission | Re-run sign-in; confirm the clone can update the sequence fields | | Unsubscribed person still flagged active | CRM update failed after retry | The skill reports this; set do-not-email manually, then check permissions | | OOO treated as a reply (or the other way round) | Unusual auto-reply wording | Correct the status manually; ask the clone to add the phrase to its OOO rules | --- **Version:** 1.1.0 · **Last updated:** 2026-10-22 · Part of the Clone Use Case Library.