Back to Details

sales-people-ai

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

People.ai (Backstory) Platform Help

People.ai（Backstory）平台帮助指南

People.ai rebranded to Backstory on April 21, 2026. Same platform, same data infrastructure, new name. This skill uses "People.ai" throughout since that's what most users search for.
People.ai于2026年4月21日更名为Backstory。平台本身及数据架构保持不变，仅更换名称。本技能全程使用“People.ai”称谓，因为这是大多数用户搜索时使用的名称。

Step 1 — Gather context

步骤1 — 收集上下文信息

If 
references/learnings.md
exists, read it first for accumulated platform knowledge.
  1. Which People.ai capability are you asking about?
    • A) Activity Capture (auto-logging emails, calls, meetings → CRM)
    • B) Deal Intelligence (risk signals, stakeholder mapping, single-threading detection)
    • C) Pipeline & Forecasting (pipeline health, revenue predictions, coverage analysis)
    • D) MCP Integration (connecting AI agents to People.ai data)
    • E) CRM Sync & Data Quality (Salesforce/Dynamics/Oracle sync issues)
    • F) Pricing, plan selection, or comparison with another tool
    • G) Something else — describe it
  2. Which CRM are you on?
    • A) Salesforce
    • B) Microsoft Dynamics
    • C) Oracle
    • D) Multiple CRMs
  3. How big is your sales team?
    • A) Under 20 reps
    • B) 20-100 reps
    • C) 100-500 reps
    • D) 500+ reps
Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
若
references/learnings.md
文件存在，请先阅读该文件获取已积累的平台相关知识。
  1. 您咨询的是People.ai的哪项功能？
    • A) 活动捕获（自动记录邮件、通话、会议 → 同步至CRM）
    • B) 交易智能（风险预警、利益相关者映射、单线对接检测）
    • C) 销售管道与预测（销售管道健康度、收入预测、覆盖分析）
    • D) MCP集成（将AI Agent与People.ai数据连接）
    • E) CRM同步与数据质量（Salesforce/Dynamics/Oracle同步问题）
    • F) 定价、方案选择或与其他工具的对比
    • G) 其他内容——请描述
  2. 您使用的是哪款CRM？
    • A) Salesforce
    • B) Microsoft Dynamics
    • C) Oracle
    • D) 多款CRM
  3. 您的销售团队规模如何？
    • A) 少于20名销售代表
    • B) 20-100名销售代表
    • C) 100-500名销售代表
    • D) 500名以上销售代表
跳过规则：若用户的提问已包含足够上下文信息，可直接进入步骤2。

Step 2 — Route or answer directly

步骤2 — 转介或直接解答

If the question is about...Route to...
Conversation intelligence / call recording / coaching
/sales-gong [question]
or 
/sales-note-taker [question]
Revenue forecasting strategy across tools
/sales-forecast [question]
Deal health assessment methodology
/sales-deal-inspect [question]
CRM data quality strategy (not People.ai-specific)
/sales-data-hygiene [question]
Building outbound sequences
/sales-cadence [question]
When routing, provide the exact command.
若问题涉及...转介至...
对话智能/通话录制/销售辅导
/sales-gong [问题]
或 
/sales-note-taker [问题]
跨工具的收入预测策略
/sales-forecast [问题]
交易健康度评估方法
/sales-deal-inspect [问题]
CRM数据质量策略（非People.ai专属）
/sales-data-hygiene [问题]
构建外呼序列
/sales-cadence [问题]
转介时，请提供准确的命令。

Step 3 — People.ai platform reference

步骤3 — People.ai平台参考资料

Read 
references/platform-guide.md
 for the full platform reference — modules, integrations, MCP setup, pricing, known issues.
Answer the user's question using only the relevant section. Don't dump the full reference.
**阅读
references/platform-guide.md
**获取完整平台参考内容——包括模块、集成、MCP设置、定价、已知问题等。
仅使用相关章节内容解答用户问题，不要直接输出完整参考资料。

Step 4 — Actionable guidance

步骤4 — 可落地指导建议

