build-zoom-contact-center-app

build-zoom-contact-center-app is a skill for Claude Code, Codex from zoom/zoom-plugin. It costs 48 tokens per session (1,372 once invoked), scanned A, a copy of build-zoom-contact-center-app, MIT.

Implementation guidance for connecting software to Zoom Contact Center, Zoom's system for handling customer conversations and support work. It covers integrations for Zoom client apps, websites, and Android or iOS apps.

In plain words
What is it for?
Use it to build Contact Center apps inside Zoom, embed chat or video on a website, connect native mobile apps, handle engagement state, and troubleshoot version differences.
Why use it?
It helps developers choose the correct integration path and manage conversation context, state, campaigns, callbacks, and changes between versions. It also points call-control and queue work toward the relevant API guidance.

Skill for Claude CodeCodex

Part of the zoom-plugin plugin — 47 skills, 7 MCP servers shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/zoom/zoom-plugin/contact-center
Any agent
npx skills add zoom/zoom-plugin --skill contact-center
Clone the repo
git clone --depth 1 https://github.com/zoom/zoom-plugin

Made for: Claude Code, Codex.

Or install zoom-plugin, the plugin that ships this one along with the rest of its 47 skills, 7 MCP servers.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for build-zoom-contact-center-app

README.md
[![agentmods](https://agentmods.dev/badge/skills/zoom/zoom-plugin/contact-center.svg)](https://agentmods.dev/skills/zoom/zoom-plugin/contact-center)
Your own site
<a href="https://agentmods.dev/skills/zoom/zoom-plugin/contact-center"><img src="https://agentmods.dev/badge/skills/zoom/zoom-plugin/contact-center.svg" alt="Measured on agentmods" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,372 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 86% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.01372
Opus 5 $0.00024 $0.00686
Sonnet 5 $0.00010 $0.00274
Haiku 4.5 $0.00005 $0.00137

Measured 6d ago against content hash f067f0caff13, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

build-zoom-contact-center-app scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

86% identical to build-zoom-contact-center-app — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/contact-center/SKILL.md · 130 lines

How it starts

The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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

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

Read the full file on GitHub · 130 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 130 lines · 48 tokens per session scan A f067f0caff13

Subscribe to this mod's changes

build-zoom-contact-center-app is a skill published in the GitHub repository zoom/zoom-plugin (7 stars, last pushed 29d ago), licensed MIT. It adds 48 tokens to every session and 1,372 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to build-zoom-contact-center-app, differing in 8 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens