sales-social-listening

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Social Listening & Brand Monitoring Strategy

社交聆听与品牌监测策略

Helps the user plan and execute social listening programs — from choosing the right tool and setting up monitoring through sentiment analysis, competitive intelligence, crisis detection, and reporting.
帮助用户规划并执行社交聆听项目——从选择合适的工具、设置监测,到情感分析、竞争情报、危机检测及报告。

Step 1 — Gather context

步骤1 — 收集背景信息

If
references/learnings.md
exists, read it first for accumulated knowledge.
Ask the user:
  1. What do you need help with?
    • A) Choosing a social listening tool
    • B) Setting up brand monitoring (keywords, sources, alerts)
    • C) Competitive intelligence / share of voice
    • D) Sentiment analysis and brand health tracking
    • E) Crisis detection and real-time alerts
    • F) Consumer insights and trend analysis
    • G) Reporting and stakeholder communication
    • H) Something else — describe it
  2. What's your primary use case?
    • A) PR / Communications — tracking media coverage and brand perception
    • B) Marketing — understanding audience sentiment and campaign impact
    • C) Sales / Competitive intel — monitoring competitors and market signals
    • D) Product — tracking feature requests, complaints, and user feedback
    • E) Executive / C-suite — brand health dashboards and crisis alerts
    • F) Agency — managing monitoring for multiple clients
  3. Current setup?
    • A) No monitoring in place yet
    • B) Manual monitoring (Google Alerts, manual social checks)
    • C) Using a tool — which one?
    • D) Evaluating tools / switching platforms
  4. Budget range?
    • A) Free / minimal (under $100/mo)
    • B) Mid-market ($100-1,000/mo)
    • C) Enterprise ($1,000+/mo)
    • D) Not sure yet
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.
references/learnings.md
存在,请先阅读其中积累的知识。
询问用户:
  1. 你需要哪方面的帮助?
    • A) 选择社交聆听工具
    • B) 设置品牌监测(关键词、来源、警报)
    • C) 竞争情报/声量份额分析
    • D) 情感分析与品牌健康追踪
    • E) 危机检测与实时警报
    • F) 消费者洞察与趋势分析
    • G) 报告与利益相关者沟通
    • H) 其他——请描述
  2. 你的主要使用场景是什么?
    • A) 公关/传播——追踪媒体报道与品牌认知
    • B) 营销——了解受众情绪与活动效果
    • C) 销售/竞争情报——监测竞争对手与市场信号
    • D) 产品——追踪功能需求、投诉与用户反馈
    • E) 高管/管理层——品牌健康仪表盘与危机警报
    • F) 代理机构——为多个客户管理监测项目
  3. 当前的监测设置情况?
    • A) 尚未开展任何监测
    • B) 手动监测(Google Alerts、手动检查社交媒体)
    • C) 使用某款工具——具体是哪一款?
    • D) 正在评估工具/更换平台
  4. 预算范围?
    • A) 免费/低成本(每月低于100美元)
    • B) 中端市场(每月100-1000美元)
    • C) 企业级(每月1000美元以上)
    • D) 尚未确定
如果用户的请求已提供大部分此类背景信息,请直接跳至相关步骤。 先基于合理假设(需明确说明)给出最佳答案,最后仅询问最关键的1-2个澄清问题。

Step 2 — Route or answer directly

步骤2 — 转介或直接解答

If the request maps to a platform-specific skill, route:
  • Sprout Social setup, config, or features →
    /sales-sproutsocial
  • Brandwatch setup, config, or features →
    /sales-brandwatch
  • Meltwater setup, config, or features →
    /sales-meltwater
  • Influencity Monitoring or influencer marketing →
    /sales-influencity
  • Influencer discovery or campaign tracking →
    /sales-influencer-marketing
  • Email marketing analytics →
    /sales-email-marketing
  • SEO keyword research →
    /sales-semrush
  • Sales intent signals →
    /sales-intent
  • GRIN social listening setup or configuration →
    /sales-grin
Otherwise, answer directly from the strategy knowledge below.
若请求对应特定平台技能,请转介:
  • Sprout Social的设置、配置或功能 →
    /sales-sproutsocial
  • Brandwatch的设置、配置或功能 →
    /sales-brandwatch
  • Meltwater的设置、配置或功能 →
    /sales-meltwater
  • Influencity监测或网红营销 →
    /sales-influencity
  • 网红发掘或活动追踪 →
    /sales-influencer-marketing
  • 电子邮件营销分析 →
    /sales-email-marketing
  • SEO关键词研究 →
    /sales-semrush
  • 销售意向信号 →
    /sales-intent
  • GRIN社交聆听设置或配置 →
    /sales-grin
否则,直接根据下方的策略知识解答。

