Back to Details

sales-agency-outbound

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Multi-Client Outbound for Agencies

面向机构的多客户外发运营指南

Help the user architect, scale, and operate outbound infrastructure for a lead generation agency — from client isolation and domain strategy through warmup at scale, onboarding playbooks, and cross-client reporting. This skill is tool-agnostic and covers Smartlead, Instantly, Mailshake, and multi-tool setups.
帮助线索生成机构构建、扩展和运营外发基础设施——从客户隔离、域名策略到规模化预热、入职手册制定和跨客户报告。本技能不绑定特定工具，涵盖Smartlead、Instantly、Mailshake以及多工具组合部署场景。

Step 1 — Gather context

步骤1 — 收集上下文信息

Ask the user:
  1. How many clients do you serve (or plan to)?
    • A) Starting out — 1-3 clients
    • B) Growing — 4-10 clients
    • C) Scaled — 10-25 clients
    • D) Enterprise agency — 25+ clients
  2. What's the typical sending volume per client?
    • A) Light — under 100 emails/day
    • B) Standard — 100-500 emails/day
    • C) High volume — 500-2,000 emails/day
    • D) Varies widely across clients
  3. What tooling are you using?
    • A) Smartlead (unlimited mailboxes, master inbox)
    • B) Instantly (bulk warmup, simple UI)
    • C) Mailshake (Lead Catcher, CRM integration)
    • D) Apollo (prospecting + sequences)
    • E) Mix of tools — describe
    • F) Haven't decided yet
  4. What's your client onboarding process today?
    • A) Ad hoc — no standard process
    • B) Have a rough checklist but it's inconsistent
    • C) Documented and repeatable
    • D) Starting from scratch — need to build it
  5. What's your biggest challenge right now?
    • A) Setting up infrastructure for the first time
    • B) One client's issues affecting others (cross-contamination)
    • C) Scaling — adding clients without proportional ops work
    • D) Reporting — clients want better visibility
    • E) Deliverability across multiple domains/clients
    • F) Something else — describe it
  6. Do you need white-labeling? (client-facing branding)
  7. What's your team structure? (solo founder, small team, dedicated account managers per client)
If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.
向用户询问以下问题：
  1. 您当前服务（或计划服务）多少位客户？
    • A) 起步阶段 — 1-3位客户
    • B) 增长阶段 — 4-10位客户
    • C) 规模化阶段 — 10-25位客户
    • D) 企业级机构 — 25位以上客户
  2. 每位客户的典型发送量是多少？
    • A) 低发送量 — 每日少于100封邮件
    • B) 标准发送量 — 每日100-500封邮件
    • C) 高发送量 — 每日500-2000封邮件
    • D) 不同客户发送量差异较大
  3. 您正在使用哪些工具？
    • A) Smartlead（无限邮箱、主收件箱）
    • B) Instantly（批量预热、简洁UI）
    • C) Mailshake（线索捕获器、CRM集成）
    • D) Apollo（线索挖掘+营销序列）
    • E) 混合工具 — 请描述具体组合
    • F) 尚未确定
  4. 您当前的客户入职流程是怎样的？
    • A) 临时流程 — 无标准流程
    • B) 有大致清单但执行不一致
    • C) 已文档化且可重复执行
    • D) 从零开始 — 需要构建完整流程
  5. 您当前面临的最大挑战是什么？
    • A) 首次搭建外发基础设施
    • B) 某一客户的问题影响其他客户（交叉污染）
    • C) 规模化扩展 — 新增客户时运营工作量不成正比增长
    • D) 报告能力 — 客户要求更高的运营可见性
    • E) 多域名/多客户场景下的邮件送达率
    • F) 其他问题 — 请描述
  6. 您是否需要白标设置？（面向客户的品牌化配置）
  7. 您的团队结构是怎样的？（solo创始人、小型团队、为每位客户配备专属客户经理）
如果用户的请求已提供大部分上述上下文信息，可直接跳至相关步骤。 先基于合理假设（需明确说明）给出最佳方案，最后仅询问最关键的1-2个澄清问题——不要要求用户提供完整上下文后才给出回复。

Step 2 — Architecture decisions

步骤2 — 架构决策

Infrastructure model

基础设施模型

