AutoGineer
Generated banner for Build Zoom Contact Center App
Generated logo for Build Zoom Contact Center App

Build Zoom Contact Center App

AnthropicOfficialCreated by ZoomDistributed by Anthropic

  • Skill
  • Guidelines
  • Automation and integrations
  • MIT
  • No issues found
Download ZIP

From the author

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.
— the description by Zoom

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill serves as the primary technical reference for developers building integrations with Zoom Contact Center. It provides architectural guidance, lifecycle patterns, and troubleshooting strategies for implementing chat, video, and callback functionality across various surfaces, including Zoom Apps, web embeds, and native mobile SDKs. It acts as a hub for navigating platform-specific documentation and resolving common integration challenges.

What it does

  • Provides architectural patterns for Zoom Contact Center integrations.
  • Outlines the standard lifecycle for managing engagement sessions.
  • Offers troubleshooting paths for version drift and common integration errors.
  • Maps environment variables to specific Contact Center configuration requirements.
  • Provides guidance on handling engagement state changes and context switching.
  • Links to platform-specific SDK documentation for web, Android, and iOS.

When to use it

  • When starting a new Zoom Contact Center integration project.
  • When troubleshooting engagement state or event-handling issues.
  • When configuring environment variables for web or mobile SDKs.
  • When determining the correct SDK path for a specific deployment surface.
  • When resolving common integration failures or version compatibility problems.

Advantages

  • Centralizes complex documentation into a single navigation hub.
  • Standardizes the lifecycle approach for consistent engagement handling.
  • Provides clear guardrails for routing between different SDK platforms.
  • Includes practical troubleshooting patterns derived from developer forum data.

Usage examples

“How do I initialize the Zoom Contact Center SDK for a web chat embed?”
The agent will guide you through the lifecycle pattern, starting with platform context initialization, setting up the entry ID, and registering listeners before starting the flow.
“My engagement events are missing. How do I debug this?”
The agent will suggest verifying listener registration timing, checking network layers, and ensuring event coverage for the specific channel and engagement phase.
“What environment variables are required for a campaign-driven web embed?”
The agent will provide the list of required keys, including ZCC_CAMPAIGN_API_KEY and ZCC_WEB_API_KEY, and explain where to retrieve them in the Contact Center Admin portal.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/anthropics/build-zoom-contact-center-app/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip build-zoom-contact-center-app.zip -d .agents/skills

Documentation by Zoom

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

  1. concepts/architecture-and-lifecycle.md

  2. scenarios/high-level-scenarios.md

  3. references/forum-top-questions.md

  4. references/versioning-and-compatibility.md

  5. references/samples-validation.md

  6. references/environment-variables.md

  7. troubleshooting/common-drift-and-breaks.md

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

  1. Initialize platform context early.

  2. Build a channel item (entryId for chat/video/ZVA, apiKey for scheduled callback and campaign flows).

  3. Get service/client instance.

  4. Register listeners/delegates before user interaction.

  5. Start flow (fetchUI, startVideo, or web SDK open/show path).

  6. Handle engagement state changes (start, hold, resume, end) and context switching.

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

Files

RUNBOOK.md

Contact Center 5-Minute Preflight Runbook

Use this before deep debugging. It catches the most common Zoom Contact Center integration failures quickly.

Skill Doc Standard Note

  • Skill entrypoint is SKILL.md.

  • This runbook is an operational convention (recommended), not a required skill file.

  • SKILL.md is a navigation convention for larger skill docs.

1) Confirm Integration Path

  • Contact Center app inside Zoom client: use Zoom Apps SDK APIs/events (getEngagementContext, onEngagementStatusChange, etc.).

  • Website embed: use Contact Center web SDK/campaign script path.

  • Native mobile app: use Android/iOS Contact Center SDK binaries and service lifecycle.

Wrong path is the top source of confusion.

2) Confirm Required Credentials

  • entryId for chat/video/ZVA channels.

  • apiKey for scheduled callback and campaign/web-tag scenarios.

  • If building a Contact Center app in Zoom client, validate app credentials and OAuth setup in Marketplace.

3) Confirm Lifecycle Order

Common native/mobile order:

  1. Initialize SDK context early.

  2. Get service instance.

  3. Initialize service with ZoomCCItem.

  4. Register listener/delegate.

  5. login() where required (typically chat/ZVA).

  6. fetchUI() to present the channel view.

Web app path:

  1. zoomSdk.config(...)

  2. getEngagementContext() and getEngagementStatus()

  3. subscribe to onEngagementContextChange and onEngagementStatusChange

  4. persist state keyed by engagementId

4) Confirm Context Switching Behavior

  • A single app instance can receive multiple engagement contexts.

  • Persist draft/workflow state by engagementId.

  • Do not assume only one active engagement for chat/SMS/email workflows.

5) Confirm Cleanup Semantics

  • End action (endChat, endVideo, endScheduledCallback) is not the same as service release.

  • Apply platform-specific cleanup (logout/logoff, release/uninitialize APIs).

  • On iOS, forward app lifecycle callbacks (appDidBecomeActive, appWillTerminate, etc.) to ZoomCCInterface.

6) Version + Drift Checks

  • Zoom enforces minimum SDK versions quarterly (first weekend of February, May, August, November).

  • Re-check docs and changelog before release; naming and signatures can drift.

  • Watch deprecations:

    • iOS onService:error:detail: is deprecated in favor of onService:error:detail:description:.

7) Quick Probes

  • App context/status APIs return valid values.

  • Engagement events fire when agent switches engagements.

  • Chat/video/scheduled callback can be started and ended once each without stale state.

  • No CSP or domain allow-list blocks for web integrations.

8) Fast Decision Tree

  • No engagement data in Contact Center app -> missing SDK config capabilities or wrong runtime context.

  • Channel UI does not open -> invalid entryId/apiKey, missing init, or wrong service/channel mapping.

  • Events not firing on switch/end -> listeners not attached early enough or removed incorrectly.

  • Rejoin fails on mobile -> deep-link/scheme configuration mismatch.

Requirements and compatibility

Written for: Claude Code, Claude apps

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Zoom
Publisher
Anthropic (Official)
Distributed by
Anthropic
Source
anthropics/knowledge-work-plugins · partner-built/zoom-plugin/skills/contact-center · commit e050c2e
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from partner-built/zoom-plugin/LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Zoom or Anthropic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download build-zoom-contact-center-app.zip