Back to Details

sales-clari-copilot

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Clari Copilot Platform Help

Clari Copilot平台帮助

Step 1 — Gather context

步骤1 — 收集上下文

If 
references/learnings.md
exists, read it first for accumulated platform knowledge.
  1. What do you need help with?
    • A) Setting up Clari Copilot for the first time
    • B) Configuring battlecards, playbooks, or coaching scorecards
    • C) Troubleshooting meeting bot, CRM sync, or transcription issues
    • D) Clari API integration (forecast export, data ingestion, audit events)
    • E) Evaluating Clari Copilot vs alternatives (Gong, Avoma, tl;dv, etc.)
    • F) Understanding pricing tiers and what's gated to which plan
  2. Which Clari Copilot plan are you on?
    • A) Growth (~$60/user/mo)
    • B) Accelerator (~$90/user/mo)
    • C) Enterprise (~$110/user/mo)
    • D) Bundled with Clari Core / not sure
    • E) Evaluating — haven't purchased yet
Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
若
references/learnings.md
文件存在，请先阅读该文件以获取累积的平台知识。
  1. 您需要哪方面的帮助？
    • A) 首次搭建Clari Copilot
    • B) 配置作战卡片、剧本或指导评分卡
    • C) 排查会议机器人、CRM同步或转录问题
    • D) Clari API集成（预测导出、数据导入、审计事件）
    • E) 评估Clari Copilot与竞品（Gong、Avoma、tl;dv等）
    • F) 了解定价层级及各计划的功能权限
  2. 您使用的是哪个Clari Copilot计划？
    • A) Growth版（约60美元/用户/月）
    • B) Accelerator版（约90美元/用户/月）
    • C) Enterprise版（约110美元/用户/月）
    • D) 与Clari Core捆绑/不确定
    • E) 正在评估——尚未购买
跳转规则：若用户的提示已包含足够上下文，直接跳至步骤2。

Step 2 — Route or answer directly

步骤2 — 转介或直接解答