Choose the right isolation level based on client count, volume, and risk tolerance:
ModelHow it worksBest forRisk level
Shared mailboxesAgency-owned mailboxes used across clientsSolo operator, 1-2 clients, testingHigh — one client's reputation affects all
Dedicated per clientEach client has their own domains + mailboxes3+ clients, any volumeLow — full isolation
HybridDedicated domains per client, shared infrastructure (IPs)Budget-conscious, low-volume clientsMedium — domain-level isolation without IP isolation
Recommendation: Always use dedicated per client for domain and mailbox isolation. The cost of a single cross-contamination incident (blacklisted domain, cascading reputation damage) far exceeds the cost of separate domains.
根据客户数量、发送量和风险承受能力选择合适的隔离级别：
模型运作方式适用场景风险等级
共享邮箱机构自有邮箱跨客户共用个体经营者、1-2位客户、测试阶段高 — 一位客户的声誉会影响所有客户
客户专属配置每位客户拥有独立域名+邮箱3位以上客户、任何发送量低 — 完全隔离
混合模式每位客户使用专属域名，共享基础设施（IP）预算有限、低发送量客户中 — 仅域名级隔离，无IP级隔离
推荐方案：始终采用客户专属配置实现域名和邮箱隔离。单次交叉污染事件（域名被拉黑、声誉连锁受损）的损失远超过购买独立域名的成本。

Domain strategy

域名策略

DecisionRecommendationRationale
Domain ownershipClient-owned preferred, agency-provisioned acceptableClient keeps the asset; if they leave, their domain goes with them
Domains per client1 domain per 3-5 mailboxesDistributes reputation risk; losing one domain doesn't kill the campaign
Domain naming{client}mail.com, get{client}.com, try{client}.comClose to brand but clearly separate from primary domain
Primary domain protectionNever send cold outbound from the client's primary domainIf outbound domain gets blacklisted, primary email is protected
Example: Client "Acme Corp" (acme.com) gets:
  • acmemail.com — 5 mailboxes (jane@, mike@, sarah@, tom@, alex@)
  • getacme.com — 5 mailboxes (as backup/rotation domain)
  • acme.com — never used for cold outbound
决策项推荐方案理由
域名所有权优先选择客户自有域名，机构代注册也可接受客户保留资产；若客户终止合作，域名归其所有
每位客户的域名数量每3-5个邮箱对应1个域名分散声誉风险；单个域名失效不会导致营销活动完全终止
域名命名规则{client}mail.com、get{client}.com、try{client}.com贴近品牌但与主域名明确区分
主域名保护绝对不要使用客户主域名发送冷邮件若外发域名被拉黑，主邮箱仍可正常使用
示例：客户“Acme Corp”（acme.com）可配置：
  • acmemail.com — 5个邮箱（jane@、mike@、sarah@、tom@、alex@）
  • getacme.com — 5个邮箱（作为备用/轮换域名）
  • acme.com — 绝不用于冷邮件外发

Warmup at scale

规模化邮箱预热

Managing warmup across 20+ mailboxes requires planning:
PhaseWhat to doTimeline
Stagger startsDon't start all mailboxes on the same day — stagger by 2-3 days per batch of 5Days 1-10
Monitor reputationCheck warmup reputation scores daily — all mailboxes should reach 80+ before campaign sendsWeeks 1-3
Gradual activationAdd warmed mailboxes to campaigns in batches, not all at onceWeek 3+
Ongoing warmupKeep warmup running even during active campaigns — it supplements reputationContinuous
管理20个以上邮箱的预热流程需要规划：
阶段操作内容时间线
分批启动不要同时启动所有邮箱的预热 — 每批5个邮箱，间隔2-3天启动第1-10天
声誉监控每日检查预热声誉评分 — 所有邮箱在启动营销活动前需达到80分以上第1-3周
逐步激活分批将完成预热的邮箱加入营销活动，而非一次性全部添加第3周及以后
持续预热即使营销活动正在进行，也要保持预热 — 有助于维持邮箱声誉持续进行

Tool selection matrix

工具选择矩阵

FeatureSmartleadInstantlyMailshake
Unlimited mailboxesYes (all plans)Yes (Growth plan)No (plan-based limits)
Built-in warmupUltra Premium WarmupWarmup poolNo (use external)
Master inboxYes — unified across clientsLimitedNo
Client workspacesYes — native isolationYes — workspace managementLimited — team member isolation
White-labelYes (higher plans)NoNo
API for automationYesYesYes
Best for agency useFull-featured agency platformSimple multi-client warmupSingle-client with CRM focus
功能SmartleadInstantlyMailshake
无限邮箱是（所有套餐）是（Growth套餐）否（套餐限制数量）
内置预热功能Ultra Premium Warmup预热池否（需使用外部工具）
主收件箱是 — 跨客户统一视图有限支持否
客户工作区是 — 原生隔离是 — 工作区管理有限支持 — 仅团队成员隔离
白标设置是（高端套餐）否否
自动化API是是是
机构场景适配性全功能机构平台简洁多客户预热工具适合需CRM集成的单客户场景

Step 3 — Client onboarding playbook

步骤3 — 客户入职手册

Repeatable checklist for onboarding each new client:
适用于每位新客户的可重复执行清单：

Phase 1: Infrastructure (Days 1-3)

阶段1：基础设施搭建（第1-3天）

  1. Domain provisioning
    • Register 2 outbound domains (primary + backup) per client
    • Point DNS to your email provider
    • Configure SPF, DKIM, DMARC for each domain (→ 
      /sales-deliverability
      )
  2. Mailbox creation
    • Create 3-5 mailboxes per domain (real names, professional formatting)
    • Connect via OAuth (Gmail/Outlook) or SMTP
    • Set daily limits: 30-50 per mailbox
  3. Warmup scheduling
    • Enable warmup on all mailboxes immediately
    • Stagger start dates if provisioning 10+ mailboxes
    • Target: 2-3 weeks warmup before first campaign send
    • Monitor warmup reputation daily
  1. 域名配置
    • 为每位客户注册2个外发域名（主域名+备用域名）
    • 将DNS指向您的邮件服务商
    • 为每个域名配置SPF、DKIM、DMARC（→ 参考/sales-deliverability）
  2. 邮箱创建
    • 每个域名下创建3-5个邮箱（使用真实姓名、专业格式）
    • 通过OAuth（Gmail/Outlook）或SMTP连接
    • 设置每日发送限制：每个邮箱30-50封
  3. 预热调度
    • 立即为所有邮箱启用预热
    • 若配置10个以上邮箱，需分批启动预热
    • 目标：首次营销活动前完成2-3周预热
    • 每日监控预热声誉

Phase 2: Campaign setup (Days 3-7)

阶段2：营销活动设置（第3-7天）

  1. ICP definition + list building (→ 
    /sales-prospect-list
    )
    • Define target persona with client input
    • Build initial prospect list (200-500 for first campaign)
    • Verify emails before import
  2. Cadence design (→ 
    /sales-cadence
    )
    • Design email sequence (3-5 steps, 7-14 day cadence)
    • Write email copy with client-approved messaging
    • Set up A/B tests for subject lines
  3. Integration setup (→ 
    /sales-integration
    )
    • Connect to client's CRM (if applicable)
    • Set up lead forwarding (webhook, Zapier, or email)
    • Configure Slack/email notifications for interested replies
  1. 理想客户画像（ICP）定义+线索列表构建（→ 参考/sales-prospect-list）
    • 与客户协作确定目标用户画像
    • 构建初始线索列表（首次营销活动200-500条）
    • 导入前验证邮箱有效性
  2. 营销序列设计（→ 参考/sales-cadence）
    • 设计邮件序列（3-5个步骤，7-14天周期）
    • 撰写经客户认可的邮件内容
    • 为主题行设置A/B测试
  3. 集成设置（→ 参考/sales-integration）
    • 连接客户的CRM（如有需要）
    • 设置线索转发（webhook、Zapier或邮件转发）
    • 配置Slack/邮件通知以接收意向回复

Phase 3: Launch (Days 14-21)

阶段3：启动上线（第14-21天）

  1. Go-live checklist
    • All mailboxes have 80+ warmup reputation
    • DNS records verified (SPF/DKIM/DMARC passing)
    • SmartDelivery or mail-tester.com shows inbox placement
    • Prospect list verified (<3% expected bounce rate)
    • Email copy approved by client
    • CRM/notification integration tested
    • Daily sending limits configured correctly
    • Campaign activated with small initial batch (50-100 leads)
  1. 上线检查清单
    • 所有邮箱预热声誉达到80分以上
    • DNS记录验证通过（SPF/DKIM/DMARC配置正确）
    • SmartDelivery或mail-tester.com显示邮件可进入收件箱
    • 线索列表已验证（预计 bounce 率<3%）
    • 邮件内容已获客户认可
    • CRM/通知集成测试通过
    • 每日发送限制配置正确
    • 以小批量（50-100条线索）启动营销活动

Step 4 — Reporting and operations

步骤4 — 报告与运营

Client-facing metrics