Focus on the user's specific situation:
  • Activity Capture setup: Connect email (Gmail/Outlook) and calendar first — immediate value from auto-logging. Call integrations (Zoom/Teams) come second. Historical data analysis starts on day one (2 years back).
  • Deal Intelligence adoption: Start with pipeline health dashboards for managers, then roll out risk alerts. Single-threading detection is the highest-signal feature for deal risk.
  • Forecast accuracy: People.ai improves forecasts by replacing rep-entered data with activity-backed data. It doesn't generate forecast numbers — pair with CRM native forecasting or Clari for roll-ups.
  • MCP integration: Connects to Claude, ChatGPT, Copilot. Useful for natural language queries against your revenue data. Enterprise tier required.
  • vs Gong: People.ai captures activity data (emails, meetings, calendar); Gong captures conversation data (call recordings, transcripts). They're complementary, not competing. Many enterprises run both.
  • vs Clari: Clari focuses on forecast roll-ups and submission workflows; People.ai focuses on the data layer (activity capture + deal intelligence). People.ai feeds Clari — they're often stacked.
If you discover a gotcha, workaround, or tip not covered in 
references/learnings.md
, append it there.
聚焦用户的具体场景：
  • 活动捕获设置：先连接邮箱（Gmail/Outlook）和日历——可立即实现自动记录的价值。其次再连接通话集成（Zoom/Teams）。从启用当日起即可分析2年内的历史数据。
  • 交易智能落地：先为管理者推出销售管道健康度仪表盘，再逐步推广风险预警功能。单线对接检测是识别交易风险的最高信号功能。
  • 预测准确性提升：People.ai通过以活动数据替代销售代表手动录入的数据来提升预测准确性。它不会生成预测数值——需搭配CRM原生预测功能或Clari进行汇总。
  • MCP集成：可连接Claude、ChatGPT、Copilot。适用于对收入数据进行自然语言查询。需使用企业版套餐。
  • 与Gong对比：People.ai捕获活动数据（邮件、会议、日历）；Gong捕获对话数据（通话录制、转录文本）。二者互补而非竞争。许多企业同时使用这两款工具。
  • 与Clari对比：Clari专注于预测汇总和提交流程；People.ai专注于数据层（活动捕获+交易智能）。People.ai可为Clari提供数据支持——二者常搭配使用。
若发现
references/learnings.md
未涵盖的陷阱、解决方案或技巧，请补充至该文件中。

Gotchas

注意事项

  • No call recording or transcription — People.ai captures activity metadata (who emailed whom, which meetings happened, call duration) but does NOT record or transcribe calls. For call recording, use Gong, Fathom, or another CI tool.
  • Enterprise pricing only — no public pricing, no free tier, no self-serve signup. Custom quotes based on team size and modules. Budget $50-100+/user/month based on market reports.
  • Salesforce sync delays — activity data can take 1-2 days to fully process and appear in CRM. Don't expect real-time dashboards for call data.
  • Adoption requires executive sponsorship — reps see People.ai as "management watching" if not positioned as a productivity tool. Frame as "no more manual CRM logging" not "we're tracking your activity."
  • Multi-CRM complexity — supporting Salesforce + Dynamics across regions is a strength but adds implementation complexity. Plan for 2-4 week deployment per CRM instance.
  • Data quality depends on email/calendar hygiene — People.ai can only associate activities with CRM records if contacts exist. Garbage contacts = garbage activity mapping.
  • Backstory rebrand (April 2026) — all people.ai URLs redirect to backstory.ai. App login remains app.people.ai. Documentation and community content still references "People.ai."
  • 无通话录制与转录功能——People.ai仅捕获活动元数据（邮件收发对象、会议参与情况、通话时长），但不提供通话录制或转录服务。如需通话录制，请使用Gong、Fathom或其他对话智能工具。
  • 仅提供企业级定价——无公开定价、免费套餐或自助注册选项。根据团队规模和所选模块提供定制报价。据市场报告，预算约为每用户每月50-100美元以上。
  • Salesforce同步延迟——活动数据可能需要1-2天才能完全处理并显示在CRM中。请勿期望通话数据的实时仪表盘。
  • 落地需要高管支持——若未将People.ai定位为生产力工具，销售代表会将其视为“管理层监控工具”。应强调“无需手动录入CRM数据”而非“我们正在跟踪您的活动”。
  • 多CRM复杂度——跨区域支持Salesforce+Dynamics是其优势，但会增加实施复杂度。每个CRM实例的部署计划需预留2-4周时间。
  • 数据质量依赖邮箱/日历整洁度——只有当CRM中存在对应联系人时，People.ai才能将活动与CRM记录关联。无效联系人会导致活动映射失效。
  • Backstory品牌更名（2026年4月）——所有people.ai网址均重定向至backstory.ai。应用登录地址仍为app.people.ai。文档和社区内容仍使用“People.ai”称谓。