Problem domainRoute to
Picking a note-taker across vendors (Clari Copilot vs Gong vs Fathom, etc.)
/sales-note-taker {user's question}
Building a coaching program or training cadence
/sales-coaching {user's question}
Reviewing a specific call for coaching or scoring
/sales-call-review {user's question}
Revenue forecasting strategy (not Clari API)
/sales-forecast {user's question}
General CRM-to-tool integration (Zapier, webhooks, iPaaS)
/sales-integration {user's question}
Otherwise, answer directly below.
问题领域转至
跨供应商选择笔记工具（Clari Copilot vs Gong vs Fathom等）
/sales-note-taker {用户问题}
搭建指导体系或培训节奏
/sales-coaching {用户问题}
为指导或评分复盘特定通话
/sales-call-review {用户问题}
营收预测策略（非Clari API相关）
/sales-forecast {用户问题}
通用CRM与工具集成（Zapier、webhooks、iPaaS）
/sales-integration {用户问题}
若非上述情况，请直接在下方解答。

Step 3 — Clari Copilot platform reference

步骤3 — Clari Copilot平台参考资料

Read 
references/platform-guide.md
 for the full platform reference — modules, pricing, integrations, data model, API, workflows.
Answer the user's question using only the relevant section. Don't dump the full reference.
**阅读
references/platform-guide.md
**获取完整平台参考——模块、定价、集成、数据模型、API、工作流。
仅使用相关章节解答用户问题，请勿直接输出完整参考内容。

Step 4 — Actionable guidance

步骤4 — 可落地指导

You no longer need the platform guide — focus on the user's specific situation.
Setup decisions to walk through:
  • Battlecard frequency vs rep distraction — start with 2-3 critical battlecards, not every competitor
  • Coaching scorecards — pick 3-5 behaviors that correlate with win rates, avoid scoring everything
  • CRM sync — map only the fields reps actually use in their workflow, not every available field
  • Gametapes — curate 5-10 best calls per use case, don't let the library bloat
When to escalate to Clari support:
  • Meeting bot consistently fails to join (not just late) — likely a calendar/permissions issue on Clari's side
  • CRM field mapping returns errors — may need Clari admin to adjust field permissions
  • Enterprise API access not provisioned — requires account team intervention
If you discover a gotcha, workaround, or tip not covered in 
references/learnings.md
, append it there.
此时无需再查阅平台指南——聚焦用户的具体场景。
需逐步推进的搭建决策：
  • 作战卡片频率与销售代表干扰平衡——先启用2-3个关键作战卡片，而非覆盖所有竞品
  • 指导评分卡——选择3-5个与赢单率相关的行为，避免对所有行为评分
  • CRM同步——仅映射销售代表工作流中实际使用的字段，而非所有可用字段
  • 比赛录像——针对每个用例精选5-10个最佳通话，避免库内容冗余
需升级至Clari支持团队处理的场景：
  • 会议机器人持续无法加入（并非偶尔延迟）——大概率是Clari端的日历/权限问题
  • CRM字段映射返回错误——可能需要Clari管理员调整字段权限
  • 企业级API权限未开通——需要客户团队介入
若发现
references/learnings.md
未涵盖的陷阱、变通方案或技巧，请将其追加至该文件中。

Gotchas

常见陷阱

Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
  • Copilot API is Enterprise-only. Growth and Accelerator plans don't get API access. If you need programmatic access to call data, confirm Enterprise pricing first.
  • Battlecards can be distracting. Multiple users report cards popping up repeatedly mid-call. Start with a small set of high-value battlecards and expand gradually — don't enable every card at launch.
  • Bot joining is not instant. Clari's meeting bot can take a few minutes to join after a call starts, potentially missing the opening. Invite the bot manually before critical calls if auto-join is unreliable.
  • 15-language transcription limit. If your team sells globally, Clari Copilot supports fewer languages than competitors like tl;dv (30+) or Notta (58). Check your language coverage before committing.
  • CRM sync requires clean data. Incomplete or stale CRM records cause sync failures and inaccurate deal intelligence. Clean your CRM data before rolling out Copilot — don't expect Copilot to fix data quality.
  • Steep learning curve. Users describe the UI as "overwhelming" with complex navigation. Plan for 2-4 weeks of admin ramp time and schedule team training sessions.
  • Implementation costs add 20-30% to first year. Budget $15K-75K for professional services on top of per-seat pricing. Negotiate this as part of the initial contract.
  • Clari acquired Salesloft (late 2025). The product roadmap is merging. If evaluating Clari Copilot standalone, ask your account team about Salesloft bundling and how features will consolidate.
基于研究的最佳实践——请重点关注与计划权限限制及集成陷阱相关的内容，这些信息可能已过时。
  • Copilot API仅面向Enterprise版用户：Growth版和Accelerator版无API访问权限。若需以编程方式访问通话数据，请先确认Enterprise版定价。
  • 作战卡片可能造成干扰：多位用户反馈卡片在通话中反复弹出。先启用少量高价值作战卡片，再逐步扩展——不要在上线时启用所有卡片。
  • 机器人加入并非即时：Clari会议机器人可能在通话开始后几分钟才加入，可能错过开场环节。若自动加入不可靠，请在重要通话前手动邀请机器人。
  • 转录语言限制为15种：若您的团队面向全球销售，Clari Copilot支持的语言少于tl;dv（30+种）或Notta（58种）等竞品。在决定使用前请确认语言覆盖范围。
  • CRM同步需要干净的数据：不完整或过时的CRM记录会导致同步失败及交易智能数据不准确。在推广Copilot前请清理CRM数据——不要指望Copilot解决数据质量问题。
  • 学习曲线较陡：用户反馈UI“过于复杂”，导航难度大。请规划2-4周的管理员上手时间，并安排团队培训课程。
  • 实施成本占首年费用的20-30%：除按席位定价外，需预留1.5万-7.5万美元的专业服务预算。请在初始合同中协商此项费用。
  • Clari于2025年末收购Salesloft：产品路线图正在合并。若评估独立版Clari Copilot，请咨询客户团队关于Salesloft捆绑方案及功能整合的相关信息。

Related skills

相关技能

  • /sales-note-taker
    — Picking an AI note-taker across vendors (Fathom, Fireflies, Avoma, Gong, etc.) or wiring APIs for transcript pipelines
  • /sales-coaching
    — Building coaching programs, onboarding, role-play, certifications, measuring coaching impact
  • /sales-call-review
    — Review a specific call for coaching or scoring
  • /sales-forecast
    — Revenue forecasting, pipeline coverage, commit validation, gap analysis
  • /sales-gong
    — Gong platform help — direct competitor, often compared on pricing and features
  • /sales-integration
    — General CRM/tool integration patterns (Zapier, webhooks, iPaaS)
  • /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-note-taker
    ——跨供应商选择AI笔记工具（Fathom、Fireflies、Avoma、Gong等）或为转录流水线配置API
  • /sales-coaching
    ——搭建指导体系、入职培训、角色扮演、认证、衡量指导效果
  • /sales-call-review
    ——为指导或评分复盘特定通话
  • /sales-forecast
    ——营收预测、管线覆盖、承诺验证、差距分析
  • /sales-gong
    ——Gong平台帮助——直接竞品，常被用于定价和功能对比
  • /sales-integration
    ——通用CRM/工具集成模式（Zapier、webhooks、iPaaS）
  • /sales-do
    ——不确定使用哪个技能？该路由会将任何销售目标匹配至合适的技能。安装方式：
    npx skills add sales-skills/sales --skill sales-do

Examples

示例

Example 1: Battlecards overwhelming reps

示例1：作战卡片干扰销售代表

User says: "Our reps complain that Clari Copilot battlecards pop up constantly during calls and distract them from the conversation." Skill does:
  1. Reads platform guide for battlecard configuration
  2. Recommends reducing active battlecards to top 3-5 competitors the team actually encounters
  3. Suggests configuring trigger sensitivity to only fire on explicit competitor mentions, not adjacent keywords
  4. Advises reviewing battlecard engagement analytics after 2 weeks to see which ones reps actually use Result: Focused battlecard strategy that helps instead of distracts.
用户提问：“我们的销售代表抱怨Clari Copilot的作战卡片在通话中频繁弹出，干扰他们与客户的对话。” 技能处理流程：
  1. 查阅平台指南中作战卡片配置相关内容
  2. 建议将启用的作战卡片减少至团队实际遇到的前3-5个竞品
  3. 建议配置触发敏感度，仅在明确提及竞品时弹出，而非相关关键词
  4. 建议在2周后查看作战卡片参与度分析，了解销售代表实际使用的卡片 结果：聚焦的作战卡片策略能够提供帮助而非造成干扰。

Example 2: Evaluating Clari Copilot pricing

示例2：评估Clari Copilot定价

User says: "We're a 30-person sales team on HubSpot. Clari quoted us $90/user/month for Accelerator. Is that worth it vs Gong?" Skill does:
  1. Reads pricing section — Accelerator at $90/user = $32,400/yr for 30 users, plus $15-50K implementation
  2. Compares to Gong at ~$1,600/user/yr + $5-50K platform fee = $48K+ for 30 users
  3. Notes Clari Copilot is cheaper but Gong has deeper conversation analytics and larger integration ecosystem
  4. Flags that Accelerator doesn't include API access — Enterprise ($110/user) needed for that
  5. Recommends requesting a Gong quote for direct comparison, and evaluating whether Clari Core forecasting (bundled) justifies the premium over dedicated note-takers like Fathom Business ($25/seat) Result: Clear pricing comparison with the right questions to ask each vendor.
用户提问：“我们是拥有30人的销售团队，使用HubSpot。Clari给我们的Accelerator版报价是90美元/用户/月。对比Gong是否值得？” 技能处理流程：
  1. 查阅定价部分——Accelerator版90美元/用户，30名用户年费用为32400美元，另加1.5万-5万美元实施费
  2. 对比Gong的定价：约1600美元/用户/年 + 5千-5万美元平台费，30名用户总费用4.8万美元以上
  3. 指出Clari Copilot价格更低，但Gong拥有更深入的对话分析和更庞大的集成生态
  4. 强调Accelerator版不包含API访问权限——需升级至Enterprise版（110美元/用户）才能获得
  5. 建议获取Gong的直接报价进行对比，并评估Clari Core预测功能（捆绑销售）是否比Fathom Business（25美元/席位）等专用笔记工具更值得溢价 结果：清晰的定价对比及向各供应商提问的方向。

Example 3: Clari API integration for forecast data

示例3：Clari API集成用于预测数据导出

User says: "I need to export our Clari forecast submissions to Snowflake every night. How do I set this up?" Skill does:
  1. Reads API reference for forecast export endpoints
  2. Walks through: POST 
    /export/forecast/{forecastId}
    to initiate, GET 
    /export/jobs/{jobId}
    to poll status, GET 
    /export/jobs/{jobId}/results
    to download
  3. Notes auth via 
    apikey
    header, 100 req/sec rate limit
  4. Recommends a nightly cron job with error handling for FAILED/ABORTED states
  5. Flags that API access requires Enterprise plan Result: Working architecture for automated forecast export.
用户提问：“我需要每天将Clari预测提交数据导出至Snowflake。该如何设置？” 技能处理流程：
  1. 查阅API参考中预测导出端点相关内容
  2. 逐步指导：调用POST 
    /export/forecast/{forecastId}
    发起导出，调用GET 
    /export/jobs/{jobId}
    轮询状态，调用GET 
    /export/jobs/{jobId}/results
    下载结果
  3. 说明通过
    apikey
    头部进行身份验证，速率限制为100请求/秒
  4. 建议设置每日定时任务（cron job）并为FAILED/ABORTED状态添加错误处理
  5. 强调API访问权限仅面向Enterprise版用户 结果：可运行的自动化预测导出架构。

Troubleshooting

故障排查

Meeting bot not joining or joining late

会议机器人未加入或加入延迟

Symptom: Clari Copilot bot doesn't appear in calls, or joins minutes after the call starts Cause: Calendar permission issues, calendar sync delays, or bot capacity during peak hours Solution: Verify calendar integration permissions in Clari admin. For critical calls, manually invite the Copilot bot before the call starts. Check that the meeting organizer's calendar is connected (not just attendees). If persistent, contact Clari support — this is a known issue from user reviews.
症状：Clari Copilot机器人未出现在通话中，或在通话开始数分钟后才加入 原因：日历权限问题、日历同步延迟或高峰时段机器人容量不足 解决方案：在Clari管理员后台验证日历集成权限。对于重要通话，提前手动邀请Copilot机器人。确认会议组织者的日历已连接（而非仅参会者）。若问题持续，请联系Clari支持团队——这是用户反馈中已知的问题。

CRM fields not syncing after calls

通话后CRM字段未同步

Symptom: Call data captured by Copilot doesn't appear in Salesforce/HubSpot/Pipedrive Cause: Field mapping misconfiguration, CRM field permissions, or stale contact data Solution: In Clari admin, verify each mapped field exists in the CRM and has write permissions. Check that the contact/deal exists in the CRM before the call — Copilot can't create new CRM records, only update existing ones. Test with a single rep before rolling out to the team.
症状：Copilot捕获的通话数据未出现在Salesforce/HubSpot/Pipedrive中 原因：字段映射配置错误、CRM字段权限问题或联系人数据过时 解决方案：在Clari管理员后台，验证每个映射字段在CRM中存在且具备写入权限。确认通话前联系人/交易已存在于CRM中——Copilot无法创建新的CRM记录，仅能更新现有记录。在向全团队推广前先与单个销售代表进行测试。

Transcription accuracy issues with accents or industry jargon

口音或行业术语导致转录准确性问题

Symptom: Transcripts contain frequent errors, especially with technical terms or non-native English speakers Cause: Clari Copilot's ASR has 92-96% accuracy — lower than some competitors for accented speech Solution: No custom vocabulary feature exists currently. For critical terminology, train reps to speak technical terms clearly. Consider supplementing with a tool like Notta (58 languages, higher multilingual accuracy) if your team is globally distributed. Monitor accuracy over time — Clari's models improve with usage.
症状：转录内容频繁出错，尤其是技术术语或非英语母语者的发言 原因：Clari Copilot的自动语音识别（ASR）准确率为92-96%——针对带口音的语音，准确率低于部分竞品 解决方案：目前无自定义词汇功能。对于关键术语，培训销售代表清晰发音。若团队面向全球分布，可考虑搭配Notta（支持58种语言，多语言准确率更高）等工具。持续监控准确率——Clari的模型会随使用次数提升性能。