disqualification-handling

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Disqualification Handling

不合格潜在客户处理

Processes leads that didn't pass ICP qualification. Instead of ignoring them, this composite handles each category appropriately: polite rejection, referral request, or nurture routing. No inbound lead should feel ghosted.
本流程用于处理未通过ICP资格判定的潜在客户。不会直接忽略这类客户,而是根据不同情况进行恰当处理:礼貌拒绝、推荐请求或培育跟进。确保每一位入站潜在客户都不会被“幽灵式”对待。

When to Auto-Load

自动加载场景

Load this composite when:
  • User says "handle the disqualified leads", "draft rejection emails", "what do we do with the ones that didn't qualify?"
  • inbound-lead-qualification
    has completed and disqualified/near-miss leads need handling
  • User has a list of leads that don't fit and wants appropriate responses
在以下场景下加载本流程:
  • 用户提出“处理不合格潜在客户”“生成拒绝邮件”“那些不合格的客户该怎么处理?”等需求时
  • inbound-lead-qualification
    流程已完成,且需要处理不合格/接近合格的潜在客户时
  • 用户拥有一批不符合要求的潜在客户列表,需要生成合适的响应时

Architecture

架构

[Disqualified Leads] → Step 1: Categorize → Step 2: Draft Responses → Step 3: Route to Destination
                              ↓                      ↓                         ↓
                     4 handling categories    Tailored email per type    Nurture/CRM/archive

[不合格潜在客户] → 步骤1:分类 → 步骤2:生成响应邮件 → 步骤3:路由至对应目的地
                              ↓                      ↓                         ↓
                     4种处理分类    对应类型的定制化邮件    培育/CRM/归档

Step 0: Configuration (Once Per Client)

步骤0:配置(每位客户仅需一次)

On first run, establish response preferences. Save to
clients/<client-name>/config/disqualification-handling.json
.
json
{
  "sender_name": "",
  "sender_title": "",
  "company_name": "",
  "tone": "warm-professional | casual-friendly | formal",
  "nurture_sequence_tool": "Smartlead | HubSpot | Mailchimp | CSV export | none",
  "referral_incentive": "none | mention mutual value | offer resource",
  "include_resource_link": true,
  "resource_url": "",
  "resource_description": "",
  "feedback_survey_url": "",
  "do_not_contact_list": "Supabase | CSV | none"
}
On subsequent runs: Load config silently.

首次运行时,设置响应偏好。保存至
clients/<client-name>/config/disqualification-handling.json
json
{
  "sender_name": "",
  "sender_title": "",
  "company_name": "",
  "tone": "warm-professional | casual-friendly | formal",
  "nurture_sequence_tool": "Smartlead | HubSpot | Mailchimp | CSV export | none",
  "referral_incentive": "none | mention mutual value | offer resource",
  "include_resource_link": true,
  "resource_url": "",
  "resource_description": "",
  "feedback_survey_url": "",
  "do_not_contact_list": "Supabase | CSV | none"
}
后续运行时: 静默加载配置。

Step 1: Categorize Disqualified Leads

步骤1:对不合格潜在客户进行分类

Input

输入

Leads from
inbound-lead-qualification
with sub-verdicts. Categorize each into one of four handling paths:
来自
inbound-lead-qualification
流程的带有次级判定结果的潜在客户。将每位客户归入以下4种处理路径之一:

Category 1: Right Company, Wrong Person → REFERRAL REQUEST

分类1:公司匹配,对接人不符 → 推荐请求

Trigger:
mismatch_type = right_company_wrong_person
  • The company fits ICP but the person who came inbound isn't a buyer/champion/user
  • Example: A marketing intern at a perfect-fit company downloaded a whitepaper
  • Goal: Get an introduction to the right person at that company
Identify the referral target:
  • Using the ICP's buyer personas, determine who at this company we SHOULD be talking to
  • If enrichment data or CRM has other contacts at the company, note them (but still ask for the intro — warmer than cold outreach)
