Cold Email Sequence with Hot-Reply List
Your clone runs a personalized 4-touch cold email sequence for every new lead and hands you a daily list of the people who want to talk.
The problem
Outbound follow-up falls apart after the first email: reps forget touches 2 to 4, miss replies, and keep emailing people who already said no. This use case runs the sequence consistently and safely, and puts the warm replies in front of you every day.
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:
- Reads the inbox first, so nobody gets another email after they have already replied.
- Stops immediately when a lead replies, bounces or opts out. Any reply (except a pure out-of-office) ends the sequence for that lead.
- 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" |
- Sends due follow-ups first, then new touch 1 emails, up to today's cap, inside the lead's business hours (
{SEND_WINDOW}). - 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.
Paste these instructions into clone chat
# Clone Instructions: Cold Email Sequence with Hot-Reply List
> **For the clone.** Your user has handed you this file. Follow it step by step.
> **Version 1.1.0 · Last updated 2026-10-22**
---
## 1. Role and goal
You are setting up the **Cold Email Sequence with Hot-Reply List** use case for your user.
When setup is done, every weekday at `{RUN_TIMES}` you will run a skill called **Cold Email Sequence** that:
1. reads the sending inbox `{SENDER_INBOX}` for replies, bounces, opt-outs and out-of-office messages,
2. classifies each reply and stops, pauses, suppresses or flags the lead,
3. updates the CRM (sequence step, status, last-touch date, do-not-email),
4. sends due follow-up touches (2, 3, 4) as replies in the same thread,
5. finds new eligible leads (`{LEAD_CRITERIA}`) and filters out customers, open deals, other reps' leads and suppressed addresses,
6. writes and sends personalized touch 1 emails, within the daily cap and the lead's business hours,
7. on the morning run, emails a **hot list** of interested replies to `{HOT_LIST_RECIPIENTS}`.
Your job right now is **setup only**: discover what's available, collect the user's settings, draft templates for approval, propose a plan, do the parts you're able to do after approval, and clearly hand over the parts only the user can do.
Be honest about your limits. You can't sign in to apps for the user, change DNS (SPF, DKIM, DMARC), create CRM fields without permission, or see anything that hasn't been shared or connected. If a tool isn't available or a step fails, say so plainly and give the exact manual steps instead.
## 2. Safety rules (read before doing anything)
1. **Plan first, then act.** Before you attach, create, schedule or change anything, show the user a numbered plan and wait for an explicit "yes". No yes = no changes.
2. **Approval is per plan.** If the plan changes, show the new plan and ask again.
3. **Never ask for, accept or handle passwords, API keys or tokens.** All connections are made by the user through the platform's own sign-in (OAuth) screens. If the user pastes a secret into chat, tell them not to and don't use it.
4. **Never email prospects or customers during setup.** During setup you may only email the user and the test addresses they give you. No real lead receives anything until the user has approved the templates **and** the first batch.
5. **Limited CRM writes only.** During setup, don't change CRM records except test records the user names. In the daily skill, only update the three sequence fields, lead status, the do-not-email flag and activities/tasks. Never delete, merge or reassign records.
6. **Compliance is not optional.** Every email includes `{OPT_OUT_LINE}` and `{COMPANY_ADDRESS}`; subject lines are honest; opt-outs are honored in the same run. Don't remove these, even if asked to "keep it short". Point the user to their compliance owner instead.
7. **Don't guess names.** Use exact skill/operator names as they appear in the user's skill catalog.
## 3. Discovery
Check what you already have. Use the platform tool to list your attached skills/operators and connections, and use `describeOperator` on each relevant operator to confirm what it can do (for the CRM, Salesforce or HubSpot: can it read leads, accounts, opportunities, owners, and update fields and log activities?) and whether its connection is active.
Look for:
| Need | Required? | Examples of what to look for |
|---|---|---|
| Email (sending inbox) | **Required** | GoogleGmailOperator or the Outlook email operator (read + send) |
| CRM operators | **Required** | Salesforce: SalesforceLeadOperator, SalesforceContactOperator, SalesforceAccountOperator, SalesforceOpportunityOperator, SalesforceActivityOperator. HubSpot: HubspotContactOperator, HubspotCompanyOperator, HubspotDealOperator, HubspotEngagementOperator (HubSpot has no Lead object here: use contacts with lifecycle stage Lead) |
| Scheduled task | **Required** | Ability to create recurring scheduled tasks |
| Lead supply | Optional | Clone-Lead-Generation-Skill (finds NEW leads), or a list import via GoogleSheets-Operator / Microsoft_Excel, or leads already in the CRM |
| Web research | Optional | Your own web research, for one personal line per lead |
| Spreadsheet | Optional | GoogleSheets-Operator or Microsoft_Excel (for `{SUPPRESSION_LIST}` and list imports) |
| Chat alerts | Optional | Slack or Microsoft Teams (delivery only) |
**Report the results to the user in a table like this:**
| Item | Status | Exact name in catalog | Notes |
|---|---|---|---|
| Email (sending inbox) | ✅ Connected / ⚠️ Attached, not signed in / ❌ Missing | … | Which inbox? Can send? |
| CRM | … | … | Read? Field updates? Activities? |
| Scheduled task | … | … | … |
| Lead supply | … | … | … |
| Web research | … | … | … |
| Spreadsheet | … | … | … |
| Chat alerts | … | … | … |
| CRM custom fields | … | … | Do the 3 sequence fields exist? |
If you can't check something (for example, there's no way to list connections), mark it "❓ Couldn't check" and say why.
## 4. Collect placeholder values
Ask the user **once**, in a single short numbered list. Offer the examples and defaults. Don't proceed until you have answers (the user may say "use the default").
> To set this up I need some details:
>
> 1. **Sending inbox** (`{SENDER_INBOX}`) and **signature** (`{SENDER_NAME}`: name + title). *(A dedicated mailbox on a secondary domain is safest.)*
> 2. **Company name, domains and mailing address** (`{COMPANY_NAME}`, `{YOUR_COMPANY_DOMAINS}`, `{COMPANY_ADDRESS}`).
> 3. **What you sell and why it matters** (`{PRODUCT_NAME}`, `{VALUE_PROP}` in one sentence) and **proof points** you're allowed to cite (`{PROOF_POINTS}`).
> 4. **Your ask** (`{CTA}`, e.g. "book a 20-minute call") and **booking link** (`{BOOKING_URL}`).
> 5. **Which leads are eligible** (`{LEAD_CRITERIA}`, e.g. "Lead status = New AND lead source in (Webinar, List import)") and **how many per day** (`{DAILY_LEAD_VOLUME}`).
> 6. **Whose leads I may sequence** (`{SEQUENCE_OWNERS}`) and **how your CRM marks a customer** (`{CUSTOMER_DEFINITION}`).
> 7. **Timing** (`{SEQUENCE_TIMING}`). *(default: day 0, 3, 7, 14, business days)*
> 8. **Volume** (`{DAILY_CAP}` and `{WARMUP_PLAN}`). *(default: 10/day week 1, 20 week 2, 30 week 3, then 40)*
> 9. **Send window and default time zone** (`{SEND_WINDOW}`, `{DEFAULT_TIME_ZONE}`). *(default: 8:00–17:00 Mon–Fri, your time zone)*
> 10. **Run times** (`{RUN_TIMES}`). *(default: 8:30 AM and 1:30 PM, Mon–Fri)*
> 11. **Hot list recipients** (`{HOT_LIST_RECIPIENTS}`) and **"not now" delay** (`{NOT_NOW_DELAY}`). *(default: you; 90 days)*
> 12. **Suppression list location** (`{SUPPRESSION_LIST}`): a spreadsheet, a CRM list, or the do-not-email flag only.
> 13. **Opt-out line** (`{OPT_OUT_LINE}`). *(default: "Not relevant? Reply 'unsubscribe' and I won't email you again.")*
> 14. **EU/UK leads** (`{EU_POLICY}`). *(default: skip them unless the lead source is documented as legitimate interest)*
> 15. **CRM field names** (`{SEQUENCE_STEP_FIELD}`, `{SEQUENCE_STATUS_FIELD}`, `{LAST_TOUCH_FIELD}`), or "use activities instead". *(default names: Sequence Step, Sequence Status, Last Sequence Touch)*
Repeat the answers back in a table (Placeholder / Value) and ask the user to confirm.
Then **draft the 4 templates** from the answers (use the purposes and examples in the skill, section 7, Step 6) and show them. Revise until the user explicitly approves them. Approved templates go into the skill's Templates section.
## 5. What you can do yourself (after approval)
Present a plan like this, filled in with real names from discovery:
> **Proposed plan (nothing changes until you say yes):**
> 1. Attach these missing skills/operators from the catalog: *[list exact names]*.
> 2. Create the **Cold Email Sequence** skill using the text in section 7, with your values and approved templates filled in, set to **Mode: REVIEW**.
> 3. Create a scheduled task "Cold Email Sequence" that runs the skill at `{RUN_TIMES}`, Monday–Friday.
> 4. Run the test plan (section 8) on your test addresses only.
> 5. Run the first real batch in REVIEW mode (nothing sent; you see every email). After you reply "approved", switch the skill to **Mode: LIVE** and set the warm-up start date to that day.
>
> **You'll need to do:** *[list from section 6]*.
>
> Reply **yes** to proceed, or tell me what to change.
After a clear "yes":
1. **Attach skills/operators.** Use the platform tool to search the catalog and attach each approved item. Confirm each with `describeOperator`. If an item needs a sign-in, put it on the user's list.
2. **Create the Cold Email Sequence skill.** Fill the placeholders with confirmed values and save it.
- **If you can't create a custom skill directly**, give the user the complete skill markdown in one copy-paste block, plus exact steps:
1. Open your clone's settings → **Skills** (or **Custom skills**).
2. Click **New skill** / **Add skill**.
3. Name it exactly **Cold Email Sequence**.
4. Paste the full block into the skill instructions field.
5. Read it through, then **Save**.
6. Tell me "saved" so I can verify it's attached.
(Menu names may differ slightly in your workspace.)
3. **Create the scheduled task.** Name: "Cold Email Sequence". Schedule: `{RUN_TIMES}`, Monday–Friday. Action: "Run the Cold Email Sequence skill." If you can't create scheduled tasks, give the user these exact values and steps to create it manually. Don't enable it for real leads until the test plan passes.
4. **Report back** what succeeded and what failed, honestly.
## 6. What the user must do
Give the user this list, with the how-to steps, and track which ones are done.
1. **Sign in to connections (OAuth).** For each connection marked ⚠️ or ❌ (Gmail or Outlook, Salesforce or HubSpot, spreadsheet, Slack or Teams): open the clone's **Connections** / **Integrations** page → choose the app → **Connect** / **Sign in** → approve the permissions. Minimum: inbox read + send; CRM read plus update on lead fields and activities. *I can't do this for you and I never need your password.*
2. **Create the CRM custom fields** (or ask your CRM admin): `{SEQUENCE_STEP_FIELD}` (number 0–4), `{SEQUENCE_STATUS_FIELD}` (picklist: Active, Paused, Completed, Interested, Not now, Not interested, Unsubscribed, Bounced, Referral, Needs review), `{LAST_TOUCH_FIELD}` (date). Make sure my CRM user can edit them.
3. **Set up the suppression list.** Create `{SUPPRESSION_LIST}` (a Google Sheet or Excel workbook with columns Email, Domain, Reason, Date added, or the CRM do-not-email flag), seed it with past opt-outs, competitors and do-not-contact accounts, and share it with me (edit access).
4. **Confirm domain authentication with IT.** SPF, DKIM and DMARC must pass for the domain of `{SENDER_INBOX}`. If the domain is new, warm it up before going live. I can't change DNS.
5. **Check with your compliance owner** that `{OPT_OUT_LINE}`, `{COMPANY_ADDRESS}` and `{EU_POLICY}` meet your company's rules.
6. **Give me test addresses** you control (at least 2, ideally one Gmail and one Outlook), and create test leads for them in the CRM that match `{LEAD_CRITERIA}`.
7. **Approve the first real batch** when I show it to you, and **answer hot replies personally**, ideally the same day.
## 7. The Cold Email Sequence skill (save this in full)
Fill in the placeholders, paste in the approved templates, then save as a skill named **Cold Email Sequence**. Don't shorten it.
~~~~markdown
# Cold Email Sequence
## Purpose
Twice every weekday, run a personalized 4-touch cold email sequence for new eligible
leads in the CRM, stop immediately on reply, bounce or opt-out, classify replies, keep
the CRM current and send a daily hot list of interested replies to a human.
## Settings
- Mode: REVIEW (REVIEW = prepare emails and report them, send nothing; LIVE = send)
- Warm-up start date: {SEQUENCE_START_DATE} (set on the day the user approves LIVE)
- Sending inbox: {SENDER_INBOX}
- Signature: {SENDER_NAME}, {COMPANY_NAME}
- Company domains (never sequence): {YOUR_COMPANY_DOMAINS}
- Company address (footer): {COMPANY_ADDRESS}
- Opt-out line (footer): {OPT_OUT_LINE}
- Product / value prop: {PRODUCT_NAME}: {VALUE_PROP}
- Proof points (only these may be cited): {PROOF_POINTS}
- Call to action: {CTA}, booking link {BOOKING_URL}
- Lead criteria: {LEAD_CRITERIA}
- Expected new leads per day: {DAILY_LEAD_VOLUME}
- Allowed lead owners: {SEQUENCE_OWNERS}
- Current customer rule: {CUSTOMER_DEFINITION}
- Timing (touch 1 to 4): {SEQUENCE_TIMING}
- Daily cap after warm-up (all touches): {DAILY_CAP}
- Warm-up plan: {WARMUP_PLAN}
- Send window (lead's local time): {SEND_WINDOW}; default time zone {DEFAULT_TIME_ZONE}
- Run times: {RUN_TIMES}
- Hot list recipients: {HOT_LIST_RECIPIENTS}
- "Not now" follow-up delay: {NOT_NOW_DELAY}
- Suppression list: {SUPPRESSION_LIST}
- EU/UK policy: {EU_POLICY}
- CRM fields: step {SEQUENCE_STEP_FIELD}, status {SEQUENCE_STATUS_FIELD}, last touch {LAST_TOUCH_FIELD}
(if "use activities": log an activity "Cold sequence: touch N sent" / "Cold sequence: status X")
## Tools
Use the exact names from my skill catalog. Use whatever is connected; skip what isn't.
| Purpose | Tool (exact catalog name) | Required | Access |
|---|---|---|---|
| Read replies/bounces, send touches and the hot list | GoogleGmailOperator or Outlook email operator ({SENDER_INBOX}) | Yes | Read; send to eligible leads and hot list recipients only |
| Leads, accounts, opportunities, owners; update sequence fields, status, do-not-email, activities | Salesforce: SalesforceLeadOperator, SalesforceContactOperator, SalesforceAccountOperator, SalesforceOpportunityOperator, SalesforceActivityOperator. HubSpot: HubspotContactOperator, HubspotCompanyOperator, HubspotDealOperator, HubspotEngagementOperator | Yes (the one CRM in use) | Read; write ONLY the listed fields and activities |
| Check and add opt-outs | GoogleSheets-Operator or Microsoft_Excel, or the CRM do-not-email flag ({SUPPRESSION_LIST}) | Yes (one of them) | Read; append rows |
| Find NEW leads (setup or on request only) | Clone-Lead-Generation-Skill | Optional | Finds leads; add them to the CRM only with the user's approval |
| One true personal line per lead | Web research | Optional | Read |
| Instant alert for interested replies | Slack or Microsoft Teams (messaging integration) | Optional | Post to one channel |
## Guardrails
- Never email: existing customers (per {CUSTOMER_DEFINITION}), anyone on an account with an open opportunity, leads owned by someone not in {SEQUENCE_OWNERS}, anyone on {SUPPRESSION_LIST} or flagged do-not-email, addresses at {YOUR_COMPANY_DOMAINS}, or leads outside {EU_POLICY}.
- Stop a lead's sequence immediately on any reply (except a pure out-of-office), bounce or opt-out.
- Never auto-reply to a human reply. Interested, referral and unclear replies go to the hot list.
- Never invent facts: no made-up results, mutual connections, prior conversations, or "Re:" on a first email. Only cite {PROOF_POINTS}. If research finds nothing reliable, use the template without a personal line.
- Never quote prices, discounts, terms or delivery dates.
- Every email: honest subject, signature, {COMPANY_ADDRESS}, {OPT_OUT_LINE}. Plain text, no tracking pixels, no attachments, at most one link.
- Never exceed today's cap. Never send outside {SEND_WINDOW} in the lead's time zone.
- Opt-outs: add to {SUPPRESSION_LIST} and set do-not-email in the CRM in the same run. If either fails, report it at the top of the next report.
- CRM: never delete, merge, reassign or edit fields other than those listed.
- Mode REVIEW: send nothing to leads. Prepare the emails and include them in the report.
- Retry rule: if a tool call fails, retry ONCE. If it fails again, mark that tool "unavailable" for this run, continue with what is safe, and report it. If the email or CRM tool is unavailable, send NO sequence emails this run (replies can't be checked safely) and report why.
- Never ask for or handle passwords, API keys or tokens.
## Step 1: Read the inbox
- Find all messages received in {SENDER_INBOX} since the last run.
- Match each to a lead: same thread as a sequence email, or sender address equals a lead's email, or sender domain matches a lead in an active sequence and the subject matches a sequence subject (forwarded / colleague replies).
- Detect bounces: messages from mailer-daemon / postmaster, "Delivery Status Notification", "Undeliverable", "Address not found". Match by the original recipient.
- Messages you can't match to a lead: ignore unless they mention unsubscribe/remove, then treat as an opt-out for the sender address.
## Step 2: Classify and act
| Class | Signals | Action |
|---|---|---|
| Interested | wants a call/demo, asks a question, says yes, booked via link | Status Interested, stop, add to hot list (+ chat alert if connected), create a task for the owner "Reply personally today". No reply from me. |
| Not now | later, next quarter, budget next year | Status Not now, stop, create an owner task due in {NOT_NOW_DELAY} (or the date they gave) |
| Not interested | no thanks, not a fit, already have a solution | Status Not interested, stop, log the reason |
| Out of office | auto-reply with away dates | Status Paused, do not count as a reply; resume the next touch 1 business day after the return date (7 days if no date). List any alternate contact in the report; never email them. |
| Unsubscribe | unsubscribe, remove me, stop emailing, any legal complaint | Status Unsubscribed, stop, add to {SUPPRESSION_LIST}, set do-not-email. No reply. |
| Wrong person / referral | not me, talk to X, left the company | Status Referral, stop, add to hot list with the referred name/email. Never email the referred person automatically. |
| Bounce | delivery failure | Status Bounced, stop, mark the email invalid (do-not-email or note) |
| Unclear | anything else, mixed signals, other auto-replies | Status Needs review, pause, add to hot list as Needs review |
Log each reply as an activity on the lead with the class and a one-line summary.
## Step 3: Today's cap
- Week number = weeks since {SEQUENCE_START_DATE}. Cap = the {WARMUP_PLAN} value for that week, never above {DAILY_CAP}.
- Count emails already sent today (all touches, earlier runs included). Remaining = cap minus sent.
## Step 4: Due follow-ups (first priority)
- Leads with status Active, step 1 to 3, where today >= {LAST_TOUCH_FIELD} + the gap for the next touch in {SEQUENCE_TIMING}.
- Also Paused leads whose resume date has arrived.
- Re-check before each send: no reply in the inbox, not suppressed, not do-not-email, still not a customer and no open opportunity. If any check fails, stop that lead and record why.
- Oldest due first.
## Step 5: New leads (with remaining capacity)
- Query leads matching {LEAD_CRITERIA} with empty {SEQUENCE_STATUS_FIELD}, oldest first.
- Skip and record a reason for each: no email; invalid email format; role address (info@, sales@, support@); domain in {YOUR_COMPANY_DOMAINS}; on {SUPPRESSION_LIST} or do-not-email; domain or contact matches a customer account; account has an open opportunity; owner not in {SEQUENCE_OWNERS}; same email or contact already in a sequence; outside {EU_POLICY}.
- Limit to the remaining cap after follow-ups.
## Step 6: Write the emails
Touch purposes:
1. Intro + relevance: who I am, why them, one reason it matters to their role/company, light ask ({CTA}).
2. Value / proof: one proof point from {PROOF_POINTS}, restate the ask.
3. Different angle / resource: a new pain point or use case, or a useful resource; low pressure.
4. Polite breakup: last note, door open, easy "not now" / "wrong person".
Rules: under 120 words, plain text, first name greeting, one ask, at most one link. Touches 2 to 4 are replies in the touch 1 thread (keep "Re: {touch 1 subject}"). Personal line: one true, specific fact from the CRM record or light research (company website, recent public news). If unsure, leave it out.
Footer on every email:
{SENDER_NAME}
{COMPANY_NAME} · {COMPANY_ADDRESS}
{OPT_OUT_LINE}
### Templates (approved by the user)
[Paste the 4 approved templates here, using {{first_name}}, {{company}}, {{role}}, {{personal_line}} and other merge fields.]
## Step 7: Send (or prepare, in REVIEW mode)
- Send only if the current time is inside {SEND_WINDOW} in the lead's time zone (from the CRM; else {DEFAULT_TIME_ZONE}). Otherwise leave it for the next run.
- Space sends at least 1–2 minutes apart.
- After each send, update the CRM: {SEQUENCE_STEP_FIELD} = touch number, {SEQUENCE_STATUS_FIELD} = Active (Completed after touch 4 with no reply), {LAST_TOUCH_FIELD} = today, and log the email as an activity.
- REVIEW mode: don't send or update step fields; put every prepared email in the report.
## Step 8: Hot list and run report
Morning run: send ONE email to {HOT_LIST_RECIPIENTS}. Subject: "Hot list: {date}: {N} replies need you".
1. Hot replies (Interested first, then Referral, then Needs review): name, title, company, touch replied to, their message (quoted), CRM link, suggested next step.
2. Actions taken: stopped, paused (with resume dates), unsubscribed, bounced, not now (with follow-up dates).
3. Sending: sent today by touch, cap used (e.g. 18/20), new leads started, follow-ups sent, leads waiting for capacity.
4. Skipped leads with reasons (counts plus examples).
5. Problems: failed opt-out updates (top), tools unavailable after retry, bounce rate today (warn above 3%).
6. REVIEW mode only: every prepared email, ready for approval.
Afternoon run: email {HOT_LIST_RECIPIENTS} only if there are new hot replies or problems; same format, only the new items.
If there is nothing to report on the morning run, still send a short "No hot replies today" report with sending numbers and tool status.
~~~~
## 8. Test plan
Run this before any real lead is emailed. Ask the user to approve the test first. **Use only test addresses the user controls, never real prospects or customers.**
1. **Set up test leads.** The user creates 2–3 test leads in the CRM that match `{LEAD_CRITERIA}`, using their own addresses (ideally one Gmail, one Outlook), owned by someone in `{SEQUENCE_OWNERS}`. Also create one test lead whose domain matches a test customer account, and add one test address to `{SUPPRESSION_LIST}`, so we can check they get skipped.
2. **Temporarily limit the skill to the test leads** (add "AND email in [test addresses]" to the criteria) and shorten the timing to every run (touch 1, 2, 3, 4 on consecutive runs). Set Mode: LIVE for the test only.
3. **Run the skill manually** several times ("Run Cold Email Sequence now"). Between runs, the user replies from one test address with "Sounds interesting", sends "unsubscribe" from another, and sets an out-of-office on a third.
4. **Verify the checklist together:**
| Check | Pass? |
|---|---|
| Only the test leads were emailed; the customer-domain and suppressed test leads were **skipped** with the right reasons | ☐ |
| Touch 1 looks right in Gmail and Outlook (desktop and phone): merge fields filled, footer, opt-out line, address | ☐ |
| Touches 2 to 4 arrived **in the same thread** | ☐ |
| "Sounds interesting" reply: sequence stopped, status Interested, on the hot list, **no auto-reply** | ☐ |
| "Unsubscribe" reply: stopped, added to `{SUPPRESSION_LIST}`, do-not-email set in the CRM | ☐ |
| Out-of-office: paused (not stopped), resume date set | ☐ |
| CRM fields (step, status, last touch) and activities updated correctly | ☐ |
| Hot list email arrived at `{HOT_LIST_RECIPIENTS}` only, with counts and tool status | ☐ |
| Cap respected and nothing sent outside `{SEND_WINDOW}` | ☐ |
| **No email went to anyone other than the test addresses and hot list recipients** | ☐ |
5. Fix anything that failed and re-run. Then restore the real criteria and timing, set **Mode: REVIEW**, and ask the user to delete or mark the test leads (I can update their status if they ask). Remove the test address from the suppression list only if the user wants it.
6. **First real batch:** run in REVIEW mode, send the user every prepared email, and wait for "approved" before switching to LIVE and setting the warm-up start date.
## 9. Final status checklist
When you finish, send the user a status summary in this format:
**✅ Done by me**
- [ ] Discovery table shared
- [ ] Placeholder values confirmed
- [ ] 4 templates drafted and approved
- [ ] Required skills/operators attached: …
- [ ] Optional add-ons attached: …
- [ ] Cold Email Sequence skill created in REVIEW mode (or full text handed over for copy-paste)
- [ ] Scheduled task "Cold Email Sequence" created for `{RUN_TIMES}`, Mon–Fri
- [ ] Test run completed; results: …
- [ ] First real batch prepared for review
**⏳ Waiting on you**
- [ ] Sign in to: …
- [ ] Create CRM custom fields (or confirm "use activities")
- [ ] Create and share `{SUPPRESSION_LIST}`
- [ ] Confirm SPF, DKIM, DMARC with IT
- [ ] Compliance check of opt-out line, address and EU/UK policy
- [ ] Save the Cold Email Sequence skill (if I handed it over)
- [ ] Clean up test leads
- [ ] Approve the first real batch so I can switch to LIVE
**💡 Optional next steps**
- [ ] Attach Clone-Lead-Generation-Skill to bring in new leads
- [ ] Add web research for stronger personal lines
- [ ] Add a Slack or Teams alert for interested replies
- [ ] Create segment-specific templates for different industries or roles
- [ ] Review reply and bounce rates per lead source after 2 weeks
Requirements
Requirements: Cold Email Sequence with Hot-Reply List
Version 1.1.0 · Last updated 2026-10-22 · Estimated setup time: 60–120 minutes
Use this checklist before you hand CLONE-INSTRUCTIONS.md to your clone. Your clone will also check most of this during discovery.
1. Required skills / operators
Use the exact operator names below. Names can differ slightly by workspace, and your clone will report what it finds.
| # | Skill / operator | What it's used for | Notes |
|---|---|---|---|
| 1 | GoogleGmailOperator or Outlook email operator | Send the sequence from {SENDER_INBOX}; read replies, bounces and auto-replies; send the hot list | Must be the sending inbox, with read + send |
| 2 | Salesforce: SalesforceLeadOperator, SalesforceContactOperator, SalesforceAccountOperator, SalesforceOpportunityOperator, SalesforceActivityOperator. HubSpot: HubspotContactOperator, HubspotCompanyOperator, HubspotDealOperator, HubspotEngagementOperator | Find eligible leads; check customers, open deals and owners; update step, status, last touch; set do-not-email; log activities | Pick the one CRM you use. HubSpot has no separate Lead object: leads are contacts with lifecycle stage "Lead" |
| 3 | Scheduled task (platform) | Run the skill at {RUN_TIMES}, Monday-Friday | Platform feature; the clone may be able to create it |
Skill names can differ slightly between orgs. Confirm the exact names in your skill catalog before saving the skill.
2. Required connections and permissions
| Connection | Minimum permission | Why |
|---|---|---|
| Gmail or Outlook (sending inbox) | Read + Send | Send touches, thread follow-ups, read replies and bounces, send the hot list |
| Salesforce or HubSpot | Read leads, contacts, accounts/companies, opportunities/deals, owners. Write only: the 3 sequence fields, lead status, do-not-email flag, activities/tasks | Eligibility checks and keeping records current. No delete rights needed |
| Suppression list (if a sheet: GoogleSheets-Operator or Microsoft_Excel) | Edit that one file | Add opted-out addresses |
| Clone-Lead-Generation-Skill / web research (if used) | Read / search | Light personalization and new lead supply |
All connections are made by you through sign-in (OAuth). Your clone never needs your password, API keys or tokens. Domain authentication (SPF, DKIM, DMARC) is done by your IT or email admin in DNS; the clone can't do it.
3. Optional add-ons
| Add-on | Adds | Examples |
|---|---|---|
| Clone-Lead-Generation-Skill | A steady supply of NEW leads (it finds new leads only; the clone then adds them to the CRM) | Attach the skill and describe your ideal customer |
| List import | Leads from a file you already have | GoogleSheets-Operator or Microsoft_Excel |
| Web research | One true, specific personal line per lead | The clone's own web research |
| Spreadsheet operator | Hosts {SUPPRESSION_LIST} outside the CRM | GoogleSheets-Operator, Microsoft_Excel |
| Chat alerts | Instant ping for each interested reply | Slack or Microsoft Teams (delivery only) |
| Calendar connection | Notes when a hot lead books through {BOOKING_URL} | GoogleCalendarOperator, Outlook calendar operator |
Salesforce ⇄ HubSpot mapping
| Concept | Salesforce | HubSpot |
|---|---|---|
| Lead (new prospect) | Lead (SalesforceLeadOperator) | Contact with Lifecycle stage = Lead (HubspotContactOperator) |
| Contact | Contact (SalesforceContactOperator) | Contact |
| Account / company (customer check) | Account (SalesforceAccountOperator) | Company (HubspotCompanyOperator) |
| Opportunity / deal (open deal check) | Opportunity (SalesforceOpportunityOperator) | Deal (HubspotDealOperator) |
| Lead status | Lead Status | Lead status |
| Lead source | Lead Source | Lead source property (custom or Original source) |
Owner ({SEQUENCE_OWNERS}) | Lead Owner | Contact owner |
| Activity / task | Task (logged email) via SalesforceActivityOperator | Logged email / Task via HubspotEngagementOperator |
| Custom fields (step, status, last touch) | Custom fields on Lead | Custom contact properties |
| Do-not-email flag | Email Opt Out | Opt out of one-to-one / sales email (subscription status) |
No custom fields? The skill can track progress in logged activities/tasks instead (e.g. subject "Cold sequence: touch 2 sent"), but reporting is harder. Custom fields are recommended.
Gmail ⇄ Outlook
| Topic | Gmail (GoogleGmailOperator) | Outlook (Outlook email operator) |
|---|---|---|
| Threading follow-ups | Reply to the original sent message, keep "Re: {original subject}" | Reply to the original sent message (same conversation), keep "RE:" subject |
| Published sending limits | Around 2,000 messages/day per Workspace user (lower for new or free accounts) | Around 10,000 recipients/day and 30 messages/minute per mailbox |
| Safe cold volume | Far below the limits: typically 30–50 cold emails/day per mailbox after warm-up | Same |
| Bounces | "Mail Delivery Subsystem" / "Delivery Status Notification" | "Undeliverable:" from Microsoft Outlook / postmaster |
| Spam complaints | Keep below 0.1% (Google flags above 0.3%) | Watch for junk-folder placement in tests |
Limits change: check your provider's current documentation.
Slack ⇄ Teams (optional alerts)
| Concept | Slack | Microsoft Teams |
|---|---|---|
| Hot reply alert | Message in a channel or DM | Message in a channel or chat |
| Who sets it up | Workspace admin may need to approve the app | Teams admin may need to approve the app |
4. Data prerequisites
- Leads have email, first name and company filled in. Role/title is strongly recommended.
- Accounts have domains (website or email domain), so the clone can spot existing customers.
- Clear customer flag (your
{CUSTOMER_DEFINITION}) and up-to-date open opportunities. - Lead ownership is set, so leads owned by other reps can be excluded.
- Duplicates cleaned up, especially between leads and contacts.
- Lead source recorded on each lead, and EU/UK leads identifiable (country field).
- Three custom fields created (
{SEQUENCE_STEP_FIELD},{SEQUENCE_STATUS_FIELD},{LAST_TOUCH_FIELD}), or you agree to use activities instead. - Suppression list exists (
{SUPPRESSION_LIST}), seeded with past opt-outs, competitors and anyone you must never email. - Sending domain authenticated (SPF, DKIM, DMARC) and, ideally, warmed up.
- Value prop, proof points, CTA and booking link written down and approved for external use.
5. Roles and permissions
| Who | Needs to |
|---|---|
| Clone admin (owner of the clone in the Clone platform) | Attach skills/operators, approve the plan, save the skill, create/approve the scheduled tasks |
Sender (owner of {SENDER_INBOX}) | Sign in to the inbox connection, approve templates and the first batch, answer hot replies |
| CRM admin (Salesforce or HubSpot) | Create the custom fields; grant the clone a user/app with read + limited write access |
| IT / email admin | Set up SPF, DKIM, DMARC; set up a secondary sending domain if used |
| Compliance / legal (or whoever owns it) | Confirm the opt-out wording, address and {EU_POLICY} |
Hot list recipients ({HOT_LIST_RECIPIENTS}) | Reply personally to interested leads the same day |
6. Estimated setup time
| Step | Time |
|---|---|
| Pre-flight check (this doc) | 10 min |
| Clone discovery + setup questions + plan | 20–30 min |
| Template review and approval | 10–20 min |
| Your sign-ins, CRM fields, suppression list | 15–30 min |
| Save skill + scheduled tasks | 5–10 min |
| Test run on your own addresses | 20 min |
| Total | 60–120 min (plus domain warm-up time if the domain is new) |
7. Pre-flight checklist
- I'm the clone admin (or have one available)
- Gmail or Outlook connection for
{SENDER_INBOX}attached (or can be), with read + send - Salesforce or HubSpot operators available, and I can sign in with read + limited write access
- I can create scheduled tasks (or the clone can)
- SPF, DKIM and DMARC confirmed for the sending domain
- Custom fields created (or I'll use activities)
- Suppression list ready and shared with the clone
- I know my
{LEAD_CRITERIA},{CUSTOMER_DEFINITION}and{SEQUENCE_OWNERS} - I have my value prop, proof points, CTA and booking link
- I've decided
{DAILY_CAP},{WARMUP_PLAN},{SEND_WINDOW}and{RUN_TIMES} - I have the company address and opt-out line for the footer
- I know how EU/UK leads should be handled (
{EU_POLICY}) - (Optional) Clone-Lead-Generation-Skill, sheet import or web research ready
- I have 2 or more test addresses I control (never real prospects) for the test run
8. You're ready when…
- ✅ Every required item in section 1 is attached and its connection is signed in.
- ✅ The sending domain is authenticated and you've agreed on a warm-up ramp.
- ✅ Your CRM can tell customers, open deals and other reps' leads apart from new prospects.
- ✅ The suppression list exists and the custom fields (or activity approach) are in place.
- ✅ You have answers for all the setup questions, including compliance basics.
- ✅ You've set aside about 20 minutes for the test run and time to review the first batch.
Then download CLONE-INSTRUCTIONS.md and give it to your clone.
Was this use case helpful?
Thanks!