Provides implementation guidance and state management for Zoom Contact Center SDKs and web integrations.
Install
mkdir -p .claude/skills/contact-center && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/19395" && unzip -o skill.zip -d .claude/skills/contact-center && rm skill.zipInstalls to .claude/skills/contact-center
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Zoom Contact Center skill pack for Contact Center apps, web embeds, and native mobile SDK integrations. Use for lifecycle patterns, engagement context/state handling, campaigns, callbacks, and version-drift troubleshooting.Key capabilities
- →Initialize Zoom Contact Center platform context
- →Manage engagement lifecycle states
- →Handle campaign callbacks and channel selection
- →Integrate web embeds and native mobile SDKs
- →Troubleshoot version drift in SDK implementations
How it works
The skill provides a lifecycle pattern for Zoom Contact Center, starting with context initialization, followed by channel item creation, listener registration, and state management for engagements.
Inputs & outputs
When to use contact-center
- →Integrate contact center SDK
- →Handle engagement status
- →Manage campaign callbacks
- →Troubleshoot version drift
About this skill
Zoom Contact Center
Implementation guidance for Zoom Contact Center across:
- Contact Center apps in the Zoom client (Zoom Apps SDK path)
- Web channel embeds (chat/video/campaign)
- Native mobile SDKs (Android/iOS)
Official docs:
- https://developers.zoom.us/docs/contact-center/
- https://developers.zoom.us/docs/contact-center/web/sdk-reference/
- https://marketplacefront.zoom.us/sdk/contact/android/index.html
- https://marketplacefront.zoom.us/sdk/contact/ios/index.html
Current Release Snapshot
- Web, Android, and iOS SDK changelogs are at
5.6.0(verified 2026-07-10). - Web
5.6.0adds Agent UI V3/Prism video updates, authenticated consumer chat history, campaign digital front door, Dynamics CRM share/remote control, CTI/PWA Cobrowse, and new locales/fallback behavior. - Android/iOS
5.6.0revise real-time audio translation; iOS now receives available languages and interpreter volume restrictions from the backend service. - The current Contact Center REST inventory contains 314 operations; use the generated reference for exact paths.
Routing Guardrail
- If the user is building an app inside the Zoom Contact Center desktop client, stay on the Zoom Apps SDK path and use this skill plus
zoom-apps-sdk. - If the user is embedding chat/video widgets on a website, route to web/SKILL.md.
- If the user is integrating native Android or iOS SDK binaries, route to android/SKILL.md or ios/SKILL.md.
- If the user needs Contact Center call-control or queue APIs, chain with ../rest-api/SKILL.md.
Quick Links
Start here:
- concepts/architecture-and-lifecycle.md
- scenarios/high-level-scenarios.md
- references/forum-top-questions.md
- references/versioning-and-compatibility.md
- references/samples-validation.md
- references/environment-variables.md
- troubleshooting/common-drift-and-breaks.md
- RUNBOOK.md
Platform skills:
Documentation Structure
contact-center/
├── SKILL.md
├── RUNBOOK.md
├── concepts/
│ └── architecture-and-lifecycle.md
├── scenarios/
│ └── high-level-scenarios.md
├── references/
│ ├── versioning-and-compatibility.md
│ ├── samples-validation.md
│ └── environment-variables.md
├── troubleshooting/
│ └── common-drift-and-breaks.md
├── android/
│ ├── SKILL.md
│ ├── concepts/sdk-lifecycle.md
│ ├── examples/service-patterns.md
│ ├── references/android-reference-map.md
│ └── troubleshooting/common-issues.md
├── ios/
│ ├── SKILL.md
│ ├── concepts/sdk-lifecycle.md
│ ├── examples/service-patterns.md
│ ├── references/ios-reference-map.md
│ └── troubleshooting/common-issues.md
└── web/
├── SKILL.md
├── concepts/lifecycle-and-events.md
├── examples/app-context-and-state.md
├── references/web-reference-map.md
└── troubleshooting/common-issues.md
Common Lifecycle Pattern
- Initialize platform context early.
- Build a channel item (
entryIdfor chat/video/ZVA,apiKeyfor scheduled callback and campaign flows). - Get service/client instance.
- Register listeners/delegates before user interaction.
Need to create/configure the Marketplace app first? Use Marketplace app management for app creation, General App surfaces, Contact Center product selection, OAuth scopes, event subscriptions, and credential response shapes before implementing Contact Center SDK/API workflows. Start from the General App Contact Center template or S2S Contact Center template.
- Start flow (
fetchUI,startVideo, or web SDK open/show path). - Handle engagement state changes (
start,hold,resume,end) and context switching. - End flow and release resources (
endChat/endVideo,logout/logoff, uninitialize/release).
High-Level Scenarios
- Agent side-panel app that stores notes per
engagementIdand survives context switching. - Browser chat/video campaigns launched from web tags.
- Native mobile customer app for chat/video/scheduled callback.
- Campaign-driven channel selection (chat, ZVA, video, scheduled callback).
- Rejoin flow for dropped video engagements on mobile.
- Smart Embed CRM softphone with postMessage event contracts.
See scenarios/high-level-scenarios.md for details.
Chaining
- Auth and in-client app identity: ../zoom-apps-sdk/SKILL.md and ../oauth/SKILL.md
- Contact Center REST workflows: ../rest-api/SKILL.md
- Cobrowse on web voice/chat channels: ../cobrowse-sdk/SKILL.md
Environment Variables
- See references/environment-variables.md for standardized
.envkeys and where to find each value.
When not to use it
- →Using the wrong SDK path for the target platform
- →Implementing REST workflows without proper Marketplace app configuration
- →Ignoring engagement state changes during context switching
Prerequisites
Limitations
- →Requires specific SDK paths for different integration types
- →REST inventory is limited to defined operations
How it compares
This skill provides a structured lifecycle approach for Zoom Contact Center integrations, distinguishing between web, mobile, and desktop app SDK paths.
Compared to similar skills
contact-center side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| contact-center (this skill) | 0 | 17d | Review | Advanced |
| fastapi-templates | 520 | 2mo | No flags | Intermediate |
| android-kotlin-development | 268 | 4mo | Review | Advanced |
| fastapi-pro | 79 | 3mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by zoom
View all by zoom →You might also like
fastapi-templates
wshobson
Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.
android-kotlin-development
aj-geddes
Develop native Android apps with Kotlin. Covers MVVM with Jetpack, Compose for modern UI, Retrofit for API calls, Room for local storage, and navigation architecture.
fastapi-pro
sickn33
Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and Pydantic V2. Master microservices, WebSockets, and modern Python async patterns. Use PROACTIVELY for FastAPI development, async optimization, or API architecture.
telegram-bot-builder
davila7
Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot.
telegram-mini-app
davila7
Expert in building Telegram Mini Apps (TWA) - web apps that run inside Telegram with native-like experience. Covers the TON ecosystem, Telegram Web App API, payments, user authentication, and building viral mini apps that monetize. Use when: telegram mini app, TWA, telegram web app, TON app, mini app.
stripe-integration
wshobson
Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks. Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows.