Back to Details

sales-jamie

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Jamie Platform Help

Jamie平台帮助

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) Initial setup — installing the app, connecting calendar, first recording
    • B) API integration — pulling transcripts/summaries programmatically
    • C) Webhook setup — automating workflows when meetings complete
    • D) CRM sync — connecting HubSpot, Salesforce, or Attio
    • E) Notes sync — Notion, Google Docs, or OneNote
    • F) Speaker recognition or custom terminology
    • G) Pricing / plan selection
    • H) Troubleshooting — recording not working, missing content, sync issues
  2. Which plan are you on?
    • A) Free (10 meetings/mo, 30 min limit)
    • B) Plus (20 meetings/mo, 2 hr limit)
    • C) Pro (unlimited meetings, 3 hr limit)
    • D) Team (Pro features + centralized billing)
    • E) Enterprise (SSO, admin controls, EU residency)
    • F) Not sure / evaluating
Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
如果存在
references/learnings.md
，请先阅读该文档获取已积累的平台相关知识。
  1. 您需要哪方面的帮助？
    • A) 初始设置——安装应用、连接日历、首次录制
    • B) API集成——以编程方式提取转录文本/摘要
    • C) Webhook设置——会议结束后自动触发工作流
    • D) CRM同步——连接HubSpot、Salesforce或Attio
    • E) 笔记同步——Notion、Google Docs或OneNote
    • F) 发言人识别或自定义术语设置
    • G) 定价/套餐选择
    • H) 故障排查——录制失效、内容丢失、同步问题
  2. 您使用的是哪个套餐？
    • A) 免费版（每月10次会议，单场时长限制30分钟）
    • B) Plus版（每月20次会议，单场时长限制2小时）
    • C) Pro版（无限次会议，单场时长限制3小时）
    • D) 团队版（包含Pro版功能+集中账单管理）
    • E) 企业版（SSO、管理员控制、数据存储于欧盟）
    • F) 不确定/正在评估
跳步规则：如果用户的提问已包含足够上下文信息，可直接跳至步骤2。

Step 2 — Route or answer directly

步骤2 — 转至对应模块或直接解答

