AutoGineer
Generated banner for Contact Center Web
Generated logo for Contact Center Web

Contact Center Web

AnthropicOfficialCreated by ZoomDistributed by Anthropic

  • Skill
  • Tool integration
  • Automation and integrations
  • MIT
  • No issues found
Download ZIP

From the author

Zoom Contact Center SDK for Web. Use for web chat/video/campaign embeds, engagement event handling, app-context integrations, and Smart Embed postMessage workflows.
— the description by Zoom

AutoGineer summary

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

The Zoom Contact Center Web SDK provides a comprehensive framework for embedding chat, video, and campaign functionality directly into websites. It supports multiple integration patterns, including direct web embeds, in-client Zoom Apps, and Smart Embeds using postMessage communication. The skill covers engagement lifecycle management, event handling, and state persistence, enabling developers to build interactive customer support experiences.

What it does

  • Enables embedding of chat and video interfaces into web pages.
  • Provides event hooks for tracking engagement lifecycle and status changes.
  • Supports Smart Embed configurations via postMessage event contracts.
  • Facilitates context and state management for active engagements.
  • Offers methods for controlling campaign visibility and user context updates.

When to use it

  • When building custom web-based customer support interfaces.
  • When integrating Zoom Contact Center features into an existing website.
  • When implementing Smart Embeds for cross-origin communication.
  • When managing engagement state and context within a web application.

Advantages

  • Official support for multiple integration modes including Smart Embeds.
  • Granular event handling for engagement lifecycle management.
  • Structured approach to handling app-context and state persistence.
  • Comprehensive reference map for SDK methods and event surfaces.

Usage examples

“How do I initialize the Zoom Campaign SDK on my website?”
The agent provides the initialization pattern using the waitForReady method to ensure the SDK is prepared before executing further commands.
“What events should I listen for to track engagement status?”
The agent lists relevant events such as engagement_started, engagement_ended, and onEngagementStatusChange to monitor the interaction lifecycle.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/anthropics/contact-center-web/download

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

    mkdir -p .agents/skills && unzip contact-center-web.zip -d .agents/skills

Documentation by Zoom

Zoom Contact Center SDK - Web

Official docs:

Quick Links

  1. concepts/lifecycle-and-events.md

  2. examples/app-context-and-state.md

  3. references/web-reference-map.md

  4. troubleshooting/common-issues.md

Integration Modes

  1. Contact Center App in Zoom client:

  • Zoom Apps SDK engagement APIs/events.

  1. External website embed:

  • Campaign SDK/web scripts (zoomCampaignSdk pattern).

  • Video client initialization pattern.

  1. Smart Embed:

  • iframe + postMessage event contract.

Hard Guardrails

  • For campaign SDK, gate calls behind zoomCampaignSdk:ready.

  • Persist state by engagementId.

  • Expect context switching and background app behavior.

  • Validate CSP and allow-list settings before debugging logic.

Chaining

  • For in-client app APIs and auth flows: ../../zoom-apps-sdk/SKILL.md

  • For identity and OAuth: ../../oauth/SKILL.md

  • For cobrowse workflow: ../../cobrowse-sdk/SKILL.md

Operations

  • RUNBOOK.md - 5-minute preflight and debugging checklist.

Files

RUNBOOK.md

Contact Center Web 5-Minute Preflight Runbook

Use this before deep debugging.

Skill Doc Standard Note

  • Skill entrypoint is SKILL.md.

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

  • SDK/API names can drift by version; validate current names against docs/raw-docs before release.

1) Confirm Integration Surface

  • Confirm channel target and integration mode for Web.

  • Contact Center app path and web embed path have different lifecycle rules.

  • For mobile SDKs, verify native service lifecycle and listener registration order.

2) Confirm Required Credentials

  • entryId for chat/video/ZVA entry points.

  • apiKey for scheduled callback and campaign/tag use cases.

  • If in-client app behavior is needed, verify Zoom App credentials and required scopes.

3) Confirm Lifecycle Order

  1. Initialize SDK context early.

  2. Get channel service and register listeners/delegates before actions.

  3. Authenticate/login where required.

  4. Start/fetch channel UI and handle engagement status transitions.

4) Confirm Event/State Handling

  • Track state by engagementId; do not assume single engagement forever.

  • Handle context-switch events without losing draft/chat workflow state.

  • Keep service/channel state isolated per active engagement.

5) Confirm Cleanup + Upgrade Posture

  • End channel session and release service resources cleanly.

  • Forward app lifecycle callbacks for iOS integrations.

  • Re-check release notes for renamed/deprecated methods before upgrades.

6) Quick Probes

  • Engagement context/status APIs return valid values.

  • Start/end flow works once end-to-end for target channel.

  • Listener callbacks fire on switch/end events without stale state.

7) Fast Decision Tree

  • UI does not open -> invalid entryId/apiKey or missing init/listener sequence.

  • Events missing -> listener registered too late or detached unexpectedly.

  • Rejoin/resume fails -> lifecycle callbacks or deep-link/scheme config mismatch.

8) Source Checkpoints

Official docs
Raw docs in repo

  • raw-docs/developers.zoom.us/docs/contact-center/web/

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.

Needs: Claude Code frontmatter

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/web · 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 contact-center-web.zip