Related skills

相关技能

  • /sales-gong
    — Gong platform help (conversation intelligence — complementary to People.ai's activity capture)
  • /sales-note-taker
    — Comparing AI note-takers or wiring their APIs into CRM/warehouse
  • /sales-forecast
    — Revenue forecasting strategy, pipeline coverage, commit validation
  • /sales-deal-inspect
    — Deal health assessment, stakeholder mapping, MEDDPICC extraction
  • /sales-data-hygiene
    — CRM data quality, deduplication, enrichment strategy
  • /sales-coaching
    — Building a sales coaching program, onboarding reps
  • /sales-scratchpad
    — Scratchpad platform help (Salesforce-native AI workspace — lighter-weight alternative)
  • /sales-weflow
    — Weflow platform help (Salesforce-native revenue AI with activity capture, CI, forecasting)
  • /sales-clari-copilot
    — Clari Copilot platform help (conversation intelligence + Clari forecasting)
  • /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-gong
    ——Gong平台帮助指南（对话智能——与People.ai的活动捕获功能互补）
  • /sales-note-taker
    ——AI笔记工具对比或其API与CRM/数据仓库的对接
  • /sales-forecast
    ——收入预测策略、销售管道覆盖度、提交验证
  • /sales-deal-inspect
    ——交易健康度评估、利益相关者映射、MEDDPICC信息提取
  • /sales-data-hygiene
    ——CRM数据质量、去重、数据丰富策略
  • /sales-coaching
    ——销售辅导体系搭建、销售代表入职培训
  • /sales-scratchpad
    ——Scratchpad平台帮助指南（Salesforce原生AI工作区——轻量化替代方案）
  • /sales-weflow
    ——Weflow平台帮助指南（Salesforce原生收入AI工具，含活动捕获、对话智能、预测功能）
  • /sales-clari-copilot
    ——Clari Copilot平台帮助指南（对话智能+Clari预测功能）
  • /sales-do
    ——不确定使用哪项技能？该路由工具可将任何销售目标匹配至合适技能。安装命令：
    npx skills add sales-skills/sales --skill sales-do

Examples

示例

Example 1: CRM data is stale — reps don't log activities

示例1：CRM数据过时——销售代表未记录活动

User says: "Our Salesforce data is terrible. Reps don't log emails or meetings. We're evaluating People.ai to fix this." Skill does:
  1. Confirms People.ai's core value: automatic activity capture — every email, call, and meeting logged without rep action
  2. Explains the deployment path: connect Gmail/Outlook → connect calendar → connect Zoom/Teams → 2 weeks to full visibility
  3. Notes that People.ai captures 2 years of historical data on day one
  4. Warns about contact matching: People.ai maps activities to CRM records, so contact data must be reasonably clean first Result: Implementation plan with realistic timeline and prerequisites
用户提问：“我们的Salesforce数据很糟糕，销售代表不记录邮件或会议。我们正在评估People.ai来解决这个问题。” 技能处理：
  1. 确认People.ai的核心价值：自动活动捕获——无需销售代表操作，即可记录所有邮件、通话和会议
  2. 说明部署路径：连接Gmail/Outlook → 连接日历 → 连接Zoom/Teams → 2周内实现全面可见性
  3. 指出People.ai从启用当日起即可捕获2年内的历史数据
  4. 提醒联系人匹配问题：People.ai将活动与CRM记录关联，因此联系人数据需保持基本整洁 结果：提供包含合理时间线和前置条件的实施计划

Example 2: People.ai vs Gong for a 50-person sales team

示例2：50人销售团队选择People.ai还是Gong

User says: "We're choosing between People.ai and Gong. 50 reps on Salesforce." Skill does:
  1. Clarifies they solve different problems: People.ai = activity data (emails, meetings, calendar); Gong = conversation data (call recordings, transcripts, coaching)
  2. Notes many enterprises run both — People.ai feeds the data layer, Gong provides call-level insights
  3. If budget allows one: Gong if coaching and call review are the priority; People.ai if CRM data quality and pipeline visibility are the priority
  4. Flags pricing: both are enterprise-only with custom quotes Result: Clear decision framework based on primary pain point
用户提问：“我们正在People.ai和Gong之间做选择，团队有50名销售代表，使用Salesforce。” 技能处理：
  1. 明确二者解决不同问题：People.ai = 活动数据（邮件、会议、日历）；Gong = 对话数据（通话录制、转录文本、销售辅导）
  2. 指出许多企业同时使用这两款工具——People.ai提供数据层支持，Gong提供通话层面的洞察
  3. 若预算仅允许选其一：若优先考虑销售辅导和通话复盘，选Gong；若优先考虑CRM数据质量和销售管道可见性，选People.ai
  4. 提示定价：二者均为企业级工具，需定制报价 结果：基于核心痛点提供清晰的决策框架

Example 3: Connecting People.ai to Claude via MCP

示例3：通过MCP将People.ai与Claude连接

User says: "We have People.ai and want to query our revenue data through Claude." Skill does:
  1. Confirms People.ai announced MCP integration in February 2026
  2. Explains what it enables: natural language queries against structured CRM + unstructured conversation data
  3. Notes enterprise tier is required for MCP access
  4. Suggests example queries: "Which deals are single-threaded?" "Which accounts had declining engagement this quarter?" Result: MCP setup guidance with practical query examples
用户提问：“我们使用People.ai，希望通过Claude查询收入数据。” 技能处理：
  1. 确认People.ai于2026年2月推出MCP集成功能
  2. 说明该功能的作用：针对结构化CRM数据+非结构化对话数据进行自然语言查询
  3. 指出需使用企业版套餐才能访问MCP功能
  4. 提供示例查询：“哪些交易是单线对接的？”“哪些客户本季度的互动量下降了？” 结果：提供MCP设置指导及实用查询示例

Troubleshooting

故障排查

Activity data not appearing in Salesforce

活动数据未在Salesforce中显示

Symptom: Emails and meetings are happening but not showing in CRM Solution: Check email/calendar connections in People.ai admin. Verify the contact exists in Salesforce — People.ai can only associate activities with known CRM records. Check sync status in the People.ai dashboard. Activity processing can take up to 24-48 hours for call data. If specific emails are missing, check if those email domains are excluded in sync settings.
症状：邮件和会议已发生，但未在CRM中显示 解决方案：在People.ai管理后台检查邮箱/日历连接状态。确认Salesforce中存在对应联系人——People.ai仅能将活动与已知CRM记录关联。在People.ai仪表盘中检查同步状态。通话数据的处理可能需要24-48小时。若特定邮件未同步，检查这些邮件的域名是否在同步设置中被排除。

Low team adoption

团队使用率低

Symptom: People.ai is deployed but reps ignore it / don't see value Solution: Position as a productivity tool ("no more manual CRM logging"), not a tracking tool. Show reps their own data — "here are 15 hours you saved this month on data entry." Enable pipeline views that are faster than native Salesforce. Get manager buy-in to use People.ai data in 1:1s and forecast calls — once managers use it, reps follow.
症状：已部署People.ai，但销售代表忽视它/看不到其价值 解决方案：将其定位为生产力工具（“无需手动录入CRM数据”），而非监控工具。向销售展示他们自己的数据——“本月您在数据录入上节省了15小时”。启用比原生Salesforce更快的销售管道视图。获得管理者支持，在一对一沟通和预测会议中使用People.ai数据——一旦管理者使用，销售代表会跟进。

Inaccurate contact/account matching

联系人/客户匹配不准确

Symptom: Activities are logged but associated with the wrong contacts or accounts Solution: People.ai matches activities to CRM records based on email addresses and calendar invitees. If contacts have outdated email addresses in CRM, activities won't match correctly. Run a data hygiene pass on contact emails first (use 
/sales-data-hygiene
). Check People.ai's matching rules — some require exact email match, others use domain-level inference.
症状：活动已记录，但关联到错误的联系人或客户 解决方案：People.ai基于邮箱地址和日历参会者将活动与CRM记录关联。若CRM中联系人的邮箱地址过时，活动将无法正确匹配。先对联系人邮箱进行数据清理（使用/sales-data-hygiene）。检查People.ai的匹配规则——部分规则要求邮箱完全匹配，部分规则使用域名推断。