sales-customer-feedback
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseCustomer Feedback & VoC Strategy
客户反馈与VoC策略
Help the user design, optimize, and act on customer feedback programs — from choosing the right CX metrics and survey tools through improving response rates, building closed-loop workflows, and proving ROI.
帮助用户设计、优化客户反馈项目并将反馈转化为行动——从选择合适的CX指标和调查工具,到提升响应率、构建闭环工作流,再到证明投资回报率(ROI)。
Step 1 — Gather context
步骤1 — 收集背景信息
If exists, read it first for accumulated knowledge.
references/learnings.mdAsk the user:
-
What do you need help with?
- A) Choosing a feedback tool / platform comparison
- B) Designing a VoC program from scratch
- C) Improving survey response rates
- D) Choosing the right metric (NPS vs CSAT vs CES vs custom)
- E) Closing the loop — turning feedback into action
- F) Text analytics / making sense of open-ended responses
- G) Executive reporting / proving CX ROI
- H) Survey fatigue — customers feel over-surveyed
- I) Something else — describe it
-
What type of business?
- A) B2B SaaS
- B) B2B enterprise / services
- C) B2C ecommerce
- D) B2C subscription
- E) Financial services / healthcare / regulated
- F) Other
-
Current feedback tool? (Medallia, Qualtrics, SurveyMonkey, Typeform, Delighted, AskNicely, Skeepers, none yet, other)
-
What's your scale? (monthly feedback volume: <100, 100-1K, 1K-10K, 10K+)
If the user's request already provides enough context, skip to the relevant step. Lead with your best-effort answer, then ask 1-2 clarifying questions at the end.
若文件存在,请先读取其中积累的知识。
references/learnings.md向用户询问:
-
您需要哪方面的帮助?
- A) 选择反馈工具 / 平台对比
- B) 从零开始设计VoC项目
- C) 提升调查响应率
- D) 选择合适的指标(NPS vs CSAT vs CES vs 自定义指标)
- E) 闭环管理——将反馈转化为行动
- F) 文本分析 / 解读开放式反馈
- G) 高管汇报 / 证明CX的ROI
- H) 调查疲劳——客户反馈被过度调查
- I) 其他需求——请描述
-
您的业务类型是?
- A) B2B SaaS
- B) B2B企业/服务
- C) B2C电商
- D) B2C订阅服务
- E) 金融服务/医疗/受监管行业
- F) 其他
-
当前使用的反馈工具?(Medallia、Qualtrics、SurveyMonkey、Typeform、Delighted、AskNicely、Skeepers、尚未使用、其他)
-
业务规模?(月度反馈量:<100条、100-1000条、1000-10000条、10000条以上)
**若用户的请求已提供足够背景信息,可直接跳至对应步骤。**先给出初步解答,最后再提出1-2个澄清问题。
Step 2 — Route or answer directly
步骤2 — 转介或直接解答
If the request maps to a platform-specific skill, route:
- Typeform platform questions →
/sales-typeform {your question} - SurveyMonkey platform questions →
/sales-surveymonkey {your question} - Qualtrics platform questions →
/sales-qualtrics {your question} - Medallia platform questions →
/sales-medallia {your question} - Skeepers Feedback Management →
/sales-skeepers {your question} - Pendo NPS/CSAT/PMF surveys →
/sales-pendo {your question} - Whatfix in-app NPS/usability surveys →
/sales-whatfix {your question} - Chameleon in-app microsurveys (NPS/CSAT/PMF) →
/sales-chameleon {your question} - Vitally NPS/surveys (within a Customer Success platform) →
/sales-vitally {your question} - ChurnZero NPS/CSAT/CES surveys →
/sales-churnzero {your question} - In-app NPS/CSAT surveys →
/sales-in-app-messaging {your question} - Product review collection (public reviews) →
/sales-customer-reviews {your question} - Email survey delivery optimization →
/sales-email-marketing {your question} - SMS survey delivery →
/sales-sms-marketing {your question}
Otherwise, answer directly using the strategy guidance below.
若请求属于特定平台的问题,转至对应技能:
- Typeform平台相关问题 →
/sales-typeform {您的问题} - SurveyMonkey平台相关问题 →
/sales-surveymonkey {您的问题} - Qualtrics平台相关问题 →
/sales-qualtrics {您的问题} - Medallia平台相关问题 →
/sales-medallia {您的问题} - Skeepers反馈管理相关问题 →
/sales-skeepers {您的问题} - Pendo NPS/CSAT/PMF调查相关问题 →
/sales-pendo {您的问题} - Whatfix应用内NPS/可用性调查相关问题 →
/sales-whatfix {您的问题} - Chameleon应用内微型调查(NPS/CSAT/PMF)相关问题 →
/sales-chameleon {您的问题} - Vitally NPS/调查(客户成功平台内)相关问题 →
/sales-vitally {您的问题} - ChurnZero NPS/CSAT/CES调查相关问题 →
/sales-churnzero {您的问题} - 应用内NPS/CSAT调查相关问题 →
/sales-in-app-messaging {您的问题} - 产品评论收集(公开评论)相关问题 →
/sales-customer-reviews {您的问题} - 邮件调查发送优化相关问题 →
/sales-email-marketing {您的问题} - SMS调查发送相关问题 →
/sales-sms-marketing {您的问题}
否则,直接使用以下策略指南进行解答。
Step 3 — Feedback strategy
步骤3 — 反馈策略
CX metrics comparison
CX指标对比
| Metric | Measures | Best for | Question | Scale |
|---|---|---|---|---|
| NPS | Loyalty / advocacy | Relationship health, benchmarking | "How likely are you to recommend us?" | 0-10 |
| CSAT | Satisfaction with a specific interaction | Transactional touchpoints | "How satisfied were you with...?" | 1-5 |
| CES | Effort required | Support, onboarding, self-service | "How easy was it to...?" | 1-7 |
| Custom | Whatever matters to you | Specific business outcomes | Tailored to your context | Varies |
When to use which:
- NPS: Quarterly/annual relationship surveys + post-major-milestone (onboarding complete, renewal)
- CSAT: After every service interaction (support ticket, sales call, delivery)
- CES: After self-service flows (help center, checkout, account changes)
- Don't combine all three in one survey — pick the right metric for each touchpoint
| 指标 | 衡量维度 | 适用场景 | 典型问题 | 评分范围 |
|---|---|---|---|---|
| NPS | 客户忠诚度/推荐意愿 | 客户关系健康度、基准对比 | "您向他人推荐我们的可能性有多大?" | 0-10 |
| CSAT | 特定交互的满意度 | 交易型触点 | "您对本次[服务/交互]的满意度如何?" | 1-5 |
| CES | 客户付出的努力程度 | 支持服务、新用户引导、自助服务 | "您完成[操作]的难易程度如何?" | 1-7 |
| 自定义指标 | 您关注的特定维度 | 特定业务成果 | 根据业务场景定制 | 灵活可变 |
各指标适用时机:
- NPS: 季度/年度客户关系调查 + 重大里程碑后(如新用户引导完成、续约)
- CSAT: 每次服务交互后(如支持工单关闭、销售沟通、交付完成)
- CES: 自助服务流程后(如帮助中心使用、结账、账户变更)
- 不要在同一份调查中混用三个指标——每个触点选择合适的单一指标
Platform comparison
平台对比
| Platform | Best for | Pricing | Key strength |
|---|---|---|---|
| Medallia | Enterprise, 10K+ responses/mo | Custom (high, EDR-based) | Real-time action management, DXA, AI analytics |
| Qualtrics | Enterprise, research-heavy orgs | Custom (high, seat + response) | Survey methodology depth, XM suite breadth |
| SurveyMonkey | SMB, quick surveys | From $25/mo | Ease of use, fast setup, affordable |
| Typeform | Design-focused, conversational surveys | From $25/mo | Beautiful UX, high completion rates |
| Delighted | Startup NPS/CSAT | From $224/mo | Simple, focused on CX metrics |
| AskNicely | Frontline team NPS | Custom | Frontline coaching + NPS in one |
| CustomerGauge | B2B account experience | Custom | Account-level NPS, revenue attribution |
| Zonka Feedback | Mid-market, multi-channel | From $49/mo | Strong offline/kiosk + digital |
| Birdeye | Multi-location service businesses | ~$299/mo/location | Integrated with reviews + messaging, healthcare PMS connectors |
| Skeepers | Ecommerce (reviews + feedback) | From ~3K EUR/mo | Combined reviews + NPS/CSAT in one platform |
Decision framework:
- Just starting / <100 responses: SurveyMonkey or Typeform — simple, affordable
- Growing B2C: Delighted or Zonka — focused CX metrics without enterprise complexity
- B2B account health: CustomerGauge — ties NPS to revenue by account
- Enterprise program: Medallia or Qualtrics — full VoC platforms with action management
- Multi-location service business: Birdeye — surveys integrated with reviews, messaging, and listings in one platform
- Already using reviews platform: Skeepers — adds NPS/CSAT to existing review collection
| 平台 | 适用对象 | 定价 | 核心优势 |
|---|---|---|---|
| Medallia | 企业级、月度反馈量10000条以上 | 定制化(高定价,基于EDR) | 实时行动管理、DXA、AI分析能力 |
| Qualtrics | 企业级、侧重调研的组织 | 定制化(高定价,按席位+反馈量) | 深度调研方法论、全面的XM套件 |
| SurveyMonkey | 中小企业、快速调查 | 起价25美元/月 | 易用性强、快速搭建、性价比高 |
| Typeform | 注重设计、对话式调查 | 起价25美元/月 | 出色的用户体验、高完成率 |
| Delighted | 初创企业的NPS/CSAT需求 | 起价224美元/月 | 简洁易用、专注CX指标 |
| AskNicely | 一线团队的NPS管理 | 定制化 | 一线团队培训与NPS管理一体化 |
| CustomerGauge | B2B客户账户体验管理 | 定制化 | 账户级NPS、收入归因 |
| Zonka Feedback | 中型企业、多渠道需求 | 起价49美元/月 | 强大的线下/自助终端+数字化支持 |
| Birdeye | 多地点服务型企业 | 约299美元/月/地点 | 整合评论+消息功能、医疗PMS连接器 |
| Skeepers | 电商(评论+反馈) | 起价约3000欧元/月 | 整合评论与NPS/CSAT功能 |
决策框架:
- 刚起步 / 月度反馈<100条: SurveyMonkey或Typeform——简洁、性价比高
- 成长型B2C: Delighted或Zonka——专注CX指标,无企业级复杂度
- B2B账户健康管理: CustomerGauge——将NPS与账户收入关联
- 企业级项目: Medallia或Qualtrics——全功能VoC平台,支持行动管理
- 多地点服务企业: Birdeye——整合调查、评论、消息与列表管理
- 已使用评论平台: Skeepers——在现有评论收集基础上添加NPS/CSAT功能
Response rate optimization
响应率优化
Benchmark response rates by channel:
| Channel | Typical rate | Target |
|---|---|---|
| Email survey | 5-15% | 15-25% |
| SMS survey | 10-20% | 20-30% |
| In-app survey | 15-30% | 25-40% |
| Post-chat survey | 10-25% | 20-35% |
Proven tactics (in priority order):
- Shorten the survey — 2-3 questions max for transactional, 8-12 max for relationship
- Send immediately — within 1 hour of interaction for transactional surveys
- Use the right channel — match the interaction channel (chat → in-app, phone → SMS, email → email)
- Personalize sender and subject — personal name > company name, reference the interaction
- Embed the first question in the email — 1-click NPS rating in the email body
- Throttle aggressively — no more than 1 survey per customer per 90 days minimum
- Close the loop visibly — customers who see action from their feedback are 2x more likely to respond next time
各渠道基准响应率:
| 渠道 | 典型响应率 | 目标响应率 |
|---|---|---|
| 邮件调查 | 5-15% | 15-25% |
| SMS调查 | 10-20% | 20-30% |
| 应用内调查 | 15-30% | 25-40% |
| 聊天后调查 | 10-25% | 20-35% |
经验证的优化策略(按优先级排序):
- 缩短调查长度——交易型调查最多2-3个问题,关系型调查最多8-12个问题
- 即时发送——交易型调查需在交互后1小时内发送
- 匹配渠道——与交互渠道保持一致(聊天→应用内、电话→SMS、邮件→邮件)
- 个性化发件人与主题——个人名称>企业名称,提及具体交互内容
- 在邮件中嵌入首个问题——在邮件正文中实现一键NPS评分
- 严格控制调查频率——每位客户每90天最多收到1份调查
- 透明化闭环动作——看到反馈转化为行动的客户,下次响应率会提升2倍
Closed-loop feedback workflow
闭环反馈工作流
- Capture → Feedback received (survey response, social mention, support interaction)
- Route → Alert the right person based on score, topic, and customer segment
- Acknowledge → Respond to the customer within 24-48 hours (especially detractors)
- Investigate → Root cause analysis — is this a systemic issue or one-off?
- Act → Fix the root cause, not just the symptom
- Report → Track which issues were resolved and their impact on scores
- Communicate → Tell customers what changed because of their feedback ("You said, we did")
- 收集 → 获取反馈(调查响应、社交媒体提及、支持交互)
- 分派 → 根据评分、主题和客户细分,将反馈推送给对应负责人
- 确认 → 在24-48小时内回复客户(尤其是差评客户)
- 调查 → 根因分析——是系统性问题还是个别案例?
- 行动 → 解决根本原因,而非仅处理表面症状
- 汇报 → 跟踪已解决的问题及其对评分的影响
- 沟通 → 告知客户因他们的反馈做出了哪些改变(如“您的建议,我们已落实”)
Proving CX ROI
证明CX的ROI
- Link NPS to revenue: Promoters spend more / retain at higher rate than detractors
- Track closed-loop impact: Detractors who receive follow-up have higher retention
- Calculate cost of inaction: Revenue at risk from detractor accounts
- Benchmark against industry: Use published NPS benchmarks (Medallia, Qualtrics, Satmetrix)
- 关联NPS与收入: 推荐型客户的消费额/留存率远高于贬损型客户
- 跟踪闭环影响: 收到跟进的贬损型客户留存率更高
- 计算不作为的成本: 贬损型客户可能带来的收入损失
- 行业基准对比: 使用公开的NPS基准数据(来自Medallia、Qualtrics、Satmetrix)
Step 4 — Actionable guidance
步骤4 — 可落地指导
Focus on the user's specific situation: program design, survey design, tool setup, analysis, or closed-loop workflows. If you discover a tip not covered in , append it there.
references/learnings.md聚焦用户的具体场景:项目设计、调查设计、工具搭建、分析或闭环工作流。若发现未覆盖的技巧,可补充至该文件中。
references/learnings.mdGotchas
注意事项
Best-effort from research — review these, especially items about specific platform capabilities that may change.
-
NPS is not a universal metric. NPS measures loyalty/advocacy — it's meaningless for one-time transactions. Use CSAT or CES for transactional touchpoints.
-
Survey fatigue is the #1 silent killer. Over-surveying depresses response rates AND scores. Implement strict throttling rules across ALL survey tools — many organizations have multiple teams surveying the same customers independently.
-
"Improving NPS" is not a goal. NPS is a lagging indicator. Focus on fixing the drivers (product quality, support speed, onboarding friction) and the score follows.
-
Enterprise tools need enterprise budgets. Medallia and Qualtrics cost $100K-$500K+/year with professional services. Don't buy an enterprise platform for SMB survey needs.
-
Text analytics varies wildly. AI-powered text analysis from Medallia/Qualtrics is sophisticated. SurveyMonkey/Typeform text analysis is basic keyword matching. If open-ended analysis is critical, it influences tool choice.
-
Self-serve vs managed. Medallia is heavily consulting-dependent. Qualtrics is more self-serve but still complex. SurveyMonkey/Typeform are fully self-serve. Match the tool to your team's technical capability.
-
Self-improving: If you discover something not covered here, append it towith today's date.
references/learnings.md
基于研究的最佳实践——请留意这些内容,尤其是特定平台功能可能会发生变化。
-
NPS并非通用指标。NPS衡量的是忠诚度/推荐意愿——对一次性交易毫无意义。交易型触点请使用CSAT或CES。
-
调查疲劳是头号隐形杀手。过度调查会降低响应率和评分。在所有调查工具中实施严格的频率控制——许多企业存在多个团队独立向同一客户发送调查的情况。
-
“提升NPS”不是目标。NPS是滞后指标。应聚焦于解决驱动因素(产品质量、支持速度、新用户引导摩擦),评分自然会提升。
-
企业级工具需要企业级预算。Medallia和Qualtrics的年费在10万-50万美元以上,还需包含专业服务费用。不要为中小企业的调查需求购买企业级平台。
-
文本分析能力差异巨大。Medallia/Qualtrics的AI文本分析非常成熟,而SurveyMonkey/Typeform仅支持基础的关键词匹配。若开放式反馈分析至关重要,需将其纳入工具选择的考量因素。
-
自助服务vs托管服务。Medallia高度依赖咨询服务,Qualtrics相对更偏向自助但仍较复杂,SurveyMonkey/Typeform则完全自助。需根据团队的技术能力选择工具。
-
自我迭代: 若发现本文件未覆盖的内容,请添加至并标注日期。
references/learnings.md
Before recommending a specific platform skill
推荐特定平台技能前的注意事项
This skill covers a strategy domain across many platforms. Before pointing the user to any specific platform skill (any listed in , e.g., , , ), read that platform skill's actual first. The 1-line description in is enough to identify a candidate — it's not enough to commit to it or to write a prompt that invokes it well.
/sales-{platform}## Related skills/sales-mailshake/sales-klaviyo/sales-apolloSKILL.md## Related skillsHow to read it:
- If exists locally,
~/.claude/skills/{skill-name}/SKILL.mdit.Read - For skills,
sales-*directly from this repo:WebFetch— e.g., forhttps://raw.githubusercontent.com/sales-skills/sales/main/skills/{skill-name}/SKILL.md:sales-mailshake.https://raw.githubusercontent.com/sales-skills/sales/main/skills/sales-mailshake/SKILL.md - For non-skills (third-party), look up
sales-*in{org}/{repo}if installed and fetch the same~/.claude/skills/sales-do/references/skill-sources.mdpath under that repo.skills/{skill-name}/SKILL.md
After reading, ground your recommendation in something concrete from the SKILL.md (its scope, a sub-flow, its shape, or a "Do NOT use for..." negative trigger). Align any generated invocation with the platform skill's . If the platform skill turns out not to fit the user's situation, swap to another or handle the question here directly rather than recommending a poor fit.
argument-hintargument-hint本技能涵盖跨平台的策略领域。在引导用户使用任何特定平台技能(如中列出的,例如、、)之前,请先阅读该平台技能的文件。中的一行描述仅用于识别候选技能,不足以确认其适用性或编写合适的调用提示。
## 相关技能/sales-{platform}/sales-mailshake/sales-klaviyo/sales-apolloSKILL.md## 相关技能阅读方式:
- 若本地存在,直接读取。
~/.claude/skills/{skill-name}/SKILL.md - 对于技能,直接从仓库获取:
sales-*——例如https://raw.githubusercontent.com/sales-skills/sales/main/skills/{skill-name}/SKILL.md的链接为:sales-mailshake。https://raw.githubusercontent.com/sales-skills/sales/main/skills/sales-mailshake/SKILL.md - 对于非技能(第三方),若已安装,可在
sales-*中查找~/.claude/skills/sales-do/references/skill-sources.md,并从对应仓库的{org}/{repo}路径获取文件。skills/{skill-name}/SKILL.md
阅读后,需基于中的具体内容(范围、子流程、格式或“不适用于...”的排除条件)给出推荐。确保生成的调用提示与平台技能的一致。若该平台技能不符合用户场景,请更换其他技能或直接在此处解答问题,避免推荐不合适的技能。
SKILL.mdargument-hintargument-hintRelated skills
相关技能
- — SurveyMonkey platform help (survey creation, collectors, analytics, API). Install:
/sales-surveymonkeynpx skills add sales-skills/sales --skill sales-surveymonkey - — Qualtrics XM platform help (CX/EX surveys, dashboards, API, Experience Agents). Install:
/sales-qualtricsnpx skills add sales-skills/sales --skill sales-qualtrics - — Medallia platform help (Experience Cloud, DXA, contact center, APIs). Install:
/sales-medallianpx skills add sales-skills/sales --skill sales-medallia - — Skeepers platform help (Feedback Management module for NPS/CSAT). Install:
/sales-skeepersnpx skills add sales-skills/sales --skill sales-skeepers - — Birdeye platform help (surveys + reviews + messaging for multi-location businesses). Install:
/sales-birdeyenpx skills add sales-skills/sales --skill sales-birdeye - — Vitally platform help: Health Scores, NPS, Playbooks, Projects, API. Install:
/sales-vitallynpx skills add sales-skills/sales --skill sales-vitally - — ChurnZero platform help: Health Scores, Surveys (NPS/CSAT/CES), Plays, Journeys, API. Install:
/sales-churnzeronpx skills add sales-skills/sales --skill sales-churnzero - — Customer success strategy: health scores, churn prevention, onboarding, expansion, CS platform comparison. Install:
/sales-customer-successnpx skills add sales-skills/sales --skill sales-customer-success - — Product review collection strategy (different from feedback surveys — reviews are public, surveys are private). Install:
/sales-customer-reviewsnpx skills add sales-skills/sales --skill sales-customer-reviews - — Pendo platform help (in-app NPS/CSAT/PMF surveys, product analytics, guides). Install:
/sales-pendonpx skills add sales-skills/sales --skill sales-pendo - — In-app NPS/CSAT surveys as part of in-app messaging strategy. Install:
/sales-in-app-messagingnpx skills add sales-skills/sales --skill sales-in-app-messaging - — Typeform platform help — conversational forms, surveys, quizzes, API, Embed SDK. Install:
/sales-typeformnpx skills add sales-skills/sales --skill sales-typeform - — Not sure which skill to use? The router matches any sales objective to the right skill. Install:
/sales-donpx skills add sales-skills/sales --skill sales-do
- — SurveyMonkey平台帮助(调查创建、收集器、分析、API)。安装:
/sales-surveymonkeynpx skills add sales-skills/sales --skill sales-surveymonkey - — Qualtrics XM平台帮助(CX/EX调查、仪表盘、API、Experience Agents)。安装:
/sales-qualtricsnpx skills add sales-skills/sales --skill sales-qualtrics - — Medallia平台帮助(Experience Cloud、DXA、联络中心、API)。安装:
/sales-medallianpx skills add sales-skills/sales --skill sales-medallia - — Skeepers平台帮助(NPS/CSAT反馈管理模块)。安装:
/sales-skeepersnpx skills add sales-skills/sales --skill sales-skeepers - — Birdeye平台帮助(多地点企业的调查+评论+消息功能)。安装:
/sales-birdeyenpx skills add sales-skills/sales --skill sales-birdeye - — Vitally平台帮助:健康评分、NPS、Playbooks、项目、API。安装:
/sales-vitallynpx skills add sales-skills/sales --skill sales-vitally - — ChurnZero平台帮助:健康评分、调查(NPS/CSAT/CES)、Plays、客户旅程、API。安装:
/sales-churnzeronpx skills add sales-skills/sales --skill sales-churnzero - — 客户成功策略:健康评分、 churn预防、新用户引导、业务拓展、CS平台对比。安装:
/sales-customer-successnpx skills add sales-skills/sales --skill sales-customer-success - — 产品评论收集策略(与反馈调查不同——评论是公开的,调查是私密的)。安装:
/sales-customer-reviewsnpx skills add sales-skills/sales --skill sales-customer-reviews - — Pendo平台帮助(应用内NPS/CSAT/PMF调查、产品分析、引导)。安装:
/sales-pendonpx skills add sales-skills/sales --skill sales-pendo - — 应用内NPS/CSAT调查(作为应用内消息策略的一部分)。安装:
/sales-in-app-messagingnpx skills add sales-skills/sales --skill sales-in-app-messaging - — Typeform平台帮助——对话式表单、调查、测验、API、Embed SDK。安装:
/sales-typeformnpx skills add sales-skills/sales --skill sales-typeform - — 不确定使用哪个技能?该路由可将任何销售目标匹配到合适的技能。安装:
/sales-donpx skills add sales-skills/sales --skill sales-do
Examples
示例
Example 1: Starting a VoC program from scratch
示例1:从零开始搭建VoC项目
User: "I'm a B2B SaaS company with 500 customers. I have no feedback program. Where do I start?"
Approach: Start with two touchpoints — a quarterly relationship NPS survey (email, 3 questions: NPS + open-end + primary driver) and a post-support CSAT survey (triggered automatically after ticket closure). Use Delighted or SurveyMonkey to start — no need for enterprise tools at this scale. Set up a simple closed-loop: detractor alerts to CS team within 1 hour, follow-up call within 24 hours. Track NPS by cohort and segment. Graduate to Qualtrics or Medallia when you exceed 5K responses/month and need advanced analytics.
用户: "我们是一家拥有500个客户的B2B SaaS公司,目前没有任何反馈项目。应该从哪里开始?"
方案: 先从两个触点入手——季度客户关系NPS调查(邮件发送,3个问题:NPS+开放式问题+核心驱动因素)和售后CSAT调查(工单关闭后自动触发)。初期使用Delighted或SurveyMonkey即可——当前规模无需企业级工具。搭建简单的闭环流程:差评客户的反馈1小时内推送给客户成功团队,24小时内跟进电话。按客户群组和细分跟踪NPS。当月度反馈量超过5000条且需要高级分析能力时,再升级到Qualtrics或Medallia。
Example 2: NPS scores are flat despite improvement efforts
示例2:NPS分数停滞,尽管已采取改进措施
User: "Our NPS has been stuck at 32 for three quarters. We've been fixing bugs and improving support response time but the score won't budge."
Approach: Dig into the drivers, not the score. Segment NPS by customer type, product line, and tenure. Run text analytics on detractor comments to identify the top 3 themes — they may not be bugs or support speed. Check if survey population is representative (are you only surveying after support interactions?). Look at passive scores (7-8) — converting passives to promoters is often easier than converting detractors. Check survey fatigue — stagnant scores can mean only your most engaged customers respond, creating a ceiling.
用户: "我们的NPS连续三个季度停留在32分。我们一直在修复bug、提升支持响应速度,但分数毫无变化。"
方案: 深入分析驱动因素,而非仅关注分数本身。按客户类型、产品线和使用时长细分NPS数据。对差评客户的评论进行文本分析,找出Top3核心主题——可能并非bug或支持速度问题。检查调查样本是否具有代表性(是否仅在支持交互后发送调查?)。关注被动评分(7-8分)——将被动客户转化为推荐型客户通常比转化差评客户更容易。检查是否存在调查疲劳——分数停滞可能意味着只有最活跃的客户在响应,形成了评分天花板。
Example 3: Choosing between Medallia and Qualtrics
示例3:Medallia与Qualtrics二选一
User: "We're an enterprise with 50K customers across retail and digital channels. Should we go with Medallia or Qualtrics?"
Approach: Both are Gartner/Forrester leaders. Key differences: Medallia has built-in digital experience analytics (session replay, heatmaps) — Qualtrics requires a separate product. Medallia is stronger on real-time action management and contact center analytics. Qualtrics is stronger on survey methodology and research capabilities. Medallia is more consulting-dependent — expect higher professional services costs. Both are $200K+/year at enterprise scale. Request POCs from both and evaluate on: your team's technical capability (Qualtrics is more self-serve), your primary use case (action management vs research), and integration with your existing stack.
用户: "我们是一家拥有50000个客户的零售和全渠道企业,应该选择Medallia还是Qualtrics?"
方案: 两者均为Gartner/Forrester领导者。核心差异:Medallia内置数字体验分析(会话重放、热力图)——Qualtrics需单独购买相关产品。Medallia在实时行动管理和联络中心分析方面更强,Qualtrics在调研方法论和研究能力方面更突出。Medallia更依赖咨询服务——专业服务成本更高。两者的企业级年费均在20万美元以上。建议向两家供应商申请POC,从以下维度评估:团队技术能力(Qualtrics更偏向自助)、核心使用场景(行动管理vs调研)、与现有技术栈的集成度。
Troubleshooting
故障排查
Survey response rates are below 5%
调查响应率低于5%
- Audit survey length. If your transactional survey has more than 3 questions, that's likely the problem. Cut to NPS + open-end only.
- Check delivery timing. Surveys sent days after an interaction get ignored. Automate delivery within 1 hour.
- Test the email/SMS. Send yourself a test — does it land in spam? Is the subject line compelling? Can you rate in-email without clicking through?
- Audit throttling. If customers receive surveys from multiple teams/touchpoints, they tune out. Implement cross-program throttling.
- 审核调查长度。若交易型调查超过3个问题,这很可能是核心原因。精简为仅保留NPS+开放式问题。
- 检查发送时机。交互几天后发送的调查会被忽略。设置为交互后1小时内自动发送。
- 测试邮件/SMS。给自己发送测试邮件——是否进入垃圾邮件?主题是否吸引人?是否无需跳转即可在邮件内评分?
- 审核调查频率控制。若客户收到来自多个团队/触点的调查,会产生抵触情绪。实施跨项目的频率控制。
Feedback isn't driving any action
反馈未驱动任何行动
- Alerts aren't reaching the right people. Route detractor alerts to the person who can act (frontline manager, account owner), not a shared inbox.
- No accountability for follow-up. Assign ownership and SLAs for detractor follow-up (24-hour response target). Track and report on closure rates.
- Insights stay in the CX team. Share verbatim customer comments (not just scores) with product, engineering, and leadership weekly. Real quotes drive action better than dashboards.
- 警报未送达对应负责人。将差评警报推送给能够采取行动的人(一线经理、账户负责人),而非共享收件箱。
- 跟进无问责机制。为差评跟进分配负责人和服务水平协议(SLA)(如24小时内响应)。跟踪并汇报闭环完成率。
- 洞察仅停留在CX团队。每周将客户的真实评论(而非仅分数)分享给产品、工程和领导层。真实的客户声音比仪表盘更能驱动行动。
Customers complain about being over-surveyed
客户反馈被过度调查
- Implement global throttling. No customer should receive more than 1 survey per 90 days across ALL programs. This requires coordination across teams.
- Switch to always-on channels. Replace some surveys with passive feedback (in-app feedback button, website comment box, social listening). You get continuous signal without asking.
- Communicate the value. When you fix something based on feedback, tell customers: "Based on your feedback, we've improved X." This makes the next survey feel worthwhile.
- 实施全局频率控制。所有项目中,每位客户每90天最多收到1份调查。这需要跨团队协调。
- 切换至持续反馈渠道。用被动反馈替代部分调查(如应用内反馈按钮、网站意见箱、社交媒体监听)。无需主动询问即可持续获取反馈信号。
- 传递反馈价值。当根据反馈做出改进时,告知客户:"基于您的反馈,我们已优化了[功能/服务]。"这会让下一次调查更有意义。