Back to Details

sales-revenue-io

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Revenue.io Platform Help

Revenue.io平台帮助

Step 1 — Gather context

步骤1 — 收集上下文信息

If 
references/learnings.md
exists, read it first for accumulated platform knowledge.
  1. What's your role?
    • A) SDR/BDR — dialing and prospecting
    • B) AE — deals, forecasting, call coaching
    • C) Sales manager — team coaching, performance dashboards
    • D) RevOps — configuration, data, integrations
    • E) Evaluating Revenue.io vs alternatives
  2. Which Revenue.io module?
    • A) RingDNA Dialer — click-to-dial, local presence, voicemail drop
    • B) Guided Selling — cadences, sequences, task prioritization
    • C) Moments — real-time in-call coaching and notifications
    • D) Conversation Intelligence — call recording, transcription, scoring
    • E) Revenue Intelligence — dashboards, forecasting, deal scoring
    • F) Ask Revenue — AI-powered queries
    • G) General setup / evaluation
Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
若
references/learnings.md
文件存在，请先阅读该文件以获取已积累的平台知识。
  1. 你的角色是什么？
    • A) SDR/BDR — 拨号与潜在客户开发
    • B) AE — 客户成交、预测、通话辅导
    • C) 销售经理 — 团队辅导、绩效仪表盘
    • D) RevOps — 配置、数据、集成
    • E) 评估Revenue.io与竞品
  2. 涉及Revenue.io的哪个模块？
    • A) RingDNA Dialer — 点击拨号、本地号码显示、语音邮件自动发送
    • B) Guided Selling — 销售节奏、序列、任务优先级
    • C) Moments — 实时通话内辅导与通知
    • D) Conversation Intelligence — 通话录制、转录、评分
    • E) Revenue Intelligence — 仪表盘、预测、成交机会评分
    • F) Ask Revenue — AI驱动的查询功能
    • G) 通用设置 / 产品评估
跳过规则：如果用户的提问已包含足够上下文信息，直接跳至步骤2。

Step 2 — Route or answer directly

步骤2 — 路由或直接解答

Problem domainRoute to
Comparing Revenue.io to other CI tools
/sales-note-taker [your comparison question]
Building outbound sequences (not Revenue.io-specific)
/sales-cadence [your cadence question]
Coaching program design
/sales-coaching [your coaching question]
Reviewing a specific call recording
/sales-call-review [paste transcript]
Revenue forecasting methodology
/sales-forecast [your forecast question]
Salesforce CRM configuration
/sales-salesforce [your CRM question]
When routing to another skill, provide the exact command.
问题领域路由至
对比Revenue.io与其他对话智能工具
/sales-note-taker [你的对比问题]
构建外呼序列（非Revenue.io专属）
/sales-cadence [你的销售节奏问题]
辅导项目设计
/sales-coaching [你的辅导问题]
查看特定通话记录
/sales-call-review [粘贴转录文本]
收入预测方法论
/sales-forecast [你的预测问题]
Salesforce CRM配置
/sales-salesforce [你的CRM问题]
当路由至其他技能时，请提供准确的命令。

Step 3 — Revenue.io platform reference

步骤3 — Revenue.io平台参考资料

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

Step 4 — Actionable guidance

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

You no longer need the platform guide — focus on the user's specific situation.
  • Dialer issues: Check Salesforce CTI adapter settings, Chrome extension version, call disposition requirements
  • Guided Selling: Verify cadence entry/exit criteria match Salesforce field values — standard and custom fields both work
  • Moments coaching: Test notification triggers on a sandbox call before rolling out to the team
  • Conversation Intelligence: Confirm recording consent settings match your jurisdiction's requirements (one-party vs two-party)
  • Revenue Intelligence: Start with out-of-box dashboards before customizing — they cover 80% of use cases
If you discover a gotcha, workaround, or tip not covered in 
references/learnings.md
, append it there.
此时无需再查阅平台指南——聚焦用户的具体场景。
  • 拨号器问题：检查Salesforce CTI适配器设置、Chrome扩展版本、通话状态必填要求
  • Guided Selling：验证销售节奏的进入/退出条件是否匹配Salesforce字段值——标准字段和自定义字段均适用
  • Moments辅导：在向团队推广前，先在沙盒环境测试通知触发机制
  • 对话智能：确认录制 consent 设置符合所在地区法规要求（单方同意 vs 双方同意）
  • Revenue Intelligence：先使用开箱即用的仪表盘，再进行自定义——这些仪表盘可覆盖80%的使用场景
若发现
references/learnings.md
未涵盖的陷阱、解决方案或技巧，请将其追加至该文件中。

Gotchas

