Back to Details

sales-transcribeme

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

TranscribeMe Platform Help

TranscribeMe平台帮助

Step 1 — Gather context

步骤1——收集上下文

If 
references/learnings.md
exists, read it first for accumulated platform knowledge.
  1. What's your primary goal?
    • A) Transcribe audio/video files (batch transcription)
    • B) Integrate TranscribeMe API into a pipeline
    • C) Compare TranscribeMe to alternatives for my use case
    • D) Set up HIPAA-compliant medical/legal transcription
    • E) Troubleshoot a specific issue (turnaround, accuracy, uploads)
  2. What accuracy level do you need?
    • A) Good enough — AI-only is fine ($0.07/min)
    • B) High — human-edited, ~98% ($0.79/min)
    • C) Guaranteed 99% — two-step human review ($1.25/min)
    • D) Verbatim with fillers — 99% guaranteed ($2.00/min)
    • E) Not sure yet
  3. What type of content?
    • A) Sales/business calls
    • B) Medical (HIPAA required)
    • C) Legal (court proceedings, depositions)
    • D) Academic research/interviews
    • E) Call center recordings (high volume)
    • F) Mixed
Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
如果
references/learnings.md
文件存在，请先阅读它以获取积累的平台知识。
  1. 你的核心目标是什么？
    • A) 转录音频/视频文件（批量转录）
    • B) 将TranscribeMe API集成到流程中
    • C) 针对我的使用场景对比TranscribeMe与其他竞品
    • D) 设置符合HIPAA合规要求的医疗/法律转录
    • E) 排查特定问题（周转时间、准确率、上传问题）
  2. 你需要什么级别的准确率？
    • A) 足够即可——仅用AI就满足需求（0.07美元/分钟）
    • B) 高准确率——人工编辑，约98%（0.79美元/分钟）
    • C) 保证99%准确率——两步人工审核（1.25美元/分钟）
    • D) 包含填充词的逐字转录——保证99%准确率（2.00美元/分钟）
    • E) 尚未确定
  3. 内容类型是什么？
    • A) 销售/商务通话
    • B) 医疗内容（需符合HIPAA要求）
    • C) 法律内容（法庭诉讼、证词）
    • D) 学术研究/访谈
    • E) 呼叫中心录音（高容量）
    • F) 混合类型
跳转规则：如果用户的提示已包含足够上下文，直接跳至步骤2。

Step 2 — Route or answer directly

步骤2——路由或直接回答