面向客户的指标

Report what clients actually care about — not vanity metrics:
MetricWhat to reportCadence
Meetings bookedTotal meetings booked, cost per meetingWeekly
Pipeline generatedDollar value of opportunities createdMonthly
Interested repliesLeads who expressed interest (qualified replies)Weekly
Reply ratePositive reply rate (not total replies)Weekly
Campaign healthActive campaigns, leads in pipeline, next stepsWeekly
Avoid reporting: Raw open rates (unreliable with Apple MPP), total sends, click rates (meaningless for cold outbound). Clients who fixate on opens/clicks will micromanage the wrong things.
报告客户真正关心的指标——而非虚荣指标：
指标报告内容频率
已预约会议数总预约会议数、单会议成本每周
生成的销售管道价值创造的潜在机会的美元价值每月
意向回复数表达兴趣的线索（合格回复）每周
回复率正向回复率（非总回复数）每周
营销活动健康度活跃营销活动数、管道内线索数、下一步计划每周
避免报告：原始打开率（受Apple MPP影响不可靠）、总发送量、点击率（对冷邮件外发无意义）。过度关注打开率/点击率的客户会错误地干预营销过程。

Internal ops metrics

内部运营指标

Track these internally to spot issues before clients notice:
MetricTargetAction if exceeded
Bounce rate (per client)<3%Pause campaign, verify remaining list, investigate domain
Warmup reputation (per mailbox)80+Remove from campaign rotation, investigate
Cross-client deliverability<5% variance in inbox placementInvestigate outlier clients for contamination
Mailbox utilization60-80% of daily limitScale up if >80%, investigate if <40%
Warmup pipeline2+ weeks ahead of new campaignsProvision mailboxes earlier
内部跟踪这些指标，以便在客户发现问题前及时处理：
指标目标值超出目标的应对措施
单客户 bounce 率<3%暂停营销活动，验证剩余列表，排查域名问题
单邮箱预热声誉80分以上从营销活动轮换中移除，排查原因
跨客户送达率差异<5%排查异常客户是否存在交叉污染
邮箱利用率每日发送限制的60-80%利用率>80%时扩容，<40%时排查原因
预热管道储备提前2周以上为新营销活动准备好预热完成的邮箱更早配置邮箱

Scaling patterns

规模化扩展模式