Problem domainRoute to
Choosing between note-takers (Jamie vs Fireflies vs Fathom etc.)
/sales-note-taker {user's question}
Reviewing a specific sales call for coaching
/sales-call-review {user's question}
Building a coaching program
/sales-coaching {user's question}
General CRM/tool integration patterns (Zapier, iPaaS)
/sales-integration {user's question}
HubSpot platform config (beyond Jamie sync)
/sales-hubspot {user's question}
Salesforce platform config (beyond Jamie sync)
/sales-salesforce {user's question}
Otherwise, answer directly below.
问题领域转至
对比不同会议记录工具（Jamie vs Fireflies vs Fathom等）
/sales-note-taker {用户问题}
针对特定销售通话进行教练式复盘
/sales-call-review {用户问题}
搭建教练辅导体系
/sales-coaching {用户问题}
通用CRM/工具集成模式（Zapier、iPaaS）
/sales-integration {用户问题}
HubSpot平台配置（超出Jamie同步范围的内容）
/sales-hubspot {用户问题}
Salesforce平台配置（超出Jamie同步范围的内容）
/sales-salesforce {用户问题}
若非上述情况，请直接在下方解答。

Step 3 — Jamie platform reference

步骤3 — Jamie平台参考资料

Read 
references/platform-guide.md
 for the full platform reference — modules, pricing, API endpoints, webhook setup, integrations, data model.
Answer the user's question using only the relevant section. Don't dump the full reference.
**阅读
references/platform-guide.md
**获取完整平台参考信息——包括模块、定价、API端点、Webhook设置、集成方式、数据模型等。
仅使用相关章节内容解答用户问题，不要直接粘贴完整参考资料。

Step 4 — Actionable guidance

步骤4 — 可落地指导

You no longer need the platform guide — focus on the user's specific situation.
  • API vs webhooks: Use webhooks (
    meeting.completed
    ) for real-time pipelines; use REST API for batch queries and search. Combine both for production: webhook for push + nightly reconcile poll.
  • Personal vs workspace keys: Personal keys see only your meetings + shared ones. Workspace keys (admin-created) see all workspace meetings — use for team-wide dashboards or CRM sync.
  • Plan gating: API/webhooks require Pro+. CRM sync (HubSpot/Salesforce/Attio) requires Pro+. Free and Plus are personal-use only.
  • MCP: Community-built 
    vicampuzano-jamie-mcp
    connects Jamie to Claude/ChatGPT/Cursor — requires Pro+ and 
    JAMIE_API_KEY
    env var.
If you discover a gotcha, workaround, or tip not covered in 
references/learnings.md
, append it there.
您无需再查阅平台指南，请聚焦用户的具体场景。
  • API vs Webhooks：实时流水线使用Webhooks（
    meeting.completed
    事件）；批量查询和搜索使用REST API。生产环境建议结合两者：Webhooks用于推送事件+夜间轮询核对数据。
  • 个人密钥 vs 工作区密钥：个人密钥仅能查看您自己的会议及共享会议。工作区密钥（由管理员创建）可查看工作区内所有会议——适用于团队仪表盘或CRM同步场景。
  • 套餐权限限制：API/Webhooks功能需Pro版及以上。CRM同步（HubSpot/Salesforce/Attio）需Pro版及以上。免费版和Plus版仅支持个人使用。
  • MCP：社区开发的
    vicampuzano-jamie-mcp
    可将Jamie与Claude/ChatGPT/Cursor对接——需Pro版及以上，并配置
    JAMIE_API_KEY
    环境变量。
如果发现
references/learnings.md
未覆盖的注意事项、变通方案或技巧，请补充至该文档中。

Gotchas

注意事项

Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
  • Processing delays. Summaries can take 5-10 minutes even for short meetings. Users report summaries getting stuck in "processing" — if this happens, check for app updates or restart Jamie.
  • Lost/failed recordings. Multiple users report entire meetings lost, especially during app upgrades. Never update Jamie mid-meeting. For high-stakes calls, keep a backup recorder.
  • Speaker identification is inconsistent. Mislabeling, duplicating, and phantom speaker tags are common. In large meetings (7-8+ people), entire participants may be left out. Manually correct speakers in early meetings to train speaker memory.
  • No video recording. Audio only. If you need to review slide shares or demos, pair with a screen recorder or choose a video-capable note-taker.
  • No Android app. Desktop (Mac/Windows) and iOS only.
  • Free tier is very limited. 10 meetings/month with a 30-minute cap. Most competitors offer more generous free tiers (Fathom: unlimited free recordings).
  • No native Zapier integration. Automation goes through Make.com or custom webhooks.
  • CRM sync is Pro+ only. Free and Plus plans can't push notes to HubSpot/Salesforce/Attio.
  • Webhook endpoint URL can't be updated. Delete and recreate if the URL changes. Events are also immutable after creation.
  • Audio deleted after transcription. You can't re-listen to or re-process a meeting.
基于研究整理的最佳实践——请重点关注套餐权限限制相关内容及可能过时的集成注意事项。
  • 处理延迟：即使是短会议，摘要生成也可能需要5-10分钟。用户反馈摘要会卡在“处理中”状态——遇到此情况，请检查应用更新或重启Jamie。
  • 录制丢失/失败：多名用户反馈整个会议录制丢失，尤其是在应用升级期间。绝对不要在会议进行中更新Jamie。对于高重要性通话，请使用备用录制工具。
  • 发言人识别不一致：常见错误包括标签错误、重复标签、出现虚拟发言人标签。在7-8人以上的大型会议中，甚至可能遗漏部分参会者。在初期会议中手动修正发言人标签，可训练发言人记忆功能。
  • 无视频录制：仅支持音频录制。如果需要回顾幻灯片分享或演示内容，请搭配屏幕录制工具或选择支持视频的会议记录工具。
  • 无Android应用：仅支持桌面端（Mac/Windows）和iOS端。
  • 免费版限制严格：每月10次会议，单场时长上限30分钟。多数竞品提供更宽松的免费版政策（如Fathom：无限次免费录制）。
  • 无原生Zapier集成：需通过Make.com或自定义Webhooks实现自动化。
  • CRM同步仅Pro版及以上支持：免费版和Plus版无法将笔记推送至HubSpot/Salesforce/Attio。
  • Webhook端点URL无法更新：若URL变更，需删除后重新创建。事件创建后也无法修改。
  • 转录完成后音频将被删除：无法重新收听或重新处理会议内容。

Related skills

相关技能

  • /sales-note-taker
    — Compare note-takers, plan API integration architecture, normalize transcript formats across vendors
  • /sales-call-review
    — Review a specific call for coaching
  • /sales-coaching
    — Build coaching programs that consume call data
  • /sales-integration
    — General CRM/tool integration patterns (Zapier, Make, 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 -a claude-code -y
  • /sales-note-taker
    — 对比会议记录工具、规划API集成架构、统一不同供应商的转录文本格式
  • /sales-call-review
    — 针对特定通话进行教练式复盘
  • /sales-coaching
    — 搭建可利用通话数据的教练辅导体系
  • /sales-integration
    — 通用CRM/工具集成模式（Zapier、Make、Webhooks、iPaaS）
  • /sales-do
    — 不确定使用哪个技能？该路由可将任何销售目标匹配至合适的技能。安装方式：
    npx skills add sales-skills/sales --skill sales-do -a claude-code -y

Examples

示例

Example 1: Setting up Jamie webhooks with Make.com

示例1：将Jamie Webhooks与Make.com集成

User says: "I want Jamie to automatically create a Notion page for every meeting." Skill does:
  1. Confirms user is on Plus+ plan (webhooks require it)
  2. Walks through: Jamie Settings → Integrations → Webhooks → Create Webhook → paste Make.com webhook URL
  3. Notes to select 
    meeting.completed
    event and API Key auth with 
    x-make-apikey
    header
  4. Shows Make.com scenario: webhook trigger → parse JSON → create Notion page with summary + action items Result: Automated Notion pages for every completed meeting.
用户提问：“我希望Jamie为每场会议自动创建一个Notion页面。” 技能处理流程：
  1. 确认用户使用的是Plus版及以上套餐（Webhooks功能需此权限）
  2. 分步指导：Jamie设置 → 集成 → Webhooks → 创建Webhook → 粘贴Make.com的Webhook URL
  3. 提醒需选择
    meeting.completed
    事件，并使用
    x-make-apikey
    头进行API密钥认证
  4. 展示Make.com场景配置：Webhook触发 → 解析JSON → 创建包含摘要和行动项的Notion页面 结果：每场会议结束后自动生成Notion页面。

Example 2: Building a transcript pipeline via Jamie API

示例2：通过Jamie API搭建转录文本流水线

User says: "I need to pull all meeting transcripts from Jamie into our data warehouse nightly." Skill does:
  1. Recommends workspace API key (admin-created, sees all workspace meetings)
  2. Shows: 
    GET /v1/workspace/meetings
    with date filters → paginate → for each meeting fetch transcript (Markdown format)
  3. Flags 100 req/min rate limit — add throttling for large workspaces
  4. Suggests hybrid: webhook for real-time + nightly batch to catch gaps Result: Production-ready architecture for transcript ingestion.
用户提问：“我需要每晚将Jamie中的所有会议转录文本提取到我们的数据仓库中。” 技能处理流程：
  1. 推荐使用工作区API密钥（由管理员创建，可查看工作区内所有会议）
  2. 展示操作步骤：使用带日期筛选的
    GET /v1/workspace/meetings
    接口 → 分页处理 → 为每个会议获取转录文本（Markdown格式）
  3. 提醒存在每分钟100次请求的速率限制——针对大型工作区需添加限流机制
  4. 建议采用混合方案：Webhooks用于实时同步+夜间批量拉取以弥补数据缺口 结果：可投入生产环境的转录文本摄取架构。

Example 3: Jamie not picking up speakers correctly

示例3：Jamie无法正确识别发言人

User says: "Jamie keeps labeling my colleague as 'Speaker 2' instead of their name." Skill does:
  1. Explains speaker memory: Jamie learns speakers over time from repeated meetings
  2. Walks through: manually label speakers in the first few meetings → Jamie's speaker memory learns the voice
  3. Notes custom words feature for proper nouns and company-specific terminology
  4. Flags: bot-free recording relies on device microphone quality — if remote participants are quiet, diarization suffers Result: Clear steps to improve speaker identification accuracy.
用户提问：“Jamie总是把我的同事标记为‘发言人2’，而不是他们的名字。” 技能处理流程：
  1. 解释发言人记忆功能：Jamie会通过多次会议逐步学习发言人的声音
  2. 分步指导：在最初几次会议中手动标记发言人 → Jamie的发言人记忆功能将学习该声音
  3. 提醒可使用自定义词汇功能处理专有名词和公司特定术语
  4. 提示：无机器人录制依赖设备麦克风质量——如果远程参会者声音较小，说话人分离效果会受影响 结果：明确提升发言人识别准确率的步骤。

Troubleshooting

故障排查

Meeting summary stuck in processing or lost entirely

会议摘要卡在处理中或完全丢失

Symptom: Meeting ends but summary never appears, stays in "processing" indefinitely, or disappears Cause: App update during recording, network interruption, or processing pipeline failure. Users report ~80% reliability — critical meetings can be missed. Solution: Never update Jamie during an active meeting. If stuck: restart the Jamie app, check for pending updates, and verify internet connectivity. For high-stakes meetings, run a backup recorder (screen recording or a second tool). If a summary is lost, there's no recovery — Jamie deletes audio after transcription.
症状：会议结束后摘要始终未生成、一直显示“处理中”，或直接消失 原因：录制期间更新应用、网络中断，或处理流水线故障。用户反馈可靠性约为80%——重要会议可能会丢失。 解决方案：绝对不要在会议进行中更新Jamie。如果卡在处理中：重启Jamie应用、检查待更新内容、验证网络连接。对于高重要性会议，请使用备用录制工具（屏幕录制或其他工具）。如果摘要丢失，无法恢复——Jamie在转录完成后会删除音频。

Speaker mislabeled or missing in large meetings

大型会议中发言人标签错误或缺失

Symptom: Speakers labeled as "Speaker 2" instead of names, phantom speaker tags appear, or participants entirely missing from transcript (common in 7-8+ person meetings) Cause: Bot-free recording relies on device microphone quality. Remote participants with poor audio, crosstalk, or similar voices cause diarization failures. Speaker memory needs multiple meetings to learn voices. Solution: Manually correct speaker labels in the first 3-5 meetings with each person to train speaker memory. Use custom words for uncommon names. For large meetings, ensure good microphone quality (headset > laptop mic). Accept that large-group diarization will be imperfect — consider Gong or Fireflies for 8+ person calls.
症状：发言人被标记为“发言人2”而非姓名、出现虚拟发言人标签，或转录文本中完全遗漏参会者（在7-8人以上会议中常见） 原因：无机器人录制依赖设备麦克风质量。远程参会者音频质量差、交叉通话或声音相似都会导致说话人分离失败。发言人记忆功能需要多次会议才能学习声音。 解决方案：在与每位参会者的前3-5次会议中手动修正发言人标签，以训练发言人记忆功能。对不常见姓名使用自定义词汇。大型会议中确保麦克风质量良好（头戴式耳机优于笔记本内置麦克风）。需接受大型会议的说话人分离效果会存在不足——8人以上会议可考虑使用Gong或Fireflies。

Webhook not firing after meeting ends

会议结束后Webhook未触发

Symptom: Webhook endpoint never receives 
meeting.completed
event Cause: Webhook requires Plus+ plan, endpoint must be HTTPS, or webhook was created with wrong event Solution: Verify plan is Plus or higher. Check webhook URL is HTTPS (HTTP is rejected). In Jamie Settings → Integrations → Webhooks, confirm the webhook shows 
meeting.completed
as the selected event. Test with a short meeting. Check delivery logs — Jamie retries up to 5 times with exponential backoff. Note: processing delays (5-10 min) mean the webhook fires later than expected — don't assume failure until 15 minutes have passed.
症状：Webhook端点从未收到
meeting.completed
事件 原因：Webhooks功能需Plus版及以上套餐、端点必须为HTTPS，或Webhook创建时选择了错误事件 解决方案：验证套餐为Plus版或更高版本。检查Webhook URL为HTTPS（HTTP会被拒绝）。在Jamie设置 → 集成 → Webhooks中，确认Webhook已选择
meeting.completed
事件。通过短会议进行测试。查看交付日志——Jamie最多会重试5次，采用指数退避策略。注意：处理延迟（5-10分钟）意味着Webhook触发时间会晚于预期——15分钟后仍未触发再判定为失败。