Back to Details

sales-jiminny

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Jiminny Platform Help

Jiminny平台帮助

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 call recording and transcription
    • B) Configuring CRM integration (Salesforce, HubSpot, Pipedrive, etc.)
    • C) Conversation intelligence — call insights, competitive mentions, topic tracking
    • D) Revenue intelligence — pipeline visibility, deal risks, win/loss analysis
    • E) Sales coaching — call scoring, performance tracking, team coaching
    • F) Dialer integration (Aircall, Dialpad, RingCentral, Five9, etc.)
    • G) API integration — pulling activity data into other systems
    • H) Comparing Jiminny to alternatives (Gong, Avoma, Fireflies)
  2. What's your Jiminny seat type?
    • A) Recording Seat ($83/mo — full recording + transcription + insights)
    • B) Insights Seat ($42/mo — view/listen only, no recording)
    • C) Listener Seat (free — playback only)
    • D) Evaluating — haven't started yet
  3. What CRM do you use?
    • A) Salesforce
    • B) HubSpot
    • C) Zoho / Pipedrive / Close / Bullhorn / Copper / Microsoft Dynamics
    • D) None / other
Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
如果存在
references/learnings.md
，请先阅读该文档以获取累积的平台知识。
  1. 您需要哪方面的帮助？
    • A) 设置通话录制与转录
    • B) 配置CRM集成（Salesforce、HubSpot、Pipedrive等）
    • C) 对话智能——通话洞察、竞品提及、主题追踪
    • D) 营收智能——销售管道可见性、交易风险、赢单/丢单分析
    • E) 销售辅导——通话评分、绩效追踪、团队辅导
    • F) 拨号器集成（Aircall、Dialpad、RingCentral、Five9等）
    • G) API集成——将活动数据导入其他系统
    • H) 对比Jiminny与竞品（Gong、Avoma、Fireflies）
  2. 您的Jiminny席位类型是什么？
    • A) 录制席位（每月83美元——完整录制+转录+洞察功能）
    • B) 洞察席位（每月42美元——仅查看/收听，无录制权限）
    • C) 听众席位（免费——仅回放）
    • D) 评估中——尚未开始使用
  3. 您使用的CRM是什么？
    • A) Salesforce
    • B) HubSpot
    • C) Zoho / Pipedrive / Close / Bullhorn / Copper / Microsoft Dynamics
    • D) 无/其他
跳步规则：如果用户的提示已包含足够上下文，直接跳至步骤2。

Step 2 — Route or answer directly

步骤2 — 转接或直接解答

Problem domainRoute to
Building a coaching program or training cadence (tool-agnostic)
/sales-coaching {user's question}
Reviewing a specific call recording for coaching
/sales-call-review {user's question}
Comparing AI note-takers / conversation intelligence platforms
/sales-note-taker {user's question}
General CRM integration patterns (Zapier, webhooks, iPaaS)
/sales-integration {user's question}
Gong-specific questions
/sales-gong {user's question}
When routing to another skill, provide the exact command.
问题领域转接至
构建辅导项目或培训节奏（与工具无关）
/sales-coaching {用户问题}
为辅导目的查看特定通话录制内容
/sales-call-review {用户问题}
对比AI笔记工具/对话智能平台
/sales-note-taker {用户问题}
通用CRM集成模式（Zapier、webhooks、iPaaS）
/sales-integration {用户问题}
Gong相关问题
/sales-gong {用户问题}
转接至其他技能时，请提供准确的命令。

Step 3 — Jiminny platform reference

步骤3 — Jiminny平台参考资料

Read 
references/platform-guide.md
 for the full platform reference — modules, pricing, integrations, data model, API quick ref, 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.
Key decision points:
  • Recording vs Insights seats — only Recording seats capture calls; Insights seats are for managers/leaders who review but don't record
  • CRM sync depth varies by CRM — Salesforce and HubSpot have the deepest native integrations
  • Dialer compatibility — check that your dialer is supported before committing (not all dialers have native integration)
  • API is partial REST — good for pulling activity data out, but limited compared to Gong's API breadth
If you discover a gotcha, workaround, or tip not covered in 
references/learnings.md
, append it there.
此时无需依赖平台指南——专注于用户的具体场景。
关键决策点：
  • 录制席位vs洞察席位——仅录制席位可捕获通话；洞察席位供管理者/领导者查看但无法录制
  • CRM同步深度因平台而异——Salesforce和HubSpot拥有最完善的原生集成
  • 拨号器兼容性——在确认前请检查您的拨号器是否受支持（并非所有拨号器都有原生集成）
  • API为部分REST风格——适合提取活动数据，但相比Gong的API，功能广度有限
如果发现
references/learnings.md
中未涵盖的陷阱、解决方案或技巧，请将其添加至该文档。

Gotchas

常见陷阱

Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
  • Transcription accuracy degrades with accents and background noise. This is a known limitation across G2 reviews (57 mentions). Consider post-processing or use quiet environments for important calls.
  • Calls may take time to appear in Jiminny after completion. Tagging complexity and processing delays are the #1 complaint (71 G2 mentions). Don't assume a missing call was unrecorded — check after 20-30 minutes.
  • AI insights require specificity to be useful. Generic prompts to the AI produce generic output. Set up specific coaching frameworks and scoring criteria to get actionable results.
  • API download links expire after 24 hours. If you're building a pipeline that stores recordings, fetch and persist the media promptly after receiving the API response.
  • API key generation is admin/owner-only. Regular users can't generate API keys — this must go through Organization Settings.
  • No platform fee, but one-time setup fee exists. Unlike Gong's $5K-50K platform fee, Jiminny charges a one-time setup fee (amount varies by deal).
  • 12-month minimum contract. No monthly billing option — annual commitment required.
基于研究的最佳实践——请特别留意与计划限制功能和集成陷阱相关的内容，这些信息可能已过时。
  • **转录准确率会因口音和背景噪音下降。**这是G2评论中多次提及的已知局限性（57次提及）。对于重要通话，可考虑后期处理或选择安静环境。
  • **通话结束后可能需要一段时间才会在Jiminny中显示。**标签复杂度和处理延迟是最常见的投诉（G2评论中71次提及）。不要默认未显示的通话未被录制——请等待20-30分钟后再检查。
  • **AI洞察需要明确指令才能发挥作用。**向AI发送通用提示只会得到通用结果。请设置具体的辅导框架和评分标准以获取可落地的结果。
  • **API下载链接24小时后过期。**如果您正在构建存储录制内容的管道，请在收到API响应后立即获取并保存媒体文件。
  • **API密钥仅管理员/所有者可生成。**普通用户无法生成API密钥——必须通过组织设置操作。
  • **无平台使用费，但存在一次性设置费。**与Gong的5000-50000美元平台费不同，Jiminny收取一次性设置费（金额根据交易而定）。
  • **最低12个月合约。**无月度计费选项——需签订年度合约。

Related skills

相关技能

  • /sales-note-taker
    — Comparing conversation intelligence platforms (Fathom, Fireflies, Avoma, Gong, etc.) or wiring APIs for transcript pipelines
  • /sales-coaching
    — Building coaching programs that consume call data
  • /sales-call-review
    — Reviewing specific sales calls and extracting coaching insights
  • /sales-gong
    — Gong platform help (the main enterprise competitor)
  • /sales-outdoo
    — Outdoo platform help (mid-market alternative with AI roleplay)
  • /sales-forecast
    — Revenue forecasting and pipeline analytics
  • /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
    ——对比对话智能平台（Fathom、Fireflies、Avoma、Gong等）或为转录管道配置API
  • /sales-coaching
    ——构建使用通话数据的辅导项目
  • /sales-call-review
    ——查看特定销售通话并提取辅导洞察
  • /sales-gong
    ——Gong平台帮助（主要企业级竞品）
  • /sales-outdoo
    ——Outdoo平台帮助（具备AI角色扮演功能的中端市场替代方案）
  • /sales-forecast
    ——营收预测与销售管道分析
  • /sales-integration
    ——通用CRM/工具集成模式（Zapier、webhooks、iPaaS）
  • /sales-do
    ——不确定使用哪个技能？该路由工具可将任何销售目标匹配至合适的技能。安装命令：
    npx skills add sales-skills/sales --skill sales-do

Examples

示例

Example 1: CRM sync not working

示例1：CRM同步失败

User says: "Jiminny isn't syncing call notes to our Salesforce — what should I check?" Skill does:
  1. Reads platform guide for Salesforce integration details
  2. Walks through common sync issues — field mapping, permissions, sync frequency
  3. Recommends checking Jiminny's activity log for sync errors and verifying Salesforce connected app authorization Result: Step-by-step troubleshooting for CRM sync with specific Jiminny settings to check
用户提问："Jiminny无法将通话笔记同步到我们的Salesforce——我应该检查哪些内容？" 技能操作：
  1. 查阅平台指南中Salesforce集成的详细信息
  2. 逐步排查常见同步问题——字段映射、权限、同步频率
  3. 建议检查Jiminny的活动日志以查看同步错误，并验证Salesforce关联应用的授权状态 结果：针对CRM同步的分步故障排除指南，包含需检查的Jiminny特定设置

Example 2: Evaluating Jiminny vs Gong

示例2：评估Jiminny vs Gong

User says: "Should I go with Jiminny or Gong for a 30-person sales team?" Skill does:
  1. Compares pricing (Jiminny Recording $83/mo vs Gong ~$133/mo + platform fee)
  2. Compares features — Gong has deeper analytics/ecosystem, Jiminny is more accessible and coaching-focused
  3. Recommends Jiminny if budget matters and coaching is the priority; Gong if deep deal intelligence and ecosystem integration are critical Result: Clear comparison with a recommendation based on budget and priorities
用户提问："我们销售团队有30人，应该选择Jiminny还是Gong？" 技能操作：
  1. 对比定价（Jiminny录制席位每月83美元 vs Gong约每月133美元+平台费）
  2. 对比功能——Gong具备更深入的分析/生态系统，Jiminny更易用且专注于辅导
  3. 建议如果预算有限且以辅导为优先，选择Jiminny；如果需要深度交易智能和生态系统集成，则选择Gong 结果：清晰的对比分析，并基于预算和优先级给出建议

Example 3: Pulling call data via API

示例3：通过API提取通话数据

User says: "I need to extract all call transcripts from Jiminny into our data warehouse." Skill does:
  1. Reads API reference for activity retrieval endpoints
  2. Recommends batching in 500-1000 activity pulls, respecting 30 req/min rate limit
  3. Warns about 24-hour download link expiry for recordings
  4. Suggests regular incremental pulls rather than annual dumps Result: API integration pattern with rate limit handling and data pipeline recommendations
用户提问："我需要将Jiminny中的所有通话转录内容提取到我们的数据仓库中。" 技能操作：
  1. 查阅API参考中活动检索端点的信息
  2. 建议按500-1000条活动批量提取，遵守每分钟30次请求的速率限制
  3. 提醒录制内容的下载链接24小时后过期
  4. 建议定期增量提取而非年度一次性导出 结果：包含速率限制处理和数据管道建议的API集成方案

Troubleshooting

故障排除

Calls not appearing in Jiminny

Jiminny中不显示通话

Symptom: A call was made but doesn't show up in the Jiminny dashboard Cause: Processing delays, tagging issues, or the dialer integration not triggering correctly Solution: Wait 20-30 minutes — calls can take time to process. If still missing, check: (1) the dialer integration is connected and active, (2) the call was made from a Recording Seat (Insights/Listener seats don't record), (3) no recording rules excluded this call type. Contact Jiminny support if the call is still missing after an hour.
症状：已进行通话但未在Jiminny仪表盘中显示 原因：处理延迟、标签问题或拨号器集成未触发 解决方案：等待20-30分钟——通话可能需要时间处理。如果仍未显示，请检查：(1) 拨号器集成已连接且处于活跃状态，(2) 通话是通过录制席位发起的（洞察/听众席位无法录制），(3) 没有录制规则排除该类型通话。如果一小时后仍未显示，请联系Jiminny支持团队。

Meetings connected to wrong colleague

会议关联到错误的同事

Symptom: A recorded meeting appears under the wrong team member's profile Cause: Calendar or dialer mapping mismatch — Jiminny maps calls to users based on calendar events or dialer user IDs Solution: Verify the user's email matches between Jiminny and the calendar/dialer. Check for shared calendar entries that might confuse the mapping. Jiminny support can manually reassign recordings if needed.
症状：录制的会议显示在错误团队成员的个人资料下 原因：日历或拨号器映射不匹配——Jiminny根据日历事件或拨号器用户ID将通话关联至用户 解决方案：验证用户的邮箱在Jiminny与日历/拨号器中是否一致。检查是否存在共享日历条目导致映射混淆。如有需要，Jiminny支持团队可手动重新分配录制内容。

Transcription accuracy poor for non-English calls

非英语通话转录准确率低

Symptom: Transcripts for calls in non-English languages or with heavy accents contain many errors Cause: ASR models vary in quality across languages and accents — Jiminny supports 60+ languages but accuracy varies Solution: For critical calls, review and manually correct transcripts. Ensure the correct language is set for the call. Background noise compounds accuracy issues — use quiet environments for important recordings.
症状：非英语语言或带有浓重口音的通话转录内容存在大量错误 原因：ASR模型在不同语言和口音下的质量存在差异——Jiminny支持60多种语言，但准确率各不相同 解决方案：对于关键通话，审核并手动修正转录内容。确保为通话设置了正确的语言。背景噪音会加剧准确率问题——重要录制请选择安静环境。