Skill

build-zoom-contact-center-app

Reference skill for Zoom Contact Center. Use after routing to a contact-center workflow when implementing app, web, or native integrations; engagement context and state handling; campaigns; callbacks; or version-drift troubleshooting.

Install

npx claudepluginhub anthropics/claude-plugins-official --plugin zoom-plugin

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Background reference for Zoom Contact Center integrations across app, web, and native mobile surfaces.

Supporting Assets

SKILL.md

Similar Skills

connections-optimizer

Reorganizes X and LinkedIn networks: review-first pruning of low-value follows, priority-based add/follow recommendations, and drafts warm outreach in user's voice.

everything-claude-code

158.8k

content-engine

Generates platform-native social content for X, LinkedIn, TikTok, YouTube, newsletters from source material like articles, demos, docs, or notes. Adapts voice and format per platform.

everything-claude-code

158.8k

configure-ecc

Interactively installs Everything Claude Code skills and rules to user-level (~/.claude) or project-level (.claude) directories, verifies paths, and optimizes files. Activate on 'configure ecc' or setup requests.

everything-claude-code

158.8k

Stats

Stars1

Forks0

Last CommitApr 3, 2026

Actions

View Source View Plugin View on GitHub View README

/build-zoom-contact-center-app

Background reference for Zoom Contact Center integrations across app, web, and native mobile surfaces.

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:

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:

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 (entryId for chat/video/ZVA, apiKey for scheduled callback and campaign flows).
Get service/client instance.
Register listeners/delegates before user interaction.
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 engagementId and 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 .env keys and where to find each value.

/build-zoom-contact-center-app

Background reference for Zoom Contact Center integrations across app, web, and native mobile surfaces.

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:

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:

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 (entryId for chat/video/ZVA, apiKey for scheduled callback and campaign flows).

Get service/client instance.

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 engagementId and 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.

Chaining

Environment Variables

See references/environment-variables.md for standardized .env keys and where to find each value.