营销安装
- 作者仓库星标 25
- 许可证 MIT
- 作者更新于 实时读取
- 作者仓库 sales
- 领域
- 工程开发 · sales · contact-center · ccaas
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 100 / 100 · 已通过审计
- 作者 / 版本 / 许可
- @sales-skills · v1.0.0 · MIT
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- macOS · Linux · Windows
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- Shell 执行
- 网络行为
- 允许外网请求
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
---
name: sales-talkdesk
description: Talkdesk platform help — cloud contact center (CCaaS) with AI virtual agents, omnichannel routin…
category: 工程开发
runtime: 无特殊运行时
---
# sales-talkdesk 输出预览
## PART A: 任务判断
- 适用问题:代码实现、重构、调试或代码审查。
- 输入要求:目标材料、限制条件、期望输出和验收方式。
- 证据边界:围绕“Step 1 — Gather context / Step 2 — Route or answer directly / Step 3 — Talkdesk platform reference”读取原文规则,不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断:确认你的需求是否属于代码实现、重构、调试或代码审查,并标出输入、限制和预期结果。
- **02** 执行计划:优先按“Step 1 — Gather context / Step 2 — Route or answer directly / Step 3 — Talkdesk platform reference”拆成步骤,说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果:给出可复制的命令、文件改动、检查清单或内容草稿,并说明如何继续迭代。
- **04** 风险边界:结合 读取文件、写入/修改文件、执行终端命令、会按任务需要访问外部网络、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件、执行终端命令;会按任务需要访问外部网络;通常不需要额外 API Key。
- 先小样例验证,再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 原文出现了 `/sales-coaching`、`/sales-call-review`、`/sales-note-taker`、`/sales-integration`、`/sales-observe-ai` 这类斜杠命令;如果你的 Agent 支持命令触发,优先用命令开场,再补充目标和边界。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是:读取文件、写入/修改文件、执行终端命令。
先用一个小任务确认它会围绕“Step 1 — Gather context / Step 2 — Route or answer directly / Step 3 — Talkdesk platform reference”工作;涉及文件或命令时,先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作;如果输出泛泛而谈,就补充输入、边界和验收标准后重跑。
---
name: sales-talkdesk
description: Talkdesk platform help — cloud contact center (CCaaS) with AI virtual agents, omnichannel routin…
category: 工程开发
source: sales-skills/sales
---
# sales-talkdesk
## 什么时候使用
- 用于审阅代码、文档或方案并给出可执行反馈 适合处理工程开发场景下的代码实现、调试、重构、测试或代码审查,核心价值是把输入、判断、执行、验证和交付边界固定下来,避免 Agent 泛泛回答。 围绕 sales、contact-center…
- 面向代码实现、重构、调试或代码审查,优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「Step 1 — Gather context / Step 2 — Route or answer directly / Step 3 — Talkdesk platform reference」组织步骤,不把推断写成作者事实。
- 读取文件、写入/修改文件、执行终端命令;会按任务需要访问外部网络;通常不需要额外 API Key。
- 先跑小样例,确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown,不编造命令、平台或依赖。 作者原文负责流程事实;仓库文件负责来源和命令;流狐只补充适用场景、限制和质量判断。
skill "sales-talkdesk" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> Step 1 — Gather context / Step 2 — Route or answer directly / Step 3 — Talkdesk platform reference
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件、执行终端命令 | 会按任务需要访问外部网络
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
} Talkdesk Platform Help
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
What do you need help with?
- A) ACD routing, IVR (Studio), or call flow setup
- B) Digital channels (email, chat, SMS, social messaging)
- C) AI features — Autopilot (virtual agents), CoPilot (agent assist), Navigator (routing)
- D) Quality management — QA scoring, evaluations
- E) Workforce management — forecasting, scheduling, adherence
- F) Outbound dialer or campaign management
- G) Reporting and analytics
- H) API integration or Connections setup
- I) Pricing comparison or tier selection
- J) Salesforce or CRM integration
- K) Comparing Talkdesk to another platform (Five9, NICE CXone, Genesys)
- L) Other
What's your current setup?
- A) Evaluating whether to buy
- B) New — haven't started implementation
- C) In implementation
- D) Running but having issues
- E) Expanding to new modules
Contact center size?
- A) Small (< 25 agents — consider Express free tier)
- B) Mid-size (25-200 agents)
- C) Large (200-1,000 agents)
- D) Enterprise (1,000+ agents)
Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
Step 2 — Route or answer directly
| Problem domain | Route to |
|---|---|
| Building a coaching program or training cadence | /sales-coaching {user's question} |
| Reviewing a specific call transcript for coaching | /sales-call-review {user's question} |
| Choosing between note-taker/conversation intelligence platforms | /sales-note-taker {user's question} |
| General CRM/tool integration patterns (Zapier, webhooks) | /sales-integration {user's question} |
| Overlay QA tools for Talkdesk (Observe.AI, Balto, Cresta) | /sales-observe-ai or /sales-balto or /sales-cresta |
| Comparing to NICE CXone | /sales-nice-cxone {user's question} |
Otherwise, answer directly using the platform reference below.
Step 3 — Talkdesk platform reference
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.
Step 4 — Actionable guidance
You no longer need the platform guide — focus on the user's specific situation.
Tier selection framework:
- Small US/Canada team (< 25 agents) → Express (free, 25 licenses)
- Digital-only → Digital Essentials ($85/agent/mo)
- Voice-only → Voice Essentials ($105/agent/mo)
- Omnichannel + WFM + screen recording → Elite ($165/agent/mo)
- Industry-specific (healthcare, banking, retail) → Experience Cloud ($225/agent/mo)
- AI features (Autopilot, CoPilot, Navigator) are paid add-ons on all tiers — budget 20-60% above base price
- All pricing assumes 3-year contract — negotiate 15-25% below list
When comparing to competitors:
- vs Five9: Five9 stronger on intelligent IVR and virtual agents, concurrent pricing model (cheaper for shift-based teams). Talkdesk deploys faster, more flexible with smaller teams, better industry-specific clouds.
- vs NICE CXone: CXone has deeper WFM, more mature QM, broader digital channels. Talkdesk easier to implement, better for mid-market. CXone stronger at enterprise scale.
- vs Genesys Cloud CX: Genesys stronger on AI-driven routing and predictive engagement. Talkdesk easier to deploy. Both Gartner Leaders. Similar enterprise pricing range.
If you discover a gotcha, workaround, or tip not covered in references/learnings.md, append it there.
Gotchas
Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
- AI features are all expensive add-ons. Autopilot, CoPilot, Navigator, and Interaction Analytics require separate quotes even on Elite ($165/agent/mo). Total costs typically climb 20-60% above listed per-agent price. Get an all-in quote before committing.
- 3-year contract required for listed pricing. Shorter terms cost more. No publicly advertised volume discounts.
- Telecom costs are separate. PSTN usage, toll-free, and inbound numbers are billed in addition to per-user monthly fees. Budget for these on top of the agent license.
- Implementation can take months. Multiple reviews report 6-12+ months to go live with full implementation, with continued charges during setup. Define clear milestones and go-live criteria in contract.
- Support tickets take 3-4 days. For a call-center solution, this response time is unusually slow. Dedicated TAM add-on improves this but costs extra.
- Call quality issues. Dropped calls, crackling audio, and unclear error messages are consistently reported. Often related to WebRTC/browser issues — test in Chrome with cleared cache.
- API access is restricted. Only enterprise customers and AppConnect partners get API access — not included in base plans. Submit a request with account info.
Related skills
/sales-nice-cxone— NICE CXone platform help (primary CCaaS competitor)/sales-observe-ai— Observe.AI platform help (QA overlay that integrates with Talkdesk)/sales-balto— Balto platform help (real-time AI guidance for contact centers)/sales-cresta— Cresta platform help (enterprise contact center AI)/sales-call-review— Review specific calls and extract coaching insights/sales-coaching— Build coaching programs for contact center agents/sales-note-taker— Compare conversation intelligence tools or wire APIs into CRM/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
Examples
Example 1: Choosing the right Talkdesk tier
User says: "We have 80 agents handling phone and chat. Which Talkdesk plan do we need and what will it actually cost?" Skill does:
- Identifies Elite ($165/agent/mo) as baseline for omnichannel
- Warns that AI features (Autopilot, CoPilot) are add-ons — budget $200-260/agent/mo all-in
- Calculates annual cost range and suggests negotiation targets
- Notes 3-year contract requirement and separate telecom fees
- Compares to Five9 and NICE CXone pricing for context Result: Clear tier recommendation with realistic all-in cost estimate
Example 2: Talkdesk calls keep dropping
User says: "Our agents keep getting disconnected mid-call and the audio quality is terrible" Skill does:
- Confirms call quality issues are a known Talkdesk problem across reviews
- Troubleshoots: browser cache/cookies, Chrome version, incognito mode test
- Checks WebRTC and firewall configuration requirements
- Recommends bandwidth verification (100 Kbps per concurrent call minimum)
- Suggests opening a support ticket with browser console logs Result: Systematic troubleshooting plan with fallback options
Example 3: Comparing Talkdesk to Five9
User says: "We're evaluating Talkdesk vs Five9 for our 200-agent contact center with heavy outbound calling" Skill does:
- Notes Five9 is stronger for outbound-heavy (progressive dialer, TCPA compliance built-in)
- Five9 concurrent pricing saves money for shift-based teams vs Talkdesk per-user
- Talkdesk deploys faster and has industry-specific clouds (healthcare, banking)
- Both Gartner Leaders — decision is about fit, not quality
- Recommends POC criteria Result: Side-by-side comparison tailored to their outbound-heavy use case
Troubleshooting
Calls dropping or audio quality issues
Symptom: Agents get disconnected, crackling audio, customers can't hear clearly Cause: WebRTC issues, browser cache corruption, or network configuration Solution: Clear browser cache and cookies. Test in incognito mode. Use Chrome (recommended). Check bandwidth (100 Kbps per concurrent call). Verify WebRTC isn't blocked by firewall. Check Talkdesk status page (status.talkdesk.com) for active incidents.
Reporting is hard to customize
Symptom: Managers can't build useful reports, advanced features feel hidden Cause: Reporting UI has a steep learning curve with non-intuitive navigation Solution: Start with prebuilt reports before building custom. Use Explore API for programmatic data extraction to BI tools (Tableau, Power BI). Use Live API for real-time dashboards. Consider Data Extraction APIs for external analytics.
Implementation taking too long
Symptom: Months into implementation, still not live, being charged during setup Cause: Complex enterprise deployments with many modules, integrations, and customizations Solution: Define clear go-live milestones in contract. Start with core voice before adding digital channels. Phase AI add-ons after core stabilization. Escalate to executive sponsor if timeline slips past contracted milestones. Get written go-live date commitment.
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核