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.

Jump to install Review files

Repository: anthropics/knowledge-work-plugins
Last source activity: April 9, 2026 at 23:28
Detected SKILL.md language: English
Stars: 25,764
Forks: 3,038

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with an AI assistant

Copy this prompt into the AI assistant you're using.

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/anthropics/knowledge-work-plugins/tree/main/partner-built/zoom-plugin/skills/contact-center.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill build-zoom-contact-center-app

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

27 files

SKILL.md

Source instructions · Read-only preview

name: build-zoom-contact-center-app
description: 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.
triggers: ["contact center sdk","zoom contact center","zcc","engagement context","engagement status","campaign sdk","scheduled callback","getengagementcontext","onengagementstatuschange","zoom contact center app"]

# /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: - https://developers.zoom.us/docs/contact-center/ - https://developers.zoom.us/docs/contact-center/web/sdk-reference/ - https://marketplacefront.zoom.us/sdk/contact/android/index.html - https://marketplacefront.zoom.us/sdk/contact/ios/index.html ## 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](web/SKILL.md). - If the user is integrating native Android or iOS SDK binaries, route to [android/SKILL.md](android/SKILL.md) or [ios/SKILL.md](ios/SKILL.md). - If the user needs Contact Center call-control or queue APIs, chain with [../rest-api/SKILL.md](../rest-api/SKILL.md). ## Quick Links Start here: 1. [concepts/architecture-and-lifecycle.md](concepts/architecture-and-lifecycle.md) 2. [scenarios/high-level-scenarios.md](scenarios/high-level-scenarios.md) 3. [references/forum-top-questions.md](references/forum-top-questions.md) 4. [references/versioning-and-compatibility.md](references/versioning-and-compatibility.md) 5. [references/samples-validation.md](references/samples-validation.md) 6. [references/environment-variables.md](references/environment-variables.md) 7. [troubleshooting/common-drift-and-breaks.md](troubleshooting/common-drift-and-breaks.md) 8. [RUNBOOK.md](RUNBOOK.md) Platform skills: - [android/SKILL.md](android/SKILL.md) - [ios/SKILL.md](ios/SKILL.md) - [web/SKILL.md](web/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 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](scenarios/high-level-scenarios.md) for details. ## Chaining - Auth and in-client app identity: [../zoom-apps-sdk/SKILL.md](../zoom-apps-sdk/SKILL.md) and [../oauth/SKILL.md](../oauth/SKILL.md) - Contact Center REST workflows: [../rest-api/SKILL.md](../rest-api/SKILL.md) - Cobrowse on web voice/chat channels: [../cobrowse-sdk/SKILL.md](../cobrowse-sdk/SKILL.md) ## Environment Variables - See [references/environment-variables.md](references/environment-variables.md) for standardized `.env` keys and where to find each value.

View on GitHub

Back to search Back to installation

ad-manager

The ads consultant that becomes an ads agent. Reads paid-ad performance natively through the TikTok Ads connector, or via a build-connector Zapier connection for other ad platforms, explains in plain English what is working and what is burning money, recommends budget, targeting, and creative changes with the dollar impact of each, drafts new ad copy in the owner's voice plus Canva creative briefs, and — only after an explicit yes — executes the approved changes in the ad account. Works from exported CSV reports when nothing is connected, the normal starting point. Use this whenever the owner talks about ads or ad spend at all, including "are my ads working," "what's my ROI on ads," "I'm spending money on Facebook and I don't know what I'm getting," "should I turn this campaign off," "my cost per lead is going up," "write me a new ad," "who should I be targeting," or "the ad guy quit."

2026-09-15

ap-processor

Works the bill pile end to end: reads bills and vendor statements out of the AP inbox or from uploaded PDFs and phone photos, pulls out vendor, amount, due date, and line detail, codes each one to the right account and job, matches it against the purchase order and the receiving ticket, then stages the entries and a proposed payment run in QuickBooks, Xero, or NetSuite for the owner to approve in one pass. Nothing is entered and nothing is paid without an explicit yes. Reach for this whenever bills, vendor invoices, or paying people comes up — including "what do I owe," "the bills are piling up," "pull the invoices out of my email and into QuickBooks," "code these for me," "who needs to get paid this week," "did we get billed twice," or when the owner forwards a supplier invoice with no message at all. Use it before cash-flow-snapshot or month-end-prep so those run on real payables instead of a guess.

2026-09-15

brand-style

Sets and updates the owner's brand look and output preferences, which every page and document the plugin produces then follows automatically. Captures the brand from a pasted website link or a plain-words description — never a hex code, color picker, or upload — previews it on a sample page, asks how they want their outputs delivered (visual artifacts, Word docs, markdown, Notion pages, Canva Docs, or best-for-the-skill), and saves both to the business profile. Runs inside smb-onboard on first setup and stands alone forever after. Use when the owner says "update my brand," "we rebranded," "change my colors," "make the reports match our new look," "change how you give me reports," "I want Word docs instead," or anything about the look or format of what the plugin hands them.

2026-09-15

View all from this repository

build-zoom-contact-center-app

Source facts

Install options

Install with an AI assistant

Review the source files

More from this repository

Install with an AI assistant

More from this repository