SKILLKnowledge Work

build-zoom-contact-center-app

プラグイン: Zoom
ソース: GitHub で見る ↗

説明

Zoom Contact Center（ズームが提供するコンタクトセンター機能）の参照用スキルです。 **次のような場合に使用:** - アプリ、ウェブ、ネイティブアプリ（プラットフォーム固有の方式）の統合を実装する際 - コンタクトセンターのワークフロー（業務の流れ）へのルーティング後に対応する - 利用者とのやり取りの状態管理を行う - キャンペーンを実行・管理する - コールバック（折り返し電話）機能を利用する - バージョンのズレ（更新による不具合）のトラブルシューティング（問題解決）を行う

原文を表示

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.

ユースケース

アプリやウェブの統合を実装するとき
コンタクトセンターのワークフローへルーティングするとき
利用者とのやり取りの状態管理を行うとき
キャンペーンを実行・管理するとき
コールバック機能を利用するとき
バージョン不具合のトラブルシューティングを行うとき

本文

/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.

原文・著作権は Anthropic および各プラグイン作者に帰属します。日本語訳は Claude API による自動翻訳です。

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.

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.