TriggerAction
Client reaches daily limitAdd mailboxes (1 per 50 emails/day needed)
Client adds new personaNew domain + mailboxes for isolation
Bounce rate creeping upRotate to fresh domain, investigate list quality
New client onboardedFollow Phase 1-3 playbook (14-21 day ramp)
Client churnsDecommission domains (don't reuse for other clients)
触发条件应对措施
客户达到每日发送限制添加邮箱（每需增加50封/日发送量则新增1个邮箱）
客户新增目标用户画像配置新域名+邮箱以实现隔离
Bounce率逐渐上升切换至新域名，排查线索列表质量
新客户入职遵循阶段1-3手册（14-21天启动周期）
客户流失停用域名（切勿复用给其他客户）

Step 5 — Platform-specific implementation

步骤5 — 平台专属实现方案

In Smartlead

在Smartlead中

  • Master inbox: Unified view across all client campaigns — manage replies from one interface
  • Client workspaces: Create a workspace per client (Settings > Clients). All campaigns, leads, and sender accounts scoped to the workspace.
  • White-label: Settings > White Label — custom domain, logo, colors for client-facing access
  • Unified analytics: Cross-client performance dashboard with per-client drill-down
  • SmartSenders: Bulk-provision mailboxes per workspace. Warmup runs per-mailbox automatically.
  • 主收件箱：跨所有客户营销活动的统一视图——从一个界面管理所有回复
  • 客户工作区：为每位客户创建独立工作区（设置>客户）。所有营销活动、线索和发件人账户均归属于对应工作区。
  • 白标设置：设置>白标——为客户访问配置自定义域名、Logo和配色
  • 统一分析：跨客户绩效仪表盘，支持按客户钻取详情
  • SmartSenders：按工作区批量配置邮箱。自动为每个邮箱启动预热。

In Instantly

在Instantly中

  • Workspace management: Create separate workspaces per client for isolation
  • Bulk warmup: Instantly's warmup pool handles large mailbox counts efficiently
  • Campaign organization: Name campaigns with client prefix (e.g., "Acme - Q1 VP Eng")
  • Limitation: No native white-label or master inbox — less agency-friendly than Smartlead
  • 工作区管理：为每位客户创建独立工作区实现隔离
  • 批量预热：Instantly的预热池可高效处理大量邮箱
  • 营销活动组织：为营销活动命名时添加客户前缀（例如："Acme - Q1 VP Eng"）
  • 局限性：无原生白标或主收件箱——对机构的友好度低于Smartlead

In Mailshake

在Mailshake中

  • Team member isolation: Assign team members per client, but isolation is weaker than workspace-based tools
  • Lead Catcher: Useful for per-client reply management, but no master inbox across clients
  • CRM integration: Strong native CRM integration (Salesforce, HubSpot) — good if clients require direct CRM sync
  • Limitation: Plan-based mailbox limits make scaling expensive for agencies
  • 团队成员隔离：为每位客户分配专属团队成员，但隔离力度弱于基于工作区的工具
  • Lead Catcher：便于管理单客户回复，但无跨客户主收件箱
  • CRM集成：原生CRM集成能力强（Salesforce、HubSpot）——适合要求直接同步CRM的客户
  • 局限性：套餐限制邮箱数量，规模化扩展成本高

In Reply.io

在Reply.io中

  • Agency plan: Dedicated Agency plan (~$166/mo) with unlimited clients and unlimited users
  • Client isolation: Each client gets isolated sequences and contact lists
  • Unified dashboard: Manage all clients from a single dashboard
  • Built-in warmup: Warmup for all client mailboxes included
  • API access: Programmatic client management — create seats, add mailboxes via Master API Key
  • 机构套餐：专属机构套餐（约$166/月），支持无限客户和无限用户
  • 客户隔离：每位客户拥有独立的营销序列和联系人列表
  • 统一仪表盘：从单个仪表盘管理所有客户
  • 内置预热功能：包含所有客户邮箱的预热服务
  • API访问：程序化客户管理——通过Master API Key创建席位、添加邮箱

In Woodpecker

在Woodpecker中

  • Agency panel: Add-on at €27/month per active client — manage all clients from a single dashboard
  • Client isolation: Each client gets separate campaigns, prospects, mailboxes, and deliverability settings
  • Agency API: HQ API key + 
    x-company-id
    header to manage clients programmatically — create API keys per company, manage mailboxes and campaigns across clients
  • Per-client warmup: Each client's mailboxes get independent warmup slots — no cross-contamination of sender reputation
  • Pricing model: Scales per active client (€27/client) + per contacted prospects tier. Compare: Smartlead has flat agency pricing, Woodpecker scales linearly.
  • White-labeling: Not natively supported — agency panel is Woodpecker-branded
  • 机构面板：附加功能，每位活跃客户€27/月——从单个仪表盘管理所有客户
  • 客户隔离：每位客户拥有独立的营销活动、线索、邮箱和送达率设置
  • 机构API：HQ API密钥+
    x-company-id
    头信息实现程序化客户管理——为每个公司创建API密钥，跨客户管理邮箱和营销活动
  • 单客户独立预热：每位客户的邮箱拥有独立预热插槽——不会出现发件人声誉交叉污染
  • 定价模式：按活跃客户数（€27/客户）+ 触达线索量层级计费。对比：Smartlead采用固定机构定价，Woodpecker按线性规模计费。
  • 白标设置：无原生支持——机构面板为Woodpecker品牌

Cross-platform setup

跨平台配置

  • Some agencies use different tools for different clients based on client needs (e.g., Smartlead for high-volume, Mailshake for CRM-heavy clients)
  • Standardize reporting across tools — use a shared dashboard (Google Sheets, Looker, or custom) that aggregates metrics from all platforms
  • Maintain per-client tool documentation so any team member can pick up any client
  • 部分机构会根据客户需求使用不同工具（例如：Smartlead用于高发送量客户，Mailshake用于重度依赖CRM的客户）
  • 跨工具标准化报告——使用共享仪表盘（Google Sheets、Looker或自定义工具）聚合所有平台的指标
  • 维护每位客户的工具文档，确保任何团队成员均可接手客户运营

Gotchas

注意事项

  • Don't share sending domains across clients. One client's reputation meltdown (high bounces, spam complaints, blacklisting) poisons all clients sharing that domain. The cost of a $12/year domain is nothing compared to rebuilding reputation for 5 clients.
  • Don't skip per-client warmup. New domains need their own warmup regardless of mailbox age. Even if you're reusing an established mailbox on a new domain, the domain itself has zero reputation. Follow the full warmup schedule.
  • Don't report vanity metrics. Report meetings booked and pipeline generated, not opens and clicks. Clients who focus on opens will micromanage subject lines instead of trusting the process. Set expectations during onboarding about which metrics matter.
  • Don't use a single Zapier account for all clients. Billing, rate limits, and error handling cascade across all zaps in one account. If one client's integration breaks and triggers retries, it can exhaust your Zapier task quota and break every other client's integration. Use separate Zapier accounts or a dedicated integration layer.
  • 切勿跨客户共享发送域名。一位客户的声誉崩溃（高 bounce 率、垃圾投诉、域名被拉黑）会影响所有共用该域名的客户。一个每年$12的域名成本远低于为5位客户重建声誉的损失。
  • 切勿跳过单客户预热流程。新域名无论邮箱使用时长如何都需要独立预热。即使将已使用的邮箱绑定到新域名，该域名本身也没有任何声誉。请遵循完整的预热时间表。
  • 切勿报告虚荣指标。报告已预约会议数和销售管道价值，而非打开率和点击率。过度关注打开率的客户会过度干预主题行，而非信任运营流程。在客户入职阶段就明确告知哪些指标才是关键。
  • 切勿为所有客户使用同一个Zapier账户。账单、速率限制和错误处理会影响账户内所有Zap。若某一客户的集成故障触发重试，可能会耗尽Zapier任务配额，导致其他所有客户的集成失效。请使用独立Zapier账户或专用集成层。

Related skills

相关技能

  • /sales-smartlead
    — Smartlead platform help (SmartSenders, SmartInfra, campaigns, API)
  • /sales-deliverability
    — Domain authentication, warmup schedules, inbox placement
  • /sales-cadence
    — Design outbound cadences and email content
  • /sales-prospect-list
    — Build targeted prospect lists for client campaigns
  • /sales-integration
    — Connect outbound tools to CRM via webhooks, Zapier, or API
  • /sales-mailshake
    — Mailshake platform help
  • /sales-reply
    — Reply.io platform help (Agency plan with unlimited clients)
  • /sales-woodpecker
    — Woodpecker platform help (Agency panel with per-client management)
  • /sales-do
    — Not sure which skill to use? The router matches any sales objective to the right skill.
  • /sales-smartlead
    — Smartlead平台使用帮助（SmartSenders、SmartInfra、营销活动、API）
  • /sales-deliverability
    — 域名认证、预热时间表、收件箱投递率
  • /sales-cadence
    — 设计外发营销序列和邮件内容
  • /sales-prospect-list
    — 为客户营销活动构建目标线索列表
  • /sales-integration
    — 通过webhook、Zapier或API连接外发工具与CRM
  • /sales-mailshake
    — Mailshake平台使用帮助
  • /sales-reply
    — Reply.io平台使用帮助（支持无限客户的机构套餐）
  • /sales-woodpecker
    — Woodpecker平台使用帮助（支持单客户管理的机构面板）
  • /sales-do
    — 不确定使用哪个技能？该路由可将任何销售目标匹配到合适的技能。

Examples

示例场景

  • "First 3 clients on Smartlead" → Dedicated domains per client (2 each), 3-5 mailboxes per domain via SmartSenders, client workspaces for isolation, staggered warmup plan, Phase 1-3 onboarding checklist
  • "Client blacklisted, other clients' rates dropping" → Diagnose shared domain/IP as cross-contamination cause, pause affected client, check blacklists, provision new domains, re-warmup, design strict per-client isolation going forward
  • "Build repeatable onboarding process" → Phase 1-3 playbook (14-21 days), reusable checklist template, handoffs to 
    /sales-prospect-list
    , 
    /sales-cadence
    , 
    /sales-integration
    , client kickoff questionnaire, milestone tracking
  • "首次为3位客户配置Smartlead" → 为每位客户配置专属域名（各2个），通过SmartSenders为每个域名配置3-5个邮箱，使用客户工作区实现隔离，制定分批预热计划，遵循阶段1-3入职清单
  • "某客户域名被拉黑，其他客户的送达率下降" → 诊断是否因共享域名/IP导致交叉污染，暂停受影响客户的活动，检查黑名单，配置新域名，重新预热，制定严格的单客户隔离规则
  • "构建可复用的客户入职流程" → 阶段1-3手册（14-21天）、可复用清单模板、对接/sales-prospect-list、/sales-cadence、/sales-integration、客户启动问卷、里程碑跟踪