Testimonial Collector

客户推荐语收集工具

Mode

模式

Detect from context or ask: "One script, full system, or full system with campaign?"

Mode	What you get	Best for
`quick`	1 outreach script + 1 format template	Asking one client, right now
`standard`	Full collection system: timing, scripts, formatting, display guidance	Building repeatable social proof
`deep`	Full system + multi-channel strategy + case study pipeline	Sales enablement, proposal library

Default:
standard
— use

quick

if they have one client in mind. Use

deep

if they want a system they can hand to a VA.

从上下文推断或询问用户："单脚本、完整系统还是带推广活动的完整系统？"

模式	你将获得	适用场景
`quick`	1份外联脚本 + 1份格式模板	当下只需要向单个客户索要推荐语
`standard`	完整收集系统：时机选择、脚本、格式、展示指导	搭建可复用的社交证明体系
`deep`	完整系统 + 多渠道策略 + 案例研究pipeline	销售赋能、方案库搭建

默认模式：
standard
— 如果用户已经有明确的目标单个客户，使用

quick

模式。如果用户需要一套可以交给虚拟助理（VA）执行的系统，使用

deep

模式。

Context Loading Gates

上下文加载门槛

Before proceeding, gather:

Client name, company, and industry
Project type and specific deliverables
Key results — push for at least one number ("even a rough estimate")
Desired output format (short quote / medium paragraph / full narrative)
Urgency (this week vs. building a library)

If results are vague (e.g., "things improved"), stop and ask: "Can you name one specific number — even a rough estimate? That's what makes a testimonial credible and usable." Do not draft until you have this.

If the user wants to skip a field: note it and flag the quality impact in the output.

在继续操作前，收集以下信息：

客户姓名、公司及所属行业
项目类型和具体交付物
核心成果——尽量索要至少一个量化数据（"哪怕是粗略估算的也行"）
期望的输出格式（短引语 / 中等长度段落 / 完整叙述）
紧急程度（本周要用 vs 搭建资源库）

如果成果描述模糊（例如"情况有所改善"），停下并询问用户： "你能提供一个具体的数字吗？哪怕是粗略估算的也可以。这是让客户推荐语可信、可用的核心。" 在拿到这个信息前不要起草内容。

如果用户想要跳过某个字段：记录该情况，并在输出中标注对内容质量的影响。

Phase 1: Situation Analysis

阶段1：情况分析

Before drafting anything, reason through:

Client relationship stage: Was this a quick project or a deep engagement? Depth affects how much authentic language is available.
Results clarity: Are the outcomes measurable (numbers, timelines, named outcomes) or soft (vibes, general satisfaction)?
Format match: What placement does the user need this for? A homepage needs different length than a sales deck.
Voice data: Does the user have existing communication from this client (emails, Slack, quotes) that can inform tone?

Output a brief situation summary:

"You have a [length] engagement with [client] in [industry], with [strong/weak] results data. I'll draft in [format] with [authentic/templated] voice. Main gap to address: [specific gap]."

在起草任何内容前，先梳理清楚以下几点：

客户关系阶段： 这是一个短期项目还是深度合作？合作深度决定了可以使用的真实语言的丰富度。
成果清晰度： 产出是可衡量的（数字、时间线、明确的成果）还是软性的（感受、总体满意度）？
格式匹配度： 用户需要把推荐语放在什么位置？首页用的版本和销售PPT用的版本长度要求完全不同。
语气参考： 用户有没有和该客户的现有沟通记录（邮件、Slack消息、引语）可以用来参考语气？

输出简短的情况总结：

"你和[所属行业]的[客户名称]有[时长]的合作，成果数据[充足/不足]。我将采用[格式]、用[真实/模板化]语气起草内容。需要解决的核心缺口：[具体缺口]。"

Phase 2: Quality Scoring Framework

阶段2：质量评分框架

Score the raw testimonial content (or anticipated content) before drafting:

Dimension	Score 1	Score 3	Score 5
Specificity	No details	Vague references	Specific named result
Measurability	"It was great"	"Noticeable improvement"	"40% increase in leads"
Authentic Voice	Sounds like ad copy	Slightly stilted	Reads exactly how a person talks
Length	Too short (no context)	Decent but thin	Enough for all 3 formats

Scoring rule:

4+ on all 4 dimensions → ready to use
≤2 on any dimension → apply iteration protocol before delivering

在起草前对原始客户推荐语内容（或预期内容）打分：

