Contact Center logo

Contact Center

Organization
zoom
contact-center

Zoom Contact Center skill pack for Contact Center apps, web embeds, and native mobile SDK integrations. Use for lifecycle patterns, engagement context/state handling, campaigns, callbacks, and version-drift troubleshooting.

Overview

Publisherzoom
Repositoryskills
Skill namecontact-center
Stars
78
Forks
16
Bundled files
23
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 23 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by zoom on GitHub. Read the source before you install it.

Installation

Install the Contact Center AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/zoom/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/contact-center .claude/skills/contact-center
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Contact Center in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Contact Center on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Contact Center is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Zoom Contact Center

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:

Current Release Snapshot

  • Web, Android, and iOS SDK changelogs are at 5.6.0 (verified 2026-07-10).
  • Web 5.6.0 adds Agent UI V3/Prism video updates, authenticated consumer chat history, campaign digital front door, Dynamics CRM share/remote control, CTI/PWA Cobrowse, and new locales/fallback behavior.
  • Android/iOS 5.6.0 revise real-time audio translation; iOS now receives available languages and interpreter volume restrictions from the backend service.
  • The current Contact Center REST inventory contains 314 operations; use the generated reference for exact paths.

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.

Need to create/configure the Marketplace app first? Use Marketplace app management for app creation, General App surfaces, Contact Center product selection, OAuth scopes, event subscriptions, and credential response shapes before implementing Contact Center SDK/API workflows. Start from the General App Contact Center template or S2S Contact Center template.

  1. Start flow (fetchUI, startVideo, or web SDK open/show path).
  2. Handle engagement state changes (start, hold, resume, end) and context switching.
  3. 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

Environment Variables

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Contact Center AI skill do?

Zoom Contact Center skill pack for Contact Center apps, web embeds, and native mobile SDK integrations. Use for lifecycle patterns, engagement context/state handling, campaigns, callbacks, and version-drift troubleshooting.

Why use Contact Center on TypingMind?

Because you install it once and use it with any model. Contact Center is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Contact Center in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/zoom/skills/tree/main/skills/contact-center. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Contact Center?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Contact Center?

As many as you like. As long as a model supports skills, you can use Contact Center with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Contact Center AI skill free?

Yes. It is published on GitHub by zoom under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