Step 3 — Social listening strategy reference

步骤3 — 社交聆听策略参考

Read
references/platform-guide.md
for detailed platform comparison, monitoring setup, Boolean query guidance, sentiment analysis, competitive intelligence, crisis detection, consumer insights, and reporting frameworks.
You no longer need the platform guide details — focus on the user's specific situation.
阅读
references/platform-guide.md
获取详细的平台对比、监测设置、布尔查询指南、情感分析、竞争情报、危机检测、消费者洞察及报告框架。
你无需再关注平台指南的细节——专注于用户的具体情况。

Step 4 — Actionable guidance

步骤4 — 可落地的指导建议

Based on the user's specific question:
  1. Tool selection — recommend the best tool for their use case, budget, and team
  2. Monitoring setup — design keyword strategy, configure sources, set up alerts
  3. Competitive analysis — build competitor tracking, measure share of voice
  4. Crisis plan — configure detection, design escalation workflow
  5. Reporting — design dashboards and reports for their stakeholders
根据用户的具体问题:
  1. 工具选择——根据其使用场景、预算与团队规模推荐最合适的工具
  2. 监测设置——设计关键词策略、配置来源、设置警报
  3. 竞争分析——建立竞争对手追踪机制、衡量声量份额
  4. 危机预案——配置检测机制、设计升级流程
  5. 报告——为利益相关者设计仪表盘与报告

Gotchas

注意事项

Best-effort from research — review these, especially items about pricing and capabilities that may change.
  • Enterprise tools lock you into annual contracts. Meltwater, Brandwatch, and Talkwalker all require annual commitments with non-transparent pricing. Budget $6K-50K+/year. Negotiate hard before signing and clarify cancellation terms.
  • Sentiment analysis has a ceiling. No tool exceeds ~85% accuracy on English text. Plan for manual review of high-impact mentions. Non-English, sarcasm, and industry jargon degrade accuracy further.
  • More sources ≠ better monitoring. Noisy monitoring is worse than no monitoring. Start narrow, validate results, then expand. A focused query with 100 relevant mentions beats a broad one with 10,000 noisy ones.
  • Free tools have severe limitations. Google Alerts and free tiers miss most social mentions, have no sentiment analysis, and provide no historical data. They're fine for awareness, not for strategic intelligence.
  • Social platform data access is shrinking. X/Twitter, Reddit, and Meta regularly restrict API access. Tools that are official data partners (Meltwater is a Reddit data partner) have more reliable access. Check which platforms your tool can actually monitor.
  • ROI is hard to prove directly. Social listening ROI is often indirect (faster crisis response, better content strategy, competitive awareness). Don't promise direct revenue attribution from listening alone.
  • Self-improving: If you discover something not covered here, append it to
    references/learnings.md
    with today's date.
基于研究给出最佳建议——请特别关注可能变化的定价与功能相关内容。
  • 企业级工具要求年度合同绑定:Meltwater、Brandwatch和Talkwalker均要求年度承诺,且定价不透明。预算为每年6000-50000美元以上。签约前务必全力协商,并明确取消条款。
  • 情感分析存在精度上限:没有工具对英文文本的准确率能超过约85%。计划对高影响力提及进行人工审核。非英文内容、讽刺语及行业术语会进一步降低准确率。
  • 来源越多≠监测效果越好:嘈杂的监测不如不监测。先从窄范围开始,验证结果后再扩展。一个聚焦的查询得到100条相关提及,胜过宽泛查询得到的10000条无关提及。
  • 免费工具存在严重局限性:Google Alerts及免费版本会错过大部分社交提及,无情感分析功能,也不提供历史数据。它们仅适合用于品牌认知,不适合战略情报收集。
  • 社交平台数据访问权限正在收紧:X/Twitter、Reddit和Meta经常限制API访问。成为官方数据合作伙伴的工具(如Meltwater是Reddit数据合作伙伴)拥有更可靠的访问权限。请确认你的工具实际能监测哪些平台。
  • ROI难以直接证明:社交聆听的ROI通常是间接的(更快的危机响应、更优的内容策略、竞争认知提升)。不要承诺仅通过聆听就能直接带来收入归因。
  • 自我改进:若发现此处未涵盖的内容,请将其添加到
    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