评分维度	1分	3分	5分
具体性	无任何细节	模糊的指代	明确的、有名称的成果
可衡量性	"It was great"	"Noticeable improvement"	"40% increase in leads"
语气真实度	听起来像广告文案	略显生硬	读起来和真人说话完全一致
长度	太短（无上下文）	尚可但内容单薄	足够满足3种格式的使用需求

评分规则：

4个维度得分都≥4 → 可直接使用
任意维度得分≤2 → 交付前执行迭代流程

Phase 3: Draft Generation

阶段3：草稿生成

The Ask Templates

索要模板

Direct Ask:

Subject: Quick favor (30 seconds)

Hey [Name],

Loved working on [project] with you — especially seeing [specific result].

Would you be open to sharing a quick testimonial I could use on my site?

No pressure. If yes, I can either:
A) Send you 3 questions to answer
B) Write a draft for you to approve/edit

Whatever's easier.

Question Route:

3 quick questions:
1. What was the situation before we worked together?
2. What changed or improved?
3. Would you recommend this to others? Why?

Draft-on-Behalf Framework: Rules for writing in the client's voice:

Tone: Match their actual communication style (check emails/messages for vocabulary)
Structure: Situation Before → What Changed → Specific Result → Recommendation
Avoid: Superlatives without evidence ("amazing," "life-changing")
Avoid: Leading with praise — lead with the client's situation
Length: 50-75 words (short), 100-150 words (medium), 200+ (long/full)

Fill-in template:

"[Client situation in 1 sentence]. [What the engagement delivered — concrete]. 
[Specific result, ideally with a number]. [Recommendation statement in client's natural voice]."

直接索要：

Subject: Quick favor (30 seconds)

Hey [Name],

Loved working on [project] with you — especially seeing [specific result].

Would you be open to sharing a quick testimonial I could use on my site?

No pressure. If yes, I can either:
A) Send you 3 questions to answer
B) Write a draft for you to approve/edit

Whatever's easier.

问卷路径：

3 quick questions:
1. What was the situation before we worked together?
2. What changed or improved?
3. Would you recommend this to others? Why?

代起草框架： 用客户语气撰写的规则：

语气： 匹配客户实际的沟通风格（查看邮件/消息确认用词习惯）
结构： 之前的情况 → 发生了什么改变 → 具体成果 → 推荐
避免： 没有证据支撑的最高级形容词（"amazing"、"life-changing"）
避免： 以赞美开头 → 以客户的实际情况开头
长度： 50-75词（短版）、100-150词（中版）、200+词（长版/完整版）

填充模板：