Problem domainRoute to
Choosing a live meeting recorder or note-taker
/sales-note-taker {user's question}
Batch AI-only transcription with translation/subtitles
/sales-sonix {user's question}
Building a coaching program from call recordings
/sales-coaching {user's question}
General CRM-to-tool integration (Zapier, webhooks, iPaaS)
/sales-integration {user's question}
When routing, provide the exact command: "This is a {problem domain} question — run: 
/sales-{skill} {user's original question}
"
Otherwise, answer directly below.
问题领域路由至
选择实时会议录制工具或笔记工具
/sales-note-taker {用户问题}
带翻译/字幕的批量纯AI转录
/sales-sonix {用户问题}
从通话录音构建辅导项目
/sales-coaching {用户问题}
通用CRM到工具的集成（Zapier、webhooks、iPaaS）
/sales-integration {用户问题}
路由时，请提供准确命令："这属于{问题领域}问题——请执行：
/sales-{skill} {用户原始问题}
"
否则，直接在下方回答。

Step 3 — TranscribeMe platform reference

步骤3——TranscribeMe平台参考

Read 
references/platform-guide.md
 for the full platform reference — service tiers, pricing, integrations, data model, workflows.
If the question involves the API, also read 
references/transcribeme-api-reference.md
.
Answer the user's question using only the relevant section. Don't dump the full reference.
**阅读
references/platform-guide.md
**获取完整平台参考——服务层级、定价、集成、数据模型、工作流程。
如果问题涉及API，还需阅读
references/transcribeme-api-reference.md
。
仅使用相关部分回答用户问题，不要直接粘贴完整参考内容。

Step 4 — Actionable guidance

步骤4——可执行指导

You no longer need the platform guide — focus on the user's specific situation.
Tier selection framework:
  • Bulk/non-critical audio, speed matters most → Machine Express ($0.07/min, ~3x audio duration turnaround)
  • Business calls, interviews — "good enough" accuracy → First Draft ($0.79/min, 1 business day)
  • Legal, medical, compliance — accuracy guaranteed → Standard ($1.25/min, 1-3 business days, 99%)
  • Court proceedings, depositions — every word matters → Verbatim ($2.00/min, 2-5 business days, 99%)
  • Cost comparison vs AI-only: Sonix Standard is $10/hr ($0.17/min). TranscribeMe Machine Express is cheaper at $0.07/min but with no accuracy guarantee. For human accuracy, TranscribeMe First Draft at $0.79/min is the entry point.
When TranscribeMe beats pure AI:
  1. Heavy accents, overlapping speakers, noisy audio — human review catches what AI misses
  2. Domain-specific terminology (medical, legal) — human transcribers trained in verticals
  3. Compliance requirements — HIPAA BAA available, 99% accuracy guarantee with SLA
If you discover a gotcha, workaround, or tip not covered in 
references/learnings.md
, append it there.
你无需再查阅平台指南——专注于用户的具体场景。
层级选择框架：
  • 批量/非关键音频，速度优先 → Machine Express（0.07美元/分钟，周转时间约为音频时长的3倍）
  • 商务通话、访谈——“足够好”的准确率即可 → First Draft（0.79美元/分钟，1个工作日）
  • 法律、医疗、合规场景——需保证准确率 → Standard（1.25美元/分钟，1-3个工作日，99%准确率）
  • 法庭诉讼、证词——每个字词都很重要 → Verbatim（2.00美元/分钟，2-5个工作日，99%准确率）
  • 与纯AI工具的成本对比：Sonix Standard为10美元/小时（0.17美元/分钟）。TranscribeMe的Machine Express更便宜，为0.07美元/分钟，但无准确率保证。如需人工级准确率，TranscribeMe的First Draft（0.79美元/分钟）是入门选项。
TranscribeMe优于纯AI工具的场景：
  1. 口音浓重、说话人重叠、音频嘈杂——人工审核能捕捉到AI遗漏的内容
  2. 特定领域术语（医疗、法律）——人工转录员接受过垂直领域培训
  3. 合规要求——可提供HIPAA BAA，附带SLA的99%准确率保证
如果发现
references/learnings.md
中未涵盖的陷阱、解决方案或技巧，请将其添加到该文件中。

Gotchas

注意事项

Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
  • No live/real-time transcription. TranscribeMe is upload-only — you must upload a recorded file. For live transcription, use Fathom, Fireflies, or Otter.
  • API access requires contacting TranscribeMe. You must request an API key via a form — there's no self-serve key provisioning. Plan for lead time.
  • Turnaround times are estimates, not SLAs. "1 business day" for First Draft can stretch longer during peak periods. Rush service is available but limited to files under 70 minutes with quality audio.
  • Timestamps are at ~30-second intervals. If you need precise word-level timestamps, TranscribeMe may not be sufficient — pure AI tools like Sonix offer tighter timestamp granularity.
  • No native integrations. No Zoom, Google Meet, Teams, Zapier, or CRM connectors. Everything goes through the web portal or REST API. Plan for custom integration work.
  • Chunked upload required for large files. Files must be split into 5MB chunks for the preferred upload method. The simple upload endpoint is being deprecated.
  • BrainTree handles payment. Credit card management goes through BrainTree's SDK, not TranscribeMe directly. This adds complexity for API-only integrations.
  • Machine Express has no accuracy guarantee. The $0.07/min tier is fully automated AI with no human review — accuracy varies significantly with audio quality.
基于研究的最佳实践——请仔细查看，尤其是关于功能限制和集成陷阱的内容，这些信息可能已过时。
  • 无实时转录功能。TranscribeMe仅支持上传文件——你必须上传已录制的文件。如需实时转录，请使用Fathom、Fireflies或Otter。
  • API访问需联系TranscribeMe。你必须通过表单申请API密钥——没有自助式密钥获取渠道。请预留准备时间。
  • 周转时间为估算值，而非SLA。First Draft层级标注的“1个工作日”在高峰期可能会延长。加急服务可用，但仅适用于70分钟以内的高质量音频文件。
  • 时间戳间隔约为30秒。如果需要精确到字词级的时间戳，TranscribeMe可能无法满足需求——Sonix等纯AI工具提供更精细的时间戳粒度。
  • 无原生集成。没有Zoom、Google Meet、Teams、Zapier或CRM连接器。所有操作均需通过网页门户或REST API完成。请规划自定义集成工作。
  • 大文件需分片上传。首选上传方式要求将文件分割为5MB的分片。简单上传端点已被弃用。
  • 由BrainTree处理支付。信用卡管理通过BrainTree的SDK完成，而非直接通过TranscribeMe。这会增加纯API集成的复杂度。
  • Machine Express层级无准确率保证。0.07美元/分钟的层级完全由AI自动处理，无人工审核——准确率会随音频质量大幅波动。

Related skills

相关技能

  • /sales-sonix
    — Sonix platform help (batch AI transcription in 53+ languages, translation, SRT/VTT subtitles, REST API, SOC 2/HIPAA)
  • /sales-note-taker
    — Comparing AI meeting note-takers and conversation intelligence platforms. TranscribeMe is a backend transcription service, not a live meeting tool.
  • /sales-integration
    — General 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-sonix
    — Sonix平台帮助（支持53+种语言的批量AI转录、翻译、SRT/VTT字幕、REST API、SOC 2/HIPAA合规）
  • /sales-note-taker
    — 对比AI会议笔记工具和对话智能平台。TranscribeMe是后端转录服务，而非实时会议工具。
  • /sales-integration
    — 通用工具集成模式（Zapier、webhooks、iPaaS）
  • /sales-do
    — 不确定使用哪个技能？该路由工具可将任何销售目标匹配到合适的技能。安装命令：
    npx skills add sales-skills/sales --skill sales-do

Examples

示例

Example 1: Choosing TranscribeMe vs Sonix for medical transcription

示例1：为医疗转录选择TranscribeMe还是Sonix

User says: "I run a clinic and need HIPAA-compliant transcription for patient consultations. Should I use TranscribeMe or Sonix?" Skill does:
  1. Notes both offer HIPAA compliance — TranscribeMe with human review, Sonix AI-only
  2. Compares: TranscribeMe Standard tier ($1.25/min) gives 99% accuracy with trained medical transcribers; Sonix ($0.17/min) is cheaper but relies on AI + custom dictionary
  3. Recommends TranscribeMe Standard for patient safety-critical transcription where accuracy is non-negotiable; Sonix for lower-stakes internal notes where cost matters more Result: Clear recommendation based on accuracy requirements and risk tolerance.
用户提问：“我经营一家诊所，需要为患者咨询提供符合HIPAA合规要求的转录服务。我应该用TranscribeMe还是Sonix？” 技能处理流程：
  1. 指出两者均支持HIPAA合规——TranscribeMe提供人工审核，Sonix为纯AI
  2. 对比：TranscribeMe的Standard层级（1.25美元/分钟）由受过培训的医疗转录员提供99%准确率；Sonix（0.17美元/分钟）更便宜，但依赖AI+自定义词典
  3. 建议：对于患者安全至关重要、准确率不容妥协的转录场景，选择TranscribeMe Standard；对于风险较低的内部笔记、成本优先的场景，选择Sonix 结果：基于准确率要求和风险承受能力给出明确建议。

Example 2: Building an API pipeline for call center recordings

示例2：为呼叫中心录音构建API流程

User says: "I need to auto-transcribe 500 call center recordings per day via the TranscribeMe API. What's the architecture?" Skill does:
  1. Reads the API reference for endpoint details
  2. Sketches the pipeline: S3 event → Lambda → chunked upload (5MB chunks) → 
    POST /orders
    → configure settings (language, type, speakers) → 
    POST /orders/{id}/place
    → poll 
    GET /recordings/{id}/status
    → 
    GET /recordings/{id}/transcription
    for JSON results
  3. Notes: no webhook for completion — must poll status endpoint; OAuth2 token expires every hour — implement refresh token flow
  4. Recommends First Draft tier ($0.79/min) for call center volume as balance of cost and accuracy Result: Working pipeline architecture with TranscribeMe-specific constraints and cost estimate.
用户提问：“我需要每天通过TranscribeMe API自动转录500条呼叫中心录音。架构应该怎么设计？” 技能处理流程：
  1. 查阅API参考获取端点详情
  2. 梳理流程：S3事件 → Lambda → 分片上传（5MB分片） → 
    POST /orders
    → 配置设置（语言、类型、说话人） → 
    POST /orders/{id}/place
    → 轮询
    GET /recordings/{id}/status
    → 
    GET /recordings/{id}/transcription
    获取JSON结果
  3. 注意事项：无完成通知webhook——必须轮询状态端点；OAuth2令牌每小时过期——实现刷新令牌流程
  4. 建议：针对呼叫中心的高容量需求，选择First Draft层级（0.79美元/分钟），平衡成本与准确率 结果：提供符合TranscribeMe特定限制的可行流程架构及成本估算。

Example 3: Turnaround too slow for deadline

示例3：周转时间过慢无法满足截止日期

User says: "I submitted 3 hours of legal depositions on Standard tier and they said 1-3 business days but it's been 4 days. What do I do?" Skill does:
  1. Explains turnaround times are estimates — longer files and peak periods cause delays
  2. Notes: files over 90 minutes add 1 extra business day per TranscribeMe's policy
  3. Recommends contacting support (though response times are inconsistent per reviews), and for future submissions: break long files into <70 minute segments, consider rush service for time-sensitive work Result: Practical workaround plus prevention strategy for next time.
用户提问：“我提交了3小时的法律证词，选择的是Standard层级，他们说1-3个工作日完成，但现在已经4天了。我该怎么办？” 技能处理流程：
  1. 说明周转时间为估算值——文件过长和高峰期会导致延迟
  2. 指出：根据TranscribeMe的政策，超过90分钟的文件会额外增加1个工作日的处理时间
  3. 建议联系支持团队（但根据评论，支持响应时间不稳定）；未来提交时：将长文件分割为70分钟以内的片段，对时间敏感的工作考虑使用加急服务 结果：提供实用解决方案及未来预防策略。

Troubleshooting

故障排查

Turnaround delays on human-reviewed tiers

人工审核层级周转延迟

Symptom: Transcription takes longer than the quoted 1-3 business days Cause: Files over 90 minutes add extra processing time; peak periods slow the human transcriber queue; audio quality issues require more review passes Solution: Break long recordings into segments under 70 minutes before submitting. Use rush service for urgent files (limited to quality audio under 70 min). For predictable turnaround at scale, consider Machine Express for non-critical recordings and reserve human tiers for accuracy-critical content.
症状：转录耗时超过标注的1-3个工作日 原因：超过90分钟的文件会增加额外处理时间；高峰期会导致人工转录队列变慢；音频质量问题需要更多审核次数 解决方案：提交前将长录音分割为70分钟以内的片段。对紧急文件使用加急服务（仅适用于70分钟以内的高质量音频）。如需规模化的可预测周转时间，对非关键录音使用Machine Express层级，将人工层级保留给准确率要求高的内容。

Inconsistent punctuation and formatting

标点和格式不一致

Symptom: Sentences run together, commas in wrong places, inconsistent formatting across files Cause: Different human transcribers may apply slightly different formatting conventions; Machine Express tier has no human formatting pass Solution: If using human tiers and formatting is inconsistent, report specific examples to support — they can flag your account for formatting preferences. For Machine Express output, plan for a post-processing cleanup step. Specify domain (legal, medical) in order settings to get transcribers trained in that vertical's formatting conventions.
症状：句子连在一起、逗号位置错误、不同文件格式不一致 原因：不同的人工转录员可能采用略有不同的格式规范；Machine Express层级无人工格式审核环节 解决方案：如果使用人工层级且格式不一致，向支持团队报告具体示例——他们可以标记你的账户以应用指定格式偏好。对于Machine Express的输出，需规划后处理清理步骤。在订单设置中指定领域（法律、医疗），以获取接受过该垂直领域格式规范培训的转录员。

OAuth token expires mid-pipeline

OAuth令牌在流程中途过期

Symptom: API calls start returning 401 errors after ~1 hour of processing Cause: Access tokens expire after 1 hour (3600 seconds) Solution: Implement the refresh token flow — store the 
refresh_token
from initial auth, and when you get a 401, call 
POST /api/v1/token
with 
grant_type=refresh_token
. Better yet, use the 
applicationtoken
grant type for long-running integrations — it avoids password dependency and survives password changes.
症状：处理约1小时后，API调用开始返回401错误 原因：访问令牌每小时（3600秒）过期 解决方案：实现刷新令牌流程——存储初始认证时获取的
refresh_token
，当收到401错误时，调用
POST /api/v1/token
并传入
grant_type=refresh_token
。更好的方式是，对于长期运行的集成使用
applicationtoken
授权类型——它无需依赖密码，且在密码更改后仍有效。