/sales-{platform}
listed in
## Related skills
, e.g.,
/sales-mailshake
,
/sales-klaviyo
,
/sales-apollo
), read that platform skill's actual
SKILL.md
first. The 1-line description in
## Related skills
is enough to identify a candidate — it's not enough to commit to it or to write a prompt that invokes it well.
How to read it:
  • If
    ~/.claude/skills/{skill-name}/SKILL.md
    exists locally,
    Read
    it.
  • For
    sales-*
    skills,
    WebFetch
    directly from this repo:
    https://raw.githubusercontent.com/sales-skills/sales/main/skills/{skill-name}/SKILL.md
    — e.g., for
    sales-mailshake
    :
    https://raw.githubusercontent.com/sales-skills/sales/main/skills/sales-mailshake/SKILL.md
    .
  • For non-
    sales-*
    skills (third-party), look up
    {org}/{repo}
    in
    ~/.claude/skills/sales-do/references/skill-sources.md
    if installed and fetch the same
    skills/{skill-name}/SKILL.md
    path under that repo.
After reading, ground your recommendation in something concrete from the SKILL.md (its scope, a sub-flow, its
argument-hint
shape, or a "Do NOT use for..." negative trigger). Align any generated invocation with the platform skill's
argument-hint
. 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.
本技能涵盖跨多个平台的策略领域。在将用户引导至任何特定平台技能(如
## 相关技能
中列出的任何
/sales-{platform}
,例如
/sales-mailshake
/sales-klaviyo
/sales-apollo
)之前,请先阅读该平台技能的实际
SKILL.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.md
中的具体内容(其范围、子流程、
argument-hint
格式,或“不适用于...”的排除条件)给出推荐。确保生成的调用与平台技能的
argument-hint
一致。若该平台技能不符合用户情况,请更换其他技能或在此直接处理问题,而非推荐不合适的选项。

Related skills

相关技能

  • /sales-sproutsocial
    — Sprout Social platform help — Publishing, Smart Inbox, Analytics, Listening, Influencer, Advocacy, API
  • /sales-brandwatch
    — Brandwatch platform help — Consumer Intelligence, Social Media Management, Influence, API
  • /sales-meltwater
    — Meltwater platform help — monitoring, media relations, API, integrations
  • /sales-social-media-management
    — Social media management strategy — publishing, scheduling, engagement, tool comparison
  • /sales-employee-advocacy
    — Employee advocacy strategy — content curation, gamification, compliance
  • /sales-intent
    — Buying intent signals and prioritization from monitoring data
  • /sales-influencity
    — Influencity platform help — Monitoring module for brand tracking and competitor analysis
  • /sales-influencer-marketing
    — Influencer discovery and campaign tracking
  • /sales-content
    — Sales content management and strategy
  • /sales-brandjet
    — BrandJet AI platform help — outreach, brand intelligence, AI monitoring
  • /sales-grin
    — GRIN platform help — includes social listening with hashtag monitoring and brand mention alerts
  • /sales-ai-visibility
    — AI visibility monitoring — track what LLMs say about your brand
  • /sales-do
    — Not sure which skill to use? The router matches any sales objective to the right skill. Install:
    npx skills add sales-skills/sales --skill sales-do
  • /sales-sproutsocial
    ——Sprout Social平台支持——发布、智能收件箱、分析、聆听、网红、品牌拥护者、API
  • /sales-brandwatch
    ——Brandwatch平台支持——消费者情报、社交媒体管理、影响力、API
  • /sales-meltwater
    ——Meltwater平台支持——监测、媒体关系、API、集成
  • /sales-social-media-management
    ——社交媒体管理策略——发布、排期、互动、工具对比
  • /sales-employee-advocacy
    ——员工品牌拥护策略——内容策划、游戏化、合规
  • /sales-intent
    ——从监测数据中获取购买意向信号并排序
  • /sales-influencity
    ——Influencity平台支持——品牌追踪与竞争分析的监测模块
  • /sales-influencer-marketing
    ——网红发掘与活动追踪
  • /sales-content
    ——销售内容管理与策略
  • /sales-brandjet
    ——BrandJet AI平台支持——推广、品牌情报、AI监测
  • /sales-grin
    ——GRIN平台支持——包含带话题监测与品牌提及警报的社交聆听功能
  • /sales-ai-visibility
    ——AI可见性监测——追踪LLM对品牌的评价
  • /sales-do
    ——不确定使用哪项技能?该路由器可将任何销售目标匹配到合适的技能。安装方式:
    npx skills add sales-skills/sales --skill sales-do

Examples

示例

Example 1: Choose a social listening tool

示例1:选择社交聆听工具

User says: "I'm a PR manager at a mid-size SaaS company. I need to monitor our brand mentions across news and social. Budget is around $500/mo." Skill does:
  1. Evaluates budget constraint against platform pricing
  2. Recommends Brand24 ($79/mo) for affordable monitoring with decent coverage, or Mention ($41/mo) for simpler needs
  3. Notes that enterprise tools (Meltwater, Brandwatch) are out of budget range
  4. Suggests trial periods to test coverage quality for their specific industry Result: Clear recommendation matched to budget and use case