触发条件:
mismatch_type = right_company_wrong_person
  • 公司符合ICP要求,但入站对接人并非采购决策人/关键支持者/目标用户
  • 示例:某完全匹配ICP的公司的营销实习生下载了白皮书
  • 目标:获取该公司合适对接人的引荐
确定推荐目标:
  • 根据ICP的采购角色画像,确定我们应该对接该公司的哪类人员
  • 如果有客户 enrichment 数据或CRM中存在该公司的其他联系人,可记录下来(但仍需请求引荐——这比陌生 outreach 更有效)

Category 2: Close But Not Quite → NURTURE (FUTURE FIT)

分类2:接近但未达标 → 培育跟进(未来适配)

Trigger:
sub_verdict = near_miss_nurture
OR score 30-49 without a referral opportunity
  • Company is almost ICP but not today — too small, too early stage, wrong geography (but expanding), missing a key requirement that might change
  • Example: A 15-person startup that's clearly growing fast but below your 50-employee minimum
  • Goal: Stay on their radar. When they hit the threshold, you're top of mind.
触发条件:
sub_verdict = near_miss_nurture
或 得分30-49且无推荐机会
  • 公司接近ICP要求,但目前暂不符合——规模过小、发展阶段过早、地域不符(但正在扩张)、缺少可能会改变的关键需求
  • 示例:一家15人的初创公司,增长迅速但未达到50人的最低要求
  • 目标:保持品牌曝光,当客户达到要求时,我们能成为首选

Category 3: Clearly Outside ICP → POLITE DECLINE

分类3:明显不符合ICP → 礼貌拒绝

Trigger:
sub_verdict = disqualified_polite
OR score < 30
  • Not a fit now and unlikely to become one
  • Example: A freelancer, a student, a company in an excluded industry
  • Goal: Decline gracefully. Don't burn bridges — they might refer someone, post about you, or their situation might change unexpectedly.
触发条件:
sub_verdict = disqualified_polite
或 得分<30
  • 目前不符合要求,且未来也不太可能符合
  • 示例:自由职业者、学生、处于排除行业的公司
  • 目标:礼貌拒绝,不破坏关系——他们可能会推荐他人、宣传我们,或者情况会意外改变

Category 4: Special Flags → ROUTE DIFFERENTLY

分类4:特殊标记 → 特殊路由

Trigger:
sub_verdict = disqualified_competitor
OR
pipeline_status = existing_customer
  • Competitor employee: Do NOT send a rejection email. Log for competitive intelligence. No outreach.
  • Existing customer: Do NOT treat as disqualified. Route to customer success / account management. May be an upsell or support need.
触发条件:
sub_verdict = disqualified_competitor
pipeline_status = existing_customer
  • 竞争对手员工: 不要发送拒绝邮件。记录至竞争情报库。不进行 outreach。
  • 现有客户: 不要当作不合格客户处理。路由至客户成功/客户管理团队。可能存在 upsell 或支持需求。

Output

输出

Each lead tagged with:
handling_category
,
handling_action
,
referral_target_persona
(for Category 1)

每位潜在客户将被标记:
handling_category
handling_action
referral_target_persona
(仅分类1)

Step 2: Draft Responses

步骤2:生成响应邮件

Category 1 Response: Referral Request Email

分类1响应:推荐请求邮件

Objective: Thank them, subtly indicate they may not be the right person, and ask for an introduction — without making them feel dismissed.
Structure:
  1. Thank them for their interest (reference what they did — demo request, download, etc.)
  2. Acknowledge their role — show you understand what they do
  3. Pivot to the right person — frame it as "wanting to make sure the right person gets the most value"
  4. Make the ask easy — provide a specific persona/title to connect you with
  5. Offer something in return — a resource relevant to THEIR role (not just the buyer's)
Template framework:
Subject: Thanks for checking us out, [First Name]

Hi [First Name],

Thanks for [downloading our guide on X / requesting a demo / signing up for the trial].
[One sentence connecting their action to a genuine insight — "it's a great resource for
understanding Y."]

I took a look at [Company] — [one sentence showing you understand the company].
Given what [Product] does, I think [target persona title, e.g., "your VP of Engineering"
or "whoever leads infrastructure decisions"] would get the most out of a conversation
with us.

Would you be open to making an introduction? Happy to send you a quick blurb you
can forward, so it's zero effort on your end.

[If resource_link configured: "In the meantime, here's [resource] that might be
useful for [something relevant to THEIR role]."]

Thanks,
[Sender Name]
Rules:
  • Never say "you're not the right person" or "you don't have buying authority"
  • Never use the word "unfortunately" or "however"
  • Frame the referral as maximizing value, not correcting a mistake
  • Keep it under 120 words
  • If you know the specific name of the right person (from enrichment/CRM), mention them: "I think [Name] on your [team] would find this valuable"
目标: 感谢对方,委婉表明对接人可能不合适,并请求引荐——不要让对方感到被拒绝。
结构:
  1. 感谢对方的关注(提及他们的行为——如请求演示、下载资料等)
  2. 认可对方角色——表明你了解他们的职位
  3. 转向合适对接人——以“确保合适的人能获得最大价值”为理由
  4. 简化请求流程——提供具体的角色/职位信息,方便对方引荐
  5. 提供回报——提供与他们职位相关的资源
模板框架:
Subject: Thanks for checking us out, [First Name]

Hi [First Name],

Thanks for [downloading our guide on X / requesting a demo / signing up for the trial].
[One sentence connecting their action to a genuine insight — "it's a great resource for
understanding Y."]

I took a look at [Company] — [one sentence showing you understand the company].
Given what [Product] does, I think [target persona title, e.g., "your VP of Engineering"
or "whoever leads infrastructure decisions"] would get the most out of a conversation
with us.

Would you be open to making an introduction? Happy to send you a quick blurb you
can forward, so it's zero effort on your end.

[If resource_link configured: "In the meantime, here's [resource] that might be
useful for [something relevant to THEIR role]."]

Thanks,
[Sender Name]
规则:
  • 绝对不要说“你不是合适的对接人”或“你没有采购权限”
  • 绝对不要使用“unfortunately”或“however”这类词汇
  • 将引荐请求定位为最大化价值,而非纠正错误
  • 邮件长度控制在120词以内
  • 如果知道合适对接人的具体姓名(来自enrichment/CRM),可直接提及:“我认为你的[团队]的[Name]会对此感兴趣”

Category 2 Response: Nurture Warm-Down Email

分类2响应:培育跟进预热邮件

Objective: Keep the relationship warm without false promises. Position yourself as a future resource.
Structure:
  1. Thank them for their interest
  2. Be honest (but tactful) about fit — don't say "you're disqualified", say "given where [Company] is today, the timing might not be perfect"
  3. Offer genuine value — share a resource relevant to their current stage/situation
  4. Leave the door open — invite them to reach out when circumstances change
  5. No hard CTA — this is a soft touch, not a sales push
Template framework:
Subject: [First Name] — thanks for your interest in [Product]

Hi [First Name],

Thanks for [action they took]. I looked into [Company] and really like
[genuine compliment — what they're building, their growth, their approach].

Based on where [Company] is right now, I think [honest reason the timing
isn't right, framed positively — e.g., "you'd get the most value from us
once your team scales past X" or "this tends to be most impactful after Y
milestone"].

In the meantime, [here's a resource / I'd recommend / you might find this useful] —
[brief description of why it's relevant to them NOW, not just to your product].

I'll keep an eye on [Company] — would love to reconnect when the timing
is better. Feel free to reach out anytime.

Best,
[Sender Name]
Rules:
  • Never say "disqualified", "not a fit", "don't meet our criteria"
  • Frame timing as the issue, not them — "not yet" beats "not ever"
  • The shared resource should be genuinely useful to them at their current stage, not just a product pitch
  • Keep it under 100 words
  • Warm but not overly familiar
目标: 保持良好关系,不做出虚假承诺。将自身定位为未来可依赖的资源。
结构:
  1. 感谢对方的关注
  2. 诚实但委婉地说明适配性——不要说“你不合格”,而是“考虑到[公司]目前的情况,时机可能尚未成熟”
  3. 提供真实价值——分享与他们当前阶段/情况相关的资源
  4. 保持沟通渠道开放——邀请对方在情况变化时联系你
  5. 无硬性CTA——这是温和的触达,而非销售推送
模板框架:
Subject: [First Name] — thanks for your interest in [Product]

Hi [First Name],

Thanks for [action they took]. I looked into [Company] and really like
[genuine compliment — what they're building, their growth, their approach].

Based on where [Company] is right now, I think [honest reason the timing
isn't right, framed positively — e.g., "you'd get the most value from us
once your team scales past X" or "this tends to be most impactful after Y
milestone"].

In the meantime, [here's a resource / I'd recommend / you might find this useful] —
[brief description of why it's relevant to them NOW, not just to your product].

I'll keep an eye on [Company] — would love to reconnect when the timing
is better. Feel free to reach out anytime.

Best,
[Sender Name]
规则:
  • 绝对不要说“不合格”“不符合要求”“未达我们的标准”
  • 将问题定位为时机问题,而非客户本身——“尚未”比“永远不”更好
  • 分享的资源必须对他们当前阶段真正有用,而非仅仅是产品宣传
  • 邮件长度控制在100词以内
  • 语气热情但不过分随意

Category 3 Response: Polite Decline Email

分类3响应:礼貌拒绝邮件

Objective: Decline gracefully while leaving a positive impression of your brand.
Structure:
  1. Thank them for their interest
  2. Brief honest explanation — keep it high-level ("we specialize in X and it sounds like you need Y")
  3. Redirect if possible — suggest an alternative tool/service if you know one
  4. Close warmly
Template framework:
Subject: Thanks for reaching out, [First Name]

Hi [First Name],

Thanks for your interest in [Product]. I appreciate you taking the time to
[action they took].

We're focused specifically on [your niche/ICP in plain language], and it
sounds like [their situation — framed neutrally, not critically] might be
a different use case from what we're built for.

[If you know an alternative: "You might want to check out [Alternative] —
they're strong for [their actual need]."]

[If no alternative: "I don't want to waste your time, but if your needs
evolve, we'd be happy to chat."]

Best of luck with [something specific to their situation],
[Sender Name]
Rules:
  • Never apologize ("sorry we can't help") — you're not obligated
  • Never be dismissive or condescending
  • Keep it under 80 words
  • If you can genuinely suggest an alternative, do — it builds goodwill
  • Don't over-explain why they don't fit. One sentence is enough.
目标: 礼貌拒绝,同时留下良好的品牌印象。
结构:
  1. 感谢对方的关注
  2. 简要诚实的解释——保持宏观层面(“我们专注于X领域,而你似乎需要Y”)
  3. 如有可能,提供替代方案——如果知道合适的工具/服务,可推荐
  4. 友好收尾
模板框架:
Subject: Thanks for reaching out, [First Name]

Hi [First Name],

Thanks for your interest in [Product]. I appreciate you taking the time to
[action they took].

We're focused specifically on [your niche/ICP in plain language], and it
sounds like [their situation — framed neutrally, not critically] might be
a different use case from what we're built for.

[If you know an alternative: "You might want to check out [Alternative] —
they're strong for [their actual need]."]

[If no alternative: "I don't want to waste your time, but if your needs
evolve, we'd be happy to chat."]

Best of luck with [something specific to their situation],
[Sender Name]
规则:
  • 绝对不要道歉(“抱歉我们无法提供帮助”)——你没有义务这么做
  • 绝对不要表现出轻视或傲慢
  • 邮件长度控制在80词以内
  • 如果能真诚推荐替代方案,务必这么做——这能建立好感
  • 不要过度解释不符合的原因,一句话足够

Category 4: No Email

分类4:不发送邮件

  • Competitor: Add to competitive intel tracking. No outbound response. Log: "Competitor employee [Name] from [Company] engaged via [source] on [date]."
  • Existing customer: Draft a brief internal routing note: "Existing customer [Company] ([contact name]) came inbound via [source]. Current plan: [plan]. Account owner: [owner]. Possible upsell signal." Route to CS/AM.

  • 竞争对手: 添加至竞争情报跟踪库。不发送 outbound 响应。记录:“竞争对手员工[Name]来自[Company],于[日期]通过[渠道]触达。”
  • 现有客户: 起草简短的内部路由说明:“现有客户[Company](联系人[姓名])通过[渠道]入站。当前套餐:[套餐]。账户负责人:[负责人]。可能存在 upsell 信号。” 路由至客户成功/客户管理团队。

Step 3: Route to Destination

步骤3:路由至对应目的地

For Each Category:

各分类处理方式:

CategoryEmail ActionCRM ActionSequence Action
Referral RequestDraft ready for human review & sendTag as
referral_pending
None — single touch
NurtureDraft ready for human review & sendTag as
nurture_future_fit
, set reminder for re-evaluation in 3-6 months
Add to nurture drip if configured
Polite DeclineDraft ready for human review & sendTag as
disqualified_responded
, note reason
None — single touch
CompetitorNo emailTag as
competitor_employee
, log in competitive intel
None
Existing CustomerNo sales emailFlag for CS/AM team, note the inbound actionNone
分类邮件操作CRM操作序列操作
推荐请求生成草稿,供人工审核后发送标记为
referral_pending
无——单次触达
培育跟进生成草稿,供人工审核后发送标记为
nurture_future_fit
,设置3-6个月后的重新评估提醒
若已配置,添加至培育 drip 序列
礼貌拒绝生成草稿,供人工审核后发送标记为
disqualified_responded
,记录原因
无——单次触达
竞争对手不发送邮件标记为
competitor_employee
,记录至竞争情报库
现有客户不发送销售邮件标记给客户成功/客户管理团队,记录入站行为

Nurture Sequence Setup (Category 2)

培育序列设置(分类2)

If a nurture sequence tool is configured:
  1. Group nurture leads by their "why not yet" reason — this determines the drip content
  2. Suggest sequence themes:
    • "Too small right now" → Growth-stage content, case studies of similar companies that grew into ICP
    • "Wrong stage" → Stage-appropriate content, milestone-based check-ins
    • "Missing requirement" → Product update notifications, roadmap content
  3. Add to appropriate sequence or produce a CSV for manual import
若已配置培育序列工具:
  1. 根据“暂不符合原因”对培育跟进客户进行分组——这将决定drip内容
  2. 建议序列主题:
    • “当前规模过小” → 增长阶段内容、类似公司成长为ICP客户的案例研究
    • “阶段不符” → 适配当前阶段的内容、基于里程碑的跟进
    • “缺少关键需求” → 产品更新通知、路线图内容
  3. 添加至对应序列,或生成CSV供手动导入

Re-Evaluation Triggers

重新评估触发条件

For Category 2 (nurture) leads, define when to re-evaluate:
  • Company raises funding → re-run qualification
  • Company headcount crosses threshold → re-run qualification
  • Person gets promoted → re-run qualification
  • 6 months have passed → manual re-evaluation prompt
If signal composites are active (
funding-signal-outreach
,
hiring-signal-outreach
,
champion-move-outreach
), these triggers happen automatically.

对于分类2(培育跟进)的客户,定义重新评估的触发条件:
  • 公司完成融资 → 重新运行资格判定
  • 公司员工数量达到阈值 → 重新运行资格判定
  • 对接人晋升 → 重新运行资格判定
  • 已过去6个月 → 触发人工重新评估提示
若信号流程已激活(
funding-signal-outreach
hiring-signal-outreach
champion-move-outreach
),这些触发条件将自动执行

Output Format

输出格式

Primary: Response Queue for Human Review

主输出:人工审核响应队列

markdown
undefined
markdown
undefined

Disqualification Handling: [Date]

不合格潜在客户处理:[日期]

Summary

摘要

  • Total disqualified/near-miss leads: X
  • Referral requests (right co, wrong person): X
  • Nurture (future fit): X
  • Polite decline: X
  • Competitor (no response): X
  • Existing customer (route to CS): X

  • 不合格/接近合格潜在客户总数: X
  • 推荐请求(公司匹配,对接人不符): X
  • 培育跟进(未来适配): X
  • 礼貌拒绝: X
  • 竞争对手(无响应): X
  • 现有客户(路由至客户成功): X

Referral Requests — Review & Send

推荐请求 — 审核并发送

[Name] — [Title] at [Company]

[姓名] — [职位] @ [公司]

  • Why not them: [one sentence — e.g., "Marketing coordinator, we need VP Engineering"]
  • Referral target: [Title/persona we want to reach]
  • Known contacts at company: [from enrichment/CRM, if any]
  • Draft email:
    [email draft]

  • 不符合原因: [一句话说明——如“营销协调员,我们需要对接工程副总裁”]
  • 推荐目标: [我们需要对接的职位/角色]
  • 已知公司联系人: [来自enrichment/CRM,如有]
  • 邮件草稿:
    [邮件草稿内容]

Nurture — Review & Send

培育跟进 — 审核并发送

[Name] — [Title] at [Company]

[姓名] — [职位] @ [公司]

  • Why not yet: [one sentence — e.g., "20 employees, ICP starts at 50"]
  • Re-evaluate when: [trigger — e.g., "headcount crosses 50" or "6 months"]
  • Draft email:
    [email draft]

  • 暂不符合原因: [一句话说明——如“15名员工,ICP要求最低50人”]
  • 重新评估时机: [触发条件——如“员工数量达到50人”或“6个月后”]
  • 邮件草稿:
    [邮件草稿内容]

Polite Decline — Review & Send

礼貌拒绝 — 审核并发送

[Name] — [Title] at [Company]

[姓名] — [职位] @ [公司]

  • Why not a fit: [one sentence]
  • Suggested alternative: [if known]
  • Draft email:
    [email draft]

  • 不符合原因: [一句话说明]
  • 推荐替代方案: [如有]
  • 邮件草稿:
    [邮件草稿内容]

Flagged (No Outreach)

特殊标记(不发送邮件)

Competitors:
  • [Name] from [Company] — [what they did] on [date]
Existing Customers:
  • [Name] from [Company] — [what they did] — Current account owner: [name]
undefined
竞争对手:
  • [姓名] 来自 [公司] — [行为] 于 [日期]
现有客户:
  • [姓名] 来自 [公司] — [行为] — 当前账户负责人:[姓名]
undefined

Secondary: CSV Export

次要输出:CSV导出

Append to the qualification CSV or produce a separate handling CSV:
  • All lead fields +
    handling_category
    ,
    handling_action
    ,
    email_draft
    ,
    referral_target
    ,
    nurture_trigger
    ,
    re_evaluate_date
Save to:
clients/<client-name>/leads/disqualification-handling-[date].csv

追加至资格判定CSV,或生成单独的处理CSV:
  • 所有潜在客户字段 +
    handling_category
    handling_action
    email_draft
    referral_target
    nurture_trigger
    re_evaluate_date
保存至:
clients/<client-name>/leads/disqualification-handling-[date].csv

Handling Edge Cases

边缘情况处理

Lead who's clearly a bot or spam: Skip all categories. Tag as
spam
and archive. Don't waste an email draft. Signs: gibberish name, test@test.com, form filled in < 2 seconds, obvious fake company.
Lead who requested a demo but is clearly disqualified: Still draft a polite decline. A demo request deserves a human response even if the answer is no. Consider: if they're a strong referral opportunity (right company), prioritize the referral path over the decline path.
Lead at a competitor's customer: This is NOT a competitor employee — this is someone at a company that uses a competitor. They came inbound, which means they might be looking to switch. Do NOT disqualify. Route back to qualification as a high-priority signal.
Multiple people from the same company, some qualified, some not: For disqualified people at a company where someone else qualified: Draft a softer version that acknowledges "we're already in touch with your team at [Company]" — don't send a rejection to someone whose colleague is in active talks.
Lead who's a journalist, analyst, or investor: Not a customer, but not a "decline" either. Flag separately: "Non-customer interest from [Name], [Role] at [Publication/Fund]. May be PR/AR opportunity." Route to marketing or founder.
Very high-volume batches (50+ disqualified):
  • Category 3 (polite decline) and Category 2 (nurture) can use lighter-touch templates rather than personalized drafts
  • Category 1 (referral requests) should always be personalized — these are the highest-value disqualified leads

明显是机器人或垃圾信息的潜在客户: 跳过所有分类。标记为
spam
并归档。不要浪费时间生成邮件草稿。特征:乱码姓名、test@test.com邮箱、2秒内完成表单填写、明显虚假的公司信息。
请求演示但明显不合格的潜在客户: 仍需生成礼貌拒绝邮件。演示请求值得人工响应,即使答案是否定的。如果是高价值推荐机会(公司匹配),优先采用推荐请求路径而非拒绝路径。
竞争对手客户的潜在客户: 这并非竞争对手员工——而是使用竞争对手产品的公司的员工。他们主动入站,意味着可能有更换供应商的意向。不要判定为不合格,路由回资格判定流程并标记为高优先级信号。
同一公司多人入站,部分合格部分不合格: 对于合格客户所在公司的不合格对接人,生成更温和的版本,提及“我们已与[公司]的团队取得联系”——不要向正在洽谈的同事发送拒绝邮件。
记者、分析师或投资人潜在客户: 并非客户,但也不属于“拒绝”范畴。单独标记:“非客户关注,来自[姓名],[职位] @ [媒体/基金]。可能存在PR/AR机会。” 路由至营销团队或创始人。
大批量潜在客户(50+不合格):
  • 分类3(礼貌拒绝)和分类2(培育跟进)可使用简化模板,而非个性化草稿
  • 分类1(推荐请求)必须始终个性化——这些是价值最高的不合格潜在客户

Email Hard Rules

邮件硬性规则

All draft emails must follow these rules regardless of category:
  1. No lies. Don't say "we'd love to work with you" if you're declining them.
  2. No guilt. Don't make them feel bad for reaching out.
  3. No jargon. "ICP", "qualification", "disqualified" never appear in emails.
  4. Brevity. Referral < 120 words. Nurture < 100 words. Decline < 80 words.
  5. One CTA maximum. Referral: make the intro. Nurture: check the resource. Decline: none or soft redirect.
  6. No false urgency. These are goodwill emails, not sales emails.
  7. Genuine value. If you offer a resource, it should actually help them — not be a disguised pitch.
  8. Reply-friendly. Write in a way that they COULD reply if they wanted to. No "noreply" energy.

所有邮件草稿无论分类,都必须遵循以下规则:
  1. 禁止说谎。如果要拒绝对方,不要说“我们很乐意与你合作”。
  2. 禁止制造愧疚感。不要让对方为主动联系而感到不适。
  3. 禁止使用行话。邮件中绝对不能出现“ICP”“qualification”“disqualified”这类词汇。
  4. 简洁。推荐请求邮件<120词,培育跟进邮件<100词,礼貌拒绝邮件<80词。
  5. 最多一个CTA。推荐请求:请求引荐;培育跟进:查看资源;礼貌拒绝:无或软引导。
  6. 禁止虚假紧迫感。这些是建立好感的邮件,而非销售邮件。
  7. 真实价值。如果提供资源,必须真正对对方有用——而非伪装成资源的产品宣传。
  8. 便于回复。邮件语气应让对方愿意回复,不要带有“noreply”的冷漠感。

Tools Required

所需工具

  • Email drafting — references
    email-drafting
    capability for tone and structure
  • CRM access — to update lead status, add tags, set reminders
  • Nurture sequence tool — to add leads to drip campaigns (Smartlead, HubSpot, etc.)
  • Supabase client — for pipeline lookups and signal cross-reference
  • Read/Write — for CSV output and config management
  • 邮件生成 — 依赖
    email-drafting
    能力处理语气和结构
  • CRM访问权限 — 用于更新潜在客户状态、添加标签、设置提醒
  • 培育序列工具 — 用于将客户添加至drip营销(如Smartlead、HubSpot等)
  • Supabase客户端 — 用于管道查询和信号交叉引用
  • 读写权限 — 用于CSV输出和配置管理