sales-nice-cxone
NICE CXone (Mpower) platform help — full CCaaS with omnichannel routing, WFM, quality management, AI analytics, digital engagement, and virtual agents. Use when setting up NICE CXone ACD routing or IVR, WFM forecasting and scheduling not working, quality management scorecards not scoring correctly, CXone Copilot freezing agent UI, comparing NICE CXone pricing tiers (Digital $71 to Complete $209/agent/mo), integrating CXone with Salesforce or other CRM, CXone reporting hard to understand, or audio quality issues on CXone calls. Do NOT use for building a general coaching program (use /sales-coaching) or reviewing a specific call transcript (use /sales-call-review).
What this skill does
# NICE CXone Platform Help
## Step 1 — Gather context
If `references/learnings.md` exists, read it first for accumulated platform knowledge.
1. **What do you need help with?**
- A) ACD routing, IVR, or omnichannel setup
- B) Workforce management (WFM) — forecasting, scheduling, adherence
- C) Quality management (QM) — scorecards, evaluations, coaching
- D) CXone Copilot / AI features
- E) Digital engagement (chat, email, social, SMS)
- F) Recording (voice + screen)
- G) Reporting and analytics
- H) API integration or SDK setup
- I) Pricing comparison or tier selection
- J) Salesforce or CRM integration
- K) Comparing CXone to another platform (Five9, Genesys, Talkdesk)
- L) Other
2. **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
3. **Contact center size?**
- A) Small (< 50 agents)
- B) Mid-size (50-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}` |
| Observe.AI overlay for contact center QA | `/sales-observe-ai {user's question}` |
Otherwise, answer directly using the platform reference below.
## Step 3 — NICE CXone 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:**
1. Digital-only teams → Digital Agent ($71/agent/mo)
2. Voice-only teams → Voice Agent ($94/agent/mo)
3. Mixed channels → Omnichannel Agent ($110/agent/mo)
4. Need QM/screen recording → Essential Suite ($135/agent/mo)
5. Need WFM → Core Suite ($169/agent/mo)
6. Need analytics + sentiment → Complete Suite ($209/agent/mo)
7. Negotiate 15-25% below list on multi-year contracts
**When comparing to competitors:**
- vs **Five9**: Five9 is strongest on intelligent IVR and virtual agents. CXone is broader (WFM + QM built-in vs Five9 add-ons). Five9 easier to implement for mid-market.
- vs **Genesys Cloud CX**: Most direct competitor at enterprise tier. Genesys stronger on AI-driven routing and predictive engagement. CXone stronger on WFM depth and breadth of digital channels. Similar pricing range.
- vs **Talkdesk**: Talkdesk deploys faster, better for mid-market. CXone has deeper WFM, more mature QM, broader integration ecosystem.
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.*
- **UI freezes when Copilot is enabled.** Agents report severe UI freezes, delayed input, and unreliable call controls with Copilot active. Workflows return to normal when Copilot is disabled. Test Copilot with a small group before rolling out.
- **Reporting is hard to understand.** Users consistently cite reporting as the weakest module — confusing navigation, non-intuitive dashboard building, and limited out-of-box reports. Budget time for report customization.
- **Can't forecast DFO digital channels.** WFM forecasting only works for legacy email and chat — if you're using Digital First Omnichannel (DFO) chat and email, you cannot forecast those channels in CXone WFM.
- **Audio quality issues.** Crackling audio and diffused calls are reported. Often resolved by clearing browser cache/cookies, but recurs. Check WebRTC/browser compatibility.
- **Support can take weeks.** Without a dedicated Technical Account Manager (TAM), bug resolution and support tickets are slow. Consider TAM add-on for production environments.
- **Portal login issues.** Password-saving and SSO issues cause recurring monthly login problems. Keep backup admin access.
- **Pricing lacks transparency.** Six tiers from $71-$209/agent/mo, but feature breakdown across tiers is unclear. Get a detailed feature matrix before committing.
## Related skills
- `/sales-talkdesk` — Talkdesk platform help (mid-market CCaaS competitor)
- `/sales-observe-ai` — Observe.AI platform help (enterprise QA overlay for CXone contact centers)
- `/sales-balto` — Balto platform help (real-time AI guidance that integrates with CXone)
- `/sales-cresta` — Cresta platform help (enterprise contact center AI with CXone integration)
- `/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-enthu` — Enthu.AI platform help (affordable contact center QA 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`
## Examples
### Example 1: Choosing the right CXone tier
**User says**: "We have 150 agents handling phone and chat. Which CXone plan do we need?"
**Skill does**:
1. Identifies Omnichannel Agent ($110/agent/mo) as baseline for mixed channels
2. Asks if they need QM/screen recording (→ Essential $135) or WFM (→ Core $169)
3. Calculates annual cost range and suggests negotiation targets
4. Compares to Five9 and Genesys pricing for context
**Result**: Clear tier recommendation with cost estimate and negotiation guidance
### Example 2: CXone reporting not useful
**User says**: "Our managers can't get useful reports out of CXone — they're building everything in Excel instead"
**Skill does**:
1. Confirms reporting is a known weak point — non-intuitive dashboard building
2. Recommends using prebuilt data visualization dashboards (Omnichannel+ tiers)
3. Suggests Data Extraction APIs for pushing data to BI tools (Tableau, Power BI)
4. Points to Real-Time Data APIs for custom dashboards
**Result**: Reporting strategy that works around CXone's limitations
### Example 3: Comparing CXone to Five9
**User says**: "We're evaluating NICE CXone vs Five9 for our 300-agent contact center"
**Skill does**:
1. Compares pricing: CXone $110-$209/agent vs Five9 $175-$325/agent
2. Maps strengths: CXone WFM + QM depth vs Five9 IVR + virtual agent ease
3. Notes CXone's broader digital channel support (30+) vs Five9's AI focus
4. Recommends POC criteria and pilot approach
**Result**: Side-by-side comparison tailored to their scale
## Troubleshooting
### Copilot causing agent UI freezes
**Symptom**: Agent workspace becomes unresponsive, delayed input, call controls unreliable
**Cause**: CXone Copilot AI processing overloading the browser-based agent workspace
**Solution**: Disable Copilot for affected agents temporarily. Test with Chrome latest version and cleared cache. Reduce concurrent AI features. Report to NICE support with browser console logs. This is a known issue — monitor release notes for fixes.
### Audio quality degradation
**Symptom**: Crackling audio, diffused calls, agents and customers can't hear clearly
**Cause**: WebRTC issues, browser cache corruption, or network configuration
**Solution**: Clear browser cache and cookies. Test in incognito mode. Check bandwidth requirements (100 Kbps per concurrent call minimum). Verify WebRTC is not blocked by firewall. Switch browsersRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.