用户提问:"我是一家中型SaaS公司的公关经理。我需要监测新闻和社交媒体上的品牌提及。预算约为每月500美元。" 技能处理
  1. 根据预算限制评估平台定价
  2. 推荐Brand24(每月79美元),它能提供性价比不错的监测覆盖;若需求更简单,可推荐Mention(每月41美元)
  3. 说明企业级工具(Meltwater、Brandwatch)超出预算范围
  4. 建议试用不同工具,测试其在特定行业的覆盖质量 结果:给出符合预算与使用场景的明确推荐

Example 2: Set up competitive monitoring

示例2:设置竞争监测

User says: "I want to track how our brand is performing vs. three competitors in terms of online mentions and sentiment" Skill does:
  1. Designs monitoring queries for each brand (including name variations)
  2. Sets up share of voice tracking across matched channels
  3. Configures sentiment comparison dashboard
  4. Creates a monthly competitive report template Result: Competitive intelligence program ready to run
用户提问:"我想追踪我们品牌与三个竞争对手在在线提及量和情感方面的表现对比" 技能处理
  1. 为每个品牌设计监测查询(包括名称变体)
  2. 在匹配渠道上设置声量份额追踪
  3. 配置情感对比仪表盘
  4. 创建月度竞争报告模板 结果:可直接运行的竞争情报项目

Example 3: Build a crisis detection system

示例3:构建危机检测系统

User says: "We need early warning if something negative goes viral about our company" Skill does:
  1. Defines crisis keyword combinations (brand + negative terms)
  2. Configures real-time alerts with volume spike thresholds
  3. Designs escalation workflow (detect → assess → escalate → respond → monitor)
  4. Sets up a crisis dashboard with real-time metrics Result: Crisis detection system with automated alerts and escalation plan
用户提问:"我们需要提前预警关于公司的负面内容是否会传播开来" 技能处理
  1. 定义危机关键词组合(品牌+负面词汇)
  2. 配置带有提及量激增阈值的实时警报
  3. 设计升级流程(检测→评估→升级→响应→监测)
  4. 设置包含实时指标的危机仪表盘 结果:具备自动警报与升级计划的危机检测系统

Troubleshooting

故障排除

Monitoring returns too much noise

监测结果噪音过多

Symptom: Thousands of irrelevant mentions drowning out real brand conversations Cause: Queries are too broad, missing NOT exclusions, or source filters are too wide Solution: Review the top 50 mentions. Identify recurring false positive patterns (common words, unrelated companies with similar names, spam domains). Add NOT exclusions for each pattern. Narrow source filters. Consider using NEAR/n proximity operators if your tool supports them.
症状:数千条无关提及淹没了真实的品牌对话 原因:查询范围过宽,缺少NOT排除条件,或来源过滤器设置过广 解决方案:查看前50条提及,识别重复出现的误报模式(常见词汇、名称相似的无关公司、垃圾域名)。为每种模式添加NOT排除条件。缩小来源过滤器范围。若工具支持,可考虑使用NEAR/n proximity运算符。

Missing important mentions

遗漏重要提及

Symptom: You find out about brand mentions from colleagues or customers, not from your monitoring tool Cause: Queries are too narrow, missing name variations, or platform coverage gaps Solution: Audit your keyword list — add misspellings, abbreviations, nicknames, hashtags, and executive names. Check which social platforms your tool actually monitors (some don't cover TikTok, Reddit, or forums). Consider adding a second tool for gap coverage.
症状:你从同事或客户那里得知品牌提及,而非通过监测工具 原因:查询范围过窄,缺少名称变体,或平台覆盖存在缺口 解决方案:审核关键词列表——添加拼写错误、缩写、昵称、话题标签及高管姓名。检查工具实际能监测哪些社交平台(部分工具不覆盖TikTok、Reddit或论坛)。考虑添加第二款工具以填补覆盖缺口。

Stakeholders don't find reports useful

利益相关者认为报告无用

Symptom: Executives or team members ignore your social listening reports Cause: Reports show data without actionable insights, or metrics don't connect to business outcomes Solution: Lead with insights and recommendations, not raw numbers. Connect metrics to business outcomes (e.g., "negative sentiment spiked 40% after the pricing change — here's what customers are saying"). Tailor report depth to audience — executives want 1-page summaries, marketing wants detailed analysis.
症状:高管或团队成员忽略你的社交聆听报告 原因:报告仅展示数据而无 actionable insights,或指标与业务成果无关 解决方案:以洞察与建议为核心,而非原始数据。将指标与业务成果关联(例如:"价格调整后负面情绪激增40%——以下是客户的反馈内容")。根据受众调整报告深度——高管需要1页摘要,营销团队需要详细分析。