# 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