Phone

Organization

zoom

phone

Zoom Phone skill pack for OAuth, Phone APIs, webhooks, Smart Embed postMessage events, URI schemes, and call-history migration patterns. Use for CRM/CTI dialer workflows, real-time call tracking, and call handling automation.

Overview

Publisher	zoom
Repository	`skills`
Skill name	`phone`
Stars	78
Forks	16
Bundled files	13
License	MIT
Links	Skill source Repository

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.
13 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 Phone AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
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.

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/phone .claude/skills/phone

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Phone 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 Phone 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 Phone 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 Phone

Implementation guidance for Zoom Phone integrations across API, webhook/event, Smart Embed, and URI-launch workflows.

Official docs:

https://developers.zoom.us/docs/phone/
CRM sample reference: https://github.com/zoom/CRM-Sample

The current API Hub inventory contains 391 Phone operations (verified 2026-07-10), including expanded call-handling/settings coverage and call-element recording/voicemail resources. Use the generated Phone API reference for exact paths rather than relying on an older endpoint list in examples.

Routing Guardrail

If the user needs embedded softphone behavior in a web app, use Smart Embed (examples/smart-embed-postmessage-bridge.md).
If the user needs call records, analytics, or automation, use Phone REST API and webhooks (references/deprecations-and-migrations.md).
If the user needs click-to-dial/SMS launch from external UI, use URI schemes (zoomphonecall://, zoomphonesms://).
If the user mixes Zoom Phone and Contact Center, chain with ../contact-center/SKILL.md.

Quick Links

Start here:

concepts/architecture-and-lifecycle.md
scenarios/high-level-scenarios.md
references/deprecations-and-migrations.md
references/forum-top-questions.md
references/smart-embed-event-contract.md
references/call-handling-patterns.md
references/environment-variables.md
references/crm-sample-validation.md
troubleshooting/common-issues.md
RUNBOOK.md
examples/smart-embed-postmessage-bridge.md
examples/phone-api-service-pattern.md
references/source-map.md

Common Lifecycle Pattern

Provision account prerequisites (Zoom Phone license, admin setup, SMS readiness).
Create OAuth app and scopes in Marketplace.
Choose integration surface:

Smart Embed (iframe + postMessage)
REST + webhooks
URI launch (callto, tel, zoomphonecall, zoomphonesms)

Capture real-time events (Smart Embed events and/or webhooks).
Persist call identifiers and correlate records (call_id, call_history_uuid, call_element_id).
Apply migration-safe data mapping (v1 -> v2 -> v3) and handle renamed fields.
Harden security (origin validation, webhook signature validation, least-privilege scopes).

Need to create/configure the Marketplace app first? Use Marketplace app management for General App or S2S app setup, admin/user scope selection, event subscription behavior, and credential response shapes before implementing Phone APIs or Smart Embed workflows. Start from the General App Phone template or S2S Phone template.

High-Level Scenarios

CRM softphone pane using Smart Embed + contact search/match callbacks.
Click-to-call from account/contact table via zp-make-call.
Call disposition workflow using zp-save-log-event and custom notes page.
SMS engagement workflow with zoomphonesms:// and zp-sms-log-event.
Real-time operational board driven by phone.* webhook events.
Call analytics migration from legacy call logs to call history/call elements.
Admin automation for user/auto-receptionist/call-queue call-handling settings.

See scenarios/high-level-scenarios.md for details.

Chaining

OAuth setup/token lifecycle: ../oauth/SKILL.md
Marketplace app creation and manifest validation: ../rest-api/references/marketplace-apps.md
Phone and account resources via REST: ../rest-api/SKILL.md
Event delivery and signature validation: ../webhooks/SKILL.md
Contact Center blended journey: ../contact-center/SKILL.md

Environment Variables

See references/environment-variables.md for standardized .env keys and where to find each value.

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 Phone AI skill do?

Why use Phone on TypingMind?

Because you install it once and use it with any model. Phone 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 Phone in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/zoom/skills/tree/main/skills/phone. 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 Phone?

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 Phone?

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

Is the Phone 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

Pdf

anthropics

OrganizationPopular

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart,…

Landing Report

Read-only queue dashboard for workspace-aware ship. (gstack)

Gstack Openclaw Ceo Review

garrytan

CommunityPopular

Use when asked to review a plan, challenge a proposal, run a CEO review, poke holes in an approach, think bigger about scope, or decide whether to expand or reduce the plan.

Ui Styling

Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Zoom Phone

Routing Guardrail

Quick Links

Common Lifecycle Pattern

High-Level Scenarios

Chaining

Environment Variables

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now