常见陷阱

Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
  • Salesforce-only — Revenue.io does not work with HubSpot, Pipedrive, or any non-Salesforce CRM. If you're not on Salesforce, this is not the right tool.
  • Mandatory call dispositioning — reps cannot receive new calls until they disposition the current one. This is by design but slows high-volume dialers. Configure dispositions to be as simple as possible (3-5 options max).
  • Duplicate lead creation — clicking phone numbers in the UI can create duplicate Salesforce leads. Use the dialer's click-to-dial button, not raw phone number links.
  • No predictive contact search — unlike Salesloft/Outreach, the search doesn't auto-complete as you type. Type most of the contact name before searching.
  • Guided Selling vs Salesforce tasks — these are separate task systems. Reps must manage both unless you configure Guided Selling to be the single task source and suppress native Salesforce task creation.
  • Pricing opacity — no published pricing. Expect ~$2,400/mo starting, ~$59K/yr median contract (Vendr data). Budget for 15+ seats minimum.
  • No public API — no documented REST API. All integration goes through native Salesforce objects and the Chrome extension. Custom integrations require working with Revenue.io support.
  • Conversation Intelligence on Orchestrate only — full CI suite (AI summaries, deal scoring, Ask Revenue) requires the highest tier.
基于研究的最佳实践建议——请重点关注这些内容，尤其是关于套餐限制功能和可能过时的集成陷阱。
  • 仅支持Salesforce — Revenue.io不兼容HubSpot、Pipedrive或任何非Salesforce的CRM。若你未使用Salesforce，该工具并不适合你。
  • 强制设置通话状态 — 销售代表在完成当前通话的状态设置前，无法接收新通话。这是设计使然，但会降低高容量拨号器的效率。请将通话状态选项配置得尽可能简单（最多3-5个选项）。
  • 重复创建线索 — 点击UI中的电话号码可能会在Salesforce中创建重复线索。请使用拨号器的点击拨号按钮，而非原始电话号码链接。
  • 无预测性联系人搜索 — 与Salesloft/Outreach不同，搜索功能不会在你输入时自动补全。请输入大部分联系人姓名后再进行搜索。
  • Guided Selling与Salesforce任务的冲突 — 这是两个独立的任务系统。除非你将Guided Selling配置为唯一任务来源并禁用原生Salesforce任务创建，否则销售代表必须同时管理两个系统的任务。
  • 定价不透明 — 无公开定价。根据Vendr数据，起价约为每月2400美元，中位合同约为每年5.9万美元。最低需购买15个席位。
  • 无公开API — 无文档化的REST API。所有集成均通过原生Salesforce对象和Chrome扩展完成。自定义集成需联系Revenue.io支持团队。
  • 对话智能仅在Orchestrate套餐提供 — 完整的对话智能套件（AI摘要、成交机会评分、Ask Revenue）仅最高层级套餐可用。

Related skills

相关技能

  • /sales-note-taker
    — Comparing conversation intelligence platforms or wiring transcripts into your stack
  • /sales-cadence
    — Building outbound sequences across any platform
  • /sales-coaching
    — Designing coaching programs and manager frameworks
  • /sales-call-review
    — Reviewing a specific sales call for coaching insights
  • /sales-forecast
    — Building revenue forecasts with pipeline coverage analysis
  • /sales-salesforce
    — Salesforce CRM configuration and admin
  • /sales-salesloft
    — Salesloft platform help (common alternative)
  • /sales-gong
    — Gong platform help (common alternative)
  • /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 -a claude-code -y
  • /sales-note-taker
    — 对比对话智能平台或将转录文本接入你的技术栈
  • /sales-cadence
    — 在任意平台构建外呼序列
  • /sales-coaching
    — 设计辅导项目和经理框架
  • /sales-call-review
    — 查看特定销售通话以获取辅导见解
  • /sales-forecast
    — 结合销售管道覆盖分析构建收入预测
  • /sales-salesforce
    — Salesforce CRM配置与管理
  • /sales-salesloft
    — Salesloft平台帮助（常见竞品）
  • /sales-gong
    — Gong平台帮助（常见竞品）
  • /sales-do
    — 不确定使用哪个技能？该路由工具可将任意销售目标匹配到合适的技能。安装命令：
    npx skills add sales-skills/sales --skill sales-do -a claude-code -y

Examples

示例

Example 1: Dialer not logging calls

示例1：拨号器未记录通话

User says: "My reps' calls aren't showing up in Salesforce — they dial from Revenue.io but the activity log is empty." Skill does:
  1. Checks CTI adapter configuration and Chrome extension status
  2. Verifies call disposition requirements (calls without dispositions may not sync)
  3. Reviews Salesforce activity object permissions and field-level security
  4. Tests with a single rep to isolate whether it's a user-level or org-level issue Result: Troubleshooting checklist that identifies the sync failure point
用户提问："我的销售代表从Revenue.io拨号，但通话未显示在Salesforce中——活动日志是空的。" 技能执行操作：
  1. 检查CTI适配器配置和Chrome扩展状态
  2. 验证通话状态必填要求（未设置状态的通话可能不会同步）
  3. 查看Salesforce活动对象权限和字段级安全性
  4. 针对单个销售代表进行测试，以确定问题是用户级别还是组织级别 结果：提供可识别同步故障点的排查清单

Example 2: Choosing the right tier

示例2：选择合适的套餐层级

User says: "We have 25 AEs on Salesforce. We want a dialer and basic coaching. Do we need Orchestrate?" Skill does:
  1. Maps their needs to Revenue.io tiers — dialer + coaching = Engage tier
  2. Explains what Orchestrate adds (AI summaries, deal scoring, Ask Revenue) and whether it's worth the uplift
  3. Recommends starting with Engage and upgrading if AI features become a priority Result: Clear tier recommendation with upgrade path
用户提问："我们有25名使用Salesforce的AE。我们需要拨号器和基础辅导功能。是否需要Orchestrate套餐？" 技能执行操作：
  1. 将他们的需求映射到Revenue.io套餐层级——拨号器+辅导=Engage套餐
  2. 解释Orchestrate套餐新增的功能（AI摘要、成交机会评分、Ask Revenue）以及是否值得升级
  3. 建议从Engage套餐开始，若AI功能成为优先级再进行升级 结果：清晰的套餐推荐及升级路径

Example 3: Revenue.io vs Gong

示例3：Revenue.io vs Gong

User says: "We're evaluating Revenue.io and Gong for our Salesforce-native team. What's the real difference?" Skill does:
  1. Frames the core difference: Revenue.io = real-time in-call coaching + engagement, Gong = post-call analysis + revenue intelligence
  2. Highlights Revenue.io's Salesforce-native advantage (no shadow CRM) vs Gong's deeper analytics
  3. Notes Revenue.io includes a dialer and cadences, while Gong requires pairing with a separate engagement tool Result: Decision framework based on whether the team values real-time coaching or post-call analytics more
用户提问："我们正在为使用Salesforce的团队评估Revenue.io和Gong。两者的核心区别是什么？" 技能执行操作：
  1. 明确核心差异：Revenue.io=实时通话内辅导+客户互动，Gong=通话后分析+收入智能
  2. 强调Revenue.io的Salesforce原生优势（无影子CRM）对比Gong更深入的分析能力
  3. 指出Revenue.io包含拨号器和销售节奏功能，而Gong需要搭配单独的客户互动工具使用 结果：基于团队更看重实时辅导还是通话后分析的决策框架

Troubleshooting

故障排查

Calls creating duplicate leads in Salesforce

通话在Salesforce中创建重复线索

Cause: Clicking phone number links in the UI triggers lead creation instead of matching existing records Solution: Train reps to use the RingDNA dialer's click-to-dial button exclusively. Check Salesforce duplicate matching rules — Revenue.io respects them but only if they're configured. Review the lead matching settings in Revenue.io admin.
原因：点击UI中的电话号码链接会触发线索创建，而非匹配现有记录 解决方案：培训销售代表仅使用RingDNA拨号器的点击拨号按钮。检查Salesforce重复匹配规则——Revenue.io会遵循这些规则，但前提是规则已配置。查看Revenue.io管理后台的线索匹配设置。

Guided Selling tasks competing with Salesforce tasks

Guided Selling任务与Salesforce任务冲突

Cause: Revenue.io creates its own task objects alongside native Salesforce tasks Solution: Decide on a single task source. Either suppress Salesforce task auto-creation for activities Revenue.io manages, or configure Guided Selling to write directly to Salesforce tasks. Don't run both systems — reps will ignore one.
原因：Revenue.io会创建独立的任务对象，与原生Salesforce任务并存 解决方案：确定单一任务来源。要么禁用Revenue.io所管理活动的Salesforce任务自动创建，要么配置Guided Selling直接写入Salesforce任务。请勿同时运行两个系统——销售代表会忽略其中一个。

Real-time coaching notifications not appearing

实时辅导通知未显示

Cause: Moments requires the Chrome extension active and proper keyword/trigger configuration Solution: Verify the RingDNA Chrome extension is installed, up to date, and not disabled. Check Moments configuration — triggers must match actual conversation patterns (avoid overly specific phrases). Test on a sandbox call with a colleague before rolling out.
原因：Moments功能需要Chrome扩展处于激活状态，且关键词/触发配置正确 解决方案：验证RingDNA Chrome扩展已安装、更新至最新版本且未被禁用。检查Moments配置——触发条件必须匹配实际对话模式（避免过于具体的短语）。在向团队推广前，先与同事在沙盒环境中进行测试。