"[Client situation in 1 sentence]. [What the engagement delivered — concrete]. 
[Specific result, ideally with a number]. [Recommendation statement in client's natural voice]."

Phase 4: Format Production

阶段4：格式输出

Short Format (2-liner)

短格式（2行版）

"[One punchy outcome sentence — lead with the result]"
— [Name], [Title] at [Company]

Use for: Homepage, LinkedIn featured section, proposal proof points

"[One punchy outcome sentence — lead with the result]"
— [Name], [Title] at [Company]

适用场景： 首页、LinkedIn精选栏、方案证明点

Medium Format (2-3 sentences)

中格式（2-3句话）

"[Problem or situation]. [What changed]. [Recommendation or result]."
— [Name], [Title] at [Company]

Use for: Services page, sales decks, email sequences

"[Problem or situation]. [What changed]. [Recommendation or result]."
— [Name], [Title] at [Company]

适用场景： 服务介绍页、销售PPT、邮件序列

Long Format (Full narrative)

长格式（完整叙述）

Structure:

Context paragraph (2-3 sentences on the situation)
Transformation paragraph (what happened during the engagement)
Results paragraph (outcomes, numbers, named wins)
Closing recommendation sentence

Use for: Case study pages, downloadable PDFs, high-trust sales assets

结构：

上下文段落（2-3句话介绍背景情况）
转变段落（合作期间发生的变化）
成果段落（产出、数字、明确的成果）
结尾推荐句

适用场景： 案例研究页、可下载PDF、高信任度销售素材

Phase 5: Self-Critique Pass (REQUIRED)

阶段5：自我校验环节（必填）

After generating all formats, evaluate:

Specificity check: Does the short version have at least one concrete outcome (not just "great results")? Voice check: Could the client have actually written this, or does it sound like a marketing headline? Placement check: Is the recommended format actually correct length for the stated use case? Ethics check: Does the draft contain any claims the client didn't make or numbers you added?

Flag any issues: "The short version lacks a specific metric — you'll need to get one number from the client before using this on a homepage."

生成所有格式后，评估以下几点：

具体性检查： 短版本是否至少包含一个具体成果（不只是"成果很棒"）？ 语气检查： 这是不是客户可能会写出来的内容，还是听起来像营销标题？ 场景匹配检查： 推荐的格式长度是否符合声明的使用场景要求？ 合规性检查： 草稿中是否包含任何客户没有提到的主张，或者你自行添加的数字？

标注所有问题："短版本缺少具体指标——你在首页使用该内容前需要从客户处拿到一个具体数字。"

Iteration Protocol

迭代流程

If the received testimonial scores ≤2 on any dimension, send this gentle follow-up:

"Thanks so much — this is great. One small ask: could you add one specific 
number or outcome? Even rough ('saved us about 5 hours a week') makes it 
much more compelling for other clients. Totally optional, but makes a real difference."

If a second request still yields nothing specific: use Tier 3 proxy language:

"noticeable improvement in [area]" or "process now runs without manual oversight"

如果收到的客户推荐语任意维度得分≤2，发送以下温和的跟进消息：

"Thanks so much — this is great. One small ask: could you add one specific 
number or outcome? Even rough ('saved us about 5 hours a week') makes it 
much more compelling for other clients. Totally optional, but makes a real difference."

如果第二次请求仍然没有得到具体信息：使用三级替代表述：

"在[领域]有明显提升" 或者 "流程现在无需人工监督即可运行"

Placement Recommendation

投放位置推荐

Always deliver a placement recommendation with the formatted testimonials:

Format	Recommended Locations	Why
Short (2-liner)	Homepage, proposals, LinkedIn	Trust at first glance
Medium	Services page, email, sales decks	Overcome late-stage objections
Long	Case study page, PDF, portfolio	Deep proof for serious buyers

Cross-reference: If this client has a strong story, suggest running

case-study-builder

to expand into a full case study.

交付格式化的推荐语时，始终同步提供投放位置建议：

格式	推荐位置	原因
短版（2行）	首页、方案、LinkedIn	第一眼就建立信任
中版	服务页、邮件、销售PPT	打消决策后期的异议
长版	案例研究页、PDF、作品集	为高意向买家提供深度证明

交叉参考： 如果该客户的故事性很强，建议运行

case-study-builder

将其扩展为完整的案例研究。

Output Structure

输出结构

markdown

undefined

markdown

undefined

Testimonial: [Client Name] — [Date]

Quality Assessment

Specificity: [X/5]
Measurability: [X/5]
Authentic Voice: [X/5]
Length: [X/5]
Total: [X/20] — [Ready to use / Needs iteration]

Specificity: [X/5]
Measurability: [X/5]
Authentic Voice: [X/5]
Length: [X/5]
Total: [X/20] — [Ready to use / Needs iteration]

Short Format (2-liner)

"[Quote]" — [Name], [Title], [Company]

Medium Format

"[Quote]" — [Name], [Title], [Company]

Long Format

[Full narrative]

Placement Recommendation

[Where to use each format]

Next Step

[Iteration note OR cross-reference to case-study-builder]


---

*Skill by Brian Wagner | AI Marketing Architect | brianrwagner.com*

[Iteration note OR cross-reference to case-study-builder]


---

*技能作者：Brian Wagner | AI营销架构师 | brianrwagner.com*

testimonial-collector

Original

Translation

Testimonial Collector

客户推荐语收集工具

Mode

模式

Context Loading Gates

上下文加载门槛

Phase 1: Situation Analysis

阶段1：情况分析

Phase 2: Quality Scoring Framework

阶段2：质量评分框架

Phase 3: Draft Generation

阶段3：草稿生成

The Ask Templates

索要模板

Phase 4: Format Production

阶段4：格式输出

Short Format (2-liner)

短格式（2行版）

Medium Format (2-3 sentences)

中格式（2-3句话）

Long Format (Full narrative)

长格式（完整叙述）

Phase 5: Self-Critique Pass (REQUIRED)

阶段5：自我校验环节（必填）

Iteration Protocol

迭代流程

Placement Recommendation

投放位置推荐

Output Structure

输出结构

Testimonial: [Client Name] — [Date]

Testimonial: [Client Name] — [Date]

Quality Assessment

Quality Assessment

Short Format (2-liner)

Short Format (2-liner)

Medium Format

Medium Format

Long Format

Long Format

Placement Recommendation

Placement Recommendation

Next Step

Next Step