Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Welcome to Artificial Intelligence Documentation.
Artificial Intelligence BluepaperAI CompanionCustom AI CompanionZoom's Commitment to Responsible AIThe Zoom Technical Library is your destination for advanced Zoom product documentation and processes! We understand there are many settings, switches, and knobs available across our platform, and we want to support Zoom platform admins with the best resources we can, so we’ve created this library with systems admins and technical folks in mind. Below is a sneak peek at the types of resources you can expect to see added over time:
Whether you’re a seasoned Zoom admin, or you're just getting started, there will be something for everyone. Bookmark this site and check back for updates as we grow this space.
When you’re ready to jump in, use the menu on the left to choose a product, expand its documentation options, and select the resource that best fits your needs.
Added Contacts Field Guide
Added Zoom Node Explainer
Added the Zoom for Blackberry Field Guide
Added the SSO Field Guide
Added the Zoom Customer Experience Bluepaper
Added the Zoom Phone Bluepaper
Added the Custom AI Companion
Added the Zoom Team Chat Migration App Field Guide
Added the Sub Accounts Field Guide
Added the VDI Explainer
Added the Zoom Whiteboard Explainer
Added the Microsoft 365 Calendaring Field Guide
Explainers
Explainers are scannable resources designed to make Zoom’s products easier to understand. By blending the structure of an FAQ with some elements of a whitepaper, these documents break down technical concepts into short summaries and fuller explanations. Each section header delivers a quick takeaway, while the accompanying content offers clarity for those seeking more depth.
Field Guides
Field Guides act as navigation tools and deployment guides for Zoom products and features. These documents focus on helping IT admins complete complex tasks or processes, like deploying the Zoom Phone Local Survivability Module or configuring advanced Zoom Contact Center features. Within these documents, you can expect clear, step-by-step instructions and practical tips that streamline implementation and support successful, organization-wide deployments.
Bluepapers
Bluepapers, named after Zoom’s signature color, serve as in-depth strategic resources that expand on standard whitepapers. These documents explore entire product lines or services—like Zoom Phone and Zoom Contact Center—with comprehensive overviews, key insights, and summaries of essential topics. Ideal for gaining a complete understanding, Bluepapers serve as a go-to resource for deep insight into Zoom's products.



Authored by Jakob Ganschow
The AI Bluepaper examines artificial intelligence's expanding influence throughout the Zoom ecosystem. AI continues to redefine how we work, unlocking fresh possibilities for workplace transformation and helping teams accomplish more through intelligent efficiency.
The following pages attempt to bring clarity and structure to AI's many applications across Zoom—from foundational features like Live Transcription to the comprehensive capabilities of AI Companion and Custom AI Companion within the Zoom Workplace app. Throughout, we've included screenshots, real-world examples, security and privacy context, and practical guidance for both users and administrators. You'll also find direct links to our Support Center to streamline learning, activation, and adoption of these features.
Above all, this content is designed to be authentic, transparent, and relevant to your daily work—because that's where transformation happens. Our goal is not only to inform but to inspire, revealing what becomes possible when a unified communications platform places AI at the heart of everything it does.
This document is designed to help you understand Zoom's AI capabilities in bite-size chunks that make learning about artificial intelligence easier. Throughout this document, we've organized the information in two main ways:
Approaching AI features categorically and topically. AI features and deployment models are grouped in short, clear summaries that demystify complex concepts—always paired with relevant support links when possible.
Explanatory headers to save on time. Wherever we can, we’ve used headers that explain themselves—so you don’t have to dig for the point. For example:
A title like “Zoom’s AI Deployment Models” signals a broad overview.
A more detailed header like
At the end of the day, we know the modern boom of artificial intelligence can seem overwhelming, and we've done our best to organize this information in a way that's clear, practical, and genuinely helpful as you evaluate Zoom's AI capabilities for your business needs. Whether you're an IT administrator trying to understand the technical requirements, a decision-maker evaluating security implications, or someone who just wants to know what AI features are available, the AI Bluepaper is designed to give you the information you need to make confident choices about Zoom's AI platform.
This section provides an overview of core features, dataflows, diagrams, and options for administrating AI Companion.
This pages provides an overview of administrating Zoom AI Companion.
LicensingFeature ManagementSecurity and Privacy SettingsZoom AI Companion supports a flexible architecture that helps customers align with data residency preferences and service locality requirements. The following sections outline those capabilities and clarifications.
For customers outside the U.S., Zoom offers Zoom-Hosted Models Only (ZMO) and Zoom-Hosted Models Plus (ZM+) to align with regional data processing preferences. With ZMO or ZM+ enabled, AI processing is localized to the customer’s selected region.
When AI Companion features use third-party models (e.g., Perplexity AI), data may be stored and processed in the U.S., even for customers located elsewhere. This should be considered for regional data residency preferences.
Zoom AI Companion does not process or store information such as facial scans or voiceprints without user enrollment and consent through their Zoom account.
This section provides an overview of core features, dataflows that power Zoom AI algorithms.
Algorithm FeaturesAlgorithm Diagrams and DataflowsThis section provides technical implementation details, configuration workflows, and strategic practices designed specifically for administrators deploying Zoom solutions.
You'll find step-by-step procedures that streamline complex configurations, troubleshooting resources that accelerate resolution times, and practical examples that demonstrate real-world application scenarios.
Topics within this section connect technical specifications to measurable business outcomes, enabling you to architect solutions, support client implementations, and identify opportunities for feature expansion. Whether you're conducting initial deployments, optimizing existing environments, or evaluating advanced capabilities for your organization, this documentation serves as your definitive resource for successful Zoom product utilization.
Zoom Mail and Calendar Client ExplainerZoom Mail and Calendar Services ExplainerThis section provides technical implementation details, configuration workflows, and strategic practices designed specifically for administrators deploying Zoom solutions.
You'll find step-by-step procedures that streamline complex configurations, troubleshooting resources that accelerate resolution times, and practical examples that demonstrate real-world application scenarios.
Topics within this section connect technical specifications to measurable business outcomes, enabling you to architect solutions, support client implementations, and identify opportunities for feature expansion. Whether you're conducting initial deployments, optimizing existing environments, or evaluating advanced capabilities for your organization, this documentation serves as your definitive resource for successful Zoom product utilization.
The following sections describe Zoom AI Companion features and functionality integrated with Zoom Docs.
Zoom Docs’ Content Generation and Revision feature assists users in creating and refining documents and tables. When used, AI Companion can offer suggestions for new content, generate summaries, and revise existing content using user-provided prompts. This feature helps enhance productivity by providing contextually relevant ideas, making document creation and editing faster and more efficient.
This feature is especially useful for teams and individuals who need to quickly draft, refine, or collaborate on documents. It helps users streamline the content creation process, especially in fast-paced environments or when revising complex documents. This can benefit project managers, content creators, and professionals working in collaborative teams, helping ensure documents are clear, concise, and aligned with their intended message.
Refer to Zoom’s support center for more information on with AI Companion.
Zoom Docs’ Sentence Completion feature assists users by providing predictive writing suggestions while composing content. This feature helps streamline the writing process, offering real-time prompts and completions that keep the flow of ideas intact.
Refer to Zoom’s support center for more information on with AI Companion.
The following section describes Zoom AI Companion features and functionality integrated with Zoom Whiteboard.
Zoom Whiteboard’s Content Generation feature enables users to easily generate ideas, refine existing content, and add visual elements to a whiteboard with AI assistance. By using AI Companion, users can create sticky notes, tables, text, mindmaps, and more—all with a simple prompt. This feature helps streamline the brainstorming process, designed to make it faster and more efficient to visualize and organize ideas.
Refer to Zoom’s support center for more information on Whiteboard Content Generation with AI Companion.
The following sections discuss various security and compliance components as they pertain to AI Usage at Zoom.
Zoom AI Companion offers several controls that help organizations manage how meeting data is stored, accessed, and shared. These controls are designed to help reduce the risk of unauthorized access, comply with legal obligations, and align with internal security policies. The following sections explain how Zoom handles transcript retention, summary access, legal holds, and admin-managed sharing behavior.
Zoom offers a Zero Data Retention option with respect to Zoom’s retention of the temporary transcript**,**screen shared content via OCR, and in-meeting chat messages used to provide a Meeting Summary. When enabled, these inputs will be deleted by Zoom immediately after the summary is created. If a summary fails to be created it will be retained for up to 24 hours to allow for retries. To enable this feature please reach out to your account team or log a support ticket.
Zoom Meetings are best experienced through the native Zoom Workplace desktop application, mobile app, or a Zoom Room, but you can also attend a Zoom meeting from the web, as a dial-in user (by calling in to the meeting by phone), or via third-party room devices (Zoom’s Conference Room Connector allows SIP/H.323-based video conferencing devices). This document provides a comprehensive overview of the available settings and in-meeting features you can use to help secure Zoom Meetings against uninvited automated meeting tools.
The Zoom App Marketplace is your resource to access and download applications and integrations that can enhance your meeting or event experience. Among those applications are bots, which, along with certain integrations and third-party services, constitute automated meeting tools. While automated meeting tools are intended to extend and enhance the Zoom Meetings experience, their presence may lead to unwanted data access through the recording of in-meeting media. Many of the following security features have individual user-level controls that empower Zoom users to manage the security of their own meetings, but you will also find several administrator-level configurations that account owners and admins can use to make meetings more secure for your entire account.
This section describes the current limitations of Custom AI Companion. Information provided within this section is accurate as of this document’s publication date, but may change over time. Customers with questions about these limitations or feature availability are encouraged to speak with their Zoom account team for more information.
Custom AI Companion features currently support English only, however, Zoom expects to expand the list of supported languages over time. This limitation does not apply to the script-translation abilities of Custom Avatar Clips.
The following pages discuss AI Companion Features:
Zoom Phone Short Message Service (SMS) allows users to send and receive text messages using the Zoom Workplace desktop application, Zoom Workplace mobile application, or Zoom Web App. This document provides a comprehensive overview of SMS configuration, along with guidance surrounding administrative controls and capabilities.
Zoom offers a wide range of API endpoints to meet the diverse needs of customers and developers. These APIs enable organizations to seamlessly integrate Zoom’s robust communication features into existing workflows, extend functionality, and build custom solutions tailored to specific business requirements.
Currently, many of AI Companion’s features—such as Meeting Summaries, Meeting Transcripts, and Phone Transcripts—are closely tied to individual Zoom products. As a result, APIs related to these features are accessed through their respective product-specific API endpoints. Except for the ability to archive conversations within the Companion panel, Zoom does not currently provide API access to AI Companion Panel features.
For detailed information on Zoom AI Companion APIs and guidance on getting started, please visit the .
Welcome to Zoom Phone documentation
Getting started with ZPLS.
Before deploying ZPLS within a network, there are several considerations related to user access, site design, signaling and media, and PSTN integrations that should be considered before deployment. The following pages explore these scenarios. After reading, you can expect to understand the implications of high-level technical design to guide your rollout.
Zoom does not currently prevent users from copying, downloading, or forwarding summary content that has been shared with them. Summaries can be accessed via web browsers, and Information Barriers do not currently restrict meeting summary sharing or access.
Zoom AI Companion data, including summaries and transcripts, is subject to eDiscovery and legal hold processes. If a meeting is under legal hold, content will be retained even if deleted by a host.
Zoom employees cannot access meeting or messaging content (audio, video, transcripts, whiteboards, etc.) unless:
Authorized by the account admin/owner, or
Required for legal, safety, security, or support reasons
Zoom enforces least-privilege, role-based access controls and maintains audit logs to detect unauthorized access.
While Zoom cannot technically prevent users from exfiltrating content (e.g., via personal email or file transfer), admins can:
Disable summary delivery via email
Require authentication to view summary links
These settings help mitigate risk of unauthorized sharing.
Our AI services are expanding over time. To learn more about current availability in your region, please contact your Zoom account team.


This section provides technical implementation details, configuration workflows, and strategic practices designed specifically for administrators deploying Zoom solutions.
You'll find step-by-step procedures that streamline complex configurations, troubleshooting resources that accelerate resolution times, and practical examples that demonstrate real-world application scenarios.
Topics within this section connect technical specifications to measurable business outcomes, enabling you to architect solutions, support client implementations, and identify opportunities for feature expansion. Whether you're conducting initial deployments, optimizing existing environments, or evaluating advanced capabilities for your organization, this documentation serves as your definitive resource for successful Zoom product utilization.


Zoom AI Companion is designed with user privacy and system integrity in mind. The following sections explain how memory is allocated, isolated, and cleared during the lifecycle of each user request—designed to ensure data is not leaked between users or retained in memory unnecessarily.
To prevent data from leaking across requests, Zoom assigns each incoming user request to a dedicated thread. A thread is the smallest unit of execution in modern computing and includes its own call stack and memory space. This provides that the memory used to handle one user’s request is not accessible to another, even if multiple requests are processed concurrently.
While threads isolate memory per request, Zoom also uses containerization to separate entire services. Each AI Companion service runs inside its own isolated container environment, with independent runtime dependencies, configurations, and libraries. This helps ensure consistency across deployments and adds an additional layer of infrastructure-level protection, even though it’s not intended to isolate individual user requests.
Once a thread finishes handling a request, all memory it used is automatically released by the underlying operating system or runtime. This default behavior ensures that memory does not persist beyond the lifecycle of the request, reducing the risk of residual data lingering in memory.
Zoom engineers follow secure development best practices to proactively minimize memory-related risks:
Temporary data structures are cleared once they’re no longer needed.
User-specific data is not stored in global or static memory.
Languages and frameworks with automatic memory management and garbage collection are leveraged to ensure memory is reliably reclaimed by the system.
Together, these layered practices—thread-based execution, containerized service isolation, automatic memory release, and disciplined secure coding—help ensure that memory in Zoom AI Companion is managed responsibly, securely, and in alignment with enterprise-grade expectations for user data protection.
Zoom AI Companion is powered by a combination of proprietary and third-party large language models (LLMs), designed to provide contextual intelligence across Zoom’s products. The following sections describe Zoom’s practices for training data, hallucination management, and system performance tuning.
Zoom does not use communications-like customer content—such as audio, chat, screen share, whiteboards, or reactions—for training any Zoom or third-party models.
Zoom trains its models using:
Public domain data
Purchased third-party datasets
Zoom-created training materials
Zoom reviews the datasets to determine whether they were obtained lawfully and whether the license is applicable to Zoom’s proposed use. Note that we also use third party model providers, such as OpenAI and Anthropic, as part of our federated model. Please refer to any information they provide on training data.
As with any generative model, AI Companion may generate outputs that are factually incorrect or irrelevant (hallucinations). Zoom recommends reviewing outputs carefully. Zoom reduces hallucinations by:
Testing models against real use cases
Improving context via retrieval-augmented generation (RAG)
Enhancing language support with translation pipelines (e.g., English-to-Spanish)
Zoom regularly monitors model performance, tracks quality metrics, and updates internal systems to improve accuracy and transparency. While explainability is limited by model design, performance regressions are addressed through testing and update cycles.
Zoom is committed to developing Al responsibly, with security and privacy at the core of the generative Al capabilities it provides to its customers. Zoom recognizes that generative Al presents an evolving set of risk considerations for its customers, and the company is committed to prioritizing transparency and customer choice as it brings generative Al features to market.
To learn more about Zoom’s responsible AI practices and data handling, see the AI Companion Security and Privacy Whitepaper and the Zoom Privacy Statement.
The following diagram illustrates how Personal Audio Isolation functions within the Zoom Workplace app.

This section outlines the options available for account administrators to manage and provision licenses for Zoom AI Companion. Administrators can assign and control user access through automated provisioning methods, such as single sign-on (SSO) with SAML or SCIM, as well as through manual assignment via the Zoom web portal. Details of each method are provided in the following sections.
Zoom AI Companion is included with any paid Zoom license (e.g., Zoom Meetings, Zoom Phone, etc.). However, user access can be controlled at the account or user-group level, enabling administrators to selectively enable or restrict AI Companion features across their organization.
Administrators have multiple methods available to assign licenses and control access to AI Companion and Custom AI Companion features. These include automated provisioning methods (SAML and SCIM) and manual assignment via the Zoom web portal.
Accounts utilizing single sign-on (SSO) can streamline user management by automatically assigning licenses through either SAML (Security Assertion Markup Language) response mapping or SCIM (System for Cross-domain Identity Management).
SAML
SAML-based provisioning allows automatic assignment of the following:
Zoom AI Companion access (controlled by paid license status and group/account-level access)
Custom AI Companion add-on license
User entitlements and assignments automatically update each time the user authenticates via SSO, based on configured response mappings from the identity provider.
SCIM
SCIM-based provisioning dynamically synchronizes user assignments and entitlements from your identity provider to Zoom. SCIM supports automatic assignment of:
Zoom AI Companion (controlled by paid license status and group/account-level access)
Custom AI Companion add-on license
For more information on provisioning users over SCIM, refer to the Zoom App Marketplace for a and options.
Administrators can manually manage licenses and entitlements directly through the Zoom web portal using individual user editing or bulk editing via CSV file uploads.
Individual User Assignment
The Zoom web portal interface enables administrators to individually assign licenses and entitlements. Admins can manage:
Standard AI Companion access through paid license verification and user group configurations
Custom AI Companion Add-on licenses
For more information on this process, refer to Zoom’s support center article on .
CSV Bulk Upload
For larger user groups, CSV bulk uploads enable administrators to simultaneously assign licenses and manage entitlements. When provisioning users via CSV uploads, administrators can define:
User access to standard AI Companion (based on group membership)
Custom AI Companion Add-on license assignments
For more information on this process, refer to Zoom’s support center article on .
Zoom’s Generative AI Virtual Background feature allows users to create custom AI-generated backgrounds for their meetings without the need for manual image selection or uploads. By leveraging generative AI, users can quickly generate unique and professional virtual backgrounds tailored to their preferences, enhancing their on-screen presence with minimal effort. Users simply input text, which is transformed into an image output through Zoom’s fine-tuned, internally-hosted model.
When AI Companion processes the user's input, the algorithm converts the request into patterns—called embeddings—that correspond to elements of the request. These embeddings convert the meaning of words into the mathematical format that the algorithm uses to generate images, essentially turning human language into machine-readable instructions for creating visual content. After, the system then introduces "noise" to the canvas, which establishes a baseline for the image.
The Stable Diffusion model then begins its iterative refinement process, gradually removing the noise while using the text embeddings as guidance. Through multiple steps, the algorithm transforms the random static into recognizable features, with each iteration bringing the image closer to matching the original request. This step-by-step denoising approach allows AI Companion to create images by making small, controlled improvements at each stage until the final visual output emerges.
Before delivering the image to the user, the system processes it through a third-party moderation service, which analyzes the generated content to help avoid offensive images, then the image is returned back to the user’s Zoom Workplace app.
Refer to Zoom’s support center for more information on and use AI Companion’s generation feature.
The Events Compose feature helps users quickly generate content for event-related areas, including descriptions, session details, speaker bios, and lobby announcements. By providing context or a prompt, users can receive AI-generated text suggestions that match their style and tone.
Refer to Zoom’s support center for more information on Events Compose with AI Companion.
Zoom Events’ Image Generation feature allows event hosts to create custom images for their events using AI. This includes generating images for event headers, session images, expo images, and more. Users can enter specific prompts, choose from AI-suggested styles, and set image ratios (landscape, portrait, square). Once generated, images can be previewed and applied directly to the event, enhancing the visual appeal of the event without the need for external design tools.
Refer to Zoom’s support center for more information on with AI Companion.
Zoom Events’ Email Compose feature helps users create email content for event communication quickly. By inputting prompts, users can generate email bodies, subject lines, and call-to-action text tailored to their needs. This feature allows event hosts to draft and refine emails more efficiently, helping ensure messages are contextually relevant and aligned with the event’s tone.
Refer to Zoom’s support center for more information on with AI Companion.
Zoom Events’ Chat Compose feature allows users to quickly craft professional and contextually-aware responses within an event’s lobby. This is especially useful for maintaining dynamic engagement in large events, where quick and appropriate responses are needed to keep discussions flowing or provide guidance or direction.
Refer to Zoom’s support center for more information on with AI Companion.
The following sections describe Zoom AI Companion features and functionality integrated with Zoom Team Chat.
The Team Chat Compose feature uses AI to assist users in drafting messages more efficiently. By analyzing the context of ongoing conversations, it can offer suggestions that adjust tone, provide topic prompts, or modify message length, helping ensure communication is both effective and aligned with the intended message. Chat Compose can also rewrite drafted messages, changing the tone and content to match the user’s preference, such as making a message more professional, or casual, depending on the user’s preference.
Refer to Zoom’s support center for more information on with AI Companion.
Zoom Team Chat’s Thread Summary feature allows users to quickly catch up on important conversations by providing an AI-generated summary of all messages within a thread. This summary highlights key points, decisions, and action items discussed within the thread, making it easier for users to stay informed without having to read through each individual message.
With this feature, users can save time and efficiently stay up to date, especially in active threads with many participants. It’s particularly useful for teams managing multiple conversations or for new team members who need to get up to speed quickly.
Refer to Zoom’s support center for more information on with AI Companion.
Zoom Team Chat’s Quick Schedule feature allows users to schedule meetings directly from the chat interface with just a few clicks. By integrating with the Zoom calendar, it automatically suggests available times based on participants’ schedules, streamlining the process of setting up a meeting without having to leave the chat.
This feature is particularly useful for teams that need to coordinate meetings quickly, eliminating the back-and-forth of finding an available time slot. With Quick Schedule, users can instantly create and share meeting invites, making it easier to schedule impromptu meetings or follow-ups without interrupting the flow of conversation.
Refer to Zoom’s support center for more information on with AI Companion.
Zoom Team Chat’s Sentence Completion feature assists users by offering AI-generated suggestions to finish sentences as they type. The feature predicts the most likely continuation of a message based on the context of the conversation, helping users write more efficiently and maintain a consistent flow in their communication.
In the following screenshot, the suggested sentence completion text is highlighted within the box.
Refer to Zoom’s support center for more information on with AI Companion.
Team Chat includes built-in summarization for shared text files and Zoom Docs links, allowing users to quickly understand document contents without leaving the chat interface. When a file is shared in a conversation, it appears as an attachment card. By hovering over the attachment and selecting the AI Companion button, it automatically generates a concise overview of the document’s key points.
The summary appears directly within the chat, giving users an at-a-glance understanding of the material without needing to open, download, or process the file separately. This integrated approach streamlines collaboration by keeping context and comprehension in one place.
Refer to Zoom's support center for more information on
This section provides an overview of Custom AI Companion's general dataflow diagrams.
The following diagram outlines typical dataflows for Custom AI Companion’s Custom Meeting Summary Templates under Zoom’s federated approach.
The following diagram outlines a typical dataflow for a Custom Dictionary applied to a meeting’s transcript to generate a meeting summary under Zoom’s federated approach.
The following diagrams outline typical dataflows for using Custom AI Companion’s Custom Avatars feature under Zoom’s federated model.
Avatar Creation
The following diagram outlines the process for creating a custom avatar without generating a clip.
Clip Creation
The following diagram outlines the process for creating a clip using a pre-existing avatar.
The following diagrams outline typical data flows for Knowledge Bases with Custom AI Companion under Zoom’s federated approach.
Direct Data Uploads
Web Sync
Third-Party Cloud Storage
Third-Party Index
The following diagram outlines typical dataflows for using Custom AI Companion with third-party integrations under Zoom’s federated approach.
The following sections describe Zoom AI Companion features and functionality integrated with Zoom Recordings.
For cloud recorded meetings or clips, Smart Recording enhances meeting recordings by automatically generating a structured summary, highlighting key moments, and identifying action items without requiring manual review from a user. Using the recording’s transcript, Zoom AI Companion creates searchable, time-stamped highlights, making it easy for users to navigate and review important content.
With this feature, users can quickly find relevant information without watching the entire recording, saving time and improving efficiency. This is particularly beneficial for teams managing multiple meetings or for participants who were unable to attend. Smart Recording also allows users to access AI-generated chapters, summaries, and speaker insights, providing a streamlined way to catch up on discussions and next steps.
The following image provides an example of these features, detailing chapters, highlighted moments, etc.
Refer to Zoom’s support center for more information on with AI Companion, and Zoom’s YouTube channel for a .
The Voice Recording feature brings the power of AI Companion to in-person conversations—letting users capture, transcribe, and summarize live discussions directly within the Zoom Workplace mobile app. Ideal for on-site training or a face-to-face client meeting, users can record high-quality audio and automatically generate transcripts and AI summaries similar to those generated from meetings and phone calls.
Each recording generates a complete set of documentation assets: the original audio file, a searchable transcript with speaker labels, and an AI-generated summary that surfaces key themes, decisions, and action items. These assets automatically tie into Zoom Workplace, making it easy to revisit details, share context, and transition from conversation to follow-up.
Heads Up
During initial setup, users are prompted to confirm that they are following all applicable laws when recording conversations.
Refer to Zoom’s support center for more information on with AI Companion.
This document is designed to provide readers with a general overview, description, and understanding of Zoom Phone — Zoom’s cloud-based telephony service. Within this document, readers will be presented with a wide range of features available with Zoom Phone, insights into the service's functionality, and information to help set up a new account, including their network environment. While this document aims for thorough coverage, it does not encompass every available feature, as the Zoom Phone team continues to innovate and release new features regularly. Readers with questions are encouraged to speak with their account or sales team for any inquiries related to this product to help ensure a tailored understanding of what Zoom Phone can provide your business.
This document is designed to provide you information in bite-size chunks that makes learning a new product easier. Throughout this document, we have done this in two ways:
Summarizing explanatory content within the headers, when possible.
Listing Zoom Phone’s features and experiences categorically, with small, helpful summaries that break content down into simple concepts, complete with links to relevant support articles.
For example, on the Zoom Phone Overview page you will read that, “Zoom Phone offers three primary service offerings: Native, BYOC Cloud Peering, and BYOC Premises Peering.” The purpose of this header is to provide you with the information up front, so you know the general idea of what you’re reading without requiring you to decipher several paragraphs of text.
In other places, we’ve followed a topical approach, because some features are a little too nuanced to easily summarize in a bite-size header of text. For example, Zoom Phone features like “Auto Receptionists,” “Zoom AI Companion,” and “Security Standards” are listed topically in an effort to make locating them and their relevant content easier. Consequently, when you read the next header, “Zoom Phone Native”, you know that you’re reading about that service offering, and any other important distinctions relevant to it.
At the end of the day, we want this document to be clear, helpful, and informative to you, the reader. For that reason, we’ve included illustrations, recommendations, notes, a few cautions, and many, many links to our support center, so you can always have the most recent instructions for each relevant feature. With that said, we hope this document is invaluable to you as you consider and explore Zoom Phone for your business needs.
As an alternative to cloud peering, Zoom Phone also supports a Bring Your Own Carrier (BYOC) premises peering (BYOC-P) service model, where a business connects their on-premises hardware—specifically, a session border controller (SBC) connected to a carrier—with Zoom Phone's cloud PBX system.
With this service model, businesses continue to have access to Zoom Phone's cloud PBX features, like Call Queues, Auto Receptionists, number assignment, etc., while the underlying PSTN connections are handled by the company's chosen provider. This service model is nearly identical to Zoom Phone's Cloud Peering model (BYOC-C), with the exception that the customer provides and maintains their own supported SBC to peer with Zoom Phone's data centers, instead of the underlying carrier.
Unlike the Zoom Phone Native and cloud peering services, which contain general lists of serviceable countries and territories, premises peering service areas are determined by the customer's chosen telephony service provider. Businesses are encouraged to consult with their chosen telephony provider to ensure their coverage will meet their business needs.
Zoom Hub allows users to ask Zoom AI Companion questions about files directly from Hub, without opening or manually searching through each document. When a file is selected from the Zoom Hub file list, users can ask AI Companion to retrieve specific information, create summaries, or pull out insights from that file.
This capability supports a wide range of file types, including Data Tables, Docs, Summary Docs, Meeting Agendas, Meetings, Whiteboards, Clips, and Recordings. Users can also reference Zoom Hub files directly from the AI Companion side panel by using a slash ( / ) to insert and access file content seamlessly.
By enabling direct question-and-answer interaction with stored content, this feature helps users locate key details and surface relevant information faster—reducing the need to manually review entire files.
Zoom Tasks helps users stay organized by capturing action items, follow-ups, and priorities directly within the Zoom Workplace desktop app. Integrated with Zoom AI Companion, it can automatically generate tasks from meeting summaries, turning discussions into clear, trackable action items. Tasks can be assigned to others or self-assigned, helping to ensure accountability and follow-through. By keeping AI-generated tasks linked to their original conversations and meetings, Zoom Tasks streamlines workflow management, making it easier to stay on top of responsibilities.
Refer to Zoom’s support center for using Zoom Tasks with AI Companion.
Maintain telephony services during internet outages with the Zoom Phone Local Survivability module.
Zoom Phone is a cloud-based telephony service that is dependent on internet provider connectivity to Zoom’s data centers to operate. However, maintaining telephony services in the event of an internet service failure or a service impacting event is critical for business continuity and operations. To address this, Zoom offers the Zoom Phone Local Survivability (ZPLS) module as a Zoom Node workload to provide telephony resiliency in the event of an internet outage.
During a survivability event, users register to the ZPLS module, which provides basic telephony services — like internal calling — until full service can be restored. Customers can expand this functionality by integrating the ZPLS module with an on-premises private branch exchange (PBX) system or a customer-provided carrier (BYOC) to route calls across the public switched telephone network (PSTN).
When integrated with an SBC, businesses have the best of both worlds: the simplicity and ease of a cloud-managed phone system, with the survivability and resiliency of on-premises infrastructure when the unforeseen occurs. With ZPLS, businesses can comfortably deprecate most legacy, on-premises telephony appliances and migrate to a cloud-based phone system with confidence.
To that end, this guide provides a comprehensive overview and deployment flow to the ZPLS module, including product installation and deployment, design and implementation considerations, feature support, use cases, and more.
This guide is designed to provide you information in bite-size chunks that makes learning a new product easier. Instead of offering long, tedious paragraphs packed full of information, we have broken content down into shorter summaries, with elaborations in the body for additional information or context.
For example, you will read that, “ZPLS is an on-premises virtual appliance that supports internal phone calls between users in a common site when Zoom data centers are unreachable.” If that statement makes sense to you on its own, you can feel free to skip the text underneath the summary and move onto the next, where you will read, “ZPLS also supports cross-site calling when ZPLS appliances and their associated sites are connected through a common network.”
When you combine these summaries, the bigger picture begins to form:
ZPLS is an on-premises virtual appliance that supports internal phone calls between users in a common site when Zoom data centers are unreachable.
ZPLS also supports cross-site calling when ZPLS appliances and their associated sites are connected through a common network.
If these summaries provide you enough information to understand the product—great! But if you want to know more, there’s additional context and information available underneath each summary.
The full list of pages within this guide follow below and can be visited out of order, if you know which specific content you're looking for:
The following sections describe Zoom AI Companion features and functionality integrated with Zoom Contact Center.
Zoom Contact Center’s Sentiment Analysis feature provides real-time insights into customer sentiment during messaging and voice interactions. Using AI, it continuously evaluates conversation transcripts to gauge consumer sentiment throughout the engagement.
This feature is particularly useful for customer support teams, helping agents identify and respond to shifts in sentiment as conversations evolve. By recognizing positive, neutral, or negative language, agents can adjust their approach to improve customer experience and engagement.
Zoom Contact Center’s default sentiment analysis model—distinct from the one used in Zoom Quality Management—evaluates sentiment based on the consumer’s
Information contained within this section is derived from the . Copies of information from this document are provided within this document for convenience; however, customers are encouraged to refer to the webpage for the most current information. For your convenience, notable, frequently-requested information is provided below.
Zoom does not use any customer audio, video, chat, screen sharing, attachments, or other communications-like customer content (such as poll results, whiteboard, and reactions) to train Zoom’s or its third-party artificial intelligence models.
Zoom AI Companion features must use certain content to provide the service.
Account administrators have visibility into what automated meeting tools are installed and how they’re utilized by their account users through the analytics provided in the App Marketplace. Admins can see an activity log for each automated meeting tool, including:
which users are pre-approved to use the tool
There are multiple that can be used if an uninvited automated meeting tool, dial-in user, or third-party room device joins your meeting. See the following options for managing, removing, and reporting uninvited meeting participants.
When a Zoom meeting is locked, no new participants can join, even if they have the meeting ID and passcode. To lock a meeting, click the Security icon at the bottom of your Zoom window and click the Lock Meeting option. The meeting can also be unlocked if new participants need to be added.
This section outlines the supported platforms, necessary calling plans, and current limitations for SMS and Multimedia Messaging Service (MMS) functionality.
Zoom has provided the following whitepapers and legal resources to assist customers with understanding compliance requirements, implementing security protocols, evaluating data handling practices, and making informed technology adoption decisions across AI Companion services and platform-wide legal obligations.
The describes Zoom AI Companion's security and privacy features, third-party subprocessors, and data handling practices.
The ZPLS module is an on-premises appliance that allows users within the same Site, connected by a common network, to place phone calls to each other when Zoom data centers are unreachable. This creates a survivability solution for business continuity in the event of a network outage or your network disconnects from Zoom Phone data centers.
This section provides a brief overview of Zoom’s Custom AI Companion add-on. Additional details of these features are available in other sections of this document.
Zoom Phone Native numbers and numbers that are ported into Zoom Phone are almost always considered Voice over IP (VoIP) phone numbers and may have different capabilities compared to numbers classified as mobile-only within certain countries.
For instance, two-factor authentication providers may not support VoIP phone numbers. Consequently, if a mobile number associated with two-factor authentication is ported into Zoom Phone, the user may no longer be able to approve authentication prompts. Additionally, Zoom Phone requires a data connection, e.g., Wi-Fi or 4G/5G, to make and receive calls from a mobile device. Users cannot make a cellular signal-based phone call without an existing data connection.
The Zoom Assistant is a lightweight widget that runs on a user's desktop as an extension of the Zoom Workplace app, offering Zoom Phone Pro and Licensed users a consolidated phone interface.
With docking capabilities, the Zoom Assistant remains hidden when not in use, and extends when hovered over with a cursor or when there's an active call. This compact design grants users full use of their desktop space while working, allowing them to minimize the Zoom Assistant panel when it's not in use.
With this always-available tool, users can simplify their workflows and processes in conjunction with virtually any other application, granting flexibility and ease of use. Core features of the Zoom Assistant include:
The following personas illustrate how AI Companion redefines work across the Zoom Workplace platform. While the characters are imagined, the challenges they face and the decisions they make reflect real-world demands faced by professionals in HR, sales, customer support, and small business leadership. From multilingual onboarding and automated follow-ups to strategic content creation and live customer escalations, each story shows how AI Companion embeds intelligence into the rhythm of work—minimizing manual effort, accelerating execution, and freeing users to focus on what matters most.
Each persona profile includes an overview of the role, core pain points, relevant AI Companion and Custom AI Companion features, a day-in-the-life narrative, and a clear summary of how AI transforms their workday from reactive execution to proactive impact.
In the end, these personas offer a glimpse into something far greater than productivity gains: they show what becomes possible when artificial intelligence is deeply woven into a unified platform for communication and work. With Zoom’s business platform spanning Meetings, Phone, Team Chat, Docs, Contact Center, Tasks, Whiteboard, and more, this isn’t about bolting on AI as a trend—it’s about building intelligence into the core. By placing AI at the center of how people meet, message, create, and act, Zoom is redefining how work gets done.
To view step-by-step instructions for assigning Zoom Phone calling plans, please see the Managing Phone Users support article.
Along with a supported calling plan, users must have a 10-digit phone number assigned to use SMS. For users outside of the US and Canada, the mobile phone number type is required. To view detailed instructions for assigning phone numbers, please see the Number Management support article.
Users in the US or Canada must have one of the following Zoom Phone Calling Plans assigned to use SMS:
Zoom Phone Metered
Unlimited, Pro Plus
Business Plus (US and Canada numbers)
Users in Australia must have one of the following Zoom Phone Calling Plans assigned to use SMS:
Zoom Phone Regional Calling Plan for AU/NZ
Zoom Phone Pro with AU/NZ additional phone numbers
Business Plus (AU/NZ numbers)
Users in the UK must have one of the following Zoom Phone Calling Plans assigned to use SMS:
Zoom Phone Regional Calling Plan for UK/IR
Zoom Phone Pro with UK/IR phone numbers
Business Plus (UK/IR numbers)
The following limitations apply to Zoom Phone SMS:
SMS is not supported on physical desk phones.
SMS is only available in the US, Canada, UK, and Australia. It is not available in New Zealand or Ireland at this time.
International SMS is only available for US/CA.
MMS is only available for US/CA.
Zoom Phone Pro Global Select Unlimited does not support the mobile phone number type.
Consistent with Zoom’s Privacy Statement, Zoom employees may not access or use customer content, including meeting, webinar, messaging, or email content (specifically, audio, video, files, in-meeting whiteboards, messaging, or email content), any content generated or shared as part of other collaborative features (such as out-of-meeting whiteboards), or content generated by AI Companion, unless authorized by the account owner or administrator of the account hosting the Zoom product or service where the customer content was generated, or as required for legal, safety, or security reasons.
Zoom’s federated approach to AI utilizes multiple AI models and AI services to provide its AI Companion features. Below is a summary of the models used for AI Companion. AI Companion strategically leverages these models to provide high-quality results in response to users’ interactions with Zoom’s product.
Zoom-hosted models*
Anthropic models (e.g., Claude 3.5)
OpenAI models (e.g., GPT-4, DALL·E 3)
Zoom also uses the following model providers for particular features:
Zoom uses Perplexity to provide web content search results for the AI Companion panel.
Zoom uses ElevenLabs to generate audio for the Zoom Clips AI Avatars feature.
Changes to the models used in federation can occur at any time to improve the service or resolve issues and outages. In addition, maintenance of the models hosted by Zoom may include changes to their capabilities and responses. Customers on Zoom-hosted Models Only will not utilize external models in the event of an outage or other service interruption.
*IMPORTANT NOTE: Zoom offers a Zoom–Hosted Models Only (ZMO) option, which means that data will not be sent to third-party models for processing. We also offer Zoom-Hosted Models Plus (ZM+), which includes Zoom-hosted Models plus Anthropic models made available using Amazon Bedrock, a fully managed service provided through Zoom’s existing cloud services provider AWS. To enable ZMO or ZM+ please reach out to your account team or log a support ticket.
In general, Zoom stores and retains customer content and personal data for as long as required to engage in the uses described in its Privacy Statement, unless a longer retention period is required by applicable law.
After providing the AI Companion service, Zoom may retain the customer content(see tables under the** AI Companion Features section**)** for up to 30 days for support and debugging purposes*** unless a longer retention period is required by applicable law, including for trust and safety purposes, or based on customer request or account settings. In the context of data retention and processing, “trust and safety purposes” refers to measures taken to protect the safety and integrity of a service and its users. This involves retaining certain data for a period of time to help prevent abuse and misuse. Additional information on Zoom’s Trust and Safety processes may be found in Zoom's Safety Center. In addition, certain content may be stored in accordance with the customer’s retention settings or policies, as described under “Customer Data Storage and Retention” and in the tables below.
If the AI Companion feature relies on a third-party artificial intelligence model, pursuant to Zoom’s contracts, the third-party model provider may retain the content used to provide the service for trust and safety purposes, within the U.S., for up to 30 days, unless a longer retention period is required by applicable law.
*IMPORTANT NOTE: Zoom offers a Zero Data Retention option with respect to Zoom’s retention of the temporary transcript, screen shared content via OCR, and in-meeting chat messages used to provide a Meeting Summary. When enabled, these inputs will be deleted by Zoom immediately after the summary is created. If a summary fails to be created these inputs will be retained for up to 24 hours to allow for retries. To enable this feature please reach out to your account team or log a support ticket.
Customers may choose Zoom’s storage location for some of the AI Companion outputs for their account. These settings differ based on the feature in use, and many align with existing retention policies of the related Zoom product.
AI Companion features are subject to limitations in certain regions that are not supported by our third-party model providers, as well as for customers in specific industry verticals. For customers with accounts specifically provisioned and hosted in a region outside of the US, supported AI Companion features are made available using ZM+ or ZMO. For customers hosted in the EU, Zoom uses ZM+ to support account data residency preferences (available features indicate EU processing in the “AI Companion Features” section of the whitepaper). Customers that prefer to use ZMO can reach out to their account team or log a support ticket. Meanwhile, customers hosted in regions beyond the U.S. or the EU, can access available AI Companion features through ZMO. Furthermore, if the underlying product is not available in a particular region, related AI Companion features will not be available.
The AI Companion for Financial Services Best Practice & Use Case Guide provides financial services organizations with industry-specific implementation strategies, regulatory compliance guidance, and practical use cases for deploying AI Companion within highly regulated banking and financial environments.
The Zoom Privacy Statement provides transparent disclosure of personal data collection practices, processing purposes, retention policies, and user rights across Zoom products and services, enabling customers to understand how their information is handled throughout the platform ecosystem.
The Zoom Third-Party Processors & Zoom Affiliates documentation details subprocessors, third-party service providers, and affiliate organizations that may access customer data during service delivery, providing complete transparency for compliance teams conducting vendor risk assessments and due diligence processes.
The Legal and Compliance Guide to AI Companion delivers practical implementation strategies for decision-makers, covering data governance requirements, privacy configuration options, regulatory compliance considerations, and organizational policy frameworks necessary for deploying AI Companion within complex legal and compliance environments.




















Refer to Zoom’s support center for more information on using Sentiment Analysis with AI Companion.
Zoom Contact Center’s Agent Talk Metrics feature provides real-time insights into an agent’s speaking speed and speech length during engagements. By analyzing conversation patterns, it helps agents recognize when they may be speaking too quickly or for too long, allowing them to adjust their approach for a better customer experience.
This feature is particularly useful for customer service teams focused on improving communication quality, helping ensure conversations remain clear, engaging, and balanced to enhance overall customer interactions.
Benchmarks for these analytics are as follows:
Too Slow
Good
Too Fast
Talk Speed(Words Per Minute)
1-110
110-160
160+
Positive
Negative
Speech Length(Time)
< 2:30
> 2:30
Refer to Zoom’s support center for more information on using Agent Talk Metrics with AI Companion.
When Zoom Contact Center’s Conversation Summary feature is enabled, agents can preview a summary of the consumer’s previous conversation when receiving a transferred engagement either from a virtual agent or another contact center agent.
For example, the following image displays a transfer from a virtual agent to a live agent for assistance and includes a brief, AI-generated summary of the user’s conversation with the virtual agent.
Alternatively, the following image provides an example of the AI-generated summary when preparing to transfer an engagement to another agent.
Refer to Zoom’s support center for more information on viewing engagement summaries.
Zoom Contact Center’s AI-Generated Follow-Up Tasks feature helps agents stay organized by automatically identifying and suggesting follow-up actions based on conversation details. If a consumer raises an issue and the agent agrees to take action, AI Companion generates a suggested task so it can be addressed.
Refer to Zoom’s support center for more information on using Follow-Up Tasks with AI Companion.
Zoom Contact Center’s Smart Responses feature helps agents refine their messaging by providing AI-generated suggestions for copyediting, rephrasing, and tone adjustments. This helps ensure agent responses remain professional, clear, and aligned with company communication standards.
Refer to Zoom’s support center for more information on using smart responses with AI Companion.

when a tool was pre-approved
which users installed the tool and when
which users have uninstalled the tool and when
API calls made by users on the account
Log in to marketplace.zoom.us as an administrator. Click Manage in the upper right corner of the screen and then click Apps on Account within the Admin App Management menu to see the list of automated meeting tools added to your organization’s account. Logs and management options for each tool can be accessed here:
Administrators of multi-user managed accounts have the ability to pre-approve or restrict certain automated meeting tools. Your account type may impact whether or not admin pre-approval is required. The ability to use certain tools may or may not be automatically enabled and visible in the meeting client depending on your account type, as well.
Log in to marketplace.zoom.us as an administrator and click Manage in the upper right corner of the screen, then go to the Admin App Management section of the menu. Click Permissions to manage the approval of automated meeting tools. Click Notifications to manage how your admins are notified of requests, and also manage how users are notified of approvals.
The Active App Notifier Report allows admins to see and manage the automated meeting tools that have accessed all account users’ meeting content during the past 30 days. This gives admins the opportunity to make informed decisions about whether they want to approve the use of these tools in their meetings and webinars. Admins can also use the report to easily view the App Marketplace page for each active tool to learn more about it and disable it if needed.
To view the Active App Notifier Report, log in to marketplace.zoom.us as an administrator. Click Manage in the upper right corner of the screen and then click Apps on Account within the Admin App Management menu to see a list of automated meeting tools added to your organization’s account.
The Active Apps Notifier Report will appear in the lower-right corner of the screen and will list the tools that have accessed meeting or webinar content on your account in the past 30 days.
There are several administrative settings shared later in this document that can be enabled on your account to manage automated meeting tools, along with dial-in users or third-party room devices. These account-level settings help to ensure that the automated meeting tools joining your meetings are authorized according to your organization’s meeting security policy.
Establish an automated meeting tools policy within your organization that outlines how they may or may not be utilized on your account. Specify which tools are approved for use and configure your account settings according to your organization’s best practices.
By suspending participant activities in a meeting, hosts can stop meeting activity and take action regarding any uninvited or disruptive participants that have joined. This may include managing or removing uninvited automated meeting tools, dial-in users, or third-party room devices.
During your meeting, click the Security icon and select Suspend Participant Activities to temporarily halt all in-meeting video, audio, screen or whiteboard sharing, chat, access to files shared in the meeting, and recording, and close any active Breakout Rooms. This prompt gives you the option to report the issue to Zoom’s Trust & Safety team and confirm your choice to suspend activity.
You can resume the meeting by re-enabling the suspended features individually from the Security menu.
A host can remove disruptive or uninvited participants or automated meeting tools from their meeting.
This can be done by clicking the Security icon in the Zoom Meeting window and then clicking Remove Participant. You can then select the participant to be removed from the meeting. You can also report the user to Zoom’s Trust & Safety team. The removed participant cannot rejoin the meeting.
You can also report participants for inappropriate behavior during meetings. This may include uninvited automated meeting tools, dial-in users, third-party room devices, or users joining from the Zoom meeting client or mobile app, or a Zoom Room.
Report a meeting participant engaging in inappropriate behavior by clicking the blue menu button in the upper right corner of the participant’s video thumbnail and then clicking Report… in the menu.
You can include a screenshot if necessary and use the dropdown menu to provide a reason why you are reporting the participant. This report is automatically sent to the Zoom Trust & Safety team, which will determine whether any misuse of the platform occurred and block the user if necessary. The user(s) will be removed from your meeting once the report is submitted.
Hosts and participants can use the following in-meeting tools to see when an automated meeting tool has joined a meeting. This gives users the ability to confirm that the tool has been initiated by one of the meeting attendees. Hosts can also remove and report an automated meeting tool if they are unable to positively identify the participant who manages it or feel that the tool should not be in the meeting or webinar.
The Active Apps Notifier is an in-meeting tool that notifies the host and participants that an automated meeting tool has joined a meeting and also indicates what kind of data the tool is accessing. An automated meeting tool can also be identified in the Participants list and the Waiting Room (if enabled for the meeting).
Look at the name of the automated meeting tool attending the meeting to confirm that it is owned by one of the meeting participants. Evaluate whether it is appropriate for the tool to record meeting content in that meeting. You can suspend all participant activity if you are unsure if the automated meeting tool should be in your meeting to help keep your meeting content secure.
You may wish to remove an automated meeting tool from a meeting if it is not claimed by a participant or if you do not want the content of that meeting to be recorded. You can also report the tool if it appears to be uninvited. All reports are delivered to Zoom’s Trust & Safety team for review.
On its own, a ZPLS module provides survivability to users within a common Zoom Phone Site. However, multiple ZPLS modules connected through a local, campus, or wide-area network can support cross-Site communication, connecting users from different Sites during a survivability event so long as the internal network remains operational.
Customers can integrate the ZPLS module with a session border controller (SBC) for external public switched telephone network (PSTN) connectivity when Zoom data centers are unreachable. This allows users with PSTN numbers provided by Zoom or third-party BYOC carriers to receive inbound calls from external parties when call forwarding for survivability is enabled in the cloud, and to place external phone calls regardless of local network conditions or Zoom data center availability.
ZPLS modules support Survivability Distribution Groups (SDGs) for nuanced call-routing configurations during a survivability event. With SDGs, a business can route internal and inbound PSTN calls to an individual user, a group of users (similar to a Call Queue or shared group), an IVR menu, another phone number, or, if necessary, another SDG.
Although SDGs do not provide the same full-featured functionality as standard-operation Call Queues, shared line groups, or Auto Receptionists, SDGs can continue to support a business’ critical call routing needs until normal operations are restored.
The following diagram demonstrates the network ports and data flows used with a ZPLS module and an SBC configuration.
Refer to Zoom’s support center for more information on Zoom Phone Local Survivability.
As AI becomes a deeper part of daily workflows, businesses need solutions that reflect their unique processes, language, and goals. Rather than relying on one-size-fits-all models, Zoom’s Custom AI Companion empowers organizations to expand on Zoom AI Companion’s core capabilities, and tailor its knowledge to fit their specific needs—delivering more relevant insights, smarter automation, and stronger alignment with the way they work.
Custom AI Companion gives businesses tools to tailor their employees' AI Companion experiences to their unique workflows and content. These features are briefly highlighted below, with more exhaustive descriptions further within the document.
With Custom Meeting Summary Templates, businesses can create custom post-meeting summaries that align with your organization’s specific style, priorities, and format through customizable templates and prompts.
Custom Dictionary enables AI Companion to recognize and better transcribe unique terms, including company-specific names, industry terminology, and specialized vocabulary. This helps meeting summaries and transcripts reflect the unique language, names, and terms essential to your business operations and industry context.
With Custom Avatars, users can create AI-generated video clips using pre-set avatar personas, or create a custom avatar that reflects their likeness. Once created, users can create videos by uploading a transcript in any supported language and watch the avatar come to life.
Knowledge Bases allow organizations to enhance Zoom AI Companion responses with trusted, organization-specific content—such as internal documentation, knowledge bases, or indexed data sources—so that responses are grounded in the context of the business. By integrating these Knowledge Bases, AI Companion can deliver more relevant and tailored answers.
With Third-Party Applications, Zoom AI Companion can interface with external applications to perform skillful actions within those systems, acting as an extension of the user across platforms. Rather than simply surfacing information, AI Companion can now drive execution—helping to initiate tasks, update records, and follow through on next steps—all without requiring the user to leave their current workflow.
AI Companion for Third-Party Meetings extends Zoom AI Companion’s meeting summary capabilities to meetings hosted on other platforms, such as Microsoft Teams or Google Meet. This allows users to benefit from consistent, high-quality meeting summaries across their entire calendar, when meeting on a supported third-party platform.
Zoom Custom AI Companion is available as a per-user licensed add-on, meaning organizations can assign this license on a user by user basis. Those with the license will gain access to Custom AI Companion’s features, while paid license users without the add-on will continue to have access to AI Companion’s standard features.
Zoom AI Studio serves as the dedicated configuration hub within the Zoom web portal where account administrators can access Custom AI Companion settings and tailor the AI experience to align with their organization's specific requirements. Within AI Studio, admins can create a custom dictionary to refine outputs, upload Knowledge Bases for better contextual awareness, and create custom meeting summary templates.
While all users with Custom AI Companion licenses may benefit from the enhanced AI capabilities, AI Studio serves as the primary environment where account administrators—not end users—configure customizable features. Once the customizations are published, licensed users will have access to Custom AI Companion features consistent with admin permissioning.
Note
Zoom Phone currently exclusively offers mobile-classified numbers for SMS support within Australia and the United Kingdom. All other Zoom Phone numbers offered are classified as VoIP numbers.
Zoom Phone does not offer or support dialing with virtual phone numbers. Further, customers cannot port-in virtual numbers, as any number ported into Zoom Phone must meet certain requirements.
Due to the nature of wireless connectivity, factors such as signal interference, coverage limitations, and bandwidth fluctuations can introduce quality issues, leading to potential disruptions or degradation in communication reliability and clarity. For this reason, businesses that are heavily reliant on Wi-Fi connectivity are encouraged to conduct wireless site surveys, as this can help ensure that wireless access points and antennas are optimized for your facilities, reducing the likelihood of quality-related problems.
Because Zoom Phone is a VoIP telephony provider, devices require internet connectivity to make and receive phone calls. Consequently, in the event of an emergency, including the loss of power or local internet, analog telephony adapter-enabled devices may be unable to make outbound calls.
To account for these scenarios, businesses are encouraged to have alternative telephony services for emergency resources—like security, fire, and elevator lines—through an analog telephone line or 4G/5G connectivity from a mobile device.
Zoom Phone Native phone numbers and numbers ported into Zoom Phone are not dynamically transferable between accounts, including sub-accounts. For accounts that require transitioning phone numbers between sub accounts, refer to Zoom’s support center for instructions on how to transfer phone numbers between accounts.
In some circumstances, forwarding calls to external numbers across the PSTN may result in additional charges at a metered call rate. This primarily happens when a Call Queue, Auto Receptionist, or user with a metered calling plan forwards a call to an external number, like an after-hours, third-party contact center or a personal cell phone. In these circumstances, the account will incur charges for the duration of the forwarded call.
Users and Zoom Phone admins must agree to the potential charges before saving any PSTN-forwarding capable configuration; however, account admins can restrict this setting ahead of time, including removing this capability altogether.
Start meeting from contact card*
Start chat from contact card*
Start phone call from contact card*
Send SMS from contact card*
Refer to Zoom's support center for more information on enabling and disabling or using the Zoom Assistant.
Place a call
Receive a call
Dialpad
Contact lookup
Speed Dial
Record a call
Park Call
Transfer Call
Merge Call
Self-Mute
Open call history*
Open voicemail*
Call Queue visibility
Open Call Queue Team Chat*
Shared Line Appearance Visibility
Shared Line Group Visibility
To perform a Zoom Phone network connectivity test on the Zoom Workplace Windows desktop app, perform the following steps:\
Open the Zoom Workplace app on your desktop.
Press Ctrl+Alt+Shift+D to open the Network Diagnostics Tool (requires version 5.13.10 or higher).
Click the Phone Test option.
On the following screen, click Test.
The results will be displayed after completion.
To perform a Zoom Phone network connectivity test on the Zoom Workplace Mac desktop app, perform the following steps:
Open the Zoom Workplace app on your desktop.
Press Cmd+Option+Shift+D to open the Network Diagnostics Tool (requires version 5.13.10).
Click the Phone Test option.
On the following screen, click Test.
The results will be displayed after completion.
Users are encouraged to refer to Zoom’s support center for a list of frequently asked questions.
Users experiencing issues with Zoom Phone error codes or that require general troubleshooting support are encouraged to review Zoom’s support center for troubleshooting assistance. For other issues not found on the support center, feel free to open a ticket with Zoom support.





Zoom Phone supports the following AI Companion features that can simplify user workflows and help save time. These features are described in the following sections.
Zoom Phone’s Call Summary feature provides AI-generated post-call summaries that capture key details such as dates, names, discussion points, and action items. When enabled, the Zoom user who enabled the feature will receive an automatic summary within the Zoom Workplace app, allowing them to review essential information without manually taking notes.
This feature is particularly useful for sales teams, customer support agents, and professionals handling frequent calls, helping ensure important details are documented and easily accessible. Users can also edit, email, or share summaries as needed to streamline follow-ups and maintain clear communication.
Refer to Zoom’s support center for more information on with AI Companion.
Zoom Phone’s Voicemail Prioritization feature helps users manage voicemail more efficiently by automatically identifying and prioritizing messages that match a user’s predefined topics or intents. This helps ensure that critical or time-sensitive messages are surfaced first, allowing users to respond more quickly to high-priority communications.
This feature is especially beneficial for professionals who receive a high volume of voicemails, such as customer service representatives, sales teams, and executives, helping them focus on urgent matters without manually sorting through their inbox.
Refer to Zoom’s support center for more information on with AI Companion.
Zoom Phone’s Voicemail Task Suggestions feature helps users stay organized by analyzing voicemail content and automatically suggesting tasks based on key details. This allows users to quickly identify action items, making it easier to manage follow-ups and stay on track, especially when handling a high volume of messages.
This feature is particularly useful for professionals who rely on voicemail for client communications, such as sales representatives, customer support teams, and executives. By streamlining task management, it helps users respond efficiently and stay productive.
Refer to Zoom’s support center for more information on with AI Companion.
Zoom Phone’s Summarize Team SMS Threads feature allows Call Queue and Auto Receptionist members with the Power Pack add-on to generate AI summaries of Team SMS conversations. This helps users quickly understand ongoing discussions and craft appropriate responses without having to review entire message histories.
This feature is particularly useful when following up on lengthy SMS exchanges or transferring conversations to another agent, helping ensure seamless communication and continuity in customer support or team collaboration.
Refer to Zoom’s support center for more information on with AI Companion.
Users who complete a Zoom Phone call with AI Companion enabled can easily generate a Zoom doc containing a structured call summary once the call concludes. After each eligible call, users can press the Open summary in Docs button to create a document that automatically includes AI Companion–generated insights such as call summaries, next steps, and action items.
This capability removes the need for manual transcription or note-taking. The resulting document is titled “Call Summary with [User]” or “Call Summary with [Number]” when the contact is not recognized, enabling consistent organization across call records.
Refer to Zoom's support center for more information on Zoom docs.
When AI Companion is enabled during a Zoom Phone call, users can engage with it in real time to ask context-aware questions about the ongoing call or afterward about the completed conversation. AI Companion analyzes the live transcript to surface relevant details, allowing users to clarify or retrieve information without searching manually.
For example, if a caller mentions a specific date, time, or event detail, the user can simply ask, “When did they say the event is happening?”, and AI Companion will reference the transcript to provide a prompt, accurate response.
This capability enhances understanding during or after the call, helping users stay focused on the conversation while still capturing and recalling critical details with ease.
Refer to Zoom's support center for more information on with AI Companion.
The Phone tab in the Zoom Workplace app serves as the main location to utilize Zoom Phone for both mobile and desktop users. From the Phone tab, users can make and receive calls, view call history, access voicemail, view shared lines, and send SMS/MMS messages.
Zoom Recommendation
For a quick course on Zoom Phone, check out our Zoom Phone Overview on YouTube or our support center.
After opening the Phone tab, users can make outbound calls using the dialpad, searching by name or contact or typing in the phone number. When typing or searching by name, internal and external user contacts will automatically display and filter as the criteria narrows based on user input. Additionally, if a user is assigned more than one line—like they would with Call Delegation, a Shared Line Group, or Call Queue—they can select their outbound caller ID before making the call.
While a call is live, users can access a variety of call menu options, including:
Mute to silence the speaker's microphone.
Keypad for pressing menu options or using DTMF tones.
Audio to select or adjust speaker and microphone settings.
From the History tab, users can review their recent call history, including the ability to filter their history by several criteria, including missed calls, recorded calls, or calls from a specific line.
From the Voicemail tab, users can access their voicemail and videomail messages, including the ability to filter their messages marked as read, for follow up, or messages received on a specific line.
Additionally, when viewing a message, users can see transcriptions, AI-generated tasks (if enabled), and other general call information.
From the Lines tab, users can see shared phone lines they have access to, such as phone numbers associated with Call Delegation or a Shared Line Group.
From the SMS tab, users with a sufficient can send and receive text messages to individuals or up to 10 numbers at once. Users with a Zoom Phone Power Pack add-on can also send text messages from a Call Queues' or Auto Receptionist's phone number if .
Refer to Zoom's support center for more information on .
Zoom's Live Transcription feature serves as a core technology that enables many features of Zoom's comprehensive suite of AI workplace solutions, including many features of AI Companion. By converting real-time audio into structured, searchable text data, Live Transcription creates the foundational layer that powers intelligent meeting summaries, automated action item extraction, sentiment analysis, and advanced collaboration workflows across the entire Zoom Workplace ecosystem.
When Live Transcription is enabled, live audio from sessions such as meetings, webinars, or phone calls is transmitted into Zoom's automatic speech recognition service, which converts the speech-to-text and distributes the dynamic transcript to applicable participants' Zoom Workplace apps. Participants can view the transcript in real-time, access segments through closed captioning, or leverage AI Companion to ask live, in-meeting questions. After the session ends, if the transcript is retained, it can be utilized further by AI Companion for transcript-dependent features like Meeting Summaries, post-meeting queries, and context-aware follow-ups, etc.
Live Transcription operates independently of large language models, relying instead on Zoom's automatic speech recognition technology to convert audio to text. However, the structured text output generated by Live Transcription serves as critical input data for large language models that power AI Companion's advanced features, enabling these models to analyze conversation content and generate intelligent insights.
Refer to Zoom’s Support Center for more information on how Live Transcription powers features like AI Companion’s and , as well as non-AI Companion features such as .
As of Zoom Workplace app version 6.5.3, users can now access local, on-device live transcription that processes audio directly on their device, instead of using cloud-based processing. While this option is designed to provide enhanced privacy and reduced latency, transcripts generated through local processing cannot be utilized by AI Companion features, which require cloud-based transcript data to function.
Zoom's Live Translation feature operates as an extension of the Live Transcription feature, where the original live transcript serves as the foundation for the translation process. The live transcript data is transmitted from the Live Transcription module to Zoom's live translation module, which processes the transcript in the detected source language and translates it into the user-requested target language(s). The translated transcripts are then returned to the live transcription service, which distributes the localized content to meeting participants through their Zoom Workplace apps, enabling real-time multilingual communication without interrupting the natural flow of conversation.
Refer to Zoom’s support center for more information on .
Personal Audio Isolation leverages a user’s voiceprint to differentiate their voice and suppress background noise, even in open environments. Users authorize Zoom to create a voiceprint, which captures the unique characteristics and nuances of their voice patterns. The user can also choose to upload a recording of their voice. The user’s voiceprint enables Zoom to intelligently filter and isolate the user's voice from ambient background audio detected by their microphone. The technology effectively suppresses environmental sounds such as coffee shop chatter, vacuum cleaners, barking dogs, or conversations from other people within microphone range, helping ensure that only the user's voice is prominently transmitted.
Refer to Zoom’s support center for more information on .
The following sections describe Zoom AI Companion features and functionality integrated with the Zoom Mail Client.
Zoom’s Email Compose feature helps users draft emails more efficiently by providing AI-generated suggestions. Users can input a draft or prompt, and AI Companion generates contextually relevant content based on the email thread or specific user inputs. This feature allows users to create emails quickly, while helping ensure their responses align with the conversation’s tone and context.
Using this feature, users can streamline the email composition process, helping to save time and improve productivity. This feature is especially helpful when responding to existing threads or crafting new messages, as AI Companion’s suggestions help maintain clarity and consistency in communication.
For example, the following image demonstrates a prompt and output to thank Paxton for his work in launching a customer loyalty program.
In addition to generating initial emails, AI Companion’s Email Compose feature can also generate a response to received emails. In this context, users do not write a prompt, instead, they click the AI Companion logo in the response, and AI Companion automatically generates a reply based on the message’s content.
For example, if replying to an email, clicking the AI Companion icon within the email reply box can automatically generate a contextually-relevant reply, saving the user time.
Refer to Zoom’s support center for more information on with AI Companion.
AI Companion can generate concise summaries of emails directly within the Zoom Workplace app, helping users quickly understand the main points of long or complex messages. When viewing an email, users can select AI Companion’s Summarize button to open the AI Companion panel alongside the message.
Once executed, AI Companion automatically analyzes the email and produces a clear, structured summary within the panel—highlighting key details, decisions, and next steps. This allows users to grasp the essential context at a glance without reading the full message or switching between applications.
Artificial Intelligence is rapidly evolving and becoming an integral part of everyday life, powering everything from large and small language models to specialized algorithmic functions. While generative AI enables seamless interaction between humans and machines for content creation, problem-solving, and decision-making, AI also exists in more specialized applications. Automation tools streamline workflows, while services like transcription and translation break down communication barriers, making collaboration more efficient and accessible. As AI continues to advance, its applications are transforming industries by enhancing efficiency, accuracy, and innovation, fundamentally reshaping the way businesses operate.
Given AI’s expanding role in the modern workplace, the AI Bluepaper serves as a detailed guide to AI features within the Zoom platform. By exploring some of Zoom’s key AI deployments, functions, and capabilities, it provides businesses with the insights needed to harness AI effectively—helping streamline workflows, enhance collaboration, and drive greater productivity across teams.
Your Personal Assistant for the Workday
The Zoom AI Companion Panel is a seamless, AI assistant directly into the Zoom Workplace desktop app, designed to support users throughout their workday by helping them stay organized, informed, and efficient. Whether scheduling meetings, preparing for discussions, retrieving key information, or crafting follow-up messages, the Companion Panel acts as a centralized hub for AI-driven productivity.
To provide meaningful examples of the capabilities of the AI Companion Panel, most examples in the following sections follow a user coordinating the launch of a loyalty program sign-up for the grand opening of an eco-friendly luxury clothing store.
Refer to Zoom’s support center for more information on within the Zoom Workplace app. For information on the dataflows for these features, refer to the AI Companion Diagrams and Dataflows page.
This document provides an overview and introduction to the Zoom Mail and Zoom Calendar Clients, not to be confused with the Zoom Mail and Calendar Services. The Zoom Mail and Calendar Clients specifically refer to the in-client user interfaces for managing a user’s email and calendars, and does not apply to Zoom’s calendaring and email infrastructure or service.
The Zoom Mail and Calendar Clients bring supported email and calendar accounts into Zoom Workplace desktop and mobile apps.
Zoom Phone supports various integrations for enhanced functionality and user workflow efficiency. Although the following list is not exhaustive, some of Zoom Phone's most popular integrations are briefly outlined in the following sections.
Integrating provides Zoom Phone users with seamless communication and collaboration natively within the Salesforce environment.
This integration empowers administrators to automate the logging of call activities and details into Salesforce records, providing a comprehensive view of interactions and contact touchpoints. Additionally, users can initiate Zoom Phone calls within the Salesforce application, using features like click-to-dial, call pop-ups, and access to recent call history. Taken holistically, this integration reduces the need for context switching between programs, enhancing user workflows and productivity.
Zoom’s Professional Services Organization (PSO) and certified channel partners offer businesses assistance with transitioning to Zoom solutions, including Zoom Phone. These groups can help businesses assess their transitional needs, develop and implement deployment plans, and provide on-site technical services during the Go-Live process.
With multiple tiers of service available, Zoom’s PSO team can help transitioning Zoom Phone customers with the following services:
This document is designed to provide readers with a comprehensive understanding of Zoom Phone's number porting capabilities across all supported regions. Number porting allows you to move your existing numbers from your current provider to Zoom Phone or Contact Center, maintaining the numbers your customers already know while transitioning to Zoom's cloud-based telephony platform.
Understanding the porting process is essential for maintaining business continuity while transitioning to Zoom's platform. Each region has distinct requirements, documentation needs, and activation windows that must be followed precisely to ensure successful number transfers. This guide covers the porting process across North America, Latin America, EMEA, and APAC regions, along with post-porting number management and troubleshooting common issues that may arise during the process.
Need assistance? Visit our for porting activation times, timeframes, and solutions to common issues.
The following security features allow meeting hosts to view and manage the participants that have joined or are attempting to join a meeting. These participants may be joining as automated meeting tools or dial-in users, or via third-party room devices, Zoom Rooms, or the Zoom client. Unlike apps using Zoom Realtime Media Streams, third-party automated meeting tools that join as participants will also be visible in the following security features.
is a virtual staging area that stops participants from joining a meeting until you, the meeting host, are ready to start the meeting. Waiting Room is an effective way to screen who is trying to enter your meeting and keep uninvited automated meeting tools, dial-in users, or third-party room systems out. Uninvited participants can be identified in the Waiting Room and removed before they join the meeting.
The Waiting Room can be viewed by clicking the Participants icon while in a Zoom Meeting. This list will show which participants are in the Waiting Room and which participants have been admitted to the meeting. The host or co-host(s) can admit users one by one or click
























Group Call Pickup
Call Queue Opt-In/Out
Add Call to add another user to the call.
Hold to place the call on hold.
Transfer to send the call to another user.
Warm Transfer to speak to the new user before transferring.
Direct Transfer to transfer without speaking to the new user.
Transfer to Voicemail to send directly to the user's voicemail.
Record to record the call.
Summarize to enable AI Companion's Call Summary feature.
Meet to elevate the call to a Zoom Meeting.
More (...) to access additional features and information not shown, including:
Call Park
End-to-End Encryption
Share Call Details


Agentic AI refers to artificial intelligence designed to do more than just answer questions—it’s built to take action on a user’s behalf. As an AI-first open work platform built for human connection, Zoom is actively developing agentic AI capabilities to help users seamlessly move from information to execution.
Rather than stopping at suggestions or meeting summaries, the vision for agentic AI is to evolve into an autonomous assistant that can help users manage next steps, complete tasks, and keep workflows moving. As AI technology continues to improve, agentic AI will increasingly function as a personalized digital assistant—helping users stay organized, follow through on priorities, and reduce the manual effort of moving information between conversations, meetings, and work tools.
Zoom AI Companion is an intelligent, conversational, digital assistant at the core of the Zoom Workplace platform, designed to enhance productivity, streamline collaboration, and reduce employee workload—all at no additional cost for customers with select paid services assigned to their Zoom user accounts.
As AI tools become increasingly integrated into the modern workforce, they are no longer limited to performing specific tasks—like automating data entry, drafting emails, generating reports, or performing basic algorithmic functions. Rather, emerging AI tools represent a transformative shift, fundamentally changing the way we work. Zoom AI Companion goes beyond simple task automation; it can act as a true companion in a user’s daily work, capable of answering general knowledge questions, generating content, offering insights, summarizing documents, messages, voice messages, and meetings, assisting with decision making, and helping users achieve new goals or unlock higher levels of performance.
As an AI-first company, Zoom AI Companion is thoughtfully integrated across Zoom’s suite of products, including Zoom Meetings, Team Chat, Phone, Contact Center, Docs, Whiteboard, and more. As Zoom continues to innovate and expand its capabilities, so too will Zoom AI Companion, offering new features and functionalities. Below is a list of key features available today, showcasing how this AI assistant can help enhance every aspect of a user’s workday.
Current key features and functionalities include:
Category
Key Capabilities
Business Value
Centralized AI Workspace
Contextual query processing, smart scheduling, cross-platform data synthesis, AI-generated follow-ups.
Unified productivity hub with intelligent workflow automation.
Meeting Intelligence
In-meeting real-time assistance, automated documentation, smart recording analytics, preparation automation.
Enhanced meeting effectiveness from preparation to follow-through.
Communication Enhancement
Intelligent chat assistance, transcript analytics, email composition, predictive writing.
Accelerated communication quality across all channels.
Contact Center Optimization
Real-time sentiment analysis, conversation intelligence, performance analytics, smart responses.
Elevated customer experience with AI-driven insights.
Zoom AI Companion brings the value of agentic AI to life by helping users easily turn information into action. When AI Companion identifies follow-up tasks—whether from a meeting, a Contact Center interaction, or another insight identified by AI—it can automatically add those action items into Zoom Tasks for follow-up or assignment. This helps ensure that key next steps don’t get lost in a meeting summary or conversation recap. Instead, they become clear, trackable tasks that can move forward. By connecting insights directly to action, AI Companion helps users stay on top of priorities, manage responsibilities, and keep their workday moving without unnecessary friction.
Beyond the intelligent, conversational LLM capabilities of Zoom AI Companion, Zoom also utilizes other AI services (i.e., algorithms) across the platform. These services often operate seamlessly in the background, powering features like real-time voice transcription, live translation, personal audio suppression, and more.
Together, these features help create a cohesive, frictionless experience that can enhance both the quality and efficiency of every interaction on the Zoom platform. Current key AI-service features and functionalities include:
Transcription
Translation
Closed Captioning
Personal Audio Isolation
As part of its AI architecture, Zoom uses the Model Context Protocol (MCP)—an open standard that enables secure connections between models, tools, data sources, and workflows. MCP plays a key role in advancing agentic AI by replacing the need for one-off integrations that each company must build and maintain separately. Instead, it provides a shared, structured framework that exposes capabilities to AI models in a consistent way. This foundation allows AI systems to act more like intelligent agents—by not only answering questions, but also taking action directly within the systems users rely on. Zoom currently supports MCP as part of its Custom AI Companion add-on, enabling organizations to build custom agents that connect with their unique data sources and applications, automating routine workflows and delivering tailored, accurate responses based on teams' actual working content.
At its core, MCP is built on a client–server model. Think of the AI environment (like ChatGPT or Claude) like a client that wants to get work done, and external systems (like Jira, Confluence, or a database) as servers that publish what they can do. Each server provides a clear list of functions—like “search knowledge base” or “create task.” The AI client then decides, in the middle of a conversation, when and how to use those functions.
In other words, connecting AI with an MCP server is just like ordering at a restaurant. You (the AI) walk into a restaurant, receive a menu (a list of services or functions available via the MCP server), and you (the AI) tell it what you want, and it responds. There is no guesswork of what is or isn’t available—everything is provided in the menu up front.
The following sections provide additional details for how MCP works:
Any system can run an MCP server. That server acts as the “menu,” publishing a structured description of the actions it supports. For example, Jira might publish functions like “search issues” or “update ticket.” Because these functions follow MCP’s shared format, the AI can understand them immediately without custom engineering.
On the other side, the AI environment plays the role of the client. It reads the menu of available functions, remembers them, and decides which to call when responding to a user. This means the AI doesn’t need to be programmed ahead of time with thousands of possible integrations—it simply learns what’s available when the connection is made.
MCP also defines how context and permissions are passed along. This helps ensure that when the AI uses a function, it does so only within the boundaries of what the user is allowed to access. For example, if a user has permission to see only their team’s Jira tickets, MCP makes sure the AI respects that scope. This security layer is what makes MCP practical for enterprise use, where sensitive data and access controls are non-negotiable.
By standardizing how AI connects to external systems, MCP removes the friction of custom integrations and ensures safety and consistency. Users benefit because the AI can not only answer questions but also take informed actions across a variety of tools in a way that feels seamless and secure.
In addition to MCP, Zoom will also use the Agent-to-Agent (A2A) Protocol as a shared language for collaboration between autonomous agents. A2A is an open standard that allows AI agents—potentially built by different vendors or running in different environments—to discover each other, share context, delegate tasks, and exchange results securely. Zoom plans to support third-party AI agents with AI Companion by using A2A to pull in context from your Zoom conversations and take action across other business apps on your behalf. (Third-party agent for ServiceNow Now Assist coming soon.)
If the Model Context Protocol (MCP) connects AI models to the tools and data they need, A2A connects the agents to each other. Together, the two standards form the backbone of interoperable, multi-agent systems, where intelligence isn’t confined to one model but distributed across a network of cooperating agents.
At its core, A2A is built on the idea that each agent can act as both a client and a server. One agent may request help or delegate a task, while another may respond and execute that task. The communication between them follows a common structure and security model, so no matter who built the agents—or where they run—they can understand each other.
You can think of it like a team of specialists working together: each agent has a clear job, a résumé describing what it can do, and a shared way to hand off work to others.
The following sections describe this process step-by-step:
Step 1: Agents Publish Their Capabilities
Every A2A-compatible agent exposes a small, structured “Agent Card.” This card acts as the agent’s identity and capability profile—it lists what the agent can do (for example, “summarize text,” “schedule a meeting,” or “query data”), what formats it supports, and how it can be reached.
Because this card follows the A2A standard, any other agent can read it and immediately understand how to interact without needing custom code or configuration.
Step 2: Agents Discover and Connect
When one agent wants to collaborate, it looks up another agent’s Agent Card—often through a directory, registry, or a well-known endpoint—and establishes a secure connection. This process allows agents to find each other dynamically, even if they were built by different teams or organizations.
Discovery ensures flexibility: a task-planning agent can find a visualization agent, or a customer-support agent can locate a translation agent, all through standard discovery mechanisms.
Step 3: Agents Exchange Tasks and Results
Once connected, agents communicate through standardized task messages. A task message might include a request (“analyze this data set”) and a response (“here are the insights”). These exchanges can happen synchronously for quick operations or asynchronously for longer-running tasks.
A2A also supports streaming and notifications, so agents can send intermediate updates or partial results as they work—mirroring how humans might collaborate in real time.
Step 4: Secure Collaboration and Context Sharing
Each interaction between agents is authenticated and scoped by the user or system that initiated it, ensuring agents only access the data or capabilities they’re authorized to use.
This controlled exchange of context allows complex workflows—like one agent summarizing a document while another creates a follow-up action—without leaking information.
Why A2A Matters
By defining a universal way for agents to talk to each other, A2A unlocks a new layer of interoperability and composability. Instead of building massive, monolithic agents that try to do everything, A2A empowers organizations to design specialized agents—each focused on a specific domain—and have them collaborate through a shared protocol.
For enterprises, this means:
Cross-vendor compatibility: Agents from different providers can interoperate securely.
Scalable design: Teams can add or replace agents without re-architecting entire systems.
Governed automation: Security, observability, and auditing are standardized from the start.
Faster innovation: New capabilities can be introduced simply by publishing a new Agent Card—no rewiring of existing integrations.
For example, when viewing Zoom Team Chat, the AI Companion Panel will present suggested prompts specifically related to team communication or message summaries, while looking at the Phone or Meetings tabs, it may offer hero prompts for summarizing previous meetings, preparing for upcoming sessions, or optimizing call workflows.
Beyond initial prompt suggestions, this contextual intelligence helps refine the scope of your queries, helping ensure that when you ask a question while viewing Team Chat, AI Companion is more likely to prioritize search functions and responses related to team messaging, thread management, and collaborative communication rather than pulling from unrelated Zoom features. This targeted approach helps eliminate the need for users to manually specify their current workspace context, delivering more precise and actionable assistance that directly supports their immediate workflow needs.
Users can ask AI Companion broad or specific questions about almost anything, such as “Tell me about _____” or “What does the term ______ mean?” For users in specialized fields, they can ask more precise questions, like “What do researchers say are the top cybersecurity threats in the last five months?
When used this way, AI Companion can provide definitions, explanations, and contextual insights by leveraging its built-in knowledge or conducting a web-based search powered by Perplexity AI. This helps users receive accurate, well-sourced answers without leaving the Zoom platform.
When prompted by a user, the AI Companion Panel streamlines meeting coordination by automatically searching a colleague's calendar to find and schedule a time that works for both parties. By eliminating the back-and-forth of manual scheduling, this feature helps ensure users can quickly secure a meeting slot without leaving the Zoom Workplace desktop app—and when calendar access is limited, it seamlessly adapts by sending calendar invitations instead.
AI Companion synthesizes data from various sources—including chat messages, emails, and past meetings—to provide users with personalized summaries, key discussion points, tasks, and relevant context before a meeting. This helps users to walk into discussions prepared with the necessary insights at their fingertips.
Leveraging insights from meeting preparation, AI Companion can generate structured agendas, helping ensure all attendees are aligned on discussion topics. This feature helps meetings stay focused and productive by clearly outlining key points and objectives ahead of time.
After meetings end, users can query AI Companion to quickly surface key details from the discussion. Ask questions like "Who were the five vendors mentioned?" or "What action items were assigned?" and receive instant, sourced responses drawn directly from the meeting transcript.
Using meeting transcripts as source material, AI Companion crafts tailored follow-up communications that reflect actual discussion points and outcomes. From supervisor updates to colleague recaps to appreciation messages, AI Companion helps users craft messages that are professionally polished.
For busy users navigating active chat channels, AI Companion can summarize recent messages or help locate specific conversation points they may not clearly remember. This saves time and helps ensure critical information is not overlooked.
AI Companion allows users to upload datasets—such as survey results, reports, or spreadsheets—and quickly generate summaries of key findings. By analyzing patterns, trends, and notable insights, AI Companion helps users extract meaningful conclusions, saving time on manual review and assisting with data-driven decision-making.
Users can ask AI Companion for guidance on crafting more effective prompts and queries. By requesting help with phrasing or structure—such as asking "How can I get better results from this question?"—users receive tailored suggestions that improve their interactions and lead to more precise, actionable AI responses.
AI Companion for Third-Party Meetings lets users can bring AI Companion to third-party meetings hosted on Microsoft Teams or Google Meet. With this feature, users can still receive post-meeting summaries and transcripts, creating a unified, cross-platform AI experience. This eliminates the need for users to switch between tools and enjoy the same AI-driven features regardless of the meeting platform.\
Users can integrate their Gmail or Microsoft 365 accounts for work and school with native calendar and email access within the Zoom Workplace app. Zoom Mail Service users automatically use the Zoom Workplace app as an email and calendar client. Information on third-party integration, authorization, and access is described below.
Users with a completed Zoom Mail and Calendar integration can access both their email account and calendars within the Zoom Workplace app, streamlining workflow and reducing dependencies on separate email applications or browsers.
Users with the Zoom Mail Client integration can access core email features and functionalities, including but not limited to an inbox, outbox, drafts, sent messages, archiving, searching, rules (filters), starring, custom labels, vacation messages, and signatures.
Users have full access to their calendars, including shared and resource calendars, within the Zoom Workplace app. This includes the ability to schedule, update, or delete calendar events for any calendars they have access and are privileged to.
Authorized delegates with scheduling privilege to a user’s calendar within their calendaring provider and in Zoom can schedule meetings directly to the user’s calendar on behalf of the user. Meetings scheduled this way are automatically scheduled under the calendar owner’s Zoom account, but can be manually scheduled under the delegate’s account if desired.
Users with the Zoom Mail and Calendar Client integrations can simplify and consolidate workflows within the Zoom Workplace app. The following features are available to users with both integrations:
Integrated scheduling (see invitee availability)
Share emails to Zoom Team Chat
Attach cloud recordings to a calendar invite
Schedule using a Zoom phone number
Starting a chat with event participants
See who has joined Zoom meeting in sidebar
Integrate Zoom contact card with mail and calendar
Zoom Mail and Calendar Clients are automatically disabled for all Zoom Business, Enterprise, Education, and Healthcare (with a signed BAA) accounts. Account admins can enable this setting from the web under Account Settings. Refer to our support documentation for more information on enabling the Zoom Mail Client and Calendar Client.
Users can opt-in to one or both integrations for mail and calendar If both Zoom Mail and Calendar Clients are enabled on an account, Zoom will prompt users to integrate both services by default. Users can opt-out of one or both integrations by deselecting scope permissions to Mail or Calendar during the account integration process.
Admins can enable the Zoom Mail Client and Calendar Client on an account or group level Account admins or authorized users can enable the Zoom Mail Client and Calendar Client for the entire account or on a group level. Refer to our support documentation for more information on enabling the Zoom Mail Client and Calendar Client.
Zoom Workplace apps do not include client-level controls like MSI or GPO settings for Zoom Mail and Calendar Clients at product launch Zoom desktop and mobile clients will not include MSI or Group Policy (GPO) controls for limiting client access to the Zoom Mail and Zoom Calendar Clients. Account admins or authorized users can restrict access to these features exclusively from the web.
Zoom Mail and Calendar Clients are not available for Zoom for Government customers Zoom Mail and Calendar Clients are not available for Zoom for Government (FedRAMP) customers.
Users can integrate a maximum of one email account at a time within the client; however, users may access as many calendars as their email account is authorized to. Users with delegate access may still receive email notifications for new calendar events if subscribed.
Similar to Zoom’s existing calendar and contacts integration, the calendaring and mail integration uses additional application scopes for email and calendar reading and writing permissions. Zoom Workplace apps fetch calendaring and email data from Gmail, Microsoft 365, and Zoom Mail through REST API requests using OAuth 2.0 authentication.
No email or calendaring data from third-party integrations with the Zoom Mail and Calendar Clients is stored within Zoom Mail servers. All data is processed directly from the service provider to the user’s client.
User calendar events are stored in temporary memory (RAM) within the local machine. This data persists within the machine until it is cleared on client exit.
Data from the email-client integration is stored within an encrypted database on the user’s local machine. This data does not expire and is not removed from the machine unless the user is logged out of their email account within the Zoom Workplace app.
The Zoom Mail Client does not support third party add-ins or development features, such as integrated scheduling for alternative video conferencing providers. Users can only schedule Zoom Meetings within the Zoom Mail Client.
Zoom Phone supports two primary integrations with Microsoft Teams: Zoom's in-app integration for Microsoft Teams and Zoom Phone for Microsoft Teams.
Zoom's in-app integration for Microsoft Teams
Zoom's in-app integration for Microsoft Teams offers users easy access to core features for Zoom Meetings, Zoom Phone, and Zoom Whiteboard within the Teams client. With easy-to-access menus and interfaces that complement existing workflows, users can perform many tasks within the Teams client, with limited dependencies on the Zoom Workplace desktop app running in the background to execute some commands.
Core features of Zoom Phone with Zoom's in-app integration for Microsoft Teams include:
Place and receive calls*
Transfer/Forward Call
View Call History
Send and Receive SMS
Record call*
Access recorded calls and transcripts
Hold call
Access Voicemail
Read Voicemail Transcription
Zoom Phone for Microsoft Teams is a direct routing as a service (DRaaS) offering that provides businesses with a strategic collaboration option by integrating Zoom Phone's PSTN services directly into the Teams client and PBX. This allows users to make and receive calls directly through the Teams interface, while utilizing Zoom Phone's telephony infrastructure alongside your company's Teams PBX system.
This service offers businesses flexibility to not only streamline communication workflows within a common application, but additionally provides an option for business continuity and disaster recovery. By offering Zoom Phone’s telephony services natively within the app, without a supplemental application or integration, users can utilize one common workflow whether Zoom Phone is being used as a primary service provider, or a secondary provider for disaster-recovery scenarios.
Zoom's in-app integration for Slack lets Zoom Phone users place calls easily from within the Slack application. The following two Zoom Phone features are available:
Initiate a Zoom Phone Call: Type /zoom call [@contact or phone number] to call another Slack user or any phone number
Call a user from a Direct Message: After clicking the Call icon within a direct message, a user can select the Phone: Zoom option. This will directly call the user over Zoom Phone
The Zoom for Google Workspace add-on provides Zoom Phone users with convenient access to essential phone features within Gmail and Google Calendar. With the add-on, users can initiate Zoom Phone calls directly from either product, review recent call history, and access Google and Zoom contacts, with the option to conveniently call a contact, provided there is at least one phone number associated with their profile.
Similar to other integrations, the Zoom for Google Workspace add-on extends its features beyond Zoom Phone, with support for Zoom Meetings as well. To explore the full capabilities of both the Zoom Phone for Google Workspace integration and the comprehensive Google Workspace package, readers are encouraged to visit Zoom's support center for more information.
Architecture & Design
Use Case Analysis
Implementation Support & Strategy
Porting & BYOC Migration
Implementation Guidance
Data Review & Optimization
Network Readiness Review
Provisioning & Configuration
Hypercare: 10 Days of Post Go-live Support
\
Customers interested in retaining the Professional Services Organization are encouraged to refer to Zoom’s website for more information or speak with their Zoom account team.
Customers transitioning to Zoom Phone without assistance from third-party companies or Zoom’s Professional Services organization may benefit from a slower, transitional phased approach. This may include moving users over to Zoom Phone in a segmented or percentage-based approach, like moving users over one Site at a time, or moving 5% of their users in daily or weekly increments, depending on the quantity of users. Benefits of a phased approach include:\
Minimized Disruption: Gradually transitioning users minimizes disruption to daily operations. Users can adapt to Zoom Phone gradually, reducing the risk of productivity loss associated with sudden changes.
Risk Management: By phasing the migration, your business can identify and address any issues or challenges that arise in each phase before proceeding to the next. This proactive approach reduces the risk of encountering major problems across the organization.
User Adoption: Users are more likely to embrace the new system when they have time to adjust gradually. Training and support resources can be provided incrementally, so users feel comfortable with the new technology.
Resource Allocation: A phased approach allows organizations to allocate resources more efficiently. IT staff can focus on supporting a smaller group of users during each phase, so they receive adequate assistance and troubleshooting support.
Evaluation and Feedback: Each phase of the migration provides an opportunity to evaluate the performance of the new system and gather feedback from users. This feedback can inform adjustments and improvements as the migration progresses.
Flexibility: Phasing the migration provides flexibility to adapt the implementation plan based on real-world experiences and feedback. Organizations can make adjustments as needed to ensure a successful transition for all users.
Overall, a transitional phased approach to adopting Zoom Phone can help organizations manage risk, promote user adoption, and make a smooth transition to the new technology.
For customers with existing on-premises PBX systems, utilizing Zoom Phone’s Bring Your Own PBX (BYOP) service model can simplify the transitional period between on-premises and cloud-based users.
With the BYOP service model, customers connect their on-premises PBX with Zoom Phone’s cloud-based PBX through a set of configurable routing rules. Once this integration is configured, users can continue to dial users with consistent workflows, such as dialing their extension or numbers on speed dial. Due to the back-end routing rules connecting the on-premises PBX and Zoom Phone, when a user dials an extension, the relevant PBX will automatically query both the on-premises and Zoom Phone PBX for the user with the dialed extension and will connect the call accordingly if a user is found.
This service model is most commonly used as an intermediary step for customers transitioning from an on-premises system to one of the previously mentioned service models. Once all users have migrated from the on-premises system to Zoom Phone, the on-premises system can be safely decommissioned or put on standby.
The following example illustrates the benefits of this service model for a transitory period, while an account begins their full conversion process.
Example
The business “Omzo” is preparing to transition 100 users from their on-premises PBX system to Zoom Phone Native. They are currently configured for a Bring Your Own PBX service model to assist with the transition.
On Monday, Alice and Bob are both registered to the on-premises PBX. Alice can easily call Bob at his extension of 100.
On Tuesday, Bob is transitioned to Zoom Phone and keeps his extension number of 100, while Alice remains registered to the on-premises PBX. Because the on-premises PBX is connected to Zoom Phone, if Alice tries to call Bob at extension 100, the query will fail within the on-premises PBX, and failover to Zoom Phone’s PBX. Because Bob retained the same extension, Zoom Phone’s PBX will identify Bob at that extension and connect the call to him through the BYOP connection.
In this scenario, neither Bob nor Alice are required to be aware of the ongoing transition. Calls will continue to connect without an impact to the user experience because the on-premises PBX and Zoom Phone’s PBX are connected and all other factors remain the same.
This document is organized to provide information in a logical flow that makes understanding the porting process easier. Throughout this document, we have structured content in several ways:
Regional organization - Each geographic region (US/Canada, South and Latin America, EMEA, APAC) has dedicated sections with region-specific requirements and procedures.
Task-based sections - Content is organized by what you need to accomplish: Getting Started, regional porting processes, Managing Your Numbers, and Troubleshooting.
Statement-answer format - Common questions and issues are presented as statements describing your situation, followed by comprehensive answers and solutions.
For example, when you see "The address on my porting order doesn't match my current provider's records," you immediately know this section addresses your situation, and the answer provides the exact steps to resolve the issue. We've included detailed requirements, step-by-step procedures, and comprehensive troubleshooting guidance to give you the most complete information available. Links to relevant support articles are provided throughout to give you access to the most current instructions for each process.
Number Management admin permissions
Zoom Phone or Zoom Contact Center license
Completed the Zoom Phone initial setup
Your account number from your current carrier (if applicable)
If it is a wireless number, your 4-digit PIN (required for all wireless ports)
This is your current service provider — the carrier you pay for the numbers. The name of the losing provider must always be listed on your porting LOA.
A DID/DDI block is a set of sequential numbers, without any gaps or missing numbers. If the service phone provider has built your numbers as a DID/DDI block on their network, then they may only allow the numbers to be ported away as a DID/DDI block when you leave them.
A BYOC to native port allows you to move pre-existing BYOC numbers from BYOC to Zoom Phone.
Local or geographic numbers: Zoom can generally port local numbers in supported countries. The ability to port also depends on whether our porting partners maintain valid interconnect agreements (ICAs) with the local carrier of record.
Toll-free or non-geographic numbers: Zoom can typically port toll-free numbers in the U.S., Canada, and certain other regions, subject to carrier arrangements and local regulations.
For additional support or questions not covered in this guide, please contact the Zoom Porting team through the web portal or visit our support documentation.
While in a meeting with Waiting Room enabled, hosts will receive an on-screen notification banner when new participants have entered the Waiting Room.
You can configure your Waiting Room Options in the Zoom web portal to allow users from your account to bypass the Waiting Room. Entire domains can also be specified, which allows participants from these specified domains to bypass the Waiting Room, as well. By allowing users from trusted accounts and domains directly into the meeting, the host will have a smaller number of participants in the Waiting Room to review and admit.
Approved third-party room devices (SIP/H.323-based video conferencing systems) can also be pre-approved to bypass the Waiting Room. This setting is found in the Waiting Room Options section of the web portal. The list of approved third-party room devices within your account will bypass the Waiting Room when the Approved SIP/H.323 Devices checkbox is selected in the Waiting Room Options section.
The following pre-approval options allow third-party room devices to bypass the Waiting Room:
SIP/H.323 Rooms managed by Zoom Connector Managed devices will be pre-approved to bypass the Waiting Room.
SIP/H.323 devices by IP address Devices using the specified IP addresses, or addresses within the specified range, will be pre-approved when joining the Waiting Room.
SIP/H.323 devices with specific public certificates This allows the uploading of a certificate that will be used to verify if a device has been pre-approved.
Users on paid Zoom plans can log in to the Zoom web portal and customize the message and title of their Waiting Room. This area is a great spot to post rules, guidelines, or an agenda for your meeting. You can also add a logo, image, or video (within size limitations). These customizations help participants know that they are in the right meeting and what to expect for the session once they are admitted.
Waiting Room can be enabled proactively for an entire account or group by an administrator or account owner. Meeting hosts can choose to enable Waiting Room while scheduling individual meetings or enable it proactively within their personal settings in the Zoom web portal. Waiting Room can also be enabled during a live meeting to allow hosts to remove disruptive participants, which could include uninvited automated meeting tools, from the meeting.
The Identifying guests in the meeting/webinar setting allows you and participants who are users on your account to see that a guest is participating in a meeting or webinar. A guest is identified as someone who either is not signed in to a Zoom account or is signed in with an email address that is not on the same account as the host. With this setting enabled, uninvited automated meeting tools, dial-in users, or third-party room devices will be listed as guests.
Meeting guests will be identified with descriptive text in both the Waiting Room (if enabled) and the Participants list for the active meeting.
The Identifying guests in the meeting/webinar setting can be enabled by administrators at an account and group level, and also in individual user settings.
Active Apps Notifier is an in-meeting notification that informs users when a host or other participant is using an automated meeting tool that is accessing meeting or webinar content, such as real-time video, audio, screen or whiteboard sharing, chat, or files shared in the meeting. These notifications are designed to empower users to know that participants are sharing content with third-party apps and make informed decisions about if and how they participate in a Zoom session.
The Active Apps Notifier icon will appear in the top-right corner of the meeting window when an automated meeting tool begins accessing meeting or webinar content. A user can click the icon to show a list of automated meeting tools that are accessing content during that session, along with what type of content they have access to and which users are using them.
The meeting host may allow the automated meeting tool to stay in the meeting, or the host may remove and/or report it if the automated meeting tool is uninvited.
Zoom AI Companion can leverage both internal Zoom data and external third-party data sources to deliver more comprehensive assistance tailored to your complete work environment. By default, AI Companion draws from available Zoom data sources including meeting transcripts, Zoom Team Chat messages, and other platform-native content to generate contextually relevant responses. However, to unlock the full potential of personalized productivity assistance, some AI Companion features may require or allow for integration with third-party data sources ranging from simple email connectivity to more sophisticated data indexing capabilities.
When enabled by account administrators and connected by individual users, AI Companion can access and index content from Microsoft and Google ecosystems, including calendar events, emails, and documents, as "data sources." This integration utilizes a RAG (Retrieval-Augmented Generation) module within Zoom that indexes and stores third-party content, allowing AI Companion to search across your broader digital workspace when responding to prompts.
To maintain relevance and data freshness, Zoom stores only content that has been viewed or edited from third-party data sources within the last 90 days for authenticated users, helping ensure that AI Companion's responses reflect your most current and active work materials. This approach helps enable AI Companion to provide more comprehensive assistance by understanding not just your Zoom activities, but your complete workflow across integrated platforms.
Data Source Category
Content Types
Refer to Zoom’s support center for more information on configuring additional data sources for .
Jessica Park serves as Human Resources Manager at TechFlow Dynamics, a 750-person technology consulting firm with offices across North America. Jessica oversees talent acquisition, employee development, and compliance for a distributed workforce, managing 15+ interviews weekly, quarterly performance reviews for 200+ employees, and constantly evolving HR policies. She struggles with inconsistent documentation across employee interactions, spending 8+ hours weekly creating training materials in multiple languages, and maintaining compliance while scaling company culture across remote teams.
Now, with AI Companion and a Custom AI Companion license, Jessica can transform HR operations from administrative burden to strategic workforce development.
Inconsistent Documentation - Previously spent 45+ minutes per meeting creating detailed notes and follow-up action plans.
Multilingual Communication Barriers - Struggled with creating training content for diverse workforce speaking 12+ languages.
Policy Knowledge Fragmentation - Employees had difficulty finding current HR policies during critical moments.
Time-Intensive Content Creation
General Knowledge Queries - AI-assisted search results with synthesized guidance.
Email Compose - Intelligent draft generation for professional communications.
Meeting Preparation - Structured guidance for upcoming conversations.
Meeting Summary - Automatic capture and documentation of meeting discussions.
Knowledge Bases - Access to company-specific policies, procedures, and historical communications for contextual analysis
Custom Meeting Summary Templates - Standardized documentation formats for consistent onboarding and meeting records
Custom Avatars - Multilingual video creation featuring realistic personal likeness
7:00 AM - Strategic Morning Intelligence Gathering
Jessica begins her day by opening the AI Companion Panel within Zoom Workplace. She received an overnight email from an employee asking about promotion criteria and wants to provide a comprehensive response.
She asks AI Companion: "What are best practices for communicating promotion criteria to employees in tech companies?" Using General Knowledge Queries, AI Companion provides insights about transparent promotion frameworks, including specific strategies for technical career progression and examples of effective communication approaches.
Jessica then accesses her Knowledge Bases (Custom AI Companion add-on license required) containing the company's promotion policies and asks: "Based on our promotion policy document, how should I explain our criteria to a software developer who's been with the company for 18 months? Also, make reference to our mentorship program." After analyzing the documents, AI Companion provides a contextual response that offers a personalized explanation referencing specific policy sections while suggesting how to frame the conversation encouragingly for the employee's career stage, as well as available mentorship opportunities.
Jessica then opens the Email tab within Zoom Workplace to draft her response. She creates a new email and uses Email Compose, pasting AI Companion's previous analysis into the context field and prompting: "Using the following information as context, draft a professional email explaining our promotion criteria to a software developer, emphasizing growth opportunities and next steps, with an encouraging tone." AI Companion generates a well-structured email explaining the promotion process and mentorship program opportunities, including specific next steps and follow-up instructions for the employee.
9:00 AM - New Employee Onboarding Meeting
Jessica has a scheduled onboarding meeting with Sarah, a new QA engineer starting her second week. Before the meeting, she uses Meeting Preparation in the AI Companion Panel, asking: "Help me prepare for an onboarding check-in meeting with a new QA engineer in their second week - what key topics should I cover to ensure they're settling in well?" AI Companion provides guidance on typical onboarding discussion points, including team integration, role clarity, initial project feedback, and common second-week concerns for technical roles.
During the 30-minute meeting, Meeting Summary automatically captures the conversation as Jessica and Sarah discuss how her first week went, any challenges with the development environment setup, her initial impressions of the team dynamics, and questions about company processes and procedures.
After the meeting, because Jessica has a Custom AI Companion license, she applies her Custom Meeting Summary Template (Custom AI Companion add-on license required) designed specifically for onboarding check-ins. This template automatically organizes the conversation into structured sections: integration progress, technical setup status, team feedback, questions raised, follow-up actions needed, and escalation items—helping ensure consistent documentation across all new hire check-ins.
11:00 AM - Employee Policy Inquiry and Documentation
Jessica receives a complex question via team chat from the marketing department about remote work policies for employees with school-age children during summer break. The thread contains multiple perspectives and concerns from different team members.
Using Chat Summaries & Search, Jessica quickly reviews the thread to identify the core issues: requests for modified schedules, questions about productivity expectations, and concerns about meeting availability during summer months.
Jessica then opens Zoom Docs to create a comprehensive policy clarification document. Using Content Generation and Revision, she prompts: "Create a summer schedule flexibility policy that addresses remote work arrangements for parents, including productivity expectations and meeting availability guidelines." AI Companion generates a well-structured document outlining flexible scheduling options, core collaboration hours, and performance standards.
She then accesses her Knowledge Bases (Custom AI Companion add-on license required) containing existing HR policies and asks: "Review this draft against our current flexible work policies to ensure consistency and identify any gaps." AI Companion analyzes both documents and suggests revisions to align with existing company policies while addressing the specific summer scheduling concerns.
2:00 PM - Multilingual Training Content Creation
Jessica is preparing welcome videos for next month's new hires, including employees who primarily speak Spanish and Mandarin. She opens Zoom Clips and begins creating content using Custom Avatars (Custom AI Companion add-on license required).
She uploads a script that reads: "Welcome to TechFlow Dynamics! I'm Jessica from HR, and I'm excited to guide you through your first week. Our company values collaboration, innovation, and work-life balance. Let me walk you through what makes our team culture special and how we support your professional growth."
Using the Custom Avatar feature, Jessica generates personalized welcome videos in English, Spanish, and Mandarin (i.e., Traditional or Simplified Chinese)—each featuring a realistic version of herself speaking the appropriate language. This allows her to maintain a personal connection while scaling content across language barriers, eliminating the need for translation services, multilingual presenters, or multiple recording sessions.
Finally, Jessica benefits from the AI-Generated Titles, Descriptions, and Tags feature in Zoom Clips that automatically organizes these videos with relevant metadata like "HR Onboarding," "Multilingual Welcome," and "New Hire Resources," making them easily discoverable for future use.
4:00 PM - Employee Benefits Enrollment Communication
Jessica needs to communicate about the upcoming annual benefits enrollment period that opens next month. This affects all 750 employees and requires clear communication about new healthcare options, retirement plan updates, and enrollment deadlines.
She opens Zoom Docs and uses Content Generation and Revision to create the benefits enrollment announcement, prompting: "Create a company-wide announcement explaining our annual benefits enrollment period, including new healthcare plan options, retirement contribution changes, and key enrollment deadlines. Keep the tone informative but approachable." AI Companion generates a comprehensive document outlining the enrollment process and benefit changes.
Jessica then opens Zoom Team Chat and uses Chat Compose to draft messages for different department channels. She prompts: "Create a brief, engaging message for our sales team chat announcing the benefits enrollment period and directing them to the full enrollment guide." The AI helps her craft department-specific messages that address likely questions for each team.
Finally, Jessica accesses her Knowledge Bases (Custom AI Companion add-on license required) containing previous benefits enrollment communications and asks: "Review this announcement against our successful enrollment campaigns from previous years to ensure we're including all critical information and following best practices for benefits communication."
Conclusion - The Strategic Transformation
With AI Companion and Custom AI Companion capabilities, Jessica has fundamentally transformed her role from administrative burden to strategic workforce architect. What once required hours of manual documentation, research, and content creation now happens in minutes—her Custom Meeting Summary Templates help ensure consistent documentation across all employee interactions, while Custom Avatars enable authentic, multilingual communication that scales globally. Her Knowledge Bases provide instant access to company policies, documents, and wisdom, and AI content generation eliminates the repetitive work that previously consumed her days. Jessica can now spend more of her time on strategic workforce development and proactive employee engagement, rather than drowning in documentation and manual processes. The AI doesn't just make her faster—it makes her indispensable as a strategic HR leader who can scale personalized, consistent employee experiences across TechFlow Dynamics' growing, diverse workforce.
This section provides an overview of AI Companion’s Security and Privacy settings.
Account admins can redact certain personal data from a meeting summary using Zoom’s pre-defined entity types. Zoom's Personal Data Redaction Service automatically identifies and redacts sensitive personal information within meeting summaries to help maintain privacy and compliance. When applying these settings, these changes are applicable only for future recordings/transcripts and historical data (i.e., past meeting summaries) will not be updated.
Entity Type
Account administrators can help prevent sensitive information from appearing in meeting summaries by configuring custom regular expressions. These regular expressions must follow Java's regex syntax and conventions. By defining specific patterns, admins can precisely control and automatically block the inclusion of sensitive phrases, numbers, or any other data types within meeting summaries.
For example,
To block credit card numbers, a Java regex like \b(?:\d[ -]*?){13,16}\b could be used.
To block a specific phrase such as "internal use only," a Java regex like (?i)internal use only(case-insensitive) could be applied.
Admins should ensure that regular expressions are thoroughly tested and validated to avoid inadvertently blocking non-sensitive or relevant meeting content.
Warning
Sensitive information may not be fully blocked by this setting. When sensitive information is blocked, the original, unredacted meeting summary can no longer be retrieved and accuracy may be impacted.
Account administrators can configure a Custom Disclaimer prompt to display custom messages to users before they access certain content or features. Disclaimers can be tailored separately for internal and external audiences, allowing admins to present different messages based on the user's audience type. Additionally, admins can require explicit user consent before proceeding.
The Custom Disclaimer prompt supports multiple languages, allowing organizations to cater to diverse, multilingual audiences. Supported languages include:
When creating the disclaimer(s), administrators must manually provide translated versions of the disclaimer messages for each desired language and audience (internal/external). The Zoom web portal does not provide an automated translation mechanism, so translations must be completed externally before being configured in the Custom Disclaimer’s settings.
David Kim serves as Enterprise Account Executive at CloudTech Solutions, a 1,200-person B2B software company specializing in enterprise data analytics platforms. David manages a portfolio of 15 major accounts worth $12M+ in annual recurring revenue, conducts 20+ prospect meetings weekly across multiple time zones, and navigates complex 6-18 month sales cycles with multiple stakeholders. He struggles with maintaining context across dozens of ongoing deals, spending 8+ hours weekly on CRM updates and follow-up communications, and keeping track of competitive intelligence and product updates that change frequently.
Now, with AI Companion and a Custom AI Companion license, David can transform sales execution from reactive relationship management to strategic revenue acceleration.
General Knowledge Queries - Strategic insights on industry trends, competitive intelligence, and advanced sales methodologies.
Meeting Preparation - Structured guidance for discovery calls, pipeline reviews, and executive briefings.
Meeting Summary - Automatic capture of client conversations, competitive discussions, and strategic planning sessions.
Context-Aware Follow-Ups
Knowledge Bases - Access to competitive battle cards, customer success stories, industry research, and ROI data for strategic positioning and proof points.
Context Management Overload - Previously struggled maintaining detailed context across 15 major accounts worth $12M+ in complex, multi-stakeholder sales cycles.
Manual CRM Documentation - Spent 8+ hours weekly on post-meeting summaries, follow-up communications, and pipeline updates.
Competitive Intelligence Gaps - Difficulty accessing current market trends and competitive positioning during live prospect conversations.
7:30 AM - Pre-Meeting Intelligence and Preparation
David begins his day preparing for a crucial discovery call with Meridian Industries, a potential $2.3M deal. He opens the AI Companion Panel within Zoom Workplace and asks: "What are the emerging trends in manufacturing data governance that could create urgency for analytics platform adoption, and how are companies typically structuring their data lake architectures to support real-time operational insights?" Using General Knowledge Queries, AI Companion provides search results with synthesized guidance about current manufacturing data trends, regulatory compliance drivers, and architectural approaches that could influence buying decisions.
David then uses Meeting Preparation, asking: "Help me prepare for a discovery call with a VP of Operations at a mid-size manufacturing company - what topics should I prioritize to uncover their biggest data challenges?" AI Companion provides structured guidance on manufacturing operational priorities, typical data bottlenecks, and strategic questions to identify budget authority and decision-making processes.
9:00 AM - Client Discovery Meeting and Documentation
David conducts his discovery call with Meridian Industries' VP of Operations and two IT directors. During the 60-minute meeting, Meeting Summary automatically captures the detailed conversation as they discuss their current data silos, compliance challenges with new manufacturing regulations, budget constraints, and decision timeline for Q1 implementation.
The prospects reveal critical information: they're currently using three separate systems that don't communicate, they have a $1.8M budget approved for Q4, and their biggest pain point is real-time visibility into production bottlenecks. They also mention they're evaluating two competitors.
After the meeting, David uses Context-Aware Follow-Ups to immediately generate personalized communications. He prompts: "Draft a follow-up email to the VP of Operations summarizing today's discussion, confirming their key pain points around data silos and real-time visibility, and proposing next steps for a technical deep-dive demonstration." AI Companion creates a comprehensive follow-up that references specific challenges discussed and suggests concrete next steps.
David then copies the AI-generated meeting summary and pastes it directly into the Meridian Industries opportunity record in Salesforce, helping ensure accurate CRM documentation without manual transcription. This seamless integration maintains detailed opportunity history while eliminating the 20+ minutes typically required for post-call CRM updates.
David then opens the AI Companion Panel and asks: "Based on what I learned about their three-system integration challenge and $1.8M budget, what should be my competitive positioning strategy against typical enterprise analytics vendors?" Using General Knowledge Queries, AI Companion provides strategic guidance on differentiation approaches for complex integration scenarios.
11:30 AM - Competitive Intelligence and Proposal Development
David needs to prepare a proposal for another prospect, Global Manufacturing Corp, who mentioned they're also evaluating Tableau and Microsoft Power BI. He opens the AI Companion Panel and asks: "What are the key architectural limitations of Tableau and Power BI when handling real-time manufacturing data streams at enterprise scale, and how do modern data platforms typically address these challenges?" Using General Knowledge Queries, AI Companion provides detailed competitive intelligence about platform limitations, performance bottlenecks, and technical differentiators.
David then opens Zoom Docs and uses Content Generation and Revision to create the proposal foundation, prompting: "Create a technical proposal outline for a $3.2M enterprise data analytics platform implementation, focusing on real-time manufacturing insights, scalability requirements, and integration with existing ERP systems." AI Companion generates a comprehensive proposal structure with technical specifications and implementation timeline.
David accesses his Knowledge Bases (Custom AI Companion add-on license required) containing competitive battle cards, product specifications, and successful case studies. He asks: "Based on our manufacturing customer success stories and product capabilities, how should I position our real-time analytics advantages against Tableau's batch processing limitations for this Global Manufacturing Corp opportunity?" AI Companion analyzes the stored competitive intelligence and customer stories to provide specific positioning strategies and proof points.
2:00 PM - Multi-Stakeholder Communication and Deal Progression
David needs to follow up with Meridian Industries while also managing communications for three other active deals. He opens the Email tab in Zoom Workplace and uses Email Compose for a complex stakeholder situation. He prompts: "Draft an email to the CFO at Meridian Industries explaining how our analytics platform will deliver measurable ROI within 6 months, referencing the operational efficiency gains we discussed with their VP of Operations yesterday, while addressing typical financial concerns about data platform investments."
AI Companion generates a sophisticated email that bridges technical benefits with financial outcomes, speaking directly to CFO priorities while maintaining consistency with the operational discussions.
David then uses Smart Scheduling to coordinate an internal strategy session about the Meridian opportunity. Instead of the typical back-and-forth email chain, AI Companion automatically finds optimal meeting times that work for David, his sales engineer in Seattle, the regional sales manager in Denver, and a product specialist in Austin, eliminating hours of internal coordination effort.
Finally, David opens Zoom Team Chat and uses Chat Compose to update his sales team on deal progress. He prompts: "Create a brief update for our sales team chat about the Meridian Industries opportunity, highlighting the $1.8M budget confirmation, competitive landscape, and next steps without revealing sensitive client details." AI Companion crafts a professional update that shares relevant information while maintaining client confidentiality.
4:30 PM - Pipeline Review and Strategic Planning
David has his weekly pipeline review with his sales manager in 30 minutes and needs to prepare comprehensive updates on his 15 active opportunities. He opens the AI Companion Panel and uses Data Analysis by uploading his quarterly pipeline report (CSV export from Salesforce). He asks: "Analyze this pipeline data to identify which deals are at risk based on velocity trends, time in stage, and last activity dates, and suggest specific actions to accelerate the top 5 opportunities."
AI Companion examines the pipeline metrics and identifies that three deals have been in the "Technical Evaluation" stage 40% longer than average, two prospects haven't had meaningful engagement in 3 weeks, and the Global Manufacturing Corp deal shows strong momentum based on recent activity patterns.
Before the meeting, David uses Meeting Preparation asking: "Help me prepare talking points for a sales pipeline review focused on Q4 quota attainment, deal risk mitigation, and resource allocation for closing my top opportunities." AI Companion provides structured guidance on how to present deal status, risk factors, and specific support needed from sales engineering and marketing teams.
During the pipeline review meeting, Meeting Summary captures the strategic discussion about deal priorities, resource allocation decisions, and specific action items for accelerating key opportunities before quarter-end.
6:00 PM - End-of-Day Strategic Follow-up and Tomorrow's Preparation
As David wraps up his day, he needs to complete follow-up actions from his pipeline review and prepare for tomorrow's customer meetings. He opens the AI Companion Panel and accesses his Knowledge Bases (Custom AI Companion add-on license required) containing industry research, competitive intelligence, and customer success metrics.
He asks: "Based on our latest customer ROI data and industry benchmarks, what are the strongest proof points I should emphasize tomorrow in my executive briefing with TechCorp's CEO about data analytics transformation impact on manufacturing efficiency?" AI Companion analyzes his stored customer case studies and industry data to provide compelling executive-level talking points focused on strategic business outcomes rather than technical features.
David then opens the Email tab and uses Email Compose to send a strategic follow-up to a prospect who's been quiet for two weeks. He prompts: "Draft a re-engagement email to DataFlow Industries' CTO that adds value by sharing relevant industry insights about manufacturing data security regulations, while naturally reopening our conversation about their analytics platform evaluation." AI Companion creates a thoughtful email that provides genuine value while professionally re-engaging the dormant opportunity.
Finally, David uses Prompt Assistance to refine his approach for tomorrow's meetings, asking: "What are the most effective techniques for identifying shadow IT initiatives and unofficial data analytics projects during enterprise discovery calls, and how can I use these insights to expand deal scope beyond the original RFP requirements?" AI Companion provides questioning frameworks that help David uncover hidden opportunities and decision influencers within complex enterprise accounts.
With AI Companion and Custom AI Companion capabilities, David has revolutionized his approach from reactive relationship management to strategic revenue acceleration. What once required hours of manual research, documentation, and coordination now happens seamlessly—his Knowledge Bases provide instant access to competitive intelligence and customer proof points during live conversations, while AI-generated analysis identifies pipeline risks before they become quota threats. David's communication quality has elevated dramatically, with AI-generated emails that speak fluently to CFO financial priorities and CTO technical concerns alike. Smart Scheduling eliminates the coordination friction that previously delayed deal progression, and Context-Aware Follow-Ups ensure no opportunity goes dark due to communication gaps. David now spends more of his time in strategic customer conversations and deal advancement rather than administrative tasks and manual research. The AI doesn't just make him more efficient—it transforms him into a strategic advisor who can navigate complex enterprise sales cycles with intelligence and responsiveness to help close deals in competitive markets.
Tyler Washington serves as Customer Support Team Lead at TechSolutions Pro, a 400-person B2B software company providing project management platforms to mid-market enterprises. Tyler manages a team of 12 support agents handling 200+ customer interactions daily across phone, chat, and email channels, while maintaining SLA compliance and customer satisfaction scores. He struggles with inconsistent case documentation across channels, spending 6+ hours weekly coaching agents on communication quality, and manually tracking escalation patterns and customer sentiment trends across complex technical support cases.
Now, with AI Companion and a Custom AI Companion license, Tyler can transform from reactive support management to proactive customer success orchestration.
Chat Compose - Professional team communications for coaching feedback and shift coordination.
Content Generation (Zoom Whiteboard) - Interactive visual troubleshooting decision trees for technical support processes.
General Knowledge Queries - Research-backed insights on customer service coaching techniques and support strategies.
Meeting Preparation - Crisis management guidance for high-priority customer escalations.
Third-Party Application Skills - Direct Jira ticket creation, search, and linking for incident management without platform switching.
Inconsistent Documentation Burden - Previously spent hours manually documenting complex technical support cases across multiple systems.
Agent Performance Visibility Gaps - Limited real-time insights into communication quality and customer sentiment during live interactions.
Cross-Platform Workflow Friction - Constant switching between Zoom meetings, Jira ticketing, and documentation systems disrupted incident management.
8:30 AM - Live Customer Engagement and Real-Time Coaching
Tyler begins his day monitoring live customer interactions through Zoom Contact Center. During a complex technical support call between agent Sarah and a frustrated customer experiencing database integration issues, he observes Consumer Sentiment Analysis tracking the conversation in real-time. The system shows sentiment shifting from "Negative" to "Neutral" as Sarah successfully diagnoses the root cause, providing Tyler immediate insights into the interaction's emotional trajectory.
Agent Talk Metrics displays that Sarah is speaking at 140 words per minute—slightly above the optimal range—and has been talking for over 4 minutes continuously. Tyler uses this real-time feedback to send Sarah a quick chat message suggesting she pause to confirm customer understanding, helping her adjust her communication approach mid-conversation.
Later, Tyler reviews Follow-Up Tasks generated from yesterday's customer interactions. He sees that agent Jennifer has three AI-generated tasks from her technical support cases: "Schedule follow-up call with DataCorp about API timeout resolution," "Send configuration documentation to MegaTech's IT team," and "Escalate recurring database error pattern to engineering team." Tyler can track completion status and ensure critical customer commitments aren't missed, transforming scattered post-call promises into organized, accountable follow-through.
10:00 AM - Team Communication and Agent Development
Tyler needs to address communication quality issues he's observed across his support team and create training materials for new agents joining next month. He opens Zoom Team Chat and uses Chat Compose to craft a message for his support team channel. He prompts: "Create a constructive team message about maintaining professional tone during high-stress customer interactions, emphasizing our commitment to customer success while providing specific communication techniques." AI Companion generates a supportive message that addresses quality concerns without singling out individual agents.
Tyler then opens Zoom Whiteboard and uses Content Generation to develop visual training materials. He prompts: "Create an interactive troubleshooting decision tree for complex API integration issues that agents can follow during live customer calls, including specific diagnostic questions, common error code interpretations, and escalation triggers for our project management software platform." AI Companion generates a sophisticated flowchart-style visual guide that helps agents navigate technical complexities systematically while maintaining customer confidence.
Finally, Tyler opens the AI Companion Panel and asks: "What are the most effective coaching techniques for improving customer service agent performance in technical support environments, particularly for complex B2B software issues?" Using General Knowledge Queries, AI Companion provides research-backed insights about coaching methodologies, performance improvement strategies, and techniques for building technical confidence in support agents.
1:00 PM - Customer Escalation Management and Strategic Communication
Tyler receives a high-priority escalation from a major client, DataFlow Enterprises, whose production system went down due to an integration issue. He needs to coordinate response across multiple teams and communicate with executive stakeholders. Tyler opens the AI Companion Panel and uses Meeting Preparation, asking: "Help me prepare for an emergency escalation call with a major client experiencing production downtime, focusing on accountability, resolution timeline communication, and relationship preservation strategies." AI Companion provides structured guidance for crisis management conversations and stakeholder communication approaches.
During the 45-minute emergency response meeting with his engineering team, account manager, and client stakeholders, Meeting Summary automatically captures the critical details: root cause identified as API rate limiting configuration, resolution timeline of 4 hours, temporary workaround implemented, and post-mortem scheduled for next week.
After the crisis call, Tyler opens the Email tab in Zoom Workplace and uses Email Compose to craft executive communications. He prompts: "Draft a professional post-incident email to DataFlow's CTO explaining the root cause of today's production issue, the permanent fix being implemented, and our additional monitoring measures to prevent recurrence, while maintaining confidence in our partnership." AI Companion generates a comprehensive email that balances technical transparency with relationship management, addressing both the immediate resolution and long-term partnership assurance.
3:30 PM - Issue Tracking and Cross-Platform Integration
Tyler needs to document the DataFlow production incident and ensure proper engineering follow-up. Instead of switching to the Jira interface, he opens the AI Companion Panel and leverages Third-Party Application Skills (Custom AI Companion add-on license required) to interact directly with their Jira system.
Tyler prompts: "Create a new Jira ticket for the DataFlow API rate limiting incident with priority 'High,' assign it to the Platform Engineering team, and include details about the root cause, temporary workaround implemented, and permanent fix timeline of 4 hours." AI Companion seamlessly creates the ticket, automatically populating relevant fields and adding the meeting summary details from the earlier escalation call.
He then asks AI Companion to "Search existing Jira tickets for similar API rate limiting issues in the past 6 months and link them to this new DataFlow ticket for pattern analysis." The system identifies three related incidents and automatically creates ticket links.
This integration transforms Tyler's incident management workflow by eliminating the need to manually switch between Zoom meetings, documentation systems, and project tracking tools—keeping all critical customer escalation work centralized within his primary communication platform while maintaining proper engineering documentation and accountability.
5:00 PM - End-of-Day Communication and Strategic Planning
As Tyler prepares to wrap up his day, he needs to coordinate with his evening shift supervisor and ensure smooth handover of critical issues. He opens the Email tab in Zoom Workplace and uses Email Compose to brief the night shift lead. He prompts: "Draft a shift handover email for our evening support supervisor covering today's DataFlow escalation resolution, the three high-priority tickets requiring follow-up, and the API troubleshooting decision tree now available for agent reference." AI Companion creates a comprehensive handover summary that ensures continuity of critical customer support issues.
Tyler then opens Zoom Team Chat and uses Chat Compose to prepare his team for tomorrow's shift. He prompts: "Create an end-of-day message for our support team highlighting today's wins with the new troubleshooting framework, noting the increase in API-related tickets we should expect tomorrow, and encouraging the team about our improved customer satisfaction scores." AI Companion crafts a motivational message that acknowledges challenges while celebrating improvements.
Finally, Tyler opens Zoom Tasks to review the AI-generated action items from today's escalation meetings and customer interactions. He sees tasks automatically created from the DataFlow incident ("Schedule post-mortem with engineering team"), agent coaching observations ("Follow up with Sarah on communication pacing techniques"), and process improvements ("Update API troubleshooting documentation based on today's patterns"). He assigns the documentation update to his senior agent, uses Smart Scheduling to coordinate the Friday post-mortem meeting across his team, engineering, and account management, and keeps the coaching follow-up for tomorrow morning, helping ensure critical support operations don't fall through the cracks.
With AI Companion and Custom AI Companion capabilities, Tyler has transformed from reactive support management to proactive customer success orchestration. His Consumer Sentiment Analysis and Agent Talk Metrics provide real-time coaching opportunities that elevate service quality during live interactions, while Third-Party Application Skills eliminate the platform-switching friction that previously disrupted incident response workflows. Content Generation in Zoom Whiteboard enables rapid creation of visual troubleshooting guides that scale agent expertise across the entire team, and Follow-Up Tasks ensure no customer commitment falls through the cracks. Tyler now spends more of his time on strategic team development and proactive process improvement rather than administrative documentation and reactive crisis management. The AI doesn't just make him more efficient—it transforms him into a strategic support leader who can maintain exceptional customer satisfaction while building scalable support operations that grow with TechSolutions Pro's expanding client base, turning every customer interaction into an opportunity for relationship strengthening and operational excellence.
Zoom Phone Native service is a cloud-based telephony system that relies on Zoom's cloud infrastructure for call delivery, handling, and transit through an internet connection and underlying network of carriers around the globe. With this service, calls are routed through the internet to Zoom's data centers, and connect to their destination either through a network of underlying carriers across the PSTN (public switched telephone network) or continue across the internet to another Zoom Phone user.
As a cloud-based service, this offering eliminates the need for customers to host or manage any on-premises hardware—like a session border controller (SBC) or SIP trunk—for telephony connectivity. Instead, users only require a working internet connection, a Zoom app or device, and a supported license to begin dialing.
In addition to simplified call connectivity, the Zoom Phone Native service offering also includes Zoom Phone's cloud-based private branch exchange (PBX), which provides numerous features, including voicemail, Auto Receptionists, Call Queues, phone number assignment, and more.
In simple terms, whether you're a small business with a handful of users or a large enterprise with thousands of users, the Zoom Phone Native service model is a cloud-based telephony solution tailored to meet your business' needs.
The Zoom Phone Native service offers international PSTN connectivity within 47 countries through 18 global data centers.
United States:
California
Colorado
New Jersey
From the following data centers, the Zoom Phone Native service provides PSTN connectivity within the following countries:
North America:
United States
Canada
Puerto Rico
Latin America:
Automated meeting tools (e.g., applications—including bots, integrations, and third-party services) can enhance the Zoom Meeting experience and assist users with several tasks, such as meeting notation, summarization, transcription, and recording. Enterprise professionals may use automated meeting tools to record their collaboration sessions for coaching purposes, and educators and students may use them to summarize lectures to be revisited during study sessions. Automated meeting tools can be added at marketplace.zoom.us or from the Apps icon found in the Zoom Workplace application. Your developers can also create unpublished or internal automated meeting tools to serve specific functions within your organization.
All automated meeting tools that utilize the Zoom Meeting SDK must comply with the so they trigger the appropriate notifications when meeting content is being accessed.
All automated meeting tools that are intended to be published to the Zoom App Marketplace undergo a dedicated . Once an automated meeting tool is submitted, the Zoom App Marketplace team reviews and either approves it or provides feedback to the developer on any remediation work required for it to be approved.
The review process’ primary goals are to:
Confirm that the automated meeting tool is ready for use by end users.
Confirm that the automated meeting tool follows best practices for privacy and security to reduce risks to users.
As of July 16, 2023, all newly submitted automated meeting tools must be approved by the App Marketplace team to join meetings that are hosted by other Zoom accounts. Automated meeting tools that are not approved by the App Marketplace team will only be able to join meetings that are hosted by the account in which they were developed after this date.
Zoom’s is your guide to building, designing, and testing new automated meeting tools. The site contains best practice information, including how to use Zoom’s . There are also reference implementations available for or the .
Navigate to the Developer resources section for each application, integration, or service available in to view its privacy policy and other support resources.
Users can join a Zoom Meeting without or from the web if they are unable to download the Zoom desktop client or mobile app. These participants can join as a guest by navigating to and clicking Join and then Join by Meeting ID. The meeting guest can then enter the meeting ID and passcode (if applicable) to join the meeting.
Some users may also join or start meetings via their web browser by entering these URLs:
https://zoom.us/wc/join/meetingID
https://zoom.us/wc/meetingID/start
Zoom automatically utilizes CAPTCHA v3 for meeting participants, which runs invisibly in the background to help ensure that uninvited automated meeting tools are not able to join meetings from the web. The CAPTCHA requirement is enabled by default for all accounts and cannot be turned off.
Automated meeting tools are managed by the user who installs them, and it is at that user’s direction that the automated meeting tool joins a meeting and records content on their behalf.
You can manually initiate an automated meeting tool and have it join an active meeting by clicking the Apps menu found in the Zoom client or through the automated meeting tool’s respective web interface. The automated meeting tool will join the meeting, start recording the specific content for which it was designed, and be listed in the Active Apps Notifier. The automated meeting tool will also trigger a recording notification, informing all attendees of its presence and function in the meeting.
Many automated meeting tools can be synchronized with a user’s calendar and their Zoom account. This allows the tool to access calendar invites that may include a Zoom Meeting invitation and automatically join those meetings if instructed by its user. You can enable or disable an automated meeting tool’s ability to automatically join meetings on your calendar.
Review your upcoming meetings to confirm whether it is appropriate for your automated meeting tool to join any meeting automatically. Disable the tool from auto-joining a scheduled meeting if the meeting content should not be recorded.
Automated meeting tools commonly join meetings as participants and appear in a manner similar to the people attending the meeting. This means they have their own video thumbnail that appears next to the other meeting participants and labeled with the name of the user who initiated it and its function (e.g., “Steve Miller’s notetaking app”). While in a meeting, the Participants list and the Waiting Room feature (when enabled) will list any automated meeting tools along with all other users, allowing hosts and participants to identify and manage automated meeting tools within their meetings.
Automated meeting tools are developed to access certain in-meeting content such as real-time video, audio, screen or whiteboard sharing, chat, or files shared in the meeting, which are then used to improve workflows like meeting summarization, transcription, or other functions.
The authorization prompt explains what types of media and data the automated meeting tool will access during a meeting. This prompt will also describe the types of user data the tool will access, which may include profile information, calendar synchronization, or account settings.
It is important to note that in addition to automated meeting tools that join meetings as apps or participants, there is another related category of tools that operate on participants’ local devices. These tools are downloaded by individuals to record their device's system audio and video from outside of the Zoom Workplace platform. Because these tools function locally and not within Zoom Meetings, options to mitigate their use are limited and beyond the scope of this document.
This section outlines how to use Zoom Phone SMS features. The following instructions assume that you are signed in to a compatible Zoom Workplace app or the Zoom Web App.
Below is a list of capabilities available with Zoom Phone SMS.
To send a new SMS Message:
Click the Phone tab, then click the SMS tab.
Click the compose icon below the SMS tab.
In the To field at the top, enter a name or phone number to search through your contacts directory, or manually enter a phone number. If the recipient is in your contacts directory, the number will be replaced by the contact’s name, otherwise, it will remain a phone number.
You can add up to 10 contacts/phone numbers.
If the contact has several phone numbers, click the right arrow icon to view and select the number to send the SMS to.
Enter a message and press Enter or click the send icon.
To reply to an existing SMS conversation:
Click the Phone tab, then click the SMS tab.
Select an SMS conversation.
Enter a message, then press Enter or click the send icon.
To attach multimedia to an SMS (MMS):
Open an SMS conversation.
Above the chat compose box, click the File button to select an image.\
To send the image, press Enter or click the send icon.
To call an SMS participant from a thread:
Select an SMS conversation.
In the top-left corner of the SMS conversation, click the Phone call button.
View phone numbers and details involved in the SMS conversation.
To view a conversation’s details:
Select an SMS conservation.
In the top-right corner of the SMS conversation, click the info button.
The dropdown will display details such as members, images, files, push notifications, and the ability to block the participant’s number.
If Team SMS is enabled by an administrator, phone users can send or receive SMS messages using Zoom Phone numbers associated with call queues or auto receptionists. This allows you to view SMS messages that are sent to a group of users. You can then reply to the conversation, which prevents other users from replying to the same conversation, and transfer a thread to another user to share information that might have been missed. You can also release a conversation to allow other members to reply.
Important
Team SMS requires that each user has a Power Pack add-on assigned to their Zoom account.
Team SMS messages will appear in the SMS tab, just like your regular SMS messages. To access SMS:
Sign in to the Zoom Workplace desktop app, Zoom Workplace mobile app, or Zoom Web App.
Click or tap the Phone tab, then click or tap SMS.
If you’ve enabled notifications at the system level (Windows, MacOS, Linux, Android, or iOS) and in the SMS conversation settings, you will receive a notification depending on the status of the SMS conversation.
You will see notifications if no members have clicked Reply to claim the conversation or you’ve clicked Reply.
You will not see notifications if another member has clicked Reply to claim the conversation.
Users can reply to messages received by the call queue or auto receptionist to claim the conversation. This prevents other members from replying to the same conversation, while other members can still see the conversation.
To claim a conversation:
Open an SMS conversation that belongs to a call queue or auto receptionist. The call queue or auto receptionist display name will appear below the caller ID of the sender.
Click Reply at the bottom of the conversation thread. You will see a pop-up notification to confirm.
Note: You will see a notification in the conversation thread if another phone user has chosen to reply, which prevents you from replying.
Click Reply to confirm.
Users can release a conversion to allow other members to reply to the conversation and claim it. To release a conversation:
Open an SMS conversation that belongs to a call queue or auto receptionist. The call queue or auto receptionist display name will appear below the caller ID of the sender.
Click Release at the top of the conversation thread.
You will see a pop-up notification to confirm.
Click Release to confirm.
If you have a Power Pack add-on license, you can summarize an SMS team thread with AI Companion using the following steps:
Open an SMS conversation.
In the text box, click the Summarize with AI Companion icon.
The summary will display within a few seconds after clicking the icon.
(Optional) In the dialog box, click Copy to copy the summary to paste it where you need.
For Zoom Phone-specific data residency, there are two distinct categories of data that cover different components of the service: Diagnostic Data and Customer Content Data. Each of these data types has different rules governing their residency, which are discussed in the following sections.
Diagnostic Data is data automatically generated or collected by Zoom through use of the Zoom service. For Zoom Phone, Diagnostic Data includes phone call, SMS/MMS, voicemail, videomail, and voice recording metadata, telemetry data (e.g., product usage and system configuration), and other service-generated data (e.g., information to provide a service requested by the end user).
Details of how Diagnostic Data and its sub-categories are collected and handled are provided within the and Zoom's . Customers with outstanding questions are encouraged to speak to their Zoom account team for more information.
Zoom Phone Customer Content Data is the data your users record or share during a phone call, including voice/video, transcripts, recordings, voicemail, videomail, and SMS/MMS.
Where this data is stored can depend on several factors and may vary depending on account, group, and user settings or call routing tool-specific settings. However, it is important to note that all call recordings will be temporarily stored and processed in the SIP zone region where the user's device is registered before it is moved to its permanent data storage location. For instance, if a user's applicable content storage is set to Germany but they are registered to a SIP zone in the U.S., the call will be recorded and processed within the U.S. data center before being transferred to long-term storage in Germany.
The following table outlines which pieces of data in Zoom Phone are customizable for residency and which are located within the account's provisioned cluster.
Zoom offers all paid customers regional data storage for applicable types of Customer Content—which is configurable at the account, group, and user levels—and for each unique Auto Receptionist, Call Queue, and Shared Line Group.
For these various groups and call-routing tools, customers can choose to store applicable Zoom Phone Customer Content in the following locations:
United States
Australia
Brazil
Canada
Refer to Zoom's support center for more information on .
Zoom Phone Customer Content Data is retained in the cloud indefinitely by default. However, customers can customize their data retention settings to between 1 and 4,000 days (approximately 11 years) for the following items:
Call Logs
Ad-Hoc Recordings
Automatic Call Recordings
Customers can also define deletion behavior, with the option initially "soft delete" data, leaving it in a recoverable state for up to 30 days before it is permanently deleted. Alternatively, customers can set it to permanently delete after the set time without a "soft delete" period.
Refer to Zoom's support center for more information on customizing the "" Zoom Phone policy.
Zoom Phone provides features for Information Barriers, assisting customers in managing user communication policies and fulfilling regulatory obligations. This includes preventing specific groups of users with sensitive information from communicating with others unauthorized to access this data.
Within Zoom Phone, users blocked by Information Barriers are unable to search, call, or text other members of affected groups. Attempting these actions will prompt an error message indicating restricted communication between certain groups and users. Furthermore, blocked users cannot invite other members of the affected group into a meeting using Zoom Phone.
Refer to Zoom's support center for more information on .
Zoom Phone supports end-to-end encrypted (E2EE) calls between two Zoom Phone users within the same account, so long as both users meet specific requirements. This offers users an extra layer of privacy and confidentiality to their Zoom Phone calls, and can be quickly enabled so long as both users are calling from a supported Zoom app or device.
Refer to Zoom's support center for more information on and end-to-end encrypted calling. For more information on Zoom Phone's end-to-end encryption practices, refer to .
Zoom has provided the , which describes Zoom's process for handling personal data and other data handling practices. Readers are also encouraged to refer to Zoom's .
Zoom maintains a list of Certifications, Attestations, and Standards within our .
As of June 25, 2025, Zoom offers Realtime Media Streams, which give developers direct access to rich, structured meeting data to unlock AI-driven insights, automate critical workflows, and build impactful integrations on the Zoom platform. Developers can reference Realtime Media Streams documentation to get started.
Realtime Media Streams remove the need for third-party automated tools in meetings. Apps will receive per-participant structured data streams reflecting the context available to the user that authorized them.
By leveraging RTMS, developers can differentiate their apps, improve performance, and expand revenue opportunities. Additionally, enterprises are met with a solution to gain real-time access to their most critical conversations for insights, compliance, and enhanced workflows.
Account admins can enable RTMS and set RTMS auto-start toggles in the Zoom web portal. Additionally, hosts can use in-meeting host tools to control whether participants must request host approval to access meeting content.
Admins can enable RTMS at the account, group, or user level within the Zoom Apps settings in the Zoom web portal.
Along with sharing real-time meeting content with apps, admins can choose to auto-start apps:
Under the Auto-start apps that access shared real-time meeting content setting, click Choose an app to auto-start.
Select the RTMS-enabled app or apps and set the Auto-start to On.
The following tools are available to meeting hosts:
Share real-time meeting content with apps: Enable participants to share meeting content.
Require host approval: Require participants to request approval from the host to access meeting content.
The following screens are examples of disclosures, notifications, and AAN screens available to the meeting host.
The standard disclosure is displayed for the host and participants: “The content of this meeting is being shared with one or more apps.”
This is the host view of the AAN when RTMS-enabled apps are set to auto-start by the account administrator.
This is the host view of the AAN when RTMS is started by the host via app UI (JS API) or REST API. In this example image, you are Carlos Washington, the host.
This modal represents scenarios in which the host requires approval to share meeting content, and:
The admin sets apps to auto-start from a different account than the host.
Participants from the same or different accounts request to use an app in-meeting, initiated via the app (JS API or REST API).
This is the host view of the request modal for a single app. The host can approve or deny the request.
The image below covers scenarios in which the host requires approval to share meeting content, AND:
Multiple apps are requested by one or more participants.
Multiple external admins set apps to auto-start for multiple participants from different accounts.
Participants from the same or different account request to share content in-meeting.
This is the host view of the request modal for multiple apps. The host can approve or deny the request:
This is the host view of the AAN of an approved app actively sharing content. It shows the name of the app, the app’s user, and the status as “Sharing."
The video tiles view of active apps is the same for all meeting participants and the host. The name of the app used by the meeting participant is displayed in their video tile.
The immersive view of active apps is the same for all meeting participants and the host. The name of the app used by the meeting participant is displayed below their video image.
The following screens are examples of disclosures, notifications, and AAN screens available to the meeting participants.
The standard disclosure is displayed for the host and participants: “The content of this meeting is being shared with one or more apps.”
This is the request modal participants use to request to share meeting content to the host.
These are the available confirmation messages shown to participants in response to their request:
Request sent to the host.
Request for app to share meeting content denied by host.
Host cannot approve your app’s access to meeting content.
Host disabled your app from sharing meeting content.
The video tiles view of active apps is the same for all meeting participants and the host. The name of the app used by the meeting participant is displayed in their video tile.
The immersive view of active apps is the same for all meeting participants and the host. The name of the app used by the meeting participant is displayed below their video image.
These are guidelines and average timeframes and are always subject to change based on losing carrier workload.
All APAC regions: 10-12 weeks
Singapore: 2:00-4:00 pm Local Time
Australia:
Simple Port (CAT-A): 10:00-11:00 am Local Time
Complex Port (CAT-C): Time slots provided upon port confirmation
The information you provide must match what is on record with your current provider.
In most APAC countries, the address noted on the LOA must match the geographic area code of the porting telephone numbers.
Porting numbers need to be in the LOA rather than as attachments unless otherwise permitted.
DDI blocks of numbers may require full port as some countries do not allow blocks/ranges of numbers to be split. Refer to our
Download and complete the required from the respective country.
See the if you need help.
If you currently have trial/temporary numbers and would like to swap them when the port completes, please complete the . Numbers swapped in will be a like-for-like replacement of the numbers swapped out.
Visit our support article on .
Zoom Phone provides comprehensive telephony services in Japan including toll-free and local number porting (both inbound and outbound). For detailed information about Japan-specific procedures including toll-free number porting requirements, local number porting with supported carriers and group scenarios, port-out processes and troubleshooting, and business address configuration in Number Management, please refer to our dedicated Japan telephony guides: , , , and . \
These are guidelines and average timeframes and are always subject to change based on losing carrier workload.
All Latin America regions: Up to 60 days
Mexico: 2:00-6:30 am Local Time
Brazil: 4:00-6:00 pm Local Time
Peru: 12:00 am-7:00 am Local Time
Argentina and Chile: Time slots provided upon port confirmation
Downtime is to be expected during LATAM number ports.
It is recommended that porting not be scheduled for a Friday or holiday.
Once a porting date is provided, porting will be executed within the specified time frame.
Porting is not yet supported in Colombia, Costa Rica, Ecuador, and Panama. However, new numbers are available to order in these countries.
The information you provide must match what is on record with your current provider.
LOA must be hand/wet signed and dated within the last 3 months. Electronically signed LOAs are not accepted in most LATAM countries.
Your service provider's name is required on the LOA.
Number portability checks can only be carried out once the order is submitted. There may be times when service providers advise that numbers as non-portable.
Account owner or admin privileges
Zoom Phone license
Completed Zoom Phone
Completed Contact Center setup (if porting into Contact Center)
Download and complete the required from the respective country.
See the if you need help.
If you currently have trial/temporary numbers and would like to swap them when the port is complete, please complete the . Numbers swapped in will be a like-for-like replacement of the numbers swapped out.
Please reference our support articles for and .
Zoom Phone SMS includes a variety of administrative controls that allow account owners and admins to control SMS settings based on organizational needs. This section outlines how to enable SMS at different levels and manage available features, including options that require the Power Pack add-on.
SMS can be enabled by Admins on an account level, group level, site level, or user level. SMS can also be enabled for Call Queue and Auto Receptionist group SMS if Power Pack add-on licenses are implemented. To view step-by-step instructions for how to enable SMS on different levels, please see the Setting Up SMS support article.
Below are the SMS settings that can be enabled/disabled by Administrators:
To specify allowed countries/regions for SMS:
Sign in to the Zoom web portal as an admin with the privilege to edit account settings.
In the navigation menu, click Account Management then Billing.
In the Zoom Phone row, click View All Plans.
Click View/Edit Countries/Regions.
To allow international SMS:
Ensure SMS is enabled at the level that you want to manage.
Under the SMS setting, select Allow International SMS.
Click Manage Country/Region.
In the dialog box, select the countries/regions that phone users can send SMS messages to, then click Save.
Account owners and admins can manage the use of emojis and attachments in SMS messages sent through Zoom Phone. They have the option to enable or disable all emojis completely, or select a specific set of emojis that users can use. Additionally, admins can choose to enable or disable attachments in SMS messages. The Allow Attachments and Allow Emojis setting is only available with Zoom Workplace app version 6.1.10 or later.
Ensure that the SMS feature is enabled at the level that you want to manage.
Under the SMS feature, enable or disable the features that you want:
Select the Allow Emojis checkbox to enable it.
When the Allow Emojis checkbox is enabled, select from the following options:
To use personal and sensitive data reaction with Zoom Phone SMS, perform the following steps:
Ensure that the SMS feature is enabled at the level that you want to manage.
Under the SMS feature, select the Redact Personal and Sensitive data checkbox to enable or disable the feature.
When the Redact Personal and Sensitive data checkbox is enabled, click Edit to select a personal and sensitive data group that will be applied to recordings, then click Save.
Once complete, click Save.
Users with a Power Pack license and a Zoom Workplace app version 6.3.0 or later can schedule SMS messages to be sent at a specific date, time, and time zone in the future. They can manage scheduled messages by viewing, editing, and deleting them. As a member in a conversation thread, users can also view scheduled messages and who scheduled the message.
This feature helps users communicate more effectively with recipients in different time zones. To enable this feature:
Ensure that the SMS feature is enabled at the level that you want to manage.
Under the SMS feature, toggle the SMS scheduled response checkbox to enable or disable the feature.
If enabled, SMS users will be able to send messages at a scheduled time.
Click Save.
The retention policy allows account owners and admins to configure rules for what data is retained, the duration of the retention period, and how to delete data after the retention duration. Account owners and admins can allow Zoom to automatically delete data after the retention duration. Please refer to the for more information.
As an admin, you can maximize SMS message efficiency with the SMS template feature to empower your call queue or auto-receptionist users, or a user with the power pack license to generate or reply to multiple messages rapidly. After setting up your SMS templates, your users can access them directly from their Zoom Workplace app. Please refer to the article to enable templates on a site, group, or individual user level.
Admins can use the SMS Etiquette Tool to create policies that identify keywords and text patterns to prevent users from inadvertently sharing unwanted SMS. When a user sends a message that triggers a policy, the message will be blocked, or a warning prompt will be displayed for the user to confirm that they want to send the SMS, depending on what the admin sets. Please refer to the article to enable this feature.
Account owners and admins can enable or disable SMS auto-replies and set auto responses for call queues and auto receptionists when no users are available in the call queue or during closed hours.
Additionally, users with the Power Pack add-on can set up an SMS auto responder to automatically respond to incoming SMS messages during specified conditions like out-of-office hours or Do Not Disturb (DND) mode. The auto responder can be configured to send a pre-defined response of up to 500 characters. Please refer to the support article for how to enable this feature.
Zoom's artificial intelligence architecture provides organizations with three distinct deployment models, each engineered to balance AI capability requirements with specific organizational security, compliance, and operational preferences. Understanding these deployment models enables administrators and decision-makers to select the optimal AI implementation that aligns with their business goals.
The following diagram provides an overview of Zoom's AI Deployment Service Models, detailed in the sections below. Diagrams across the AI Bluepaper typically default to the federated approach, but you can mentally substitute the relevant dataflows with your preferred deployment model. For instance, ZMO (Zoom-Hosted Models Only) customers can disregard the outbound Third-Party Model connections.
Amelia Miller serves as Founder and CEO of LuxeGreen Atelier, a 25-person sustainable luxury fashion company specializing in eco-conscious evening wear and accessories. Amelia manages everything from seasonal collection design to investor relations, coordinates with suppliers across three continents, and plans quarterly fashion shows while maintaining direct customer relationships. She struggles with juggling creative design work and business operations, spending 12+ hours weekly creating marketing content in multiple formats, and managing complex supplier communications across different time zones and platforms.
Now, with AI Companion and a Custom AI Companion license, Amelia can transform from overwhelmed entrepreneur to strategic fashion innovator.
Due to Zoom Phone's cloud-based architecture, configuring Zoom Phone for your network is substantially easier in comparison to legacy, on-premises phone systems. From the simplest of perspectives, users need two key factors to begin successful calling: a working internet connection and open network ports. So long as users can successfully maintain an active connection with Zoom Phone data centers and the necessary ports are not blocked, Zoom Phone is ready for use within your network.
However, despite the fundamental simplicity, there are additional networking components to consider as customer environments become increasingly complex.
For a list of firewall ports, protocols, and settings, refer to .
For customers using zero-touch provisioning, also refer to the and support sites to confirm your devices can communicate with the manufacturer's provisioning servers.
In addition to the Zoom Phone Native service offering, Zoom Phone also supports a Bring Your Own Carrier (BYOC) service with cloud peering (BYOC-C). With this service model, a business can choose one or more underlying telephony carriers to connect (i.e., cloud peer) with Zoom Phone's data centers, without requiring any on-premises hardware, like a session border controller (SBC).
BYOC-C deployments give businesses continued access to Zoom Phone cloud-based PBX features like Call Queues, Auto Receptionists, number assignment, etc., while the underlying telephony connections are handled by the chosen provider(s) without the maintenance costs of on-premises hardware.
Provisioning a user with a Zoom Phone Basic license grants users access to fundamental features of the service. From there, additional features can be granted through calling plans—elevating the user to Licensed or Pro status—and can be further supplemented through add-ons. Alternatively, non-user-specific devices can be provisioned for service with a Common Area License.
The Zoom Phone Dashboard, a subsection of , offers account admins and authorized users with sufficient access to insightful Zoom Phone data and analytics. Information available within the Dashboard includes Zoom Phone Quality of Service (QoS) data, Mean Opinion Scores (MOS), usage reports, call data and metrics, and more. The following sections outline different features and data available through the Zoom Phone dashboard.
The Quality of Service tab within the Zoom Phone dashboard provides data concerning and insights into the overall quality of voice calls for any Zoom Phone extension, including users, common area phones, Call Queues, Auto Receptionists, and Zoom Rooms.
Using a Mean Opinion Score (MOS) as the main measurement, the MOS scores call quality on a scale of 1 to 5. In this scale, a score of 1 indicates unacceptable voice quality for all users, while a score of 5 is the best voice quality, equivalent to speaking directly into a person's ear. As a general baseline, the dashboard utilizes a standard MOS of 3.5 for the average call, with a score of 3.5 or higher indicating good quality, and a score of 3.5 or lower indicating poor quality.
Manual Research and Communication - Extensive time researching best practices and crafting department-specific messaging.
Chat Summaries & Search - Quick analysis of complex team conversation threads.
Content Generation and Revision - Creation of comprehensive policy documents and announcements.
Chat Compose - Tailored messaging for different departments and audiences.
Smart Recording - Automatic content organization and metadata generation.
Email Compose - Sophisticated messaging for CFO-level communications, re-engagement campaigns, and executive outreach.
Smart Scheduling - Automated coordination across multiple time zones and complex stakeholder groups.
Chat Compose - Professional team updates that maintain client confidentiality while sharing deal progress.
Data Analysis - Pipeline analysis to identify at-risk deals and acceleration opportunities.
Prompt Assistance - Advanced questioning techniques for complex enterprise sales situations.
Content Generation and Revision - Technical proposal development and comprehensive implementation planning.
Proposal Development Inefficiency - Manual creation of technical proposals and executive-level business cases.
Pipeline Risk Assessment - Limited visibility into deal velocity patterns and proactive risk identification.
Meeting Summary - Automatic documentation of emergency response meetings and incident details.
Email Compose - Executive communications for incident management and shift handover coordination.
Data Analysis - Support metrics analysis for performance trends and SLA compliance monitoring.
Smart Scheduling - Cross-team coordination for post-incident meetings and process reviews.
Zoom Tasks - Organized workflow management from AI-generated support interaction action items.
Consumer Sentiment Analysis - Real-time emotional tracking during customer support interactions.
Agent Talk Metrics - Live coaching insights on speaking pace and conversation balance.
Follow-Up Tasks - AI-generated task tracking from customer support conversations.
Task Management Fragmentation - Critical follow-up actions from customer escalations often scattered across email, notes, and memory.
Crisis Communication Complexity - Coordinating executive-level incident communications while managing technical resolution efforts.
Content Generation (Zoom Whiteboard) - Visual mind mapping and creative brainstorming for seasonal collection planning.
General Knowledge Queries - Strategic market research on sustainability trends and luxury fashion positioning.
Smart Compose (Zoom Events) - Professional event descriptions for virtual fashion shows.
Image Generation (Zoom Events) - Visual asset creation for fashion show backdrops and promotional materials.
Email Compose (Zoom Events & Zoom Workplace) - Exclusive event invitations and customer follow-up communications.
Voicemail Prioritization - Automatic identification of urgent supplier communications.
Call Summary - Detailed documentation of customer consultations and supplier discussions.
Voicemail Task Suggestions - Automated action item generation from supplier voicemails.
Chat Compose - Team communications for design collaboration and project coordination.
Virtual Background Generation - Professional brand-consistent backgrounds for investor meetings.
Zoom Tasks - Organized workflow management from AI-generated meeting and call action items.
AI Companion for Third-Party Meetings - Meeting summaries and documentation for supplier consortium calls hosted on Microsoft Teams.
Custom Dictionary - Accurate transcription of specialized fashion and sustainability terminology during technical consultations.
Creative-Business Balance Overload - Previously struggled juggling design work with operations, investor relations, and supplier management across multiple time zones.
Marketing Content Creation Burden - Spent 12+ hours weekly creating promotional materials, event descriptions, and visual assets across multiple formats.
Complex Supplier Communication - Managing critical fabric delivery updates and technical discussions across different platforms and languages.
Customer Documentation Inefficiency - Manual note-taking for custom orders requiring 15+ minutes per consultation.
Task Management Fragmentation - Scattered action items from meetings, calls, and creative sessions lacked centralized organization.
Professional Brand Consistency - Maintaining luxury positioning across virtual meetings and digital communications.
8:00 AM - Seasonal Collection Planning and Creative Development
Amelia begins her day preparing for the Spring 2026 collection brainstorming session with her design team. She opens Zoom Whiteboard and uses Content Generation to kickstart the creative process. She prompts: "Create a mind map exploring sustainable luxury fashion trends that combine traditional craftsmanship with innovative eco-friendly materials, focusing on evening wear that appeals to environmentally conscious consumers aged 35-55."
AI Companion generates a comprehensive visual framework with interconnected concepts including regenerative silk alternatives, traditional embroidery techniques, color palettes inspired by natural dyes, and design elements that emphasize timeless elegance over fast fashion trends.
Amelia then uses the AI Companion Panel to research market positioning, asking: "What are the emerging consumer expectations for luxury fashion sustainability certifications, and how are high-end brands successfully communicating their environmental impact without compromising their premium positioning?" Using General Knowledge Queries, AI Companion provides insights about B-Corp certification trends, supply chain transparency demands, and messaging strategies that resonate with affluent eco-conscious consumers.
10:00 AM - Fashion Show Event Planning and Content Creation
Amelia needs to plan her upcoming Fall 2025 runway show and create promotional materials for the event. She opens Zoom Events and begins using Smart Compose to develop compelling event descriptions. She prompts: "Create an elegant event description for a sustainable luxury fashion show featuring evening wear made from regenerative materials, emphasizing the intersection of environmental responsibility and timeless sophistication for an audience of fashion buyers and sustainability advocates."
AI Companion generates sophisticated copy that balances luxury positioning with environmental messaging, perfect for attracting both traditional fashion buyers and eco-conscious media.
Amelia then uses Image Generation within Zoom Events to create visual assets for the show. She prompts: "Generate an elegant fashion show backdrop image featuring organic flowing fabrics in earth tones, with subtle lighting that suggests both luxury and natural harmony." The AI creates several sophisticated images that capture the brand's aesthetic while providing professional visual content for marketing materials.
Finally, Amelia uses Email Compose in Zoom Events to craft invitations to key stakeholders. She prompts: "Draft an exclusive invitation email for fashion editors and sustainability influencers, highlighting the innovative eco-materials being showcased and the limited space available for this virtual runway experience." AI Companion creates personalized invitations that emphasize exclusivity while communicating the brand's environmental values.
12:30 PM - Supplier Communications and International Coordination
Amelia receives an urgent voicemail from her organic silk supplier in Italy regarding a potential delay in fabric delivery for the Spring collection. She uses Voicemail Prioritization in Zoom Phone, which automatically identifies this message as high-priority based on keywords like "delivery delay" and "Spring collection."
She listens to the Call Summary generated from the voicemail, which captures the key details: a 2-week potential delay due to quality control issues with the new regenerative silk process, affecting 40% of her Spring collection timeline. The system also generates Voicemail Task Suggestions, recommending immediate actions like contacting the production manager and exploring alternative suppliers.
Amelia then needs to join a Microsoft Teams meeting hosted by her European fabric consortium—a group of sustainable suppliers she collaborates with regularly. Using AI Companion for Third-Party Meetings (Custom AI Companion add-on license required), she brings AI Companion capabilities into the Teams call. During the 45-minute discussion about organic certification processes and supply chain transparency, AI Companion captures detailed notes about new certification requirements and timeline changes.
After the Teams meeting, she receives a comprehensive meeting summary that helps her document critical supplier relationship information and compliance updates, even though the meeting wasn't hosted on Zoom.
2:30 PM - Customer Relationship Management and Sales Communications
Amelia receives a phone call from Victoria Chen, a high-profile customer interested in commissioning a custom sustainable evening gown for an upcoming gala. During the 25-minute conversation, they discuss fabric preferences, design inspiration from Amelia's previous collections, timeline requirements, and budget considerations for the bespoke piece.
After the call, Call Summary automatically generates a detailed summary capturing Victoria's specific requirements: preference for recycled silk with hand-embroidered details, inspiration from the "Ocean Currents" collection, needed by March 15th, and budget range of $8,000-$12,000. This eliminates Amelia's typical 15-minute manual note-taking process for custom orders.
Amelia then opens the Email tab in Zoom Workplace and uses Email Compose to follow up with Victoria. She prompts: "Draft a professional follow-up email confirming our custom gown discussion, outlining the design process timeline, sustainable material options we discussed, and next steps for the initial consultation appointment." AI Companion creates an elegant email that reinforces LuxeGreen's luxury positioning while detailing the bespoke creation process.
Later, Amelia has a video consultation with Victoria to review fabric samples. Because Amelia has a Custom Dictionary (Custom AI Companion add-on license required) containing specialized fashion terms like "Tencel Luxe," "ECONYL," "Piñatex," and "bio-fabricated silk," the meeting transcript accurately captures their technical discussion about sustainable material options rather than producing garbled text when these specialized terms are spoken.
4:00 PM - Brand Content Creation and Visual Strategy
Amelia needs to create professional backgrounds for her upcoming investor calls and brand consistency for virtual meetings. She opens Virtual Background Generation and prompts: "Generate a sophisticated virtual background featuring subtle luxury textures in earth tones that reflects an eco-friendly fashion brand's aesthetic, suitable for executive video calls." AI Companion creates several elegant backgrounds that maintain her brand's sustainable luxury positioning during virtual meetings.
Next, Amelia opens Zoom Team Chat and needs to communicate with her remote design team about tomorrow's fabric selection meeting. She uses Chat Compose to craft a message, prompting: "Create a professional but creative message for our design team chat about tomorrow's sustainable fabric review session, highlighting the new bio-based materials we'll be evaluating and the decision timeline for the Spring collection." AI Companion generates an engaging message that balances creative excitement with practical scheduling information.
Finally, Amelia opens Zoom Tasks to review the AI-generated action items from her recent meetings and phone calls. She sees tasks automatically created from today's customer consultation ("Follow up on Victoria's custom gown fabric preferences"), yesterday's supplier call ("Research alternative silk suppliers for Spring collection"), and this morning's design meeting ("Finalize sustainable embellishment options"). She assigns the supplier research task to her operations manager, delegates the embellishment research to her lead designer, and keeps the customer follow-up for herself, transforming scattered meeting notes into organized, actionable workflow management.
With AI Companion and Custom AI Companion capabilities, Amelia has revolutionized her approach from overwhelmed entrepreneur to strategic fashion innovator. What once required hours of manual content creation, supplier coordination, and task management now happens seamlessly—her AI Companion for Third-Party Meetings ensures no critical supplier information is lost regardless of platform, while Custom Dictionary captures technical sustainability discussions with precision. Creative workflows accelerate dramatically through Zoom Whiteboard Content Generation and Image Generation, enabling rapid visual concept development that previously required external design resources. Virtual Background Generation maintains her luxury brand positioning in every investor interaction, while Zoom Tasks transforms scattered meeting notes into organized action plans that keep her 25-person team aligned and productive. Amelia now spends more time on strategic design leadership and brand building rather than administrative coordination and manual documentation. The AI doesn't just make her more efficient—it transforms her into a scaling CEO who can maintain the personal touch and creative vision that built LuxeGreen Atelier while managing the operational complexity required for sustainable growth in the competitive luxury fashion market.
If you have broadband installed on any of your porting telephone numbers, you will lose your broadband service once the number port completes.
If you have alarm monitoring services on any telephone numbers, the port request may be rejected until services are moved or ceased.
Yes, you can. Contact your current service provider about forwarding to your Zoom Phone account before submitting your porting request.
Your existing service will work as is during the porting process if you do not make any account changes. Once your number has transferred to Zoom, your old service will no longer function.
Your service must remain active with your current service provider throughout the number porting process. You will be notified by Zoom once your number has successfully transferred, and you will be able to cancel your service with your old service provider at that time. Please note: Zoom cannot cancel your service on your behalf.
Porting can sometimes take longer than the standard timeframes, and there are several common reasons why this happens:The usual suspects:
Legacy infrastructure – your numbers might be on older systems (these are called "Complex Ports")
Provider migrations – your current company might be moving to new systems (common with VoIP/Cloud services)
Company changes – mergers, acquisitions, or name changes can muddy the records
Provider policies – some companies have longer response times built into their business rules
Volume-related delays – sometimes it's a busy period for porting
Port requests get automatically canceled in a few situations:Common cancellation reasons:
No response from you – if we don't hear back within 15 business days, the system cancels the port request automatically
Multiple underlying providers – your numbers belong to different carriers behind the scenes (common with VoIP/Cloud providers)
Multiple locations – your numbers are registered to different addresses
This is actually pretty common and has a technical name: "Residual Translations." Here's what's happening: Your old provider still has your numbers in their network system. They have 24 hours to remove your newly ported numbers, but sometimes they're slow about it. Contact your previous provider directly and ask them to remove the numbers from their network/switch. They can usually fix this quickly once you ask.
Our porting team is proactive about this! We check on your order status with suppliers every four business days and will reach out with updates as soon as we have them. The timing depends on the lead times for your specific region and provider.
Those lead times aren't arbitrary – they're dictated by each carrier's business rules within government regulations. Your current provider might need extra validation time or have complex back-office processes. We work hard to get responses from losing providers with enough advance notice so you can prepare for your port activation day.
Easy! Your phone number status will appear in your Zoom online account about one working day after you submit your porting order – look for "Pending Numbers." You'll also get notifications every 4 business days or whenever we have relevant updates.
Unfortunately, that's not possible. You need to list all the numbers you want to port before submitting the order. If you need to make changes, the entire order has to be canceled and resubmitted, which sets the whole process back to day one.My porting order has a scheduled date, and I want to move it earlier.Expedited porting isn't possible and isn't supported. The dates are set based on carrier availability and regulatory requirements.
We can try, but it's not always possible. Porting reversals (snap-backs) aren't universally supported and are dependent on the losing carrier. If the reversal gets denied, you'll need to contact your old service provider to start a new Local Number Portability (LNP) process to move the numbers back to their system.
Sorry, but we only support port activations on business days, Monday through Friday. No weekend, evening, or holiday port times are available.
Yes, but it's complicated. Rescheduling requires withdrawing the existing order and submitting a new one, which sets the entire process back to day one. It's a best-effort basis, and different countries have different advance notice requirements for changes. Most times, the date on toll-free port requests cannot be changed once FOC is provided.Check the country guidelines for specific timing requirements.
Order denials are actually a normal part of the porting process – don't panic! We'll try to fix most denial reasons without involving you. We'll only ask you to contact your service provider if the denial is due to information mismatches, since we don't have authorization to access your account information due to privacy rules.
We'll try to pull records to resolve the mismatch, but if that doesn't work, you'll need to get the correct address information from your provider and send it to us.
Check your most recent bill for the correct account number and send it to us for resubmission.
All numbers must be active to port successfully. Sometimes numbers appear to be active (i.e. they ring through to the user), but the account status with the current carrier is "inactive" or the numbers are not in a "portable status". This isn't anything that we can assist with, and will need to be worked out directly with the current carrier.Contact your service provider to reactivate the service, then we can try again.
Contact your service provider to get the correct BTN – this is usually the main number on your account that they use to look up your records.
We'll try to pull a copy of your records to resolve this, but if that doesn't work, you'll need to get the exact name from your service provider.
We need to update the request type. If you're keeping the main billing number with your old provider but porting other numbers, you'll need to provide a new main billing number.
Contact your mobile provider to get or update your account PIN. This is required for all wireless number ports, no exceptions.
Contact your service provider to resolve or complete the pending order, then we can proceed.
Contact your provider to remove the lock or freeze – they're the only ones who can do this.
Upload a copy of your bill that's dated within the last 45 days (some regions require 30 days or 3 months – check your specific requirements).
Contact your provider to verify who's authorized to make account changes, then either get authorization for the current person or have an authorized person submit the request.
Content Creation
Document intelligence, visual content generation, collaborative tools, media organization.
Streamlined content development and ideation processes.
Task & Workflow Management
Automated task creation, cross-platform integration, event management tools.
Reduced administrative overhead with intelligent automation.
Setup Requirements
Data Retention
Access Scope
Integration Level
Use Case
Default Zoom Data Sources
- Meeting transcripts
- Zoom Team Chat messages
- Zoom Docs
- Zoom Whiteboard content
- Meeting recordings
- For meeting transcripts, account setting: "Allow meeting hosts to retain and access meeting transcripts" must be enabled.
- No additional user authentication required.
- Follows standard Zoom data retention policies or as configured by admin.
- Only data from the last 90 days is available for reference via search in the AI Companion panel.
- Limited to Zoom platform content.
- Accessible to users with appropriate Zoom permissions.
- Supports configurable scopes of access (e.g., can disable features for Docs, Whiteboard, etc.).
Native Integration: Built-in functionality.
- Meeting Summaries
- Searching
- Content Generation
Email and Calendar Integration (Without Indexing)
- Calendar events
- Email Messages
- Account setting.
- Basic authentication with third-party providers.
- Standard OAuth connection.
- Requires active user authorization for data access.
- No content storage within Zoom Web Services.
- Real-time API calls to external services.
- Data remains on original platforms and cached within Zoom Workplace app on local device.
- Limited to scheduling and notification functions.
- No content search capabilities.
- Basic integration features only.
API Integration: Surface-level connectivity without content indexing.
- Email Compose
- Smart Scheduling
Third-Party Data Sources (With Indexing)
- Calendar events
- Email messages
- Documents (Word, Excel, PowerPoint, Google Docs, Sheets, Slides)
- Cloud storage files
- Account administrator must enable third-party Data Sources setting.
- Individual users must authenticate and connect their Microsoft or Google account.
- Requires active user authorization for data access.
- Only content viewed or edited within last 90 days is indexed and stored.
-Automatically purged after 90 days of inactivity.
- Cross-platform content access.
- Limited to authenticated user's connected accounts.
- Respects original platform permissions.
- Full content search capabilities.
- Supports configurable scopes of access (e.g., calendar, emails, documents).
RAG Module Integration: Content indexed and stored by Zoom for enhanced search and AI responses.
- Comprehensive AI search capabilities
In the dialog box, select the SMS tab.
Search for or check the countries/regions where users can send SMS.
Click Save.
All emojis: All emojis will be enabled and available for users to send through SMS messages.
Selected emojis: Selected emojis will be enabled and available for users to send through SMS messages.
Select the Allow Attachments checkbox to enable it.
Click Save.
Description
DATE_TIME
Universal date and time information.
DRIVER_ID
Driver's license numbers, consisting of alphanumeric characters.
Email addresses (e.g., [email protected]).
INTERNATIONAL_BANK_ACCOUNT_NUMBER
IBAN numbers, with country-specific formats.
IP_ADDRESS
IPv4 addresses (e.g., 198.51.100.0).
LICENSE_PLATE
Vehicle license plates, typically 5–8 uppercase letters/numbers.
MAC_ADDRESS
Unique identifier for network interfaces (NIC).
NAME
Individual's names, excluding titles or organization/address names.
PASSWORD
Alphanumeric passwords (e.g., special#pass).
PHONE
Phone, fax, or pager numbers.
PIN
Four-digit personal identification numbers.
SWIFT_CODE
Standard bank identifier code used for international transfers.
URL
Web addresses (e.g., www.example.com).
USERNAME
Account login names, screen names, nicknames, or handles.
VEHICLE_IDENTIFICATION_NUMBER (VIN)
Unique vehicle identifier numbers (ISO 3779 specification).
BANK_ACCOUNT_NUMBER (Country-specific)
US bank account numbers (typically 10–12 digits). Also recognizes last four digits.
BANK_ROUTING (Country-specific)
US bank routing numbers (typically 9 digits). Also recognizes last four digits.
PASSPORT_NUMBER (Country-specific)
US passport numbers (6–9 alphanumeric characters).
US_INDIVIDUAL_TAX_IDENTIFICATION_NUMBER (Country-specific)
US ITIN numbers (9 digits, starts with "9," fourth digit "7" or "8").
SSN (Country-specific)
US Social Security Numbers (9 digits). Also recognizes last four digits.
- English - Español - Deutsch - 简体中文 - 繁體中文 - Français
- Português - 日本語 - Русский - 한국어 - Italiano - Tiếng Việt
- Polski - Türkçe - Bahasa Indonesia - Nederlands - Svenska




Request to share meeting content cannot be sent until the host has joined the meeting.
Apps sharing meeting content have been disabled.





















Welcome to Zoom Meetings documentation.
This section provides technical implementation details, configuration workflows, and strategic practices designed specifically for administrators deploying Zoom solutions.
You'll find step-by-step procedures that streamline complex configurations, troubleshooting resources that accelerate resolution times, and practical examples that demonstrate real-world application scenarios.
Topics within this section connect technical specifications to measurable business outcomes, enabling you to architect solutions, support client implementations, and identify opportunities for feature expansion. Whether you're conducting initial deployments, optimizing existing environments, or evaluating advanced capabilities for your organization, this documentation serves as your definitive resource for successful Zoom product utilization.
Securing Zoom Meetings ExplainerVirginia
Canada:
Ontario
British Columbia
Mexico:
Querétaro
Brazil:
São Paulo
Netherlands:
Amsterdam
China:
Tianjin
Hong Kong:
Hong Kong
Germany:
Frankfurt
Beire
Singapore:
Singapore
Japan:
Tokyo
Osaka
Australia:
Melbourne
Sydney
Argentina
Brazil
Chile
Colombia
Costa Rica
Ecuador
Mexico
Panama
Peru
Asia-Pacific:
Australia
China* †
Hong Kong SAR
New Zealand
Singapore
Japan
EMEA:
Austria
Belgium
Bulgaria
Croatia
Cyprus
Czech Republic
Denmark
Estonia
Finland
France
Germany
Greece
Hungary
Ireland
Israel
Italy
Latvia
Lithuania
Luxembourg
Netherlands
Norway
Poland
Portugal
Romania
Slovakia
Slovenia
South Africa
Spain
Sweden
Switzerland
United Kingdom
Enter and send the message.
Once complete, other members will be able to reply to the conversation. If another member replies to the conversation to claim it, there is no effect on the caller ID displayed to the other SMS participant.
(Optional) Click the Summarize with AI Companion icon again to regenerate the summary if you are not satisfied with what was generated.

Germany
Japan
Singapore
Switzerland
Voicemail
Videomail
SMS/MMS
Call recordings
Call logs
Call transcripts
MMS media file
Voicemails
SMS/MMS messages
Voicemail transcripts
SMS/MMS logs
Custom greeting prompts
New Zealand: 10:00-11:00 am Local Time
Japan: 9:00-1:00 pm Local Time
Schedule: Monday – Friday (except local holidays)
Number portability checks can only be carried out once the order is submitted.
You may experience some loss of service to incoming calls during the port activation window.
Please select your request type: Zoom Phone Number Porting
Product: Select the target product (Zoom Phone or Zoom Contact Center)
Type of issue: New Number Port
Porting Country: Select Australia, New Zealand, Malaysia, Singapore, or Hong Kong.
Porting Number Quantity (Select the range of quantity of numbers to port):
Subject: Keep as it is.
Description (Please make sure the details below are present for a smooth transaction):
Zoom Phone account number
Additional details and instructions:
Add a note if the order is for the number port.
Attachments:
Completed and signed (hand-signed or digital signature).
Recent telephone bill relating to your porting numbers (should be dated within the last 30 days).
Other documents applicable to the target country (See the section).
Zoom will review and confirm receipt of the request and provide an update as the order progresses.
Zoom will send a request to your service provider to validate the information on the LOA, as the transfer request is also dependent on your service provider. Your request will either be approved or rejected:
Rejected: If rejected, Zoom will inform you that your porting request was unsuccessful. Rejection can occur due to a variety of reasons. Zoom’s porting team will inform you of the rejection reason. Resolution may require action by you or your current carrier. Note: This may add an undetermined amount of time to your porting request
Approved: If approved, Zoom will inform you that your porting order has been approved with a date for when your number will be transferred to Zoom, and the numbers will be available on or before the day of port for you to manage in the Zoom web portal.
Schedule: Monday – Friday (except local holidays)
You may experience some loss of service to incoming calls during the port activation window while the porting numbers are in progress.
Once a porting date is provided, porting will be executed in a 6-hour working time frame (maximum of 3 hours downtime). It is recommended that porting not be scheduled for a Friday or holiday.
If you are porting Contact Center numbers, inform us when you submit your porting request so the Zoom porting team can discuss your requirements.
If you are porting a combination of Zoom Phone and Contact Center numbers, note this in your ticket.
You can use the form below to request a migration from Zoom Phone to Zoom Contact Center. Be sure to inform us of the migration request.
Please select your request type: Zoom Phone Number Porting
Product: Click the drop-down arrow and make one of the following selections:
Zoom Phone: To port phone numbers to Zoom Phone
Zoom Contact Center: To port phone numbers to Zoom Contact Center (Brazil/Mexico Only)
Type of issue: New Number Port
Porting Country: Select the desired country to port
Porting Number Quantity (Select the range of quantity of numbers to port):
Description (Please make sure the details below are present for a smooth transaction):
Zoom Phone Account Number
Additional details and instructions:
Add a note if the order is for the BYOC number port.
Attachments:
Completed and hand-signed .
Recent telephone bill relating to your porting numbers (should be within the last 3 months).
Any other applicable to the country of port.
Zoom will review and confirm receipt of the request and provide an update as the order progresses.
Zoom will send a request to your service provider to validate the information on the LOA, as the transfer request is also dependent on your service provider. Your request will either be approved or rejected:
Rejected: If rejected, Zoom will inform you that your porting request was unsuccessful. Rejection can occur due to a variety of reasons. Zoom's porting team will inform you of the rejection reason. Resolution may require action by you or your current carrier. Note: This may add an undetermined amount of time to your porting request.
Approved: If accepted, Zoom will inform you that your porting order has been approved with a date for when the number will be transferred to Zoom, and the numbers will be available on or before the day of port for you to manage in the Zoom web portal.
Under the Federated Approach, Zoom communicates with multiple AI providers using APIs, including:
Anthropic: Used for content generation and summaries.
OpenAI: Used for content generation and summaries.
In addition to those services, Zoom also communicates with additional third-party providers for specific features, including:
Perplexity AI Services: Deployed for real-time web-based research, current information retrieval, and dynamic fact-checking capabilities requiring internet connectivity.
ElevenLabs: Used for voice generation.
This deployment model provides organizations with:
Complete Feature Access: Full availability of all Zoom AI Companion-powered features without functional limitations.
Intelligent Workload Distribution: Automatic routing of AI requests to the most suitable provider based on task characteristics and performance optimization.
Maximum Flexibility: Ability to leverage specialized AI capabilities from multiple providers within a unified Zoom interface
Scalability Optimization: Dynamic load balancing across multiple AI services designed to provide consistent performance during peak usage periods
Organizations selecting the Federated Approach should evaluate data routing implications, as AI processing may occur across multiple third-party environments. This model is optimal for enterprises prioritizing maximum AI functionality and feature availability while maintaining standard enterprise security protocols.
The Zoom-Hosted Models Plus (ZM+) represents a balanced deployment approach that combines extensive AI capabilities with additional data privacy control measures. Through Amazon Bedrock’s managed AI service infrastructure, Zoom provides access to dedicated instances of third-party language models. This approach enhances data control for organizations while preserving access to diverse AI capabilities.
This model utilizes Amazon Bedrock's managed AI service infrastructure to host Zoom-dedicated instances of third-party language models, and provide organizations with improved data control while maintaining access to diverse AI capabilities.
Through Amazon Bedrock integration, Zoom maintains dedicated, isolated instances of select AI models, creating a hybrid approach that delivers:
Zoom-Managed Model Instances: Data is processed on Zoom-managed instances where information is not sent to third-party model providers.
Multi-Model Support: Access to multiple AI providers through Amazon Bedrock's managed service layer, though with potentially different model versions or configurations compared to direct federated access.
Data Control: Processing occurs within Amazon's enterprise infrastructure, and is controlled by Zoom.
While ZM+ provides substantial AI capabilities, organizations should anticipate that some features available in the Federated Approach may have limited availability or modified functionality with ZM+.
This deployment model serves enterprises requiring enhanced data privacy controls while maintaining access to advanced AI capabilities. Organizations benefit from improved data control without sacrificing the intelligent task routing and multi-model optimization that characterizes Zoom's AI approach.
The Zoom-Hosted Models Only deployment represents the most restrictive AI implementation option, exclusively utilizing a language model hosted privately within Zoom's dedicated infrastructure.
This deployment model operates through:
Zoom-Hosted Models Utilization: All AI processing conducted through Zoom's hosted models.
Dedicated Infrastructure: Processing occurs entirely within Zoom's controlled environment without third-party AI service dependencies.
Simplified Data Flow: Eliminates external AI provider data routing, creating the most straightforward data governance model.
Organizations selecting this deployment model should anticipate:
Limited Feature Set: This model may result in a reduction of available AI features compared to Federated and ZM+ approaches.
Reduced Capability Scope: AI functionality constrained to capabilities supported by Zoom's hosted model.
Performance Variations: Response quality and task handling may differ significantly from multi-model approaches, particularly for specialized use cases.
The Zoom-Hosted Models Only (ZMO) deployment serves organizations with stringent data control requirements, regulatory compliance obligations, or security policies that prohibit third-party AI service utilization. While providing the least flexible AI experience when compared to other deployment models, this approach offers simplified compliance documentation while maintaining the benefits of modern AI.
The following tables summarize the differences between Zoom’s three generative AI service models.
Deployment Model
Architecture & AI Access
Feature Scope
Ideal Use Cases
Federated Approach
Direct connections to multiple providers (Anthropic Claude, OpenAI, Perplexity AI) and Zoom’s self-hosted models
Complete feature access with no functional limitations
Organizations prioritizing maximum AI functionality and feature availability
Zoom-Hosted Models+ (ZM+)
Amazon Bedrock dedicated instances and Zoom’s self-hosted models
Potential feature limitations
Privacy-conscious enterprises requiring advanced AI with additional data governance
Zoom-Hosted Models Only (ZMO)
Zoom's self-hosted models, with no third-party model subprocessors
Potential feature limitations
Organizations with stringent data sovereignty, regulatory compliance, or security requirements
Consideration
Federated
ZM+
ZMO
Feature Completeness
Maximum
May be limited
May be limited
Performance Flexibility
Intelligent workload distribution across multiple models
Multi-model with managed infrastructure
Single-model constraints
Compliance Complexity
Evaluate multi-vendor implications
Simplified through Amazon Bedrock
Streamlined single-vendor model
Beyond generative AI capabilities, Zoom's platform also incorporates sophisticated task-specific artificial intelligence models (i.e., algorithms). These algorithms are designed to enhance core communication functions through automated processing and intelligent optimization, powering features like live transcription or personal audio suppression. These specialized AI systems operate independently of the generative AI deployment models, providing consistent functionality across all Zoom implementations regardless of selected LLM deployment approach.

When planning your Zoom Phone environment, be sure to confirm all network segments (e.g., load balancers, firewalls, custom VLANs, etc.) have sufficient network access as defined in our firewall documentation. Failure to grant necessary connectivity from network segments may impact the user, provisioning, or general Zoom Phone experience.
For Quality of Service (QoS) configurations, Zoom supports two approaches for DSCP tagging: Zoom's built-in application-layer DSCP marking and manual DSCP marking.
Customers can enable Zoom's built-in DSCP marking feature from the Zoom web portal. Once enabled, Zoom Workplace desktop, mobile, and Zoom Rooms apps (version 6.0+), and most Zoom-certified Cisco, Yealink, and Poly IP phones will transmit Zoom Phone audio packets with configured DSCP markings at the application-layer.
Refer to Zoom’s support center for more information on using QoS DSCP markings.
For customers using manual DSCP markings, Zoom recommends the following settings, depending on your organization's QoS strategy.
4-Queue QoS Strategy:
Real-Time Flows
EF
46
Transactional / Mission-Critical Data
AF41
26
Signaling (for Real-Time Flows)
CS3
24
Best Effort
DF
0
12-Queue QoS Strategy:
Network Control
CS6
48
Real-Time Telephony
EF
46
Broadcast Video
CS5
40
Multimedia Conferencing
AF41
34
Zoom Phone is supported over a Virtual Private Network (VPN) connection; however, it is important to note that these connections can reduce call quality, extend latency time, and significantly impact your VPN's bandwidth utilization.
Zoom Recommendation
For the best user experience and call quality, split tunnel all Zoom-related traffic outside your company's VPN. Failure to split-tunnel traffic may overwhelm your VPN's bandwidth and impact the user experience.
DHCP options 66 and 161, if enabled, can interfere with zero-touch provisioning (ZTP) on some devices. Customers are encouraged to leave these options unconfigured if using ZTP extensively, or if using multiple phone device manufacturers within the network.
With Zoom Phone's cloud peering service model (BYOC-C), Zoom Phone customers are free to choose which underlying telephony providers they will work with to meet their coverage needs. To simplify this process, Zoom offers the Provider Exchange, which offers a list of telephony service providers pre-configured and pre-approved to cloud peer with Zoom Phone; all a business needs to do is independently set up their billing and contracts with the provider.
Companies that require broader international coverage beyond what the Zoom Phone Native service model offers can enhance their connectivity by integrating a cloud peering service provider with Zoom Phone Native. This combination can grant access to PSTN services within countries that are not readily available through the Native service model.
Cloud Peering service providers on Zoom's Provider Exchange can support PSTN connectivity within the following countries:
North America:
United States
Canada
Puerto Rico
Latin America:
Argentina
Belize
Brazil
Chile
Colombia
Costa Rica
Dominican Republic
Ecuador
El Salvador
Guatemala
Jamaica
Mexico
Nicaragua
Panama
Peru
U.S. Virgin Islands
Uruguay
Venezuela
Asia-Pacific:
Australia
Brunei Darussalam
Cambodia
China
EMEA:
Albania
Angola
Austria
Bahrain
Extension-to-Extension Dialing
Voicemail
Mobile Device Support
Emergency Calling¹
All Basic features
IP Deskphone Registration
Call Queue Membership
Shared Line Group Membership
Extension-to-Extension Dialing
Voicemail
Emergency Calling¹
Nomadic E911¹ (U.S. and Canada Only)
Zoom Phone supports the following calling plans with the Native service model:
Metered Regional Calling
Metered International Calling
Unlimited Regional Calling for following plans:
U.S. / Canada
UK / Ireland
Australia / New Zealand
Unlimited Regional Calling (within a supported country)
Metered International Calling
All calling plans include a direct inward dial (DID) number. Refer to Zoom's website for additional information on metered rates.
Zoom Phone supports the following add-ons for additional functionality:
Direct Inward Dial / Direct Dial-In Numbers:
Purchase additional Direct Inward Dial (DID) / Direct Dial-In (DDI) numbers for Main Company Numbers or secondary lines.
Toll-Free Numbers:
Purchase additional toll-free numbers, with a range of prefixes available.
International Calling:
Unlimited international calling to more than 15 countries and regions.
Zoom Phone for Microsoft Teams:
Allows Zoom Phone connectivity for users natively within the Microsoft Teams app, as a part of Zoom Phone for Microsoft Teams.
Power Pack:
Enhanced Call Queue analytics and historical insights for call center teams.
Enables Team SMS from Main Company Numbers, Auto Receptionists, and Call Queues.
Enhanced Call Queue capabilities.
Additional reports.
VIP Delegation.
See the for more information.
Additional information available within the Quality of Service tab includes:
Caller
Callee
Call Direction
Call Duration
Bitrate
Packet Loss (Average and Max)
Jitter
Network Delay
Refer to Zoom's support center for more information on viewing the Quality of Service dashboard.
The Usage & Adoption tab within the Zoom Phone dashboard provides call and SMS and MMS usage data for the entire account or a specific Site. With this data, an account admin or authorized user can view the total number of inbound and outbound calls and SMS messages for the account within a chosen time frame, providing insight into usage and adoption rates within the account.
Refer to Zoom's support center for more information on viewing the Usage & Adoption dashboard.
The Phones & Devices tab within the Zoom Phone dashboard provides a global heatmap and graph of phones and devices that are online or offline for the entire account or specific Site, including desk phones, Zoom Phone appliances, and Zoom software (e.g., the Zoom Workplace app).
Refer to Zoom's support center for more information on viewing the Phones & devices dashboard.
The SBCs (Session Border Controllers) tab in the Zoom Phone dashboard offers a global heatmap displaying near real-time and historical data for your SBCs. Real-time insights include active SBCs, and their locations and statuses, while historical data covers inbound, outbound, and normal call attempts for previous periods.
Refer to Zoom's support center for more information on viewing the SBCs dashboard.
The Emergency Tracking tab within the Zoom Phone dashboard provides emergency location tracking data for the entire account or specific Sites. With this data, account admins or users with sufficient role permissions can view metrics to see the number of phone users who have chosen to opt in or out for location sharing in emergency situations. Authorized users can also use this dashboard to re-trigger the in-app pop-up that asks for permission to track the locations for some or all users who have not opted-in.
Refer to Zoom's support center for more information on viewing the emergency tracking dashboard.
The Spam tab within the Zoom Phone dashboard provides spam summaries for all inbound calls to your Zoom Phone account. With this data, account admins or users with sufficient role permissions can view spam detection metrics based on the account's Spam Protection settings, providing insight into how spam calls may impact a specific user or how many times a number is spam-dialing users within the account.
Refer to Zoom's support center for more information on the spam protection setting.
Standard ports (100 numbers or fewer): 4-21 days
Most wireless numbers: 4 business days
Landlines from major providers: 7 business days
Landlines from smaller providers (including Canada): 10-21 business days
Project porting (101+ numbers): 3-4 weeks, depending on complexity
Our Zoom Phone Enterprise Solutions team can help set proper expectations on a case-by-case basis
Activation time: Starts at 11:30 a.m. Eastern Time
Schedule: Monday – Friday (except local holidays)
Sign in to the Zoom web portal
In the navigation menu, click Number Management then Phone Numbers.
In the top-left corner, click Add Number, then click Port Number.
Click the Product dropdown and select the product you want to port the number to (Phone or Contact Center).
Enter the numbers and click Check Portability to confirm validity.
Click Next.
(Optional for Zoom Phone) Enter an existing phone number that will be replaced with the ported number when the porting process is complete.
This allows you to use a temporary phone number during the porting process.
Note: Specifying an existing phone number will not use additional licenses. The number being swapped out will be removed from your account.
Click Next. You’ll see an online Letter of Agency (LOA) form.
Complete the online Letter of Agency (LOA) form using an invoice from the losing carrier:
Billing Telephone Number: Enter your company's phone number as indicated on the invoice.
Do not enter the carrier's phone number.
Do not enter a toll-free number.
Review to minimize delays.
Click Submit.
Zoom will send a request to your previous provider to validate the information on the LOA. If accepted, the Number Portability Administration Center (NPAC) will work with Zoom Phone and the previous provider to activate the pending port. Once approved, the numbers will be available to manage in the Zoom web portal.
Sign in to the Zoom web portal.
In the navigation menu, click Number Management then Phone Numbers > Related Features > Port History.
Next to the order you want to contact the porting team about, click the ellipsis (...)
Click Contact us about this order.
Enter your questions using the message box. Once submitted, the Porting team will reply using email.
Sign in to the Zoom web portal.
In the navigation menu, click Number Management then Phone Numbers.
At the top of the page, click Related Features then Port History.
The status of all self-service ports (placed via the Zoom portal) will appear.
Note: The current or previous toll-free or project ports will not be displayed.
To confirm porting dates, hover your cursor over FOC (Firm Order Confirmation).
Download and complete the required Letter of Agency (LOA).
Submit your order here:
Request type: Zoom Phone Number Porting
Email address: Make sure the email address is accurate
Type of Issue: New Number Port
Porting Country: Select United States or Canada
Description (Please make sure the details below are present for a smooth transaction):
Zoom Phone Account Number
Additional instructions (Optional)
Attachments (must be dated within the last 30 days):
Completed LOA (required)
Current copy of the invoice that has the toll-free number(s)
Zoom will review and confirm receipt of the request and provide an update as the order progresses.
Zoom will send a request to your service provider to validate the information on the LOA, as the transfer request is also dependent on your service provider. Your request will either be approved or rejected:
Rejected: If rejected, Zoom will inform you that your porting request was unsuccessful. Rejection can occur due to a variety of reasons. The Zoom porting team will provide you with the cause and how to resolve the rejection (which may require contacting your current carrier to resolve the issue).
Approved: If approved, Zoom will inform you that your porting order has been approved with a date for when your number will be transferred to Zoom, and the numbers will be available on or before the day of port for you to manage in the .
A project port allows you to move more than 100 pre-existing numbers from another carrier to be used on your Zoom Phone account. For in-depth information, check our support article on Requesting a Project Port (US, Canada, Puerto Rico).










After completing the initial setup process, users can access most of their Zoom Phone settings and features from the Phone tab on the web portal. By default, clicking the Phone tab will open the Settings screen; however, users can also switch to the History, Voicemail, and Recording tabs, which are also available within the Zoom Workplace app.
From the Settings tab on the web portal, users can edit the following settings and features:
Call handling settings determine how calls are routed or handled, and can be specified to operate differently during a user's defined business, closed, or holiday hours. For example, users can customize settings so that they will receive calls on the Zoom Workplace desktop and mobile apps during their defined business hours, but during closed hours, all calls will go straight to their voicemail.
Configurable settings for call handling include:
Business Hours
Holiday Hours
Apps used with Zoom Phone
Refer to Zoom's support center for more information on .
Call delegation (also known as shared line appearance) provides an easy way for phone users to assign others to handle calls on their behalf. This is commonly utilized when an executive assigns calling privileges to an assistant, allowing the assistant to make, answer, or hand off calls on the executive's behalf; however, this feature can apply to other scenarios where line sharing is beneficial as well.
Refer to Zoom's support center for more information on .
The Membership subsection of a user's settings screen displays the user's association with the following features:
Call Queues
Shared Line Groups
Group Call Pickup
Users can additionally opt in or opt out of receiving calls from their associated Call Queues and Shared Line Groups from this page, as well as from the ; however, these opt-in/out privileges do not affect the user's membership status for those groups.
For accounts utilizing the Intercom feature, users have the option to assign a common area phone or another Zoom Phone user for sending or receiving audio intercom calls. Additionally, users must utilize this section to allocate a line key on their desk phone specifically for the intercom feature.
Refer to Zoom's support center for more information on .
From the Desk Phone subsection, users can configure the following settings for a provisioned and associated IP desk phone:
Line Keys & Positions
Phone Screen Lock
Hot Desking
From the Others subsection, users can configure the following settings:
Voicemail & Video Mail
Set Access (to other users)
Call Screening
From the tab, users can access their own recordings and other recordings they have been granted access to, such as from a Call Queue or another user. From this screen, users can also search for or filter their recordings by date, name, extension and number.
Refer to Zoom's support center for more information on .
From the tab, users can access their personal call history, including the ability to filter their calls by date, name, extension, phone number, missed calls, or calls with a special designation, like if it was marked as spam or blocked due to certain conditions. Users can also use this screen to export their call history into a CSV file, block numbers from calling them, or add a client code for tracking.
Refer to Zoom's support center for more information on .
From the tab, users can access their personal and shared voicemail messages, including the ability to filter their messages by date, name, extension, and phone number. Users can also filter messages marked as read, unread, and follow up, in addition to messages with a special designation, including circumstances where a call may be marked as spam or blocked due to certain conditions.
Users and admins can use the following settings to prevent uninvited automated meeting tools, dial-in users, and third-party room systems from joining Zoom Meetings.
is a virtual staging area that stops participants from joining a meeting until the meeting host admits them. Waiting Room has several in this document that can be enabled on multiple levels within your Zoom account, ensuring that Waiting Room is active for all meetings or for specific users.
The following Waiting Room settings can be enabled by individual users in their personal settings, as well as at the group and account levels by administrators and owners:
Account owners and admins can manage telephone numbers for Zoom Contact Center and Zoom Phone through the Number Management section located in the left navigation menu of the Zoom web portal. This feature provides admins with a unified experience across Zoom products, providing consistent control over access and roles.
Account owner or admin privileges
The following sections describe Zoom AI Companion features and functionality integrated with Zoom Meetings.
The In-Meeting Questions feature allows participants to discreetly ask Zoom AI Companion questions about the meeting within the AI Companion side panel while the meeting is in progress. Using the meeting’s real-time transcript, Zoom AI Companion provides participants with contextual and relevant answers, including timestamped citations from the transcript for additional context and clarity.
With this feature, users can submit their queries directly to AI Companion, without interrupting the flow of the ongoing conversation and is particularly beneficial in large meetings or fast-paced discussions where participants may need clarification without disrupting the speaker. This feature can also help late joiners quickly catch up on missed points by offering AI-generated responses based on what has already been discussed.
This section provides an overview of core features, dataflows, diagrams, and options for administrating Custom AI Companion.
Real-Time Interactive
CS4
32
Multimedia Streaming
AF31
26
Signaling (for Real-Time Flows)
CS3
24
Transactional / Mission-Critical Data
AF21
18
Management / OAM Traffic
CS2
16
Bulk Data
AF11
10
Scavenger Class
CS1
8
Best Effort
DF
0
Provide a target port date if applicable (see the General guidelines section).
Let us know if any of the porting numbers are for Contact Center.
You can use this form to request a migration from Zoom Phone to Zoom Contact Center (if available).
Nomadic E911¹ (U.S. and Canada Only)
Receive Inbound Transferred/Forwarded PSTN Call
Call Hold
Call Transfer / Forwarding (Internal Extensions Only - No PSTN)
Auto Receptionist
Barge / Monitor / Whisper
Hoteling / Hot-Desking
Call Recording
Call Park
Outbound PSTN Dialing
SMS / MMS²
Searchable in Dial-by-Name Directory
Receive Inbound Transferred/Forwarded PSTN Call
Call Hold, Transfer, and Forwarding (Internal Only)
IP Deskphone Registration
Hoteling / Hot-desking
Outbound PSTN Dialing
Japan
Company: Enter the name of your company as indicated on the invoice. Do not enter the name of the carrier.
Authorized Person: Enter the name of a person authorized to request a port of the numbers.
Address: Enter the service address. The service address may be different from the billing address.
Account Number (Optional): Enter the account number with your current carrier as indicated on the invoice. This is required for all wireless ports and some VOIP providers.
PIN (Optional): Enter the PIN or password provided by your current carrier. This is required for all wireless ports and some VoIP providers.
CRD (Optional): Specify the customer-requested date, which is the preferred date for porting the number. This date is the best effort and is not guaranteed. If no date is specified, Zoom will request the earliest possible date.



Indonesia
Jamaica
Kazakhstan
Kyrgyzstan
Macau
Malaysia
Nauru
New Zealand
Philippines
Singapore
South Korea
Taiwan
Thailand
Timor (East)
Uzbekistan
Vietnam
Belgium
Bosnia
Bulgaria
Croatia
Cyprus
Czech Republic
Denmark
Estonia
Finland
France
Georgia
Germany
Greece
Hungary
Iceland
Ireland
Israel
Italy
Japan
Kenya
Latvia
Lithuania
Luxembourg
Macedonia
Malta
Moldova
Monaco
Netherlands
Norway
Poland
Portugal
Romania
Russia
Serbia
Slovakia
Slovenia
South Africa
Spain
Sweden
Switzerland
Turkey
Uganda
Ukraine
United Kingdom
Zoom Phone Appliance Apps
Zoom Phone Desktop Apps
Zoom Mobile Apps
Call Handling Ring Mode
Simultaneous
Sequential
Max Wait Time
When Busy on Another Call:
Call Waiting
Forward to:
Voicemail / Videomail
Another Extension
External Contact
External Number
Play Message and Disconnect
Play Busy Signal
When a Call is Not Answered:
Forward to:
Voicemail / Videomail
Another Extension
External Contact
External Number
Play Message and Disconnect
Disconnect
Allow Callers to Reach an Operator:
User
Zoom Room
Common Area Phone
Greeting and Voicemail Instruction
Agents They Can Monitor
Agents That Can Monitor Them
Zoom Phone PIN
Subscription Confirmation (Reports)
Hold Music
Audio Prompt Language
Default Voicemail Transcript Language
Call Date and Time
MOS
Codec Used
Headset Used
Microphone Used
ISP Used
Caller
To use Custom AI Companion’s third-party indexing services functionality, users must first have an active account with the third-party index provider. They must also have the necessary permissions to authorize that account for integration with their Zoom account, enabling secure access to indexed content during AI interactions.
When a user submits a query through Zoom AI Companion, the service performs a dual-pathway information retrieval process:
Querying accessible documents within the Knowledge Base for relevant content matches.
Leveraging third-party AI models and services.
When Knowledge Base matches are identified, the system extracts only the specific relevant text portions from the matched documents and ingests these targeted text segments into the model processing pipeline. The model then analyzes, synthesizes, and reformulates these selected document excerpts alongside its base knowledge to generate a comprehensive response that incorporates the pertinent textual information from your organizational documents.
For example, if a user asks AI Companion "How long of a break am I entitled to?", the system will attempt to match this query against any relevant human resource documents uploaded to the account or connected through the third-party index. When a match is identified, the system extracts only the specific relevant text portions from the matched HR documents—such as the particular policy section addressing break entitlements—and ingests these targeted text segments into the model processing pipeline. The model then processes these selected document excerpts in conjunction with model capabilities to analyze and synthesize the information. When responding, AI Companion is designed to provide the most relevant response to the user's query, incorporating the pertinent information from your organizational documents.
To obtain AI Companion responses based on specific account resources instead of general model responses in a query, users can instruct AI Companion to look for answers within an account’s Knowledge Base by clicking the + button and specifying the Knowledge Base they intend to search.
Alternatively, users can also instruct AI Companion to look for answers within an account’s index by clicking the + button and specifying their index.
This section covers the user experience for generating a Custom Avatar and Avatar Clips.
The Custom Avatar Clips feature lets users generate video clips using a selection of over 15 default avatars and seven virtual backgrounds. These avatars and backgrounds can be easily combined to match the scene or style a user prefers. For a more personalized experience, users can also create a custom avatar in their own likeness and apply any available background.
To create a custom avatar in a user’s likeness, the user must record a short clip of themselves reading a script
To create a custom avatar in a user’s own likeness, they must record a clip of them reading a short script. This clip is used to capture the user’s voice and appearance that will be used in future clips that feature the user’s likeness.
Heads Up
The quality of the user’s recorded clip will impact the quality of their custom avatar’s clips. If a user records their sample clip in a dry, monotonous tone, their custom avatar’s clips will reflect these similarities. For best results, users should record clips in a tone and manner that reflect their natural speaking voice and with natural eye contact to the best of their abilities.
After a user selects their preferred avatar and background, users can input their transcript and click the Create Clip button to generate their video. After several minutes, varying by the length of the transcript, their clip will be available.
Custom clips can also be translated into up to two additional languages when being submitted
Prior to submitting a clip, users can also select two additional languages to translate the clip into. This will result in three separate clips being created.
Multiple translations will consume additional time per-language
When users generate clips in multiple languages at once, each clip will consume additional time per requested language. This may fluctuate between languages, as some languages may take longer or shorter to process through the content.
For example, if a user creates an approximately two-minute clip in three languages, they will consume approximately six minutes of content.
This section covers the user experience for using the Custom Dictionary feature.
Custom Dictionary, once configured by an account admin, automatically applies to all users when hosting meetings on the account, regardless of individual license types. AI Companion will automatically reference the Custom Dictionary as part of the transcript generation process for any hosted meeting, helping ensure consistent terminology recognition and transcription accuracy across the organization without requiring users to perform any specific actions or configuration steps.
Custom Dictionary will not apply to meetings hosted by external users
If a user joins a meeting hosted by an external account (i.e., outside the company account), their organization's Custom Dictionary will not apply to the meeting transcript.
This section covers the user experience for using the Custom Meeting Templates feature.
To use a Custom Meeting Summary Template, AI Companion’s Meeting Summary feature must be enabled during the meeting—either by pre-configuring it in advance or by turning it on after the meeting begins.
Refer to Zoom’s support center for more information on enabling AI Companion’s Meeting Summary feature.
When scheduling a meeting, licensed Custom AI Companion users can pre-define the custom meeting summary template they’d like to apply to the meeting.
Alternatively, users can retroactively apply a custom meeting summary template after the meeting. To do this, users should locate the summarized meeting either from the Meeting Summaries section of the Zoom web portal, or through the meeting’s meeting card screen within the Zoom Workplace app. Once located, users can select their preferred summary template from the provided drop-down menu.
This section covers the user experience for using AI Companion with third-party meetings.
Zoom AI Companion identifies third-party meetings by scanning a user’s calendar through Zoom’s calendar integration service. By analyzing scheduled events, AI Companion can recognize when a meeting is hosted on a third-party platform, such as Microsoft Teams or Google Meet, and proactively prepare to join and assist, provided the feature allow AI Companion assistant to join third-party meeting is enabled.
Users have the flexibility to control how AI Companion joins third-party meetings, either by setting it to automatically join all eligible external meetings identified through their integrated calendar or by choosing to enable it manually for individual meetings when needed.
Users can manually invite AI Companion to third-party meetings by opening the calendar event within the Zoom Workspace client, clicking the AI Companion dropdown, and enabling Invite AI Companion.
AI Companion will only join a meeting at the scheduled started time
Zoom AI Companion will only join a third-party meeting at its scheduled start time according to the user’s calendar. For instance, if a meeting is postponed or moved up by 30 minutes and this change is not reflected within the calendar event, AI Companion may not be in attendance at the start of the meeting unless the calendar event is updated to reflect the new start time.
If no one joins the meeting, AI Companion will automatically disconnect after 20 minutes of no transcription
In the event participants don’t join a scheduled third-party meeting, AI Companion will still join the scheduled meeting as-intended. However, if no audio data is transmitted for 20 minutes, AI Companion will automatically disconnect from the meeting.
Users can configure AI Companion in the Zoom web portal to automatically notify the meeting host and participants when it’s scheduled to join an upcoming meeting. This helps provide additional transparency by letting everyone know ahead of time that AI Companion will be present, offering support like note-taking or summarization during the session. Alternatively, users can leave the setting off and it will automatically join the meeting at the designated start time.
In the event a meeting host or attendee does not want AI Companion present within a third-party meeting, the meeting host or a similarly-authorized user may manually remove it from the meeting using the third-party platform's meeting participant management tools. Alternatively, the user that invited AI Companion to the meeting via the Zoom Workplace calendar interface can untoggle the same option to remove it from the meeting.
This section covers the user experience for using AI Companion with third-party applications.
Before users can utilize any third-party application or connector skills, an account administrator must authorize the application for use on the account level.
Once a third-party skill application is approved for use within an account, each user must individually authorize the third-party application for use with their Zoom account. After authorizing, users may begin using third-party skills through the AI Companion side panel.
After a user successfully integrates their Zoom account with a third-party skill application, they may begin using the service through the AI Companion side panel by using the in-menu options, or through casual conversation.
\
As a Zoom Admin, sign in to zoom.us.
Click the Settings tab on the left-hand sidebar.
Ensure you are on the AI Companion tab by clicking AI Companion at the top of the screen.
Click the General tab in the secondary sidebar to jump to the appropriate settings section.
Click the toggle button next to AI companion panel in Zoom Workplace.
Settings for Zoom Meetings are found in the AI Companion settings in the secondary sidebar.
Meeting Summary
To manage the setting for meeting summaries, perform the following steps:
As a Zoom Admin, sign in to zoom.us.
Click the Settings tab on the left-hand sidebar.
Ensure you are on the AI Companion tab by clicking AI Companion at the top of the screen.
Click the Meeting tab to jump to the appropriate settings section.
Click the toggle button next to Meeting summary with AI companion, along with any other settings you are managing.
In-Meeting Questions
To manage the In-Meeting Question setting, perform the following steps:
As a Zoom Admin, sign in to zoom.us.
Click the Settings tab on the left-hand sidebar.
Ensure you are on the AI Companion tab by clicking AI Companion at the top of the screen.
Click the Meeting tab to jump to the appropriate settings section.
Click the toggle button next to Allow users to ask AI companion questions about the meeting.
Smart Recording
To manage the Smart recording setting, perform the following steps:
As a Zoom Admin, sign in to zoom.us.
Click the Settings tab on the left-hand sidebar.
Ensure you are on the AI Companion tab by clicking AI Companion at the top of the screen.
Click the Recordingtab to jump to the appropriate settings section.
Click the toggle button next to Smart recordings with AI Companion, along with any other settings you are managing.
Settings for the Team Chatare found in the AI Companion settings in the secondary sidebar.
Team Chat Compose with AI Companion
To manage Team Chat Compose, perform the following steps:
As a Zoom Admin, sign in to zoom.us.
Click the Settings tab on the left-hand sidebar.
Ensure you are on the AI Companion tab by clicking AI Companion at the top of the screen.
Click the Team Chat tab to jump to the appropriate settings section.
Click the toggle button next to Compose with AI Companion.
Thread Summary with AI Companion
To manage the Thread Summary feature, perform the following steps:
As a Zoom Admin, sign in to zoom.us.
Click the Settings tab on the left-hand sidebar.
Ensure you are on the AI Companion tab by clicking AI Companion at the top of the screen.
Click the Team Chat tab to jump to the appropriate settings section.
Click the toggle button next to Thread summary with AI Companion.
Quick Scheduling
To manage the Quick Scheduling feature, perform the following steps:
As a Zoom Admin, sign in to zoom.us.
Click the Settings tab on the left-hand sidebar.
Ensure you are on the AI Companion tab by clicking AI Companion at the top of the screen.
Click the Team Chat tab to jump to the appropriate settings section.
Click the toggle button next to Quick schedule with AI Companion.
Sentence Completion
To manage the Sentence Completion feature, perform the following steps:
As a Zoom Admin, sign in to zoom.us.
Click the Settings tab on the left-hand sidebar.
Ensure you are on the AI Companion tab by clicking AI Companion at the top of the screen.
Click the Team Chattab to jump to the appropriate settings section.
Click the toggle button next to Sentence Completion with AI Companion.
Quick Reply
To manage the Quick Reply feature, perform the following steps:
As a Zoom Admin, sign in to zoom.us.
Click the Settings tab on the left-hand sidebar.
Ensure you are on the AI Companion tab by clicking AI Companion at the top of the screen.
Click the Team Chattab to jump to the appropriate settings section.
Click the toggle button next to Quick reply with AI Companion.
Settings for Clips are found in the AI Companion settings in the secondary sidebar.
Smart Recording (title, description, tags, etc.) with AI Companion
To manage the Smart Recording feature (automatically generate title, description, tags, etc.), perform the following steps:
As a Zoom Admin, sign in to zoom.us.
Click the Settings tab on the left-hand sidebar.
Ensure you are on the AI Companion tab by clicking AI Companion at the top of the screen.
Click the Clipstab to jump to the appropriate settings section.
Click the toggle button next to Generate title, description, tags, and chapters with AI Companion.
Create Clips with AI Companion
To manage the Clip Creation feature, perform the following steps:
As a Zoom Admin, sign in to zoom.us.
Click the Settings tab on the left-hand sidebar.
Ensure you are on the AI Companion tab by clicking AI Companion at the top of the screen.
Click the Clipstab to jump to the appropriate settings section.
Click the toggle button next to Create clips with AI Companion.
Create Clips using Custom Avatars
To manage the Clip Creation with Custom Avatars feature, perform the following steps:
As a Zoom Admin, sign in to zoom.us.
Click the Settings tab on the left-hand sidebar.
Ensure you are on the AI Companion tab by clicking AI Companion at the top of the screen.
Click the Clips tab to jump to the appropriate settings section.
Click the toggle button next to Create clips using custom avatars.
Settings for Whiteboard are found in the AI Companion settings in the secondary sidebar.
Whiteboard content generation with AI Companion
To manage the Whiteboard Content Generation feature, perform the following steps:
As a Zoom Admin, sign in to zoom.us.
Click the Settings tab on the left-hand sidebar.
Ensure you are on the AI Companion tab by clicking AI Companion at the top of the screen.
Click the Whiteboard tab to jump to the appropriate settings section.
Click the toggle button next to Whiteboard content generation with AI Companion.
Settings for Tasksare found in the AI Companion settings in the secondary sidebar.
Task Creation and Management with AI Companion
To manage the Task Creation and Managementfeature, perform the following steps:
As a Zoom Admin, sign in to zoom.us.
Click the Settings tab on the left-hand sidebar.
Ensure you are on the AI Companion tab by clicking AI Companion at the top of the screen.
Click the Zoom Taskstab to jump to the appropriate settings section.
Click the toggle button next to Task creation and management with AI Companion.
Users can also choose to enable Waiting Room while scheduling individual meetings:
Requiring a meeting passcode is an integral security measure to help prevent uninvited participants from attempting to join meetings.
These settings can be enabled by individual users, or at the group and account levels by admins and owners:
Account owners and admins can lock settings to require passcodes for all meetings on their account and configure minimum passcode requirements.
Automatically generated meeting IDs are unique, randomly generated meeting ID numbers that temporarily expire after a meeting ends. This will prevent users from returning to existing meeting IDs and potentially misusing them. An automatically generated meeting ID number will not be reused for thirty days after a meeting has ended. If a meeting with an automatically generated ID number is restarted by the host, the thirty-day blackout period for that ID number will restart.
Select the Generate Automatically option under the Meeting ID section while scheduling a meeting from the Zoom desktop client, mobile app, or web portal.
Your Personal Meeting Room is a virtual meeting room permanently reserved for you that you can access with your Personal Meeting ID (PMI) or personal link, if applicable. You can start instant meetings with your PMI, or you can schedule a meeting that uses your PMI.
Your Personal Meeting ID (PMI) is ideal for use with people you know and meet with regularly. Because it is always accessible with the same Meeting ID and personal link, your PMI should not be used for back-to-back meetings or with unknown people outside of your organization. Limiting the use of your PMI to interactions with trusted users will help keep it from being distributed for potential misuse.
The following PMI settings can be enabled by individual users in their personal settings, as well as at the group and account levels by administrators and owners:
The Only authenticated meeting participants and webinar attendees can join meetings and webinars option requires participants to sign in to Zoom before they can join a Zoom Meeting or Webinar once enabled. Hosts can further restrict meeting participants and webinar attendees to Zoom users whose email addresses match a certain domain. This can be useful if you want to restrict your participant list to verified users or users from a specific organization. These settings can be enabled by individual users, or at the group and account levels by admins and owners:
If authentication is required, participants without a Zoom account will not be able to join the meeting or webinar.
The image watermark feature superimposes an image consisting of the viewing participant’s email address onto the shared content and over their video in most video layouts (Speaker, Gallery, Side-by-side). You can also display several instances of the watermark so that it’s more visibly apparent across the video or shared screen. This feature can help deter the unintended capture of content shared during meetings.
When a participant shares their screen during a meeting or webinar, the email of the user who is viewing the content will be patterned across the shared content, as well as on the video of the other visible participants. For example, if [email protected] is viewing shared content, the watermark of [email protected] will be patterned across the shared content and the videos of the participants as shown in this image.
During Zoom Meetings, participants and automated meeting tools may request the ability to start a local recording that will be stored on the computer of the participant making the request. The meeting host can grant or deny any local recording requests sent to them.
The Who can request host permission to record setting allows hosts to restrict the ability to record locally for external meeting participants. This setting can be enabled at the account level and the group level by the account owner or administrators.
When this setting is enabled, the record button will be removed from the participant control menu for external participants who have joined the Zoom Meeting.
Audio watermark, or audio signature, embeds a user’s personal information in the received audio as an inaudible watermark. This means that if someone records the meeting with either a separate microphone or a third-party tool and shares the audio file without permission, Zoom can assist with determining which participant was responsible. The audio watermark feature can only be enabled by account owners and administrators through the Account Management settings.
By selecting Computer Audio as your desired audio type for Zoom Meetings, you can disable all meeting participants’ ability to dial in by telephone/PSTN. This may be an effective option if your organization does not use telephone or third-party audio to join meetings and would like to block any uninvited participants from trying to dial in.
Audio Type can be selected by individual users, or at the group and account levels by admins and owners:
Confirm that your organization or external meeting participants are relying on something other than telephone/PSTN dial-in options to join your meetings before selecting Computer Audio as your preferred audio type.
Meeting hosts who are not using Waiting Room can block dial-in users who intend to call in to a meeting by selecting the following setting within the Zoom web portal. This setting is in the meeting security section and can be enabled by individual users, or at the group and account levels by admins and owners:
End-to-end encryption (E2EE) for meetings provides additional protection when needed and requires all meeting participants to join from the Zoom desktop client or mobile app, or a Zoom Room.
This setting is in the meeting security section of the Zoom web portal and can be enabled by individual users, or at the group and account levels by admins and owners:
Users will not be able to use any of the following technologies to join meetings when end-to-end encryption is enabled:
Telephone/PSTN
Third-party SIP/H.323 devices
On-premises configurations (Zoom Meeting Connector and Virtual Connector)
Zoom web client
Third-party clients leveraging the Zoom Web SDK
The following features can not be used when end-to-end encryption is enabled:
Translation
Captions
Archiving
AI Companion Summary
AI Companion Questions
With the Zoom Node platform, you can deploy the Zoom Meetings Hybrid module, which is an on-premises, hybrid solution that hosts a meeting’s or webinar’s audio, video, and screen sharing streams within a corporate network. Zoom Meetings Hybrid can do this in two distinct modes: hybrid mode and private mode, with both modes offering local survivability. Private mode is similar to end-to-end encryption since the encryption key is generated on premises and is not shared with the Zoom cloud. Private Mode offers a bit more flexibility than end-to-end encryption because recording can be done via the Zoom Recording Hybrid module. Also, administrators can explicitly choose to allow apps, Zoom Realtime Media Streams, and cloud services like AI Companion, though in that case, the encryption key is shared with those services. For more information about Zoom Meetings Hybrid, refer to the Zoom Node Explainer.
Zoom Meetings is a powerful tool for collaboration among your peers and Zoom users that you know and trust. However, if you intend to hold a public event with unknown participants, please consider using Zoom Webinars or Zoom Events.
Zoom has a robust set of security features designed to help hosts manage and safeguard their event experience. A Zoom Webinar or Event host may choose to manually approve or decline anyone who registers. Hosts can also remove an attendee or lock a webinar or event to prevent additional attendees from joining once the webinar or event has started. In addition, webinar and event hosts can choose to require passcodes or authentication for an added layer of security.
A Zoom Phone or Zoom Contact Center license
Zoom Phone toll-free license to obtain a toll-free phone number
User assigned a calling package to be assigned a phone number
Sign in to the Zoom web portal with admin privileges.
Navigate to Number Management → Phone Numbers.
You'll see all your numbers with their details.
For specific information in the Phone Number Table, please refer to our support article.
Sign in to the Zoom web portal with admin privileges.
Go to Number Management → Phone Numbers.
Click Add Number (top-left corner) and choose your option:
Get Number: Obtain a new number from Zoom (useful for expanding to new countries with Virtual Service numbers)
Port Number: Move existing numbers from another provider
BYOC Number: Upload your numbers from your third-party carrier provider
Users outside US, Canada, and New Zealand
You'll need to provide business address verification documents when buying toll or toll-free numbers.
After obtaining a phone number, you can assign it or add it as an entry for a voice or SMS flow. Alternatively, you can add a phone number as an entry point, using the Flows page or flow editor.
Sign in to the Zoom web portal with admin privileges.
Navigate to Number Management → Phone Numbers.
Find your Contact Center number and click the ellipsis (...)
Click Assign and choose your destination.
(Optional) Select Voice Flow and pick from the dropdown menu.
Save and you're all set!
After obtaining a phone number, you can assign it (allowing callers to directly dial a number to reach a phone user, call queue, auto receptionist, common area phone, or Zoom Rooms) or add it as an entry for SMS. Messaging is inactive until you activate it by creating a 10DLC campaign, getting it approved, and assigning that phone number to the campaign. After assigning a phone number, you can re-assign it to another extension.
Navigate to Number Management → Phone Numbers.
Find your Zoom Phone number and click the ellipsis (...)
Click Assign and choose your destination.
Search by name or extension to find exactly what you need.
Save and you're all set!
Navigate to Number Management → Phone Numbers.
Select the phone number you want to assign using the checkbox.
Click SMS Campaigns → Assign.
Choose your campaign from the dropdown menu or create a new one.
Complete the Letter of Authorization (LOA) form when prompted.
Submit and you're all set! Allow one business day for activation.
Go to Number Management → Phone Numbers.
Find the number you want to delete.
Click the three dots (...) next to it.
Select Delete and confirm in the pop-up.
Note: This removes all assignments and frees up the associated licenses
Go to Number Management → Phone Numbers.
Click Import and choose your option:
Zoom Phone number assignment: Upload a CSV file to batch assign numbers to extensions, such as users
SMS Campaign assignment: Upload a CSV file to assign numbers to SMS campaigns
Complete Authorization: A signed Letter of Authorization (LOA) is required before numbers can be enabled for SMS campaigns
BYOC Numbers: Upload a CSV file to add BYOC numbers to customer Zoom accounts
Zoom Phone BYOC emergency address: Upload a CSV file to batch confirm BYOC numbers emergency address
Zoom Phone BYOC emergency address change notification: Add email addresses to the Target Email List for address change notifications
Navigate to Number Management → Phone Numbers.
Click Export to download a CSV with all your number details.
Access additional tools via Related Features:
Navigate to Number Management → Phone Numbers.
Select Related Features:.
Plan details: See your SKUs and licenses
Main Company Number: Set your primary Zoom Phone number
Port History: View all your US/Canada self-service port orders
Port-out Verification: Set up webhook verification codes
Business Address & Documents: Manage addresses and upload required documents
Letters of Authorization: Download LOAs and view the number's contact information and submission date for the LOA
Select multiple numbers (using checkboxes) to perform batch operations:
Navigate to Number Management → Phone Numbers.
Select the phone number you want to assign using the checkbox.
At the top of the page, you can click the following actions:
Delete: Remove multiple numbers simultaneously
Caller ID Name: Set caller ID for multiple numbers (U.S./Canada only, excludes toll-free)
SMS Campaigns: Assign multiple numbers to campaigns
Site Management: Move unassigned Zoom Phone numbers between sites
BYOC Address Confirmation: Confirm emergency addresses for applicable BYOC-Premises numbers
Call Authentication: Select Enable or Disable for the , which allows customers to use TransUnion’s Spoof Call Protection and Branded Calling features
Caller ID timing note: Phone service providers update caller IDs at different times, so your caller ID name might not show immediately for recipients.
Refer to Zoom’s support center for more information on using in-meeting questions with AI Companion.
After a meeting concludes, the Meeting Summary feature automatically generates a structured summary, capturing key discussion points, decisions, and action items without requiring a manual note-taker. Using the meeting’s transcript as reference, Zoom AI Companion creates clear and concise summaries that can be shared with the meeting host and invitees.
With this feature, users receive a well-organized summary that highlights essential details, making it easier to stay aligned on next steps. This is especially useful for teams managing multiple meetings or for invitees who joined late or missed the discussion. Meeting summaries can also be shared afterward, enhancing productivity and streamlining follow-ups.
The following example demonstrates a standard post-meeting summary email a user may receive.
Additionally, customers using Zoom Docs can automatically convert meeting summaries into collaborative working documents, streamlining follow-up coordination and action item management. The following example shows how a meeting summary transforms into an editable Zoom Doc for team collaboration.
Refer to Zoom’s support center for more information on using meeting summaries with AI Companion.
The ZPLS module is an on-premises appliance that allows users within the same site to place phone calls to each other when Zoom data centers are unreachable. This creates a survivability solution for business continuity in the event of a network outage.
Within this guide, a site is a specific term used within Zoom Phone that groups users together under a common identity, like an office location. For some customers, multiple buildings are represented by a single site; for others, each building in a campus may constitute its own site. Customers should be aware of their existing or potential site configurations when considering the ZPLS module due to design considerations mentioned within this article.
ZPLS also supports cross-site calling when ZPLS appliances and their associated sites are connected through a common network
On its own, a ZPLS appliance (also referred to as a module i.e., a Zoom Node module) provides survivability to users within a common Zoom Phone site. However, multiple ZPLS modules connected through a local, campus, or wide area network can support cross-site communication, connecting users from different sites during a survivability event so long as the internal network remains operational.
Customers can integrate the ZPLS module with a session border controller (SBC) for external public switched telephone network (PSTN) calling when Zoom data centers are unreachable. This allows users with PSTN numbers provided by Zoom or third-party BYOC carriers to receive inbound calls from external parties when call forwarding for survivability is enabled in the cloud, and to place external phone calls regardless of local network conditions or Zoom data center availability; however, internal calling may be limited by site design.
During a routine boot-up process, a Zoom Phone client downloads the DNS SRV records of primary and secondary SIP zones (registration points) located within Zoom data centers. However, for survivability-enabled sites with a ZPLS module, supported client devices are additionally configured with a third SRV record, pointing to the IP Address of the site’s module.
In the course of normal operations, the ZPLS module is generally inactive within the local network and does not engage in call handling. Instead, the ZPLS module sends routine OPTIONS pings to site-specific SIP zones to monitor active connectivity between locations.
A ZPLS module only enters survivability mode when the routine OPTIONS pings between the ZPLS module and the primary and secondary SIP zones fail. Client devices that lose connection with the SIP zones at the same time as the ZPLS module will register to the module, providing there is IP connectivity between the devices. If the ZPLS module maintains connectivity to the Zoom Phone cloud, it will not accept SIP registrations.
In the event site-specific SIP zones are unreachable, the approximate device failover time to a ZPLS module is within three minutes. However, this time may vary depending on the number of concurrent devices attempting to register to each ZPLS module.
When Zoom desktop clients failover to survivability mode, users receive an alert informing them that they have no internet connection, but phone service is still available.
Once services are restored, users receive a connection restoration alert.
Users involved in an active call when disconnected from their site’s SIP zones will hear a fast busy signal before their call is disconnected. After the disconnect and failover to survivability mode, users must manually re-establish their call.
During a survivability event, devices with phone numbers registered to the Zoom Phone cloud are not reachable due to the loss of internet connectivity. However, ZPLS customers with an SBC and an independent carrier can establish call forwarding rules in the web portal for direct inward dialing. When enabled, call forwarding rules redirect inbound calls to a Zoom Phone-registered number, to a separate number bound to a customer’s on-premises PSTN trunk. This allows customers the flexibility to purchase numbers directly from Zoom while still being able to answer calls directly at a site that has lost connectivity to the cloud.
For example, if a user has the phone number X55-555-5555 registered to Zoom Phone and the user’s site enters survivability mode, the user’s phone number is unavailable from the perspective of the Zoom Cloud. If call forwarding is enabled and their number is called, Zoom Phone can forward the request to their designated forwarding phone number (e.g., X11-111-1111) through the PSTN to the customer’s SBC. Consequently, external callers can reach users within an affected site undergoing a survivability event.
ZPLS modules support Survivability Distribution Groups (SDGs) for nuanced call routing configurations during a survivability event. With SDGs, a business can route internal and inbound PSTN calls to an individual user, a group of users (similar to a call queue or shared group), an IVR menu, another phone number, or, if necessary, another SDG.
Although SDGs do not provide the same full-featured functionality as standard-operation call queues, shared line groups, or auto receptionists, SDGs can continue to support a business’ critical call routing needs until normal operations are restored.
An SDG can be added using the Add Route Group configuration within the admin portal.
During survivability mode, internal phone calls between users are protected by Secure Real-time Transport Protocol (SRTP) using AES-128 or 256 encryption, depending on .
Once the client devices and ZPLS module have re-established a connection with the site-specific SIP zones, the approximate recovery fallback time to normal operations is five minutes. This includes a period of time to ensure network connections are stable in the event of intermittent or partial network recovery (flapping). If network connectivity is intermittent, the client devices and ZPLS module will remain in survivability mode until connections are determined to be stable.
After the ZPLS module has successfully exited survivability mode and SIP zone connectivity is stable, the module will upload call detail records (CDRs) for all calls made in survivability mode. These records are marked in reports as calls that were completed while in survivability mode.
Updates to a site configuration through the Zoom web portal, including adding or modifying users or devices, are synchronized to the ZPLS module once every 10 hours. If a downtime event occurs before new configuration changes are synchronized with the ZPLS module, the module will use the last known configuration.
Customers can simulate failover events for a site by enabling Testing Mode from the web portal. Once testing mode is enabled for a specific site, the ZPLS module must be rebooted to accept client registrations. After, users that sign out and back into their desktop client will automatically register to the ZPLS module as long as testing mode is enabled.
While Testing Mode is active, the ZPLS module will operate as if a failover event is occurring. Internal users can place calls to other users within their site. Additionally, outbound and inbound calls will route through the connected SBC if configured, and inbound calls will follow call forwarding rules if configured and enabled.
After disabling Testing Mode, the ZPLS Module must be rebooted to resume normal network operations.
The following list contains supported features from the ZPLS module when survivability mode is engaged:
Calling Features
Internal Extension Dialing
Full Extension Dialing with Site Code
Dial From Call History
DTMF (RFC 2833)
Transfer & Routing
Consult Transfer
Blind Transfer
Emergency Location Identification Number
Inter-ZPLS Module Calling
Survivability Distribution
Route to User
Route to Group Members
Route to Phone Number*
Route to IVR
*Requires SBC & BYOC Integration
The following list contains features that are not supported when survivability mode is engaged:
Add/Remove Contact
Voicemail
Escalate to Multi-Party Conference (4+ Users)
Escalate to Meeting
Refer to our support center for a list of and .
The following diagram demonstrates the network ports and data flows used with a ZPLS module and an SBC configuration.
The following table lists the network ports utilized by Zoom Phone during normal operations when there is no disruption with connectivity to the cloud. Refer to our support center for a used for the Zoom Phone cloud.
The following table outlines the TCP and UDP ports utilized by Zoom Phone when failover to ZPLS is active due to disruption with connectivity to the cloud.
Customers integrating the ZPLS module with an SBC for external dialing during a survivability event must enable the required ports for premises peering. After configuring a route group, the necessary IP addresses for the route group are available on the web. To access the IPs, perform the following steps:
Sign into the Zoom web portal.
Under the Phone System Management sub-menu, select Company Info.
Click Account Settings
Locate the option for Route Groups. Click Manage to load a new page.





























Auto Receptionist
Call Queue
Shared Line Group
Call Forwarding*
Inbound/Outbound PSTN*
Contact Search/Dialing (first 25,000 contacts)
Dial By Name
Mute/Unmute
Hold/Resume Call
Call Park
Sequential Ringing
Simultaneous Ringing
Audio Prompts
Switch to Carrier
Nomadic e911 Calling
Speed Dial
Monitoring (Barge/Monitor/Whisper)
Call Delegation
Intercom
End-to-End Encrypted Calling (E2EE)
Auto Receptionist
Call Queue
Zoom Phone Client
Zoom Phone Cloud
390
Directory Search from Deskphones
UDP
Zoom Phone Client
Zoom Phone Cloud
20000-64000
SRTP Media Traffic
TCP
ZPLS
Zoom Phone Cloud
5091
SIP Options Ping (Keepalive)
TCP
ZPLS
Zoom Phone Cloud
443
Node / OS Management Traffic
TCP
ZPLS
Zoom Phone Cloud
9669
Call History / Recovery Sync
TCP
SBC
Zoom Phone Cloud
5061
SIP Signaling Traffic (BYOC)
UDP
SBC
Zoom Phone Cloud
20000-64000
SRTP Media Traffic (BYOC)
ZPLS
SBC
5061
Directory Search from Deskphones
UDP
ZPLS
SBC
20000-64000
SRTP Media Traffic
On the following page, locate the intended Route Group, and hover over the "i" icon.
Enable the specified IP address and ports within the window as necessary within your network.
TCP
Zoom Phone Client
Zoom Phone Cloud
5091
SIP Signaling Traffic
TCP
Zoom Phone Client
Zoom Phone Cloud
443
Web Traffic - Client Settings
TCP
Zoom Phone Client
ZPLS
5091
SIP Signaling Traffic
UDP
Zoom Phone Client
ZPLS
20000-64000
SRTP Media Traffic

TCP
TCP
UK: 30 days
South Africa: 45 days
Rest of EMEA: 30-60 days
Porting windows can last up to 3 hours. The below times are approximate.
UK: 9:00 am Local Time
Ireland: 11:00 am Local Time
Germany: 6:00-8:00 am Local Time
Italy: 6:00 am Local Time
Bulgaria: 9:30 am - 12:30 pm Local Time
Rest of EMEA: Time slots provided upon port confirmation
Schedule: Monday – Friday (except Bank Holidays)
Copy of telephone bill dated within the last 3 months is required.
The information you provide must match exactly what's on record with your current provider.
LOA must be hand/wet signed and dated within the last 3 months. Electronically signed LOAs are not accepted in most EMEA countries.
Please do not redline or amend the LOA template; the format and wording should not be changed.
Your phone provider's name is required on the LOA.
LOA needs to be in EU date format (dd-mm-yyyy).
In some European countries, the address noted on the LOA must match the country of the porting telephone numbers. Please check the porting guidelines for further information.
All porting numbers need to be noted on the body of the LOA rather than as attachments.
DDI blocks of numbers may require porting in full as some countries do not allow blocks/ranges of numbers to be split. Refer to our for more information.
Number portability checks can only be carried out once the order is submitted. There may be times when providers advise that numbers as non-portable.
You may experience some loss of service to incoming calls during the port activation window while the porting numbers are in progress.
Porting usually takes an average of 30 days from the day of submission.
Do not cancel your service with the losing supplier, as we cannot port inactive numbers.
Plan ahead and minimize change requests to reduce risks.
Port activations take place during business hours only in the local country of port.
In most European countries, the address noted on the LOA must match the geographic area code of the porting telephone numbers.
We cannot port international mobile numbers in EMEA countries .
Some carriers do not split blocks/ranges of numbers, therefore they must be ported in full.
LOAs must be hand/wet signed or electronically signed using DocuSign or Adobe.
Note in your request whether the incoming numbers are Zoom Phone, Zoom Contact Center, or a mix of both.
Download and complete the required Letter of Authorization (LOA) from the respective country.
See the porting guide if you need help.
Use one LOA template per supplier / per site address for all European countries.
If you currently have trial/temporary numbers and would like to swap them when the port is complete, please complete the . Numbers swapped in will be a like-for-like replacement of the numbers swapped out.
Submit your order and make sure to follow the steps below:
Please select your request type: Zoom Phone Number Porting
Your email address: Type your email address and make sure the email address is accurate.
Product: Click the drop-down arrow and make one of the following selections:
Zoom will review and confirm receipt of the request and provide an update as the order progresses. Please ensure you have sufficient licenses in available status in your Zoom Phone account, one license is required per porting number.
Zoom will send a request to your service provider to validate the information on the LOA, as the transfer request is dependent on your service provider. Your request will either be approved or rejected:
Rejected: If rejected, Zoom will inform you that your porting request was unsuccessful. Rejection can occur due to a variety of reasons. The Zoom porting team will provide you with the cause and how to resolve the rejection (which may require contacting your current carrier to resolve the issue).
Approved: If approved, Zoom will inform you that your porting order has been approved with a date for when your number will be transferred to Zoom, and the numbers will be available on or before the day of port for you to manage in the .
For up-to-date information, check our EMEA Requirements table and a list of additional documents needed per country for Local number Porting.
Download and complete the required Letter of Authorisation (LOA) from the respective country.
See the porting guides if you need help.
If you currently have trial/temporary numbers and would like to swap them when the port completes, please complete the Number Swap Sheet. Numbers swapped in will be a like-for-like replacement of the numbers swapped out.
Submit your order and make sure to follow the steps below:
Please select your request type: Zoom Phone Number Porting
Your email address: Make sure the email address is accurate
Product: Click the drop-down arrow and make one of the following selections:
Zoom Phone: To port phone numbers to Zoom Phone
Zoom will review and confirm receipt of the request and provide an update as the order progresses.
Zoom will send a request to your service provider to validate the information on the LOA, as the transfer request is also dependent on your service provider. Your request will either be approved or rejected:
Rejected: If rejected, Zoom will inform you that your porting request was unsuccessful. Rejection can occur due to a variety of reasons. The Zoom porting team will provide you with the cause and how to resolve the rejection (which may require contacting your current carrier to resolve the issue). Note: This may add an undetermined amount of time to your porting request.
Approved: If approved, Zoom will inform you that your porting order has been approved with a date for when your number will be transferred to Zoom, and the numbers will be available on or before the day of port for you to manage in the .
Refer to our support article for specific LOAs for the EMEA Region and a list of additional documents needed per country for Toll-Free porting.

This section provides an overview of Custom AI Companion's features.
Zoom’s Custom Meeting Summary Templates allow account admins to tailor meeting summaries to fit different needs and audiences. Instead of relying on a standard format, organizations can create templates that highlight the most relevant details for specific use cases.
For example, a Customer Success team could implement a Customer Experience Review Summary template that automatically organizes discussions around key performance metrics including Customer Satisfaction (CSAT) scores, Net Promoter Score (NPS) trends, Customer Retention Rate analysis, and churn risk indicators. This template could structure summaries to capture quarterly performance comparisons, identify emerging satisfaction patterns, highlight successful retention strategies, and document action items for addressing customer experience gaps.
Custom Dictionary enhances AI Companion's ability to recognize and incorporate your organization's specialized terms, industry jargon, and acronyms, resulting in more accurate and contextually relevant meeting transcripts and summaries.
When utilized, Zoom’s live transcription service will reference the account’s Custom Dictionary during the live transcription process, resulting in more accurate meeting transcripts and summaries.
This feature is especially beneficial for industries that rely on specialized language, such as healthcare, finance, or manufacturing sectors, where precision in communication is crucial. A Custom Dictionary is designed to help AI Companion adopt the unique vocabulary of the organization, improving the relevance and quality of AI-generated responses.
For example, imagine a legal team using AI Companion to generate a meeting summary from a strategy session where one attorney says, “We need to prepare a memorandum regarding the Daubert standard and its applicability in this tort case.” Without a legal custom dictionary in place, it can be difficult to accurately identify uncommon words like “Daubert,” potentially rendering it as “Dahlberg” or “dog bird,” which could lead to confusion or misinterpretation. However, with a domain-specific dictionary that defines terms like “Daubert,” “tort,” and “voir dire,” AI Companion is better equipped to recognize and transcribe specialized language.
Organizations can currently incorporate up to 1000 specialized terms into their Custom Dictionary for English-language meetings.
Custom AI Companion’s Custom Avatars feature enables users to create a personalized virtual avatar using their recorded video and voice, or select from a list of pre-provided avatars. Once an avatar is selected or generated, users can upload a script that is transformed into a Zoom Clip, with the avatar narrating the content in a natural voice and, if applicable, the user’s likeness.\
This feature is especially useful for businesses looking to scale video production efficiently, allowing users to create training materials, lessons, and presentations with just a transcript—reducing production time while maintaining quality, personalized video content.
For example, a compliance officer may need to remind employees of quarterly training requirements. Rather than recording a new message or sending another lengthy email, they use their custom avatar to generate a brief, direct video reminder from a script—quickly reinforcing the message while keeping communication efficient and repeatable.
Custom avatars also support multiple languages, enabling users to upload a script in any supported language and generate output in the same language, or produce a copy in an alternative language. For example, if a user records their custom avatar likeness in English, they can upload a script in Spanish or Russian and will receive a clip spoken in the corresponding language that reflects their authentic voice. Alternatively, a user can upload a script in English, and also receive copies of the clip in Spanish or Russian. The current list of supported languages includes:
Users with a Custom AI Companion license are allotted up to six minutes of Custom Avatar Clip generation each month. This allocation resets on each account’s monthly billing date, so if an account’s billing date falls on the 15th, users who generate their allotment of clips on or before the 14th will receive a refreshed allotment the following date.
Additional Custom Avatar Clip time can be purchased with an add-on
Customers interested in granting certain users more than six minutes of clip generation time per month may purchase an add-on for additional clip generation time. For more information on this add-on, speak with your Zoom account team.
Knowledge Bases empower organizations to connect internal documents, resources, and/or existing search infrastructure (e.g., a third-party solution with indexing capabilities) to Zoom AI Companion, enabling it to generate more contextually relevant responses. Custom AI Companion supports connecting these knowledge sources through the following methods:
Direct Data Uploads: Upload documents directly in AI Studio.
Third-Party Cloud Storage: Connect Zoom AI Companion to supported cloud storage providers such as Google Drive or OneDrive. Access to connected resources can be configured using user account mapping based on the third-party platform’s built-in permissions, or through Zoom User Groups.
Web Sync: Link publicly accessible web pages (e.g., help centers, knowledge bases) to Zoom AI Companion through a sitemap, link discovery, or URL upload list.
When using any of these methods, organizations can leverage resources like internal documents, knowledge bases, product information, and proprietary content to help AI Companion generate responses that better reflect organizational knowledge and help maintain consistency across communications.
For example, when a user asks, "What company holidays do we have off this year?" or "What's our competitive positioning against Vendor X?", AI Companion can either search through uploaded company documents to provide detailed responses or query connected resources to retrieve relevant matches and contextual explanations with source material references, depending on the organization's chosen approach.
Refer to Zoom’s support center for more information on within AI Studio.
In short:
Direct Data Uploads allow admins to directly upload documents into Zoom.
Web Sync lets AI Companion index and retrieve information from your organization’s publicly accessible websites or knowledge bases.
Third-Party Cloud Storage connects AI Companion directly to your cloud-storage providers (e.g., Google Drive, OneDrive) for seamless document retrieval.
Third-Party Index Connections
The following examples provide additional context for understanding this nuance.
Example - Direct Data Uploads
Imagine you’ve given AI Companion a curated library of company documents. If a user asks, “Where can I find the NDA template for external contractors?” or “Where’s the documentation for setting up a new VPN connection?”, AI Companion searches across the full set of documents your company has uploaded to the Knowledge Base through AI studio. If the user has access to any matching files, AI Companion will generate a summarized, contextual response, along with a link to the source for easy access.
In this scenario, Zoom AI Companion has access to the full content of the documents your company has provided—unlike an indexed system that instead provides AI Companion with relevant portions of text from documents. However, document visibility and responses are still governed by user group permissions, helping ensure that users only receive information they’re authorized to access.
Example - Web Sync
Think of AI Companion as an automated information retrieval system with access to your company's publicly available product information, marketing website, or external help center for new or updated information. When a user asks, “What integrations does our new analytics product support?” or “How can our customers reset their account passwords?”, AI Companion accesses your company’s synced external web pages. Because Web Sync regularly indexes specified external URLs—such as your help articles or public product pages—AI Companion will reference and contextualize the latest published web content , providing users with more contextually relevant responses alongside direct links to original web-based resources.
In this scenario, Zoom AI Companion reliably delivers up-to-date information sourced from your organization’s external-facing content, helping ensure accuracy and consistency in customer-facing communications.
Example - Third-Party Cloud Storage
In a scenario where AI Companion has been granted direct access to your department's organized files stored in a cloud provider like Google Drive or OneDrive, users can query their document repositories through natural language interactions. When a user asks, “Do we have a slide deck template for new business proposals?” or “Where can I find the quarterly financial reports?”, AI Companion searches through the documents stored in your connected cloud storage accounts. If it locates a matching artifact the user has access to, its response will include summarized context generated from the matching files, alongside direct links for immediate access.
In this scenario, Zoom AI Companion operates as an intelligent bridge between users and your existing cloud storage systems, transforming passive document repositories into proactive knowledge sources that can help enhance user productivity.
Example - Third-Party Index Connection
Imagine AI Companion reaching out to a dedicated resource—like a company librarian—who can reference any internal documents made available to them. If a user asks, “Who is responsible for vendor onboarding, and what’s the process?” or “Where can I find our competitive positioning against Vendor X?”, AI Companion passes the request to the company’s index (“librarian”). The index searches through the documents it has access to (based on the underlying data the requesting user is permitted to access and noting that not all company records may be included) and, if the user is authorized, returns relevant matches along with a portion of text from each document that’s most relevant to the request. AI Companion then generates a summarized, contextual response, along with a link to the source for easy access.
In this scenario, Zoom AI Companion interacts only with the information the company’s index is authorized to access based on the user’s permissions, and receives relevant portions of the matching documents.
Zoom’s Custom AI Companion supports integrations with third-party applications, enabling AI Companion to actively perform work on users' behalf across external systems without requiring platform switching or manual intervention. Through intelligent automation capabilities, AI Companion can execute comprehensive workflows—such as creating, reading, updating, deleting, and searching Jira tickets—while users remain focused on their primary tasks within Zoom Workplace.\
This functionality transforms workflow efficiency by enabling AI Companion to act as an intelligent intermediary that helps manage cross-platform operations, centralizes task execution, and eliminates the friction of juggling multiple applications. Rather than simply providing information about external systems, AI Companion becomes an active participant in business processes, autonomously handling routine operations and complex multi-step workflows across integrated platforms.
For example, when project challenges are discussed during a Zoom meeting, users can prompt AI Companion to analyze the post-meeting transcript to identify actionable items and suggest creating a Jira ticket. Upon user request, the system populates ticket fields with contextually relevant discussion details—including issue descriptions, priority indicators, and participant assignments—streamlining project management workflows while ensuring comprehensive information capture without manual data entry requirements.
Although the list of supported third-party applications will change over time, Zoom currently supports AI Companion apps with the following services:
Refer to Zoom’s support center for more information on .
Custom Agents extend the power of AI Companion by allowing organizations to create purpose-built assistants designed for their specific needs. The strength of each Custom Agent lies in its ability to combine targeted Knowledge Bases—such as internal documentation, process outlines, or support content—with Tools that enable it to perform intelligent actions across a wide range of applications. Together, these elements let Custom Agents operate with focus and autonomy, surfacing information and completing tasks on your behalf within your connected systems.
While the AI Companion Panel can already summarize information, search connected content, and perform tasks across various apps, Custom Agents introduce a new level of focus and efficiency. Each Custom Agent can be purpose-built to operate within a focused domain, drawing from a defined set of tools and knowledge bases. Within that scope, it can reason through complex workflows—performing multiple actions, using different tools, and adapting its steps as it progresses toward completion. Whether it’s managing customer data in Salesforce, surfacing related knowledge base articles, creating tasks in Jira, or combining all three, Custom Agents are designed to support complex, dynamic processes from start to finish.
The value of Custom Agents is made apparent in how they handle day-to-day work. Each Custom Agent can be paired with Hero Prompts—predefined actions or conversation starters created by admins or builders—that make it easy to launch common workflows instantly, without extra input or clarification. With a single click, users can trigger a sequence of actions or retrieve exactly what they need, all without manually steering the conversation.
While the AI Companion Panel provides general adaptability, Custom Agents deliver precision. They can be crafted for a distinct purpose, combining Knowledge Bases, Tools, and Hero Prompts to act as an intelligent, task-oriented extension of your team. Together, they form a connected ecosystem of assistants that streamline work across every system and workflow.
For example, the following image demonstrates the execution of a multi-step process, requiring the Custom Agent to search Jira for information, post the results to a Slack channel, and then create a Zoom Doc for tracking.
10DLC (10-Digit Long Code) is a compliance framework that ensures that mobile carriers know who is sending text messages from business phone numbers and for what purpose. Mobile carriers in the US and Canada (AT&T, Verizon Wireless, T-Mobile, US Cellular, and others) now require 10DLC compliance before messages can be sent via application-based services like Zoom Phone and Zoom Contact Center. This requirement helps build trust between businesses and consumers by reducing spam and ensuring that messages come from registered businesses.
There are three major steps that comprise 10DLC registration: brand creation and approval, campaign creation and approval, and assigning phone numbers to your campaign. The following sections will guide you through 10DLC registration for the mobile carrier’s review.
To use SMS with Zoom Phone, you must first create a 10DLC brand to register your business information with Zoom Phone carriers. Creating and verifying your brand’s identity gives carriers confidence that the SMS sender is legitimate. Your brand must be created and approved before creating an SMS Campaign. By default, you will be allowed to create one brand in the Zoom web portal. If you need to create more than one brand, contact your Zoom account manager for more information. Please note that each additionally registered brand will incur a monthly cost.
Zoom Phone: To port phone numbers to Zoom Phone
Zoom Contact Center: To port phone numbers to Zoom Contact Center
Type of issue: New Number Port
Porting Country: Select the desired country to port
Porting Number Quantity: Select the range of quantity of numbers to port
Subject: (Keep it as-is)
Description (Please make sure the details below are present for a smooth transaction):
Zoom Phone Account Number
Additional details and instructions
Add a note if the order is for the BYOC number port.
Let us know if any of the porting numbers are for Zoom Contact Center.
You can use this form to request a migration from Zoom Phone to Zoom Contact Center.
Attachments:
Completed and hand/wet signed or electronically signed using DocuSign or Adobe LOA. See the Requirements table below.
Recent telephone bill relating to your porting numbers' invoice (should be dated within the last 3 months).
Any other required documentation applicable to the country of port.
Zoom Contact Center: To port phone numbers to Zoom Contact Center
Type of Issue: New Number Port
Porting Country: Select the desired country to port
Porting Number Quantity: Select the range of quantity of numbers to port
PCI-PAL: Please select Yes if you require PCI-PAL (PCI-PAL provides a secure payment solution), select No if you do not require this.
Subject: (Keep it as-is)
Description (Please make sure the details below are present for a smooth transaction):
Zoom Phone Account Number
Additional instructions (Optional)
Let us know if any of the porting numbers are for Zoom Contact Center
You can use this form to request a migration from Zoom Phone to Zoom Contact Center
Attachments:
Completed and hand/wet-signed LOA.
Recent telephone bill relating to your porting numbers, which should be dated within the last 3 months.
Any other required documentation applicable to the country of port.
Chinese (Simplified)
Chinese (Traditional)
Dutch
English
French
German
Indonesian
Italian
Japanese
Korean
Polish
Portuguese
Russian
Spanish
Swedish
Turkish
Asana
Box
Coda
Confluence
Google Drive
HubSpot
Jira
Notion
Workday
OneDrive
Salesforce
ServiceNow
Slack
Zendesk

Important
You will need a valid Tax ID to complete Brand registration. If you do not have a valid Tax ID, you will need to get one. Social Security Numbers are not accepted.
Sign in to the Zoom web portal as an admin with the privilege to edit account settings.
In the navigation menu, select Number Management, then click SMS Campaigns.
You will be presented with a link to review the 10DLC Brand and Campaign creation checklist.
Select the following confirmation checkbox: I confirm that I have read and understood the 10DLC Campaign creation checklist.
Click Create 10DLC Brand to begin creating the Brand.
On the Brand Summary page, enter the following:
Legal Company Name
DBA/Brand Name (if applicable). This name will be used in your opt-in, opt-out, and help messages that are sent to SMS recipients.
Your company’s Legal Form. Choose from the following options in the dropdown: Private Profit, Public Profit, Non Profit, Government.
Country/Region of Registration. The following countries are supported: United States, Canada, Australia, Belarus, Chile, Croatia, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malaysia, Malta, Netherlands, New Zealand, Norway, Poland, Portugal, Romania, Saudi Arabia, Singapore, Slovakia, Slovenia, Sweden, Taiwan, and United Arab Emirates.
State/Province
Tax Number, VAT Number ID, or EIN (Employer Identification Number). This applies to the United States and Canada only. Businesses in Canada need to use their Business Identification Number (BIN).
Your Business Location Address
Once complete, click Continue.
In the Brand Details, complete the brand details and contact information, and enter the following:
Website: Enter your website and include https://
Vertical Type: The vertical type is your company’s industry.
Stock Exchange (if applicable)
Stock Symbol (if applicable)
Once complete, click Continue.
Review your brand information and ensure that all information is correct.
Important
Once you submit, you cannot edit your brand. Please make any necessary changes before submitting. If you need to make changes after submitting, you must delete the brand and re-submit due to legal restrictions and carrier visibility.\
By selecting “Submit”, you are E-signing to create your account with our carriers and building a new Brand to be used for SMS.
Once ready, click Submit. In most cases, brand approval takes 1–2 hours.
You can check the status of your Brand by accessing SMS Campaigns in the Zoom web portal. Under My Brand, view the status beneath the Brand Status column. The brand status will show as Pending, Rejected, or Active (if approved). The person who submitted the 10DLC Brand will receive an email notification when the brand is rejected or approved.
Once your 10DLC Brand is approved, you can create the SMS campaign that will be used to assign your company phone numbers and enable SMS. By default, you are allowed to create one campaign for Zoom Phone. However, if you are also a Zoom Contact Center or Zoom Meetings customer, you may create two campaigns, meaning one for Zoom Phone and one for Zoom Contact Center or Zoom Meetings. If you need to create more than one campaign for Zoom Phone, please contact your account manager for details. There will be a monthly cost for any additionally registered Zoom Phone campaigns.
The following steps outline the process for completing the Campaign Details portion.
Checklist Requirement
Perform the following steps:
Access SMS campaigns in the Zoom web portal, then click Create SMS Campaign. You will be directed to the Checklist Requirement page, where you will be presented with a link to review the 10 DLC Brand and Campaign creation checklist.
Click the 10DLC Campaign creation checklist link. You are required to open and view the link before continuing.
After opening and reviewing the link, select the I confirm that I have read and understood the 10DLC Campaign creation checklist checkbox. Once this is done, the campaign details section will display. On this page, you will complete the requirements and details.
Configure your SMS campaign in the following sections.
Campaign Details
In the Campaign Details section, complete the following information:
Campaign name: Enter a name for your campaign.
Description: Describe how your organization uses SMS. Provide details that cover who will send messages, who will receive messages, what kind of content is being sent, what kind of content will not be sent, and the frequency of sending these messages.
Campaign type: Choose the product for which you are creating a campaign. Ensure that you choose the correct campaign type as per the product you intend to use SMS with. Click the dropdown and select the application.
Consent to SMS Messaging
In the Consent to SMS Messaging section, provide details of how you are gathering consent from SMS recipients.
Under How are you gathering consent to send SMS/MMS?, select the following options that apply to your campaign.
Complete the description for each option and explain how you gather consent in your own words. You can only send texts to consumers who have provided you consent. Provide as much detail as possible. If you collect any phone numbers from your website, you must select the website option and provide details of how you gather consent. Otherwise, your campaign will be rejected.
Website Requirements
In the Website Requirements section, complete the following information:
Privacy Policy: Enter a link in the URL field to the privacy policy section of your brand website. Your brand website must have a third-party privacy policy to include a notice for text messaging to prove to the carrier that consumer data and consent are being handled properly.
Select the following checkbox: I confirm that I have added the required privacy policy to my brand website and understand that my campaign will be rejected without this update.
Website/Written Form: Choose an option that best describes how you use web/written forms to collect phone numbers:
I use a web/written form to collect phone numbers for this campaign. I also confirm that I have added this SMS disclosure below the web/written form.
I do not use web/written forms to collect phone numbers for this campaign.
User Permissions
In the User Permissions section, select how you want to enforce Opt In and Opt Out for your numbers associated with the campaign:
Under Outbound messages to unknown numbers, choose an option for outbound messages to unknown numbers (i.e., numbers you are texting for the first time):
Allow my users to send any message: This is the default option. Users can send any message to any number if this option is selected. They will receive a warning on the Zoom Workplace app before sending the message that states: We do not know if you have gained consent from this number. Please ensure that you have consent to text this number. Please note that this warning will not prevent the message from being sent.
Require my users to send the Opt-in message and wait for the Opt-in response: This option is where the user will be forced to send a message requesting opt in before being able to send any other message. The recipient must respond to the Opt-in message with the Opt-in keyword. Only then can subsequent messages be sent.
Prevent my users from sending any outbound message: This option prevents users from sending any outbound messages.
Under Inbound messages from unknown numbers, determine what your users can do if a new number has initiated a conversation:
Allow my users to send any message: This default option allows you to respond to an incoming message as soon as it is received. Inbound SMS is deemed as consent from the sender.
Automatically send a message that asks them to Opt in and wait for the Opt-in response: Once an inbound message has been received, an automated Opt-out message is sent and the recipient must respond with the Opt-in keyword before the user can send them any other messages. This provides an additional layer of compliance for inbound messages.
Opt-In Messaging
In the Opt-In Messaging section, set up message templates.
Opt-In Message: This is the first message that will be sent to the recipient to request opt-in consent. A carrier-approved message is pre-populated. Click Edit to customize the opt-in message, then click Save.
Message Preview: Click Edit to preview the message for the opt-in message. This message cannot be edited except for the additions.
Additions: Enter your additional message or customization for the opt-in preview or message attachment. This content will be added to the message preview and appear after the sentence that ends with your brand name.
Will you need SMS on more than 49 numbers?
Under the option for Will you need SMS on more than 49 numbers? select Yes or No. If yes, provide justification. The approval process could take up to two weeks.
Once complete, click Continue. You will be directed to the Carrier Questions section.
In the Carrier Campaign Questions section, you will provide information about your company’s SMS message categories and related information. Complete the following information:
Will messages include:
URL links?: Select Yes or No.
Phone Numbers?: Select Yes or No.
Age-gated content?: Select Yes or No.
Lending or Loan Arrangements?: Select Yes or No.
In the Sample Messages section, enter the following:
In Sample Message 1 box, type your first sample message. Ensure that the name of your business/brand is mentioned. Otherwise, your campaign will be rejected.
In the Sample Message 2 box, type your second sample message. Ensure that the name of your business/brand is mentioned. Otherwise, your campaign will be rejected.
(Optional) Click + Add another Sample Message to add additional sample messages
Click Continue. You will be directed to the Confirmation section.
Perform the following steps:
On the Confirmation page, review the Requirements & Details and Carrier Questions sections.
Click Edit to make any changes, then click Save if you make any changes.
Once your review is complete, click Submit. Allow up to 4 weeks for carriers’ review and approval.
You can check the status of your campaign by accessing SMS Campaigns in the Zoom web portal. Under SMS Campaigns, view your brand’s current status beneath the Campaign Status column. The status will show as Active when it is approved.
Once your campaign is approved and 10DLC is enabled, you can assign phone numbers to the campaign.
In the Zoom web portal, select Number Management, then click Phone Numbers.
To the left of the phone numbers, select the check box of the number you desire to assign.
Select the SMS Campaigns tab at the top of the page. In the dropdown, select Assign.
In the Choose Campaign dropdown, select the campaign to which you want to assign the phone number.
Click Continue.
You will be prompted to complete an LOA. Select Continue to LOA to view and complete the form. Once the LOA is submitted, please allow up to three business days for SMS/MMS to be activated.
Once activation is complete, SMS is ready to be utilized. Please ensure that users in need of SMS capabilities have been assigned a compatible Zoom Phone calling plan and a 10-digit phone number (that has also been assigned to a campaign). Please see the following Admin Controls section to ensure SMS is enabled for the correct users or groups.
Authored by Jakob Ganschow
These pages provide an introduction to the Zoom Mail and Zoom Calendar Services, not to be confused with the Zoom Mail and Zoom Calendar Clients. This section primarily details an overview of the Zoom-provided services for email and calendaring.
Zoom Mail is Zoom's full-featured email service, designed to centralize communication workflows within a single, cohesive platform alongside Zoom's comprehensive suite of collaboration tools—including Zoom Meetings, Zoom Phone, Zoom Contact Center, and Zoom Team Chat. Zoom Mail provides secure email transportation methods, including end-to-end encrypted emails between two active Zoom Mail users on the same account (as further described below), and password-expiring, server-side encryption for external email recipients. Standard email protocol—plain text delivered over a TLS connection—is also supported.
Zoom Mail Services offers users three encryption methods for protecting emails:\
End-to-end encryption, using local, device-generated keys—optional and exclusively available between active Zoom Mail users on the same account; availability depends on a variety of factors including whether sender and receiver have already generated encryption keys, Zoom client version, and configuration of user or account level settings.
Server-side encryption, with password-expiring emails.
Encryption in transit using TLS, securing plaintext emails as they travel between servers (how most email services work).
Alongside Zoom Mail Service, users gain access to Zoom Calendar Service—a fully integrated calendar within the Zoom client that enables scheduling meetings and appointments, either for themselves or, with the proper permissions, on behalf of others.
The Zoom Mail and Calendar Services supports core user and business-grade email features and functionalities, including but not limited to:
Customers hosted on Zoom’s European or United States global infrastructure can currently purchase Zoom Mail and Calendar Services. Zoom Mail and Calendar Services are not available for accounts hosted on other region-specific infrastructure (e.g., India, Australia, Singapore, etc.).
By default, Zoom Mail Service supports end-to-end encryption (E2EE) for emails sent between two active users on the same account, as long as both the account and users are configured to allow it. With end-to-end encryption, messages are encrypted on the sender's device and can only be decrypted on the recipient's device—no one else, including Zoom, can read the content. If Device Managed Encryption is enabled, however, authorized account admins may also have access.
When sending an end-to-end encrypted email, the Zoom Workplace app clearly marks outgoing messages accordingly. These messages are protected with client-generated encryption keys, transmitted over TLS 1.2, and stored on Zoom's servers in encrypted form, helping ensure their content remains inaccessible to Zoom and unauthorized parties, though designated Device Managed Encryption administrators can access encryption keys to decrypt content when necessary—for example, for user recovery or legal discovery purposes.
More information on Zoom Mail Service’s encryption design can be found in our .
By default, end-to-end encrypted emails can only be exchanged between users in the same account. However, if admins from two different domains enable the Encryption across domain option in Domain Management, users in those domains can send end-to-end encrypted emails to each other.
If this setting is not enabled, encrypted emails sent across accounts will use the password-expiring encryption method as the fallback.
As part of Zoom Mail Service’s design, every authorized device generates its own device-specific keys, in addition to per-user keys that are shared across all authorized devices. These per-user keys are what enable encryption and decryption of email content on each device.
When a new Zoom Mail Service device is added, fresh per-user keys are created and distributed to all devices, ensuring equal access to new email data. For security, however, newly added devices do not automatically gain access to older data or the keys that protect it.
To access historical emails, an already-authorized device must share the relevant per-user keys with the new device. If no existing device grants access, the new device cannot decrypt or view past emails. When access is granted, the devices complete a private key exchange using each device’s unique device-specific key pair.
Any authorized device can revoke another device’s access to Zoom Mail Service content. In the event a device’s access is revoked, the device’s keys are invalidated and per-user keys are rotated between all remaining authorized devices.
Users should securely store a backup key to restore access if all authorized devices are lost, since each new device must be approved by one that’s already authorized. To reduce this risk, Zoom Mail Service prompts users to download a backup key during setup, as Zoom cannot add devices or grant access on behalf of users.
If enabled on the account, admins can help restore user access to device-encrypted emails through the Device Managed Encryption (also referred to as encryption escrow) feature. Device Managed Encryption lets authorized admins securely access the keys that protect encrypted messages. With this access, they can approve new devices or restore encryption access if someone loses their existing device, helping ensure users can get back into their email without losing important information. More information on Device Managed Encryption is described further down this page.
Warning
If user access is lost without backup codes, another authorized device, or Device Managed Encryption, user data will be permanently unretrievable.
Unlike end-to-end encrypted emails, which require two users to be on the same Zoom account, password-expiring emails can be sent to any email recipient.
Expiring emails send recipients an email with a time-sensitive link to the original email, with a password embedded in the URL. After the link is sent, the Zoom Mail Service does not retain a copy of the password, exclusively allowing access through the URL.
Expiring emails are encrypted at rest within Zoom Mail Service servers and must be set to expire in one day, week, or month from their postmark. After an expiring email expires, the link is invalidated and the message’s public-facing content is deleted from Zoom Mail Service servers; however, a separate, private copy may persist within the sender’s Sent folder.
When a user receives a password-expiring email, the user must click a link to open the email in a browser window. Password-expiring emails cannot be viewed within the Zoom Mail client.
Due to the intrinsic design of end-to-end encryption and server-side encryption, emails with this designation cannot be viewed, read, or sent in the webmail client, except when opening a link to a password-expiring email. Consequently, all emails sent from webmail will use plaintext over TLS encryption.
Users cannot send end-to-end encrypted or password-expiring (server-encrypted) emails from webmail at this time.
Emails sent to a mailing list are not end-to-end encrypted, even if all users are Zoom Mail Service accounts authorized and enabled for the feature. Users must send distribution list emails using the password-expiring feature or plaintext over TLS.
Personal copies of encryption-enabled emails (such as end-to-end encrypted or password-expiring messages) are stored in the sender’s Sent folder in encrypted form. Zoom Mail Service servers do not have the keys to decrypt these copies once they are sent. As a result, encryption-enabled emails cannot be viewed through webmail, but remain accessible from the Sent folder on the sender’s authorized devices. In contrast, standard plaintext emails sent over TLS are encrypted at rest using Zoom’s key management system and can be viewed through webmail.
When emailing non-Zoom Mail recipients, users can choose to send plain text or expiring emails, with both email methods protected by TLS 1.2 in transit whenever possible.
Emails between Zoom Mail Service users and third-party email services are encrypted when stored by Zoom. Incoming messages from external services are encrypted with client-controlled keys as soon as they’re received, and outgoing messages to external accounts are saved in the sender’s Sent folder using keys provided by Zoom’s key management system.
The Zoom Calendar Service does not use end-to-end encryption for calendar events. This design allows interoperability between the Zoom Calendar Service and other calendar service providers; otherwise, calendar events and invitations would be unreadable to external parties. However, calendar events are transmitted using TLS 1.2 whenever possible for encryption in transit.
Device Managed Encryption (also referred to as encryption escrow) is a safeguard that allows an organization to securely hold a copy of the encryption keys used to protect Zoom Mail Service communications. These keys are stored in a controlled system that only designated administrators can access. When Device Managed Encryption is turned on, account members are notified, and a special virtual device is automatically added to their account. This virtual device acts like a backup device that sits alongside a user’s own devices, making it possible for administrators to recover the encryption keys tied to the account and, when required, decrypt email content.
Device Managed Encryption is designed to support two main scenarios:
User recovery: Administrators with the right permissions can approve new devices and restore access to encrypted email if a user loses all of their authorized devices.
Legal discovery: Administrators with the right permissions can request encrypted email from Zoom’s servers and decrypt it to meet compliance or investigation needs.
This system helps ensure that only the sender and recipient can read the content of messages on their personal devices, while also providing a carefully controlled way for administrators to step in when recovery or legal access is required. This balance helps organizations meet compliance needs without weakening the overall security model.
This section details functionality and additional information for the Zoom Mail and Calendar Services.
Account admins or authorized users can enable the Zoom Mail Service and Calendar Service for the entire account or on a group level. Refer to our support documentation for more information on enabling the .
When configuring a domain for the first time, admins can choose the default encryption behavior that will apply to users. This setting cannot be changed once set. The list of options is limited to:
Only use secure emails.
Default to secure emails, but users can choose.
Default to standard emails, but users can choose.
Companies on a Zoom Workplace Business plan or higher can set up the Zoom Mail Service with a custom email domain with proven ownership. Zoom does not provide domains for purchase and must be purchased through alternative providers.
Zoom Mail Service does not provide domain registration or domain management services. Instead, it works with domains that an organization already owns and configures. Admins are responsible for setting up and managing their own domain records, such as DNS, and then connecting those domains to Zoom Mail Service for use.
Users on accounts without a custom domain will use the email domain @zmail.com. The domain does not include any administration features and is for basic email access only.
Zoom accounts are granted the following Zoom Mail Service storage based on their plan type:
Pro: 50GB
Business: 100GB
Business Plus: 1TB
Enterprise: 5TB
To prevent spam email, Zoom Mail uses industry-standard protocols and techniques, such as:
Domain-based Message Authentication Reporting & Conformance (DMARC)
DomainKeys Identified Message (DKIM)
Authenticated Received Chain (ARC)
Strict Transport Security (MTA STS)
Zoom Mail Service supports integration with third-party email hygiene tools and add-on services, including advanced spam filtering, data loss prevention, and automatic archiving solutions that rely on server-side scanning. These integrations work with standard Zoom Mail Service communications (i.e., plaintext over TLS). However, when organizations choose to enable end-to-end encryption or other advanced encryption methods, external services that require access to message content will not be able to access those encrypted emails.
The Zoom Mail Service supports attachments up to 25 MB in size for inbound and outbound emails. Inbound emails with attachments greater than 25 MB will be bounced by the Zoom Mail Service. Alternatively, the Zoom Mail Client will prevent Zoom Mail Service users from uploading attachments exceeding 25 MB.
Zoom Mail Service supports small-scale email importing to help organizations move their existing mail into Zoom. For smaller migrations—such as a few hundred users—admins can usually complete the process on their own with built-in tools Zoom provides. Larger, enterprise-scale migrations involving thousands of users require additional planning, and organizations should work directly with their Zoom account team for support.
User emails created or processed through use of the Zoom Mail Service cannot be exported to third-party email services at this time. If a user discontinues their Zoom Mail Service, their emails remain within the service until deletion by the account owner or following account termination.
Zoom Mail Service data is stored within the account’s regional infrastructure. For instance, if an account is hosted on Zoom’s United States-based global infrastructure, the data will reside in the U.S.. If the account is hosted on Zoom’s European infrastructure, the data will reside in Europe.
Auto Appended Message: This content will be additional text that is included at the end of your message(s) to the recipient. This is added to help ensure your messages are compliant with carrier requirements. Click Edit to edit the auto-appended message, then click Save.
Message preview: Preview the message for the auto-appended message. This message cannot be edited except for the additions.
Add customization to Auto appended message: Add customized text to auto-appended message text. This content will be added to the beginning of the message preview.
Frequency: Select this option for this trailing text to be included in outbound messages. By default, for a new number, the Auto Appended Message text will be sent on the first outbound message only. Select from the following options for the message frequency, then click Save:
Always on every message: Include this content on all outbound messages. This is the recommended option.
On first outbound messages only: Include this content on only the first outbound message sent after the initial Opt-in Message.
View the Response to Opt-in content that will be sent when the recipient responds to your message with the opt-in text. You can also view the response’s Keywords.
View the Response to Opt-out content that will be sent when the recipient responds to your message with the opt-out text. You can also view the response’s Keywords. Only the phone number that receives the Stop keyword is opted out from sending messages.
Response to Help: This is the content that will be sent when the recipient responds to your message with HELP. Click Edit to edit the response to help, then click Save. You can also view the response’s Keywords.
Contact type: Click the dropdown and select the contact type. Your business must offer additional assistance to your customers through either a website, email, or phone number. Correctly entered URLs and emails will turn into hyperlinks after you save your changes.
Contact info: Enter the contact information for your brand’s help section. These contact details will be added to the carrier-approved message template.



User Features
Inbox
Outbox
Drafts
Sent Messages
Archiving (Personal)
Searching
Filters
Starring
Custom Labels
Contacts
Mail Merge
Scheduled Sending
Distribution Lists
Signatures
Vacation Messages
Aliases
Delegation
Address Blocking
Templates
Webmail
Admin Features
Multi-Domain Support
Domain Management
User Migration
Mailing List Migration (Google)
Contacts Migration (Google)
Resource Calendars
Mailing Lists
Aliases
Security
APIs ( and )
Legal Hold
eDiscovery
Storage Management
Delivery Management
Change History
Email Activity Management
Reporting
Email Search
Device Managed Encryption (Encryption Escrow)

Zoom Phone is Zoom's cloud-based telephony service designed to meet the telephony needs for businesses of any size. Featuring an intuitive, web-based admin menu for settings and policies, and a cloud-based service architecture that replaces legacy, on-premises equipment, Zoom Phone makes telephony simple.
This section provides an overview of Zoom Phone's services, architecture, design, network requirements, security standards, supported devices, features, licenses, and more. After reading this section, you can expect to gain a high-level understanding of Zoom Phone's fundamental design elements and functionality.
Zoom Phone offers businesses three primary service offerings to meet diverse needs across the globe: Zoom Phone Native, Zoom Phone Bring Your Own Carrier with Cloud Peering (BYOC-C), and Zoom Phone Bring Your Own Carrier with Premises Peering (BYOC-P). Each of these services are briefly described in the following sections, with a network summary available at the end of each service's description.
Zoom Phone uses a best-in-class, active-active architecture to deliver reliable, enterprise-grade phone service. Details of this design are elaborated in the following sections, with a focus on data center-specific SIP zones and Zoom's data centers at large.
In an active-active architecture, resiliency and redundancy are key. Each Zoom Phone data center features two identical, interconnected SIP zones equipped with dedicated hardware and services for independent resiliency and sustainability.
During normal operations, a load balancer evenly distributes calls between both SIP zones within a data center. Within each SIP zone, calls are equitably distributed among a cluster of call switches, which are responsible for various functions such as call routing, setup, and teardown. From the call switches, calls connect to a Session Border Controller (SBC) within each zone, which connects to Zoom's underlying network of providers for PSTN routing until the call reaches its final destination.
Within this framework, each integral piece of architecture—i.e., SBCs, load balancers, and call switches—is supplemented with redundant hardware on standby for resiliency. In the event that one SIP zone experiences a service-impacting event, a call's active media, signaling, and registration will failover to the other zone for uninterrupted service.
The following diagram illustrates a SIP zone's active-active architecture design at a high level:
From a physical perspective, Zoom's data centers are located within highly secure colocation facilities with physical security, redundant power and cooling systems, and access to leading carrier-neutral internet service providers (ISPs) and peering partners.
From a technological perspective, Zoom's data centers are built with fault-tolerant architecture, including full redundancy and rapid failover capabilities from a primary data center to a secondary data center, to enhance reliability and minimize downtime.
In the unlikely event of a complete data center outage or service-impacting event, Zoom Phone media, signaling, and registration information may be temporarily lost, requiring a convergence on the standby, secondary data center.
The following diagram illustrates Zoom’s data center redundancy design at a high level:
Zoom Phone offers customers hosted on Zoom's United States-based cluster (US01) SIP Zone and PSTN connectivity from the following list of global data centers, enabling users to connect to the most suitable data centers based on their location and needs:
North America:
U.S. West, California
U.S. Central, Colorado
U.S. East, New York
For customers that require data localization for compliance purposes and are located in supported regions, Zoom Phone also supports localized PSTN connectivity for region-specific accounts. Customers with a region-specific account are forced to initialize all calls from their region's associated data center and cannot utilize SIP zones outside of their account's region.
The following list details supported regions and region-specific data center locations available with Zoom Phone:
Australia
Sydney
Melbourne
Canada
Vancouver
Warning
Phone calls placed from region-specific accounts will transmit from data centers within the region; however, PSTN calls may traverse international networks beyond their confined region.
Apart from localized regions, Zoom Phone also supports Bring Your Own Carrier with Premises Peering (BYOC-P) connectivity within India through a specialized Zoom Phone India service offering. With Zoom Phone India, customers with a U.S. cluster-based account are provided with a unique Zoom Phone instance specific to the licensed service areas—also known as circles—where both Zoom and the customer account are authorized to operate.
As of the date of this document's publication, Zoom is authorized to operate within the following licensed service areas:
Mumbai: Local area of Mumbai, Navi Mumbai, and Kalyan
Andhra Pradesh: State of Andhra Pradesh and Telangana, including Hyderabad
Maharashtra: State of Maharashtra and Goa, including Pune
Karnataka: State of Karnataka, including Bangalore
Due to regulatory requirements, a business must meet certain criteria to be eligible for the Zoom Phone India service. Although the following list is not comprehensive, the most important criteria are outlined below:
The business must pay with the Indian Rupee, and cannot use another denomination like the U.S. Dollar or Euro
The business must be a business entity registered with the Government of India and cannot be an international entity
The business must have both an authorized signatory and a Goods and Sales Tax Identification Number (GSTIN) within the state where they are getting service
If your business meets these requirements and is interested in learning more about Zoom Phone India, reach out to your account team for more information.
Zoom Phone supports secure voice calls across various platforms, including the Zoom Workplace app for desktop and mobile, the Zoom web client, Zoom Rooms, and supported SIP devices.
During call setup, Zoom Phone utilizes SIP over TLS 1.2 with an AES 256-bit algorithm for encryption. Additionally, connections from the Zoom Workplace app for desktop and mobile, as well as the Zoom web client, encrypt call media to the Zoom Cloud using secure real-time transport protocol (SRTP) with AES 256-bit encryption.
Supported SIP devices configured with SRTP use either AES-128 or AES-256-bit algorithms for encrypting call media, while unencrypted RTP is utilized as a fallback for devices without SRTP support.
In addition to the Zoom Workplace desktop and mobile apps and Zoom Rooms app, Zoom Phone supports a growing list of IP phones, telephony hardware, and accessories.
The following lists contain supported hardware manufacturers for Zoom Phone, not specific models. Because Zoom Phone continues to support new hardware over time, visit Zoom's support center to see the most recent list of , including supported models, firmware versions, and supported encryption standards available for each.
Zoom Phone is supported natively within the following platforms:
Zoom Workplace Mac desktop app
Zoom Workplace Windows desktop app
Zoom Rooms app
Zoom Phone has limited feature support within the Zoom for Chrome Zoom Web App, which allows users to use some of the same features available on the Zoom Workplace desktop or mobile app within a Google Chrome web browser.
Refer to Zoom's support center for more information on the , or speak to your Zoom account team for more information on feature parity and capabilities.
Zoom Phone supports limited IP phone models from the following manufacturers:
AudioCodes
Avaya
Cisco
Grandstream
Zoom Phone supports limited IP phone accessories from the following manufacturers:
Poly
Yealink
Zoom Phone supports limited analog gateway devices from the following manufacturers:
AudioCodes
Cisco
Grandstream
Zoom Phone supports limited Session Border Controllers from the following manufacturers:
AudioCodes
Avaya
Cisco
Mitel
To integrate an SBC with Zoom Phone, an SBC must meet the following requirements:
Support for TLS 1.2 and SRTP
Support for Mutual TLS
Session Initiation Protocol (SIP)
Zoom Phone supports limited pagers and intercom systems from the following manufacturers:
2N
Algo
CyberData
By default, the Zoom Workplace desktop and mobile apps will use the Opus codec when connecting to a call; however, Zoom Phone also supports the following codecs for physical devices:
Opus
G.711 μ-law
G.711 A-law
The following lists outline core features available with Zoom Phone. As the Zoom Phone team continually innovates, additional unlisted features may also be available. If a feature important to your organization is not listed, please contact your account team for more information. Feature availability may be impacted by a user's and .
Zoom Phone's Online Faxing allows users to send and receive faxes right in the Zoom Workplace desktop and mobile apps using their existing Zoom Phone numbers. Online fax services are included with paid Zoom Phone subscription plans.
Refer to the or speak with your Zoom account team for more information.
Zoom Phone provides a wide range of licenses, calling plans, and add-ons to cater to various customer requirements. Fundamentally, every user or device utilizing Zoom Phone requires a Zoom Phone Basic license to access core PBX features. For Zoom Phone Native users (i.e., non-BYOC-C/P), a calling plan is essential for making outbound calls; alternatively, BYOC-enabled accounts will incur charges from the underlying carrier for their usage.
In addition to calling plans, Zoom also offers several add-ons for both Native service and BYOC-C/P customers, offering users additional features, capabilities, and functionality.
Zoom Phone supports various integrations for enhanced functionality and user workflow efficiency. Although the following list is not exhaustive, some of Zoom Phone’s most popular integrations are briefly outlined in the following section.
Zoom Contact Center (ZCC) is an enterprise-grade, omni-channel solution that integrates Zoom's unified communications platform with contact center capabilities. Designed to enhance customer experiences, ZCC can deliver prompt and personalized service across a robust suite of channels, including video, voice (phone), SMS, social media, and web chat, along with Zoom's AI-powered Virtual Agent.
For more information on Zoom Contact Center, refer to or speak with your Zoom account team.
Zoom's Workforce Engagement Management suite provides additional products and features that further supplement and expand the power of Zoom Contact Center with Zoom Phone.
With Zoom Workforce Management, businesses have access to AI-powered tools that can forecast future contact engagement volume, organize and design schedules that align with projected volume across various channels, and predict agent workloads.
With Zoom Quality Management, contact center managers have access to various tools and features that monitor and analyze consumer interactions, evaluate agent performance, offer actionable insights, and proactively identify areas for improvement.
For more information on Zoom’s Workforce Engagement Management suite, refer to or speak with your Zoom account team.
In addition to Zoom Contact Center, Zoom Phone also supports contact center integrations with Five9, Twilio, Genesys, NICE inContact, and Talkdesk.
For businesses that use a cloud-based telephony service dependent on internet provider connectivity, maintaining telephony services in the event of an internet service failure or a service impacting event is critical for business continuity and operations. To address these scenarios, Zoom offers the Zoom Phone Local Survivability (ZPLS) module as a Zoom Node workload, which provides telephony resiliency in the event of a service disruption.
During a survivability event where Zoom endpoints cannot reach the Zoom Phone cloud service, supported user devices will register to the ZPLS module, which provides basic telephony services—like internal calling and survivability distribution groups—until full service can be restored. Businesses can further expand this functionality by connecting the ZPLS module with a Session Border Controller (SBC) connected to an underlying carrier (BYOC) to route calls across the public switched telephone network (PSTN).
When integrated with an SBC, businesses have the best of both worlds: the simplicity and ease of a cloud-managed phone system, with the survivability and resiliency of on-premises infrastructure when the unforeseen occurs. In short, with ZPLS, businesses can comfortably deprecate most legacy, on-premises telephony appliances and migrate to a cloud-based phone system with confidence.
Refer to the section of this document dedicated to for more information.
Zoom Phone supports many nuanced call routing capabilities, supporting multiple Sites, external contacts, routing rules, and more. To support customer understanding for the impact of call flows, Zoom Phone processes different calling scenarios through comprehensive call routing logic.
Due to Zoom Phone's cloud-based architecture, configuring Zoom Phone for your network is substantially easier in comparison to legacy, on-premises phone systems. From the simplest of perspectives, users need two key factors to begin successful calling: a working internet connection and open network ports. So long as users can successfully maintain an active connection with Zoom Phone data centers and the necessary ports are not blocked, Zoom Phone is ready for use within your network.
This section outlines the user experience for getting started and familiar with Zoom Phone, including the web portal and Zoom Workplace app. After reading this section, you can expect to be familiar with common in-app and web-based settings and features central to using Zoom Phone as a standard user.
U.S. East, Virginia
Latin America:
Brazil, São Paulo
Mexico, Querétaro
EMEA:
Netherlands, Amsterdam
Germany, Frankfurt
APAC:
Australia, Sydney
Australia, Melbourne
China, Hong Kong
Japan, Tokyo
Japan, Osaka
Singapore, Singapore
Toronto
Europe
Germany
Amsterdam
Zoom for Government
California
New York
Tamil Nadu: State of Tamil Nadu and union territory of Pondicherry, including Chennai
Delhi: Local area of Delhi, New Delhi, Ghaziabad, Faridabad, Noida, and Gurgaon
Zoom Workplace Android mobile app
Zoom Workplace iOS/iPadOS mobile app
Mitel
Poly
Yealink
Poly
NextGen
Oracle
Ribbon
TE-Systems
Topology hiding (RFC-5853)
SIP Early Offer (mandatory)
Codecs: Opus, G.711 μ-law, G.711 A-law and/or G.729
Grandstream
G.729
Call Blocking
Call Delegation
Call Forwarding
Call Handling Settings
Call Handoff Between Devices
Call History
Call Hold
Call Monitoring (Listen, Whisper, Barge, Take Over)
Call Park
Call Presence Status
Call Queue Chats Channels
Call Queue Opt-In/Out
Call Recording
Call Transfer
Caller ID
Desk Phone Screen Lock
Elevate Call to Meeting
Emergency Calling
End-to-End Encrypted Calls
Multi-Party Conference Call
Multi-Key and Position Support
Personal Business Hours
Personal Holiday Hours
Personal Hold Music
Personal PIN Code
Select Outbound Caller ID
SMS
Video Mail
Voicemail
Voicemail Transcription
Auto Receptionists
Blocked Number List
Business Hours
Call Logs
Call Recording (Ad Hoc, Automatic)
Call Queues
Common Area Phones
Configure Email Notifications
Configure IP Phone Settings
Define Call/SMS Hours
Define Call/SMS Locations
Device Management
Dial by Name Directory
Emergency Services
End-of-Call Feedback Survey
External Contacts
Hold Music
Hot Desking
IP Address Access Control
Live Transcriptions
Mask Personal Data from Dashboard and Call Log
Paging
PIN Code Requirements
Port Range Assignment
Provisioning Template
Quality Dashboards
Routing Rules
Shared Line Groups
Single Sign-On License Assignment
Site Management
SMS Etiquette Tool
Spam Number List
Spam Protection
Subscribe to Zoom Phone Reports
Chinese (Traditional)
Chinese (Simplified)
Danish
Dutch
English (America)
English (Britain)
French (Canada)
French (France)
German
Italian
Japanese
Korean
Portuguese (Brazil)
Portuguese (Portugal)
Spanish (America)
Spanish (Spain)
Once a user is assigned a Zoom Phone license, there is a brief web-based account setup the user must perform on the Phone page before configuring additional Zoom Phone settings. This process establishes baseline information for the user profile, such as the user's country, default area code, time zone, and PIN used for features like hot desking and voicemail.
The user's chosen country and area code will affect a user's default dial string for local calling. For example, if a user chooses the United States and a 669 area code, unless otherwise specified, the user's dial string will default with +1 669, and all calls without a specified area code will route locally. For example, dialing 555-5555 will automatically translate to +1 669-555-5555. This will be overridden if the user begins a dial string with another area code, for example, dialing 212-555-5555.
The user's default time zone will determine how Zoom Phone interprets their time-sensitive settings, like Business Hours. For example, if a user is configured for the U.S. Pacific time zone (UTC -7) and actually lives in the U.S. Central time zone (UTC -5), if their business hours are configured from 8-5 Pacific, the user will experience their business hours from 10-7 locally.
If necessary, users can change their time zone at any time from their profile page on the Zoom web portal.
The user's chosen PIN code will be required for them to access their voicemail by telephone call, unlock their desk phone, or use a hot desking location.
Once a user's PIN is set, they can change it at any time from their Phone Settings screen on the Zoom web portal.
After completing the initial setup process, users can access most of their Zoom Phone settings and features from the Phone tab on the web portal. By default, clicking the Phone tab will open the Settings screen; however, users can also switch to the History, Voicemail, and Recording tabs, which are also available within the Zoom Workplace app. Please follow the link below for more information.
The Phone tab in the Zoom Workplace app serves as the main location to utilize Zoom Phone for both mobile and desktop users. From the Phone tab, users can make and receive calls, view call history, access voicemail, view shared lines, and send SMS/MMS messages. Please follow the link below for more information.
Zoom Phone supports built-in AI Companion features that can simplify user workflows and help you save time. These features are described in the following sections.
The Call Summary feature lets users generate post-call summaries of Zoom Phone conversations. If enabled during a call, designated conversations will receive an AI-generated post-call summary within the Zoom Workplace app, highlighting essential details such as dates, names, key discussion points, and next steps. Users have the option to edit, email, or share the conversation summary as needed.
Refer to Zoom's support center for more information on enabling and using call summary with AI Companion.
Zoom Phone's AI Companion enhances voicemail management through intelligent automation and prioritization tools designed to streamline communication workflows and improve response efficiency.
When viewing a Voicemail, users can ask Zoom AI Companion to analyze and automatically suggest tasks based on voicemail content, helping users catch up faster when their inbox is full, and stay on-task when returning messages.
Refer to Zoom's support center for more information on enabling and using call summary with AI Companion.
With the Voicemail Prioritization feature, AI Companion can automatically prioritize voice messages when the message content matches a user's personally defined topic or intent list. This can help users respond to their most significant, time-sensitive, or critical voicemail messages on a faster timeline when that message might otherwise be last in line.
Refer to Zoom's support center for more information on enabling and using call summary with AI Companion.
With the Summarize Team SMS threads feature, members of Call Queues and Auto Receptionists with the Power Pack add-on can use AI Companion to generate a summary of Team SMS threads to quickly understand the conversation and generate their response. This is notably beneficial when a user is following up on an existing conversation with several message exchanges, or when transferring an SMS conversation to a different agent for support.
Refer to Zoom's support center for more information on summarizing SMS threads with AI Companion.
Zoom Phone users without an elevated role (i.e., a "standard user") do not have access to Zoom Phone usage reports. However, users can access and export their call history through the web portal.
Alternatively, users with a Power Pack add-on and sufficient role privileges may have access to additional dashboards and Call Queue reports. Refer to Zoom's support Center for more information on Power Pack reporting and features.
The Zoom Phone Power Pack is an optional add-on designed to empower Licensed (i.e., non-basic) Zoom Phone users by providing access to additional features and reporting tools, strengthening customer support and user capabilities similar to a "contact center-lite" experience.
With the Power Pack add-on, users and admins with sufficient permissions have access to additional features, including:
Call Queue Real-Time Analytics
Call Queue Historical Reports
Auto Receptionist Historical Reports
Team SMS Historical Reports
Opt-Out Reason Code
Admin-User Call Queue Opt-In
VIP Delegation
SMS Templates
The following sections discuss Analytics available with the Power Pack add-on. Although the following descriptions provide general summaries of each report, some reports and associated data may require elevated (i.e., admin) privileges to view all data. Readers are encouraged to refer to each linked support article to understand the requirements for each report.
The Call Queue Real-Time Analytics dashboard provides authorized users with critical details for an account's Call Queue performance that can help make effective data-driven decisions. Data available within this report includes:
Target service level percentages
Average Call Handling Time
Call Volume
Average Call Handling Time
Average Wait Time
Longest Wait Time
Completed Call Counts
Abandoned Call Counts
Overflow Call Counts
Missed Calls
Refer to Zoom's support center for more information on viewing the real-time Call Queue analytics dashboard.
Similar to the Call Queue Real-Time Analytics dashboard, authorized users can generate Call Queue Historical dashboard reports to help make effective data-driven decisions regarding Call Queue performance.
Refer to Zoom's support center for more information on viewing the historical Call Queue analytics dashboard.
The Auto Receptionist historical report provides authorized users with insightful analytics for calls coming into their auto-receptionists. Data within this report includes:
IVR Average Duration
Inbound Calls Within Business Hours
Inbound Calls After Hours
Outbound External Calls
Auto Receptionist Routing Rates
Percentage of IVR Responses
Top 25 Auto Receptionists Performance Scoreboard
Refer to Zoom's support center for more information on viewing the historical Auto Receptionist reports dashboard.
The Team SMS historical report provides authorized users with insightful analytics for Auto Receptionist and Call Queue SMS interactions, including key volume and response time indicators. Data within this report includes:
Distributed SMS
Manual Released Count
Timeout Released Count
First Reply Time
Longest Reply Time
Average Reply Time
Total SMS Volume
Inbound
Outbound
Average SMS Volume Per Agent
Inbound
Outbound
SMS Volume Per Completed Conversation
Refer to Zoom's support center for more information on setting up or using SMS with Auto Receptionists and/or Call Queues.
The User Performance Report allows authorized users to view the performance data of Zoom Phone users, compare their statistics, and view a leaderboard of users within a location. Data provided in this report includes:
Total Calls
Total Inbound Calls
Total Unique Inbound Calls
Total Outbound Calls
Total Unique Outbound Calls
Answered Calls (Outbound)
Completed Calls (Inbound)
Calls Forwarded to Voicemail
Calls Answered by Other
Percentage of Missed Calls
Average Call Time
Total Call Time
Total Call Time (Inbound)
Refer to Zoom's support center for more information on viewing User Performance Reports.
The Feature Entitlement and Membership Report provides authorized users with a simple snapshot view of a Zoom Phone user's profile. Data available within this report includes:
Name
Extension
Calling Package
Department
Cost Center
Site
Time Zone
Phone Numbers
Outbound Caller ID
Device Types
Call Queue Membership
Shared Line Membership
Group Call Pickup Memberships
Call Handling Ring Mode
Assistant For
Can Customize Voicemail
Can Customize Message Greeting
On/Off Settings for:
Refer to Zoom's support center for more information on viewing the Feature Entitlement and Membership report.
The Zoom Phone Recording Report allows authorized users to view the history of recording logs and how Zoom Phone recordings are being used, stored, and deleted within an account. These reports allow admins to monitor recordings and understand recording usage in a comprehensive report. Data available within the report includes:
Users Configured for Automatic Recording
Users Configured for Ad-Hoc Recording
Number / Percentage of Recorded Calls
Number / Percentage of Not Recorded Calls
Number / Percentage of Recordings Not Marked for Deletion
Breakdown of User Information For
Name
Extension
Number of Ad-Hoc Recordings
Breakdown of Call / Recording Information For
Direction
Caller Number
Callee Number
Refer to Zoom's support center for more information on viewing the Zoom Phone recording report.
The Zoom Phone Access Report allows authorized users to generate a list of users that have access to shared resources, including:
Shared Voicemail inboxes
Shared Call Recordings
Call Delegation (Shared Line Appearance)
Voicemails for:
Call Queues
Auto Receptionists
Shared Line Groups
Refer to Zoom's support center for more information on viewing Zoom Phone Access Reports.
When provisioned with a Power Pack add-on, users gain access to the following features:
Users belonging to a Call Queue can designate an opt-out reason code when leaving the queue. This provides Call Queue managers with insight for user statuses, such as taking a rest or meal break, and also synchronizes to the real-time Call Queue analytics dashboard.
Users with sufficient role-based permission, such as a Call Queue admin, can opt users in to a Call Queue through the Call Queue Real-Time dashboard. This can be helpful in circumstances where a Call Queue may have users waiting in-queue, and agents have forgotten to opt back in to the queue from a break.
VIP Delegation allows a user to define who can and cannot directly call them. This feature is particularly useful for executives who do not want to be directly accessible to everyone without expressed permission.
To configure VIP delegation, users first define a VIP contact list of who can call them directly; after configuring the list, the user can define if unanswered calls will forward on to a call delegate or not.
Second, the user can define what happens when someone outside their VIP contact list calls them, with options to:
Ring them and their delegate(s) simultaneously: People not on the VIP list can ring both the user and their delegate(s).
Ring their delegate(s) first and themselves second: People not on the VIP list can ring the delegate(s) and then the primary user.
Ring themselves first and their delegate(s) second: People not on the VIP list can ring the primary user first and then their delegate(s).
Ring their delegate(s) only: People not on the VIP list can ring the delegate(s) only.
Ring themselves only: People not on the VIP list can ring the primary user only.
Send to voicemail/videomail: People not on the VIP list are sent to voicemail/videomail if voicemail/videomail is enabled.
With SMS Templates, users can optimize efficiency by promptly inserting pre-made messages, defined by administrators, when replying to or sending SMS messages through an Auto Receptionist or Call Queue. These templates facilitate customization with adaptable fields to personalize messages for recipients and offer controlled access levels at various account, group, user, and Site-specific tiers.
Refer to Zoom's support center for more information on managing SMS templates.
With Team SMS Functionality, users can answer and send text messages on behalf of an Auto Receptionist or Call Queue if they are members of the group. This lets end users (i.e., your business' customers) send SMS messages to a Call Queue or Auto Receptionist, which can be answered by members of the group collaboratively, offering additional contact channels for communicating with your customer base.
Refer to Zoom's support center for more information on using Call Queues or Auto Receptionists with SMS.
This feature was previously discussed under the AI Companion section.
The Zoom Assistant is a lightweight widget that runs on a user’s desktop as an extension of the Zoom Workplace app, offering Zoom Phone Pro and Licensed users a consolidated phone interface. Please follow the below link for more information.
This section provides an overview of administering Custom AI Companion within your company account, including roles, licenses, provisioning, and general feature use.
To access AI Studio within a Zoom account’s web portal, users (admins) must have a role with the sufficient AI Studio permissions. By default, only the account Owner will have access to this feature, and the default Admin role must be assigned these permissions.
To update a role with the applicable permissions, perform the following steps:
As a Zoom account owner or admin authorized to edit roles, navigate to the page on the web portal.
Click the pencil icon to the right of the role you are editing.
Navigate to the AI Studio subsection and define the role access as desired.
Repeat for any additional roles.
Admins with sufficient role-based permissions can access AI Studio through the Zoom web portal by clicking the AI Studio menu on the left-hand side of the screen, under the Admin subsection.
To grant end users access to Custom AI Companion, users must be assigned a Custom AI Companion add-on license.
Account admins can also assign users Custom AI Companion licenses either through manual provisioning or through SSO, via SAML response mapping or SCIM.
Refer to Zoom’s support center for more information on , provisioning through , or including the for Custom AI Companion within their identity provider’s payload.
To configure a Knowledge Base, as an admin, extend the AI Studio menu within the Zoom web portal and click Knowledge.
Within the Knowledge tab, admins can create Knowledge Bases, which operate as top-level folders for a given topic, subject, or group.
For example, if creating a Knowledge Base for Human Resources, this Knowledge Base would be filled with Data Sources (i.e., documents, resources) most commonly used by the Human Resources department.
Each account supports the creation of up to 100 distinct Knowledge Bases, providing administrators with extensive flexibility to organize and categorize content sources according to specific business requirements and access governance needs.
When creating a Knowledge Base, admins can customize the name, description, and icon for the Knowledge Base from an emoji library.
When setting up access to a Knowledge Base, administrators can use Zoom User Groups to define and restrict which users within their account are authorized to view or utilize specific content. For instance, a Knowledge Base might be restricted exclusively to a specific department, like Human Resources or Engineering.
However, if the Knowledge Base is connected through a third-party cloud-storage provider—such as Google Drive or OneDrive—and configured to use the provider’s native permissions, access will instead follow those permissions. In such cases, user access defined within the cloud-storage platform itself takes precedence over Zoom User Groups.
Readers with questions about are encouraged to refer to Zoom’s support center for more information.
Each Knowledge Base can only pull data from one source type at a time. This means that data from a Third-Party Cloud Storage provider cannot be mixed with Web Sync, Direct Data Uploads, Third-Party Index Connections, or any combination between them. Each separate data source requires a separate Knowledge Base. For example, after creating a Knowledge Base from a Web Sync, you can't later add documents from Direct Data Uploads or connect it to a third-party index.
After a Knowledge Base is created, admins can fill the Knowledge Base “folder” with the corresponding data sources relevant to the Knowledge Base, such as PDFs, .txt, .docx, and .doc filetypes.
Each individual Knowledge Base supports up to 2,500 data sources, with a combined account-wide maximum of 20,000 sources across all Knowledge Bases. At full capacity (2,500 sources each), an account can have up to eight Knowledge Bases. However, the total 20,000-source limit can also be distributed across a larger number of Knowledge Bases with fewer sources each, depending on your organization’s specific needs (e.g., 100 knowledge bases with 200 data sources each).
As of the date of this document’s publication, each Data Source must be no greater than 50MB in size.
After adding new Data Sources to a Knowledge Base, account admins can test the functionality of it by using the Test feature. Within this testing environment, admins can confirm AI Companion is able to properly reference uploaded Data Sources.
After adding new Data Sources to a Knowledge Base, account admins must Publish the updated Data Source Knowledge Base to take effect, otherwise, it will remain in a “draft” state. If the changes are not published, AI Companion will be unable to acknowledge and utilize the new Data Sources.
To upload files to Zoom, a user or admin with sufficient permissions must create or edit a manual Knowledge Base and upload the appropriate files. After testing and publishing the knowledge base, the index information will be available to Custom AI Companion-licensed users via AI Companion queries.
To create or manage a Web Sync Knowledge Base, a user or admin must have sufficient permissions to manage Knowledge Bases.
When creating a new Web Sync Knowledge Base, the user selects the desired indexing method and specifies the relevant URL(s). After, Zoom will begin indexing the designated pages. Once Zoom has indexed all specified pages within the customer-specific RAG instance, the Knowledge Base can be tested and then published for use.
During the Web Sync Knowledge Base creation process, the user may enable settings that will automatically convert content crawled from a webpage into article format to help improve readability, indexing, and accessibility of content.
The Third-Party Cloud Storage connection allows Zoom AI Companion to access, index, and deliver content from third-party cloud storage platforms (e.g., Google Drive, OneDrive) to authorized users within Zoom. To establish a connection with a third-party cloud storage provider, the Zoom user or admin must have appropriate permissions to manage Knowledge Bases. Additionally, an administrator with sufficient privileges on the third-party platform is required to authorize certain integration steps. This integration involves several key steps, detailed below.
When setting up the Cloud Drive integration for the first time, an administrator with appropriate permissions initiates an OAuth authorization flow through the Zoom App Marketplace. This OAuth integration is performed at the admin level, meaning the admin grants permissions on behalf of the entire Zoom account. However, this admin-level authorization grants Zoom access only to files explicitly accessible to the admin within the third-party platform, not all files across the entire platform.
After connecting to the cloud storage platform, the administrator must choose how access permissions will be managed:
Zoom User Group Permissions: This method uses permissions based solely on Zoom’s internal User Groups. The admin specifies which Zoom User Groups have access to the selected cloud storage documents, regardless of the third-party’s native permissions.
Third-Party Native Permissions: This method enables administrators to configure Zoom to respect the third-party platform's native permission structure (e.g., Google Drive or OneDrive user/group access settings). When configured, Zoom indexes permissions from the original source and applies access controls that align with the external platform's authorization model, helping maintain consistent document access policies across platforms.
If the administrator selects third-party native permissions, and has never previously mapped the users from their third-party platform to Zoom, Zoom will prompt them to complete a user mapping process. This matches Zoom user accounts with corresponding accounts in the third-party cloud platform, typically using unique identifiers such as email addresses. In turn, this step establishes synchronization between Zoom and the third-party system, enabling Zoom to check user access permissions based on the user's existing entitlements in the connected platform.
Once the admin selects the appropriate permission method, Zoom indexes two critical components:
Document Content: Zoom fetches, segments, and converts document content from the cloud drive into a customer-specific RAG module that can deliver contextually relevant search results based on the user’s access level and query.
Permission Metadata: Zoom indexes detailed permission metadata depending on the chosen method:
If using Zoom User Groups, Zoom records internal User Group IDs authorized by the admin for each document.
When a user performs a query, Zoom AI Companion initially queries indexed documents based on relevance and preliminary permission matching using indexed metadata. Subsequently, Zoom will check the document permissions against the indexed permissions store:
If permissions are based on Zoom User Groups, the user’s Zoom group membership is validated directly against the document’s indexed Zoom group permissions.
If permissions are based on Third-Party Native Permissions, Zoom validates the user’s mapped third-party user/group membership against the document’s indexed third-party permissions.
After, only documents that pass the verification are provided to the user.
To maintain accuracy and security, Zoom incrementally and periodically synchronizes permission data from the third-party platform into Zoom’s internal permissions store. Due to API rate limitations and latency constraints, Zoom does not perform live permission checks against the third-party platform during user queries. Instead, Zoom checks the most recently synchronized permission dataset.
Heads Up
Zoom incrementally and dynamically updates permissions from third-party providers. In most cases, permission changes should sync within minutes due to incremental updates. However, timing can vary based on your organization's size. For larger organizations or during full synchronization cycles, updates may take anywhere from 2 to 24 hours to complete. Overall, permission changes should not require more than 24 hours to fully synchronize across your Knowledge Base.
To integrate a Third-Party Index service with Custom AI Companion, a user or admin with sufficient Zoom App Marketplace permissions, as determined by their User Role, must authorize and complete the connection with the chosen provider.
Admins can use the following links to access the Third-Party Index integrations for Zoom with and in the Zoom App Marketplace. To use this feature, your account must have the setting enabled that allows AI Companion to .
After adding an integration, it will appear within the Knowledge list.
Account admins can enable or disable the use of avatars and custom avatars from the Zoom web portal. There are no further admin-level settings to consider for this feature.
Similar to other Zoom features, Custom AI Companion’s Avatars and Custom Avatar features can be disabled on the , , and levels.
Admins can access these features from the Zoom Web Portal by editing the appropriate level’s Settings, selecting the AI Companion tab, and locating the Clips subsection.
To configure a Custom Dictionary as a user or admin with sufficient AI Studio permissions, extend the AI Studio menu within the Zoom web portal and click Custom Dictionary.
Account admins can manage their account’s custom dictionary through two methods: manual management, or via CSV import/export within AI Studio.
Manual Management
To manually add words to a custom dictionary, click the + Add manually button. Within the pop-up, enter one word on each line, separated by a breakline.
To manually delete a word from the dictionary, click the trash icon .
CSV Import/Export
To create or update a custom dictionary in bulk, upload a CSV file with all new words in a single column of the document (e.g., Column A).
Before modifying a custom dictionary via CSV, account admins are encouraged to export and save a copy before making any changes. When uploading the file, account admins will be prompted to either Add to or Replace the dictionary with the file. In the event of a mis-click, the previously-saved copy can be used as a backup.
After adding additional words to the account’s Custom Dictionary, account admins can test the performance of Zoom AI Companion’s recognition of the new words either by uploading a pre-recorded audio file, or making an ad-hoc audio recording using the in-browser tool.
After adding new words to a Custom Dictionary, account admins must Publish the changes to take effect. Failure to Publish may result in AI Companion failing to recognize new terms. Once published, AI Companion will utilize the Custom Dictionary to improve transcription accuracy in all future meetings for users with the Custom AI Companion add-on.
As of the date of this document’s publication, accounts are currently limited to one custom dictionary at a time. Speak with your Zoom account team for more information.
The Custom Meeting Summary Templates section is where account users or admins with access to AI Studio can create custom meeting summary templates.
When creating a custom meeting summary, admins enter a brief prompt describing the type of meeting—such as “Quarterly Business Review”—and generative AI uses that input to build a tailored meeting summary template. For example, the resulting structure might include sections for financial performance, goal progress, key challenges, and next steps, making it easier to capture the most relevant insights for that meeting type.
During the custom summary creation process, admins can customize the list of summary topics by defining specific sections and adding descriptions that guide how AI Companion organizes meeting content. These descriptions help AI Companion understand what type of information to look for and include in each section. For example, if a summary topic is labeled “Project Risks” with a description like “Identify any potential risks or blockers mentioned during the meeting,” AI Companion will analyze the transcript and populate that section with relevant content. This flexibility gives organizations greater control over how meeting insights are captured and structured.
After confirming the list of summary topics, admins can test the customized meeting summary template using simulated conversational data, which is consequently processed through the template to check for quality and consistency.
Admins can also test the custom summary template using a prior Zoom meeting transcript
If desired, admins can test the template using a past Zoom meeting transcript to evaluate how it performs with real meeting content and assess the quality of the custom meeting summary template. This is especially useful for refining templates based on the types of meetings their teams regularly conduct.
Once the template’s test is complete, it can be published to either the entire account, or a specific subset of Zoom User Groups.
This section explains how to adjust Custom AI Companion’s settings for joining third-party meetings.
Similar to other Zoom features, Custom AI Companion’s ability to join Third-Party Meetings can be disabled on the , , and levels.
Admins can access these features from the Zoom Web Portal by editing the appropriate level’s Settings, selecting the AI Companion tab, and locating the Custom AI Companion subsection.
To integrate Third-Party Apps with Custom AI Companion, a user or admin with sufficient Zoom App Marketplace permissions, as determined by their User Role, must authorize and complete the connection with the chosen provider.
Admins can search the Zoom App Marketplace for supported AI Companion integrations, such as . To use this feature, your account must have the setting enabled that .
Account admins or authorized users can create a Custom Agent under the AI Studio sub-section by clicking the Custom Agents option in the Zoom Web Portal.
When creating a Custom Agent, admins can select from a pre-defined list of templates or start from a blank configuration. Templates offer a fast way to launch a ready-to-use setup that’s aligned with common roles or workflows, helping organizations quickly scale AI capabilities without starting from scratch.
Pre-built templates include:
Engineering Task Tracker: Helps developers manage assigned tickets and technical tasks across sprints and projects. It searches and updates issues, tracks progress, and flags bugs to keep engineers focused on priorities and deadlines.
Interview Support Assistant: Helps interviewers prepare by providing quick access to HR hiring policies, interview tips, and job-specific details. It retrieves job descriptions, reviews candidate profiles, and lists open roles from ERP platforms.
Incident Management Assistant: Helps developers streamline incident response workflows across teams. It helps organizations efficiently manage, document, and respond to incidents of all severity levels throughout the incident lifecycle.
Templates are also customizable and can be built from a blank template, allowing admins to refine their purpose, update knowledge sources, or extend capabilities with tools and prompts as needed.
Each Custom Agent can be associated with one or more Knowledge Bases that define its domain expertise. These Knowledge Bases may include internal policy documents, product guides, onboarding materials, or team-specific process outlines.
For example, Support Agent could be configured to access a combination of sources from the Support Center, internal IT articles, and product documentation. By referencing both public-facing support content and internal technical materials—such as setup guides, known issue logs, or configuration best practices—the Custom Agent can deliver precise, up-to-date answers aligned with the most current product information. This combined approach helps ensure that responses are consistent, reliable, and grounded in the same resources used by official support teams.
Tools define what a Custom Agent is capable of doing beyond conversation — they are the permissions and integrations that allow the agent to act on your behalf.
Some tools are built-in, such as the ability to read, create, or interact with a Zoom Doc. Others can be connected through Zoom App Marketplace integrations using Model Context Protocol (MCP), allowing Custom Agents to perform actions across external platforms. For example:
Create new issues or update existing ones in Jira
Retrieve and modify records in Salesforce
View or update tasks in Asana
Access structured data from internal systems via API
Admins can also design custom tools through API calls or JavaScript functions, or an MCP server to enable specific functionality unique to their organization.
Important: When creating a custom tool, the tool description becomes especially important. It tells the Custom Agent when and how to use that tool. This description acts as the instruction set the model relies on to decide whether invoking the tool is relevant to a user’s request, helping ensure that every automated action remains precise, intentional, and contextually sound.
When creating a Custom Agent, the description becomes especially important—it tells AI Companion what the agent does, when to use its tools, and how it should behave within a given context. For example, including a line like “Post results in the #Engineering Slack channel” helps the agent understand not only what to do, but where and how to do it. These details guide AI Companion’s reasoning and directly shape how it interprets and applies the agent.
A strong, well-written description helps ensure every automated action is accurate, purposeful, and aligned with the intent of the conversation. The clearer and more specific the description, the more effectively AI Companion can understand context, follow direction, and deliver results that match your expectations.
Admins can define Hero Prompts — pre-populated prompts that act as curated shortcuts for common or high-value tasks users often perform with a Custom Agent. These prompts appear directly in the AI Companion panel, allowing users to initiate workflows with a single click.
For instance, a Hero Prompt could:
Summarize the shift’s ticket activity: Gather metrics on new, resolved, and open cases from your CRM, along with trends or recurring issues.
Provide today’s Jira summary: Retrieve all newly created tickets or bug reports from the last day, categorize them by project, component, or priority, and generate a concise summary highlighting trends or recurring issues. Automatically publish the summary to a designated message channel for team visibility.
Show renewal opportunities closing this month: Query CRM data, calculate renewal timelines, and surface accounts needing attention.
By predefining these interactions, admins help users bypass redundant setup steps, enabling faster, more consistent outcomes with minimal manual input.
Opt-Out Reasons
Average Inbound
Average Outbound
Responding Time Per Completed Conversation
Average First Response Time
Average Handle Time
Call Queue SMS / Auto Receptionist Scoreboard
Total Call Time (Outbound)
Total Hold Time
Total Parked Time
User's Primary Group
User's Site
Voicemail / Videomail
Automatic Call Recording
Ad-Hoc Call Recording
Call Overflow
Call Transferring
Call Handling & Forwarding
Elevate Call to meeting
Hand Off Call to Room
Mobile Switch to Carrier
Call Delegation
SMS/MMS
Total Calls
Total Recordings
Site
Group
Call Start Time
Inbound / Outbound Direction
Call Result
Call Duration
Call Site
Call Path
Breakdown of Recording Information For
Direction
Caller
Callee
Recording Owner User
Owner User Type
Time
Recording Type
Site
User Performance Reports
Feature Entitlement and Membership Reports
Recording Reports
Access Reports
Team SMS Functionality
Team SMS Summary
Marketing Campaign Assistant: Supports marketers in planning, executing, and optimizing campaigns. It streamlines campaign creation, generates content ideas, and tracks key deadlines and performance metrics.
Search Support Ticket: Helps agents quickly find previously resolved tickets with similar issues, reducing resolution time and improving consistency by searching ticket history and providing context from past cases.








This section outlines the admin experience for managing users, devices, permissions, reports, and settings related to Zoom Phone. After reading this section, you can expect to be familiar with user provisioning, the Zoom Phone dashboard, assigning devices, updating user profile information, and more. For information on managing PBX features of Zoom Phone, refer to the section on Configuring Zoom Phone's PBX.
Zoom Phone supports user roles specific to the Zoom Phone service, allowing account administrators to provide users with precise levels of access to Zoom Phone features as required. For example, with these diverse sets of roles, a user can be a Call Queue admin without granting access to other features, like being able to edit a Site's settings or policies. Alternatively, a user can also be granted Super Admin privileges for Zoom Phone without requiring admin privileges for the rest of a Zoom account's products, service, and features.
The following table outlines the default Zoom Phone roles available; however, an account admin can also create a custom role if necessary:
Refer to Zoom's support center for more information on .
Account administrators and authorized users with appropriate role permissions can design, edit, and oversee Zoom Phone's call routing and distribution tools via the Zoom web portal. These tools, along with design and implementation considerations, were , along with links to Zoom's support center containing instructions and procedures for creating, editing, and managing each tool.
Account administrators have two main methods for provisioning Zoom Phone users, managing entitlements, and mapping information: automated workflows through single sign-on (SSO) via SCIM or SAML response mapping, or manual assignment via the Zoom web portal. These options are briefly discussed in the following two sections.
For accounts utilizing single sign-on (SSO), provisioning users through SAML (security assertion markup language) response mapping or SCIM (system for cross-domain identity management) can streamline the user entitlement and management process. With SAML response mapping, user profile details and entitlements will automatically update each time the user authenticates. Conversely, for accounts using SCIM, user profile information and entitlements will dynamically update as data synchronizes from your identity provider to Zoom.
Although Zoom provides numerous options for profile information and entitlement mapping between SAML and SCIM, how and if this information is applied largely depends on customer configurations within both their identity provider and Zoom account. For this reason, accounts are encouraged to test their SCIM and SAML response mapping configurations for surety of user profile information and entitlement grants when first setting up their Zoom Phone account.
The following Zoom Phone information can be mapped to a user's profile through SAML Response Mapping and/or SCIM API:
For more information on provisioning users over SCIM, refer to the Zoom App Marketplace for a and options.
For accounts without single sign-on or that would prefer to manually provision users, the Zoom web portal provides two primary interfaces for managing user entitlements: individual or bulk user editing through web-based user interfaces, or bulk editing through CSV file uploads.
Web Portal Interface
Account admins can manually provision and assign user licenses through the Zoom web portal's admin interface. This process typically involves individually selecting users and assigning the appropriate licenses and entitlements through pop-ups and prompts. This process can be effective for configuring a small number of users but may be tedious when configuring a large number of users. Customers provisioning more than 100 users at once may prefer mass-provisioning users through the CSV upload process, described below.
For more information on this process, refer to Zoom's support center article on .
CSV Uploads
With CSV uploads, account admins can mass-provision users through a file upload process within the web portal. When provisioning users in bulk through a CSV file, admins can assign the following features to users:
Package
Site Code
Site Name
User Template
Warning
When making bulk CSV edits, users will be updated exactly as the CSV is configured. This can unintentionally remove already configured user information.
For instance, if a user is currently assigned a phone number and a calling plan, and a bulk CSV is uploaded that only specifies the user's new device(s) without the phone number and calling plan reiterated, the user will have their calling plan and phone number removed from their profile.
Put simply, unless you are removing information from a user, all bulk CSV updates should include all current profile information in addition to the new information.
For more information on this process, refer to Zoom's support center article on .
Zoom provides a diverse range of licensing options tailored to various account requirements. Among these options are bundled licenses, wherein a single license may provide a user with access to multiple Zoom products along with additional add-ons; however, Zoom also offers unbundled licenses, which requires admins to assign a different license for each product the user needs access to.
An example of a bundled license includes the Zoom Workplace Enterprise license, in which assigning the single license to a user provisions them for Zoom Meetings, Zoom Whiteboard, Zoom Phone, the Zoom Phone Power Pack add-on, and more. However, with unbundled licenses, there is no "one size fits all" solution, and a user would have to be assigned a Zoom Meetings, Zoom Whiteboard, and Zoom Phone license, and a Power Pack add-on, separately to receive full access to those products and features.
Depending on which license type your account uses, your configuration process may change. For this reason, the following two sections are separated by bundled and unbundled licenses. If you are not sure which applies to your Zoom account, please speak with your Zoom account team.
When assigning bundled licenses, users will be automatically provisioned for all relevant entitlements upon assignment. For example, assigning a Zoom Workplace Enterprise license will automatically assign a user a Zoom Phone License, a Zoom Phone Calling Plan, and the Zoom Phone Power Pack Add-On instantly, whereas each of those components would require a separate license or entitlement with an unbundled licensing model.
If your account does not want to automatically provision a user for Zoom Phone immediately, refer to Zoom's support center for information on how to .
Single Sign-On
If your account is using single sign-on to provision users and assign bundled licenses, simply configure your SAML response mapping or SCIM configuration to provision users with the appropriate license, e.g., Zoom Workplace Enterprise or Zoom Workplace Business Plus. In some cases, you may need extra configurations for additional add-ons not covered by the bundled license.
Unless Zoom Phone provisioning is , users will automatically be assigned a Zoom Phone license, calling plan, and relevant add-ons to the license.
Manual Assignment
Refer to Zoom's support center for detailed guidance on for singular or small user groups, or for a large number of users.
When assigning unbundled licenses, users must be separately assigned a license for each relevant entitlement. For Zoom Phone, this entails being provisioned as a basic Zoom Phone user at a minimum, and adding additional components—like a calling plan and other add-ons—as needed.
Single Sign-On
When provisioning a user for Zoom Phone through Single Sign-On (SSO), keep in mind the following tips as you configure your SAML response mapping or SCIM integration:
A user must be assigned an extension to be automatically provisioned as a basic Zoom Phone user. There is no Zoom Phone Basic license.
Assigning an extension of zero (0) will automatically assign a user the next extension available for the Site. This may be ideal if you do not have extensions pre-configured in your identity provider.
If you are using multiple Sites, ensure the user also passes the criteria to map them to the applicable Site, as each Site typically has a unique Site and extension code.
Manual Assignment
Refer to Zoom's support center for detailed guidance on for singular or small user groups, or for a large number of users.
Zoom Phone customers have a variety of choices for managing and assigning phone numbers within their account. To assist with these processes, this section explores the administrative tools available for managing and allocating phone numbers within a Zoom Phone account, including number porting, using Zoom-provided numbers, and assigning numbers to users.
Zoom attempts to maintain a list of available numbers for certain regions and area codes for customers that are not porting numbers into Zoom Phone or who may simply need additional phone numbers. Customers can select these numbers from the available pool and add them to their account at any time so long as they do not exceed their direct inward dial (DID) number limit, as determined by their licenses that support direct number dialing. Once selected, numbers from the available pool become exclusively associated with your account unless they are released, removed, or ported away from your account.
Refer to Zoom's support center for information on .
In circumstances where Zoom does not have numbers available for use via the self-service process, customers can request that Zoom locate numbers for use with the service.
Refer to Zoom's support center for more information on .
Zoom Phone works with telecommunication providers when possible to port existing numbers into Zoom Phone; however, this process may vary depending on the country of origin and the quantity of numbers required to be ported. Click the links (✔) within the following table for instructions on porting numbers for your Zoom Phone account, depending on the type of number and country of origin. Readers are additionally encouraged to refer to Zoom's support center for Zoom's .
Zoom Phone supports assigning direct inward dial (DID) phone numbers to users and PBX components, including Call Queues, Auto Receptionists, shared line groups, and more. To support this process, account admins can assign phone numbers through two primary methods: single sign-on and manual assignment.
Single Sign-On
Assigning users a direct phone number through single sign-on can simplify a significant portion of user administration with Zoom Phone. To support this process, keep in mind the following tips as you configure your SAML response mapping or SCIM integration:
Zoom Recommendation
Some Zoom Phone features like Call Queues, Auto Attendants, and Shared Line Groups are not easily configured with direct numbers from an identity provider. For these instances, we recommend .
When assigning a user a DID phone number from your identity provider using SAML or SCIM, the number must be listed within your account to apply. If the DID phone number is not listed within your account, it will not be applied to the user.
When passing a phone number through SAML or SCIM, pass as complete of a phone number as possible, including country and area code. For example, +1 555-555-5555 or +44 5555-555555, not 555-5555.
Manual Assignment
Refer to Zoom's support center for detailed guidance on for singular or small user groups, or for a large number of users.
This section discusses available options and features for adding, provisioning, managing, and assigning IP phones and devices within your Zoom Phone account.
There are multiple approaches to managing phones and devices within an account, including the order of user provisioning, device provisioning, device assignment, and more. To account for these various scenarios, Zoom provides multiple options for device management, which are outlined in the following sections.
Zoom Phone offers two methods for provisioning physical devices: zero-touch provisioning and assisted provisioning. Both of these are outlined in the following two sections; however, readers are also encouraged to refer to Zoom's support center for more information on .
Warning
Customers reusing equipment like handsets, IP phones, etc., are encouraged to ensure they fully remove all of their devices and their MAC addresses from their previous provider before re-provisioning them to Zoom Phone. Not unassigning devices from the previous service provider will cause failures during the provisioning process.
Many support zero-touch provisioning (ZTP), which can automatically provision a phone for use without hands-on administrative assistance or configuring the phone through its web interface. For the ZTP process to work, be sure to add your phone to the Zoom web portal before powering it on for the first time or performing a factory reset on a previously used phone. Failure to follow this step may require additional factory resets to re-trigger the ZTP process.
Warning
Zero-touch provisioning (ZTP) requires access to NTP servers for the provisioning process. Customers are encouraged to verify that their IP phone devices can establish connection with the device's specified NTP server—default or otherwise—to successfully complete the provisioning procedure.
Further, DHCP options 66 and 161, if enabled, can impact a device's ZTP capabilities. Customers are encouraged to leave these options unconfigured if using ZTP extensively or using multiple phone device manufacturers within the network.
Finally, customers are urged to verify that their firewall configurations allow for the essential communication channels with their phone manufacturer's
Refer to Zoom's support center for more information on the .
Assisted Provisioning
If you experience issues with zero-touch provisioning or if your phone model doesn't support it, you may be required to perform the assisted provisioning process through the device's web interface.
Refer to Zoom's support center for more information on the .
Account admins can add devices to their account at any time, even if the devices are not currently assigned to users. To do this, Zoom Phone supports two primary methods for adding devices to an account: individual, manual addition through the web portal, or in bulk through a CSV file upload.
Refer to Zoom's support center for more information on or .
Account admins can assign devices to users or common areas through two primary methods: individually through the web portal interface or in bulk through a CSV file upload.
Refer to Zoom's support center for more information on or , or for general information on .
Warning
When making bulk CSV edits, users will be updated exactly as the CSV is configured. This can unintentionally remove already configured user information.
For instance, if a user is currently assigned a phone number and a calling plan, and a bulk CSV is uploaded that only specifies the user's new device(s) without the phone number and calling plan reiterated, the user will have their calling plan and phone number removed from their profile.
Put simply, unless you are removing information from a user, all bulk CSV updates should include all current profile information in addition to the new information.
The Zoom Phone Dashboard, a subsection of , offers account admins and authorized users with sufficient access to insightful Zoom Phone data and analytics. Information available within the Dashboard includes Zoom Phone Quality of Service (QoS) data, Mean Opinion Scores (MOS), usage reports, call data and metrics, and more. The following sections outline different features and data available through the Zoom Phone dashboard. Please follow the following link for more information.
Account admins or users with sufficient role-based permissions can access additional Zoom Phone reports not available to standard users. These reports provide general usage or charge-related information from the account's phone system.
Zoom Phone usage reports allow account administrators to access usage data for one or multiple Call Queues and/or Zoom Phone users during a defined time frame, with up to 100,000 call records in a single CSV file. Information within the reports include:
Account admins can also view a usage report for all charged calls or SMS/MMS messages that were made within a period. The usage report can also be used to verify calling charges on your bill.
Information within the report includes:
Originating Number
Receiving Number
Call/Message Type (Local or International)
Refer to Zoom's support center for more information on s.
If necessary, account admins or authorized users with sufficient role-based permissions can change Zoom Phone settings on behalf of a user. This can be helpful in circumstances where a user needs assistance with configuring a setting or when changing settings on behalf of a VIP user.
Refer to Zoom's support center for more information on on behalf of another user.
Extension Number
Phone Number
Set Outbound Caller ID
Allow User to Change Outbound Caller ID
SMS Enablement
User Status
Desk Phone Brand (Up to 9)
Desk Phone Model (Up to 9)
Desk Phone MAC Address (Up to 9)
Desk Phone Provision Template (Up to 9)
Users can also be assigned a real extension, which will apply if the extension is not already in use within the Site. For instance, if a user's extension prior to Zoom Phone was 222, asserting an extension value of 222 will map the extension to the user if it is available.
Assigning a user a calling plan will elevate them from a basic user to a licensed Zoom Phone user.
If a Site is not specified upon user provisioning (i.e., being assigned an extension and/or calling plan), the user will be provisioned to the main Site.
Japan
Bring Your Own Carrier (BYOC)
Duration (Minutes)
Billing Number (The phone number that was billed for the call or SMS)
Forward Billing Number (The phone number that forwarded the call, if applicable)
Calling Party Name (The display name of the extension that placed the call)
Billing Rate (per minute)
Total Charge
Charge Mode (How total charges are calculated; e.g., per minute)
Phone Super Admin
All Zoom Phone features and settings in the web portal.
Phone Site Admin
Zoom Phone features and settings for a specific Site, excluding settings that can only be changed at the account level.
Call Queue Admin
Features and settings for the specified target Call Queues, including associated call logs and recordings.
Auto Receptionist Admin
Features and settings for the specified target Auto Receptionist. This doesn't include access to the associated call logs.
Recording Admin
Full privileges to view, play, download, or delete call recordings that belong to users and Call Queues.
Compliance Admin
Full privileges to view and manage call logs, recordings, voicemail, and SMS.
Zoom Workplace Basic
Zoom Workplace Pro
Zoom Workplace Business
Zoom Workplace Business+
Zoom Workplace Enterprise
Regional Metered
Regional Unlimited
Global Select
Zoom Phone Extension
Zoom Phone Number
Zoom Phone Role
Zoom Phone Site
United States, Canada, and Puerto Rico
APAC
South America / LATAM
EMEA
Name
Extension
Total Calls Answered (Inbound/Outbound)
Outgoing Number of Calls
Inbound Number of Calls
Number of Calls Forwarded to Voicemail
Number of Inbound Calls Answered by Another User
Missed Number of Calls
Total Call Time
Total Hold Time
Total Parked Time
User Phone Site
Name
Extension
Site
Inbound Call Volume
Completed Calls (Inbound)
Abandoned Calls (Inbound)
Overflow (Inbound)
Avg. Call Waiting Time
Outbound Call Volume
This section discusses core processes and features involved in configuring Zoom Phone's PBX for your account, including Sites, call routing tools, business hours, common area devices, SMS, and more. For information on configuring users, IP phones, and other elements of Zoom Phone, refer to the Admin Experience section.
Once an account is provisioned with Zoom Phone licenses, an account admin must complete an initial setup before using the service. This process involves choosing a Main Company Number, a starting extension, and defining an emergency address. This process effectively creates the first Site for an account, and any configured information can be updated at a later time if necessary.
Refer to Zoom's support center for more information on getting started with Zoom Phone, which includes instructions for the initial setup process.
Zoom Recommendation
If your account has no more than 150 Zoom Phone licenses, you can schedule a session with a Zoom Phone Enablement Specialist who can assist with setting up your account. For more information, reach out to your account team.
A Site is a specific term used within Zoom Phone that groups users with shared characteristics—like a common access code, physical address, building, SIP Zone, department, or policies—into a single, manageable group within the Zoom web portal. For some customers, a single Site may represent all users within their business and can span multiple buildings within a campus or location; for others, multiple Sites may be required depending on your business needs, granularity of control, global presence, etc.
Zoom Recommendation
For small businesses in a single location that do not require granular levels of setting controls, a single-Site design is probably sufficient for your needs. Alternatively, if you need to control user settings by location, floor, department, or building, a multi-Site model might be best for you.
Refer to Zoom's support center for more information on .
Within Zoom Phone, the Main Company Number is the phone number assigned to each Site's Main , which is automatically assigned to the Site upon creation. If your account uses multiple Sites, you will have multiple Main Auto Receptionists, each with a unique Main Company number specific to each Site.
Within each Site, the following Policies, Settings, and Emergency Services are available for configuration. As the Zoom Phone team continually innovates, feature availability may change, and additional unlisted features may also be available. If a feature important to your organization is not listed, please contact your account team for more information.
Zoom Phone Site Policies
Call Live Transcription
Play notification prompt
External calling on Zoom Rooms Common Area
Zoom Phone Site Settings:
Routing Rules
Zoom Phone Local Survivability
Default Business Hours
Zoom Phone Site Emergency Services:
Route Emergency Calls to Public Safety Answering Point (PSAP)
For an Extension Without a Local Phone Number
Route Emergency Calls to PSAP
The following sections outline various call routing tools available within the Zoom Phone PBX.
An Auto Receptionist is a call routing feature designed to simplify call handling within the Zoom Phone system. Because an Auto Receptionist is automatically created and associated with every new Site, Auto Receptionists are commonly used as a first point of contact for most inbound callers and act as a virtual receptionist, performing roles like greeting callers with customizable, recorded messages, and providing them with options to reach their intended contact or department.
When configuring the Main Auto Receptionist associated with a Site (or a secondary Auto Receptionist), the admin should configure it with the features and routing logic best suited for their needs. For some customers, this may include connecting their Auto Receptionist with other call routing features (discussed in the following sections) like an Interactive Voice Response (IVR) menu or a Call Queue. For others, it may simply route to users or a voicemail inbox. Overall, there are many different ways to configure an Auto Receptionist, but which configuration is best for you will depend on your call routing goals and business needs.
Settings available for an Auto Receptionist include:
Refer to Zoom's support center for more information on or Auto Receptionist settings.
An Interactive Voice Response (IVR) system is a powerful call routing tool that routes callers through a menu of options using their keypad or voice commands. When paired with other call routing features like Auto Receptionists and Call Queues, an IVR can drastically simplify call routing for your business.
Once fully configured, an IVR offers a menu of options for callers to choose from, connecting them to the appropriate department, individual, Call Queue, shared line group, or Auto Receptionist, etc. based on their selection. This enhances efficiency by quickly connecting users to the right resource based on their response, and simultaneously reduces the need for manual call handling by a human agent.
However, for an IVR to work effectively, customers must provide a recording that instructs the user which dialpad key they must press to reach their intended destination, such as "Press 0 to reach the operator. Press 1 to reach sales."
To provide a functional perspective of IVRs, if an Auto Receptionist is the most common first point of contact for an inbound caller, an IVR is most likely the second most-common contact point, as it provides the underlying logic that routes a user to their intended destination. For your convenience, we've provided a functional example of how to pair an IVR with an Auto Receptionist .
Settings available for an IVR include:
Customizable IVR Greeting Audio Prompt
Timeout Options
Refer to Zoom's support center for more information on .
A Call Queue is a call routing feature that efficiently manages incoming call volume by placing callers in a virtual waiting line until an agent can assist. Once the caller is in-queue, they can be instantly greeted with customizable messages and/or music until the next agent answers their call. For most businesses, Call Queues are a call routing destination and are used to connect callers to a specific department or group of users with a speciality, like sales, IT support, or customer service. Call Queues are typically not intended to forward calls to another call routing service, like an IVR or Auto Receptionist, except in circumstances of overflow or no pickup response.
Administrators can set up multiple queues for different departments or purposes, and assign agents to specific queues based on their expertise. Additionally, Call Queues support multiple options for ring order, including sequential, simultaneous, rotating, and more, offering organizations flexibility for handling inbound calls.
With the , Call Queues can also provide real-time and historical information for monitoring and reporting, allowing supervisors and agents to track call volume, wait times, and queue performance. With this data, organizations can optimize their customer service operations, reduce call abandonment rates, and promptly and effectively handle incoming calls.
Settings available for a Call Queue include:
Refer to Zoom's support center for more information on a Call Queue or its settings.
Shared Line Groups (SLGs) are a call routing feature that allow up to 10 users to collaboratively answer and manage incoming calls for up to 10 different phone numbers. These groups are ideal for teams, departments, or work groups that need to handle incoming calls collectively, without the additional layers of infrastructure, settings, or management associated with a Call Queue.
In an SLG, ringing is always simultaneous for all members, and any time an associated phone number is dialed, each group member's phone will ring. For instance, if an SLG has 10 associated phone numbers, any time any of the numbers are dialed, all active SLG user's phones will ring until the call is answered, overflowed, or disconnected.
Like a Call Queue, an SLG is often used as a call routing destination and is not intended to forward calls to another call routing service like an IVR or Auto Receptionist, except in circumstances of overflow or no pickup response.
Refer to Zoom's support center for more information on or shared line groups.
Group Call Pickup is a call distribution tool similar to a Shared Line Group (SLG). However, instead of ringing all users within a group immediately like an SLG, users will only receive a prompt to pick up the call if the dialed user does not answer the call within a specified amount of time.
For instance, if a user and member of a Group Call Pickup queue does not answer a direct call within 10 seconds, all other group members will receive a notification to accept or dismiss the call, helping prevent missed contact opportunities or call abandonment.
Refer to Zoom's support center for more information on Group Call Pickup.
Auto Receptionists, Call Queues, and Shared Line Groups provide a range of call routing functionalities for diverse environments, and knowing which call routing tool to use could hold significance for your organization. To help clarify these tools and their limitations, readers are encouraged to refer to Zoom's support center for a consolidated and simplified .
Shared Line Groups and Call Queues share many similarities, and knowing which to use, or when to use one over the other, can be confusing at times. Put simply, a Shared Line Group is a simplified version of a Call Queue, but in an effort to help clarify the practical uses of each, the following table outlines some of the biggest key differences between the two, followed by an example use case:
Example Use Case
The law firm Omzo, Omzo, & Omzo is configuring Zoom Phone for their business. Due to the large number of daily calls to their main phone number, they are trying to decide between a Shared Line Group and Call Queue.
With the SLG, multiple receptionists or administrative staff members can share the responsibility of answering incoming calls to the firm's main phone line. Together, they can collectively manage call volume during peak times, ensuring that callers are promptly assisted and that no calls are missed. Due to the relative simplicity of the SLG, callers will not receive a customized greeting prompt, hold music, or time spent in a queue. And if all staff within the SLG are occupied, incoming calls will immediately Overflow to the assigned destination, such as voicemail or another call routing tool.
With a variety of call routing tools available, crafting a logical and efficient call routing design can be a challenging task for those new to the process. To help with this experience, consider the following tips as you plan and design call routing configurations for your business. As a bonus, we've also provided an example and reference diagram for a common Main Auto Receptionist that is used by many businesses, and is easily expanded upon:
Auto Receptionists are an excellent starting point. If you are new to designing call routes for a business, an Auto Receptionist is almost always a safe place to start. Each Site automatically receives an Auto Receptionist, making it the ideal starting place; it also supports customized greetings, and it can naturally flow into an IVR, connecting users to their next or final destination.
Interactive Voice Response Menus (IVRs) are your friend. An IVR offers users up to 12 different input options to connect to another call routing destination; this means users can probably get to their intended destination or department in a single button press. However, in some cases, it might make sense to use an IVR to route to another IVR, too. For instance, pressing 1 to route to customer support and then connecting to another IVR that can connect them to different kinds of technical support. Don't be afraid to use them to connect users to the right place.
Draw it out in pencil or on a .
Business Hours is a call management feature that lets admins and users set specific hours and days of the week for calls to adhere to "standard" handling procedures or follow alternate handling protocols, such as when the business is closed. Business hours are applicable to many features, including Call Queues, Shared Line Groups, Auto Receptionists, and Sites, and can also be defined on a user-specific level.
During a user's or tool's designated business hours, calls will be routed according to the defined rules, such as forwarding to available agents or playing custom messages. Outside of business hours, organizations can choose to route calls differently, such as sending them to voicemail, a Call Queue, an Auto Receptionist, or forwarding to an external number.
Refer to Zoom's support center for more information on ; however, to edit Business Hours for a specific call routing feature, like a Call Queue or Auto Receptionist, locate and edit the specific call routing tool within the Zoom web portal.
Holiday Hours is a complementary feature to Business Hours that is designed to manage incoming calls during holidays or special occasions when business operations may be different from regular hours. Organizations can set up specific holiday schedules in advance, indicating when they will be closed or have limited availability. During these designated holiday hours, calls will be routed according to defined rules specific to the Holiday Hours configuration, such as forwarding to voicemail, playing custom messages, or routing to an external contact.
Zoom Phone supports Short Message Service (SMS) (i.e., text messages) and Multimedia Messaging Service (MMS) (i.e., photo messages) with the Zoom Phone Native service and BYOC plans for users with the necessary entitlements.
By default, all users on the same Zoom Phone account can send SMS/MMS messages to each other; however, to send an SMS to a phone number outside the Zoom Phone account (i.e., an external number), the business must meet . For more information on this process, refer to the .
Refer to Zoom's support center for more information on , , or .
Common Area Phones are dedicated devices intended for shared use in common areas within an organization, such as lobbies, break rooms, or conference rooms. These phones provide basic calling capabilities for employees or visitors without personal calling plans or entitlements, and are typically configured with essential features like dialing and receiving calls, making them ideal for general use by anyone within the organization.
Refer to Zoom's support center for more information on or
Using Zoom Phone with Zoom Rooms or a allows users to seamlessly transition between voice calls and video conferencing within the conference room environment. With this feature, Zoom Rooms and third-party conference rooms can reduce the amount of hardware devices required by making use of the microphones and speakers that are already present within the room.
Refer to Zoom's support center for more information on , , or .
Zoom Phone's 911 service operates differently from traditional emergency calling setups. With traditional emergency calling, a phone provider routes calls to a local emergency responder or Public Safety Answering Point (PSAP) based on the caller's telephone number. Alternatively, with Zoom Phone's enhanced 911 (E911) service, we take it a step further. With Zoom Phone, when a user calls 911, the service will automatically send the user's address (if they've provided it) and telephone number to the appropriate PSAP based on their current location, connecting users to emergency resources with the best available information.
Further, because Zoom Phone allows customers and their users to utilize the service wherever there's internet access and to acquire numbers not necessarily tied to their current location, Zoom Phone provides two extra features suited for modern workplaces: Nomadic Emergency Services and Emergency Call Routing. Each of these features are described in the following sections.
In today's hybrid working world, Nomadic Emergency Services provide the ability to dynamically detect and report a Zoom Phone user's location when making an emergency call.
Under normal circumstances, such as when a user makes an emergency call from within the office, the corresponding emergency address for the user's assigned Site or location (configured by an admin in the web portal) is sent to emergency responders. However, with Nomadic Emergency Services, whenever a user is identified at a location outside their office, they can define a new emergency address specific to their current location. Consequently, if a user makes an emergency call while working nomadically, like at home, a hotel, or coffee shop, Zoom Phone will automatically transmit the nomadic emergency address to emergency responders.
Refer to Zoom's support center for more information on and the .
With Emergency Call Routing customization, businesses can choose to route emergency calls to a public-safety answering point (PSAP) and/or an internal safety response team that handles emergencies. For companies spanning large geographical areas, like multi-building campuses, this capability aids on-site teams in swiftly addressing emergencies within their facilities, or collaborating with emergency responders to rapidly pinpoint the emergency location.
Alternatively, businesses can also disable emergency calling for phone users, which can be useful when phone users are not within the country associated with their phone number due to travel or are permanently located in another country.
Refer to Zoom's support center for more information on .
For businesses that do not require assigning every user a dedicated phone number or calling plan, Emergency Number Pools maintain a list of dedicated emergency phone numbers available for their users.
With an Emergency Number Pool, when a Zoom Phone user without a dedicated phone number (i.e., extension-only) places an emergency call, a number from the pool will be chosen as the extension's temporary caller ID. This allows emergency responders to contact the user back, as they otherwise would not have access to the user's extension and would be unable to reach them. Consequently, for the next two hours, any additional incoming calls made to that caller ID will be directed to the original extension that made the emergency call.
Dedicated numbers enable extension-only users to make outbound emergency calls using a direct phone number belonging to a Call Queue or Auto Receptionist. Unlike Emergency Number Pools, dedicated numbers must be associated with a Call Queue or Auto Receptionist and cannot be waiting on standby.
With dedicated numbers, when an extension-only dials emergency services, the Call Queue or Auto Receptionist's phone number will be presented as the caller ID to the PSAP. Consequently, any returned calls from emergency services will be routed to the associated Call Queue or Auto Receptionist, and must route back to the user organically.
Warning
This method should only be used when a Call Queue or Auto Receptionist is the best method for handling emergency callbacks in your environment.
Maintaining emergency services connectivity during an internet outage or service-impacting event is critical for many businesses. To proactively address these scenarios, customers can maintain survivability connectivity with the Zoom Phone Local Survivability (ZPLS) service module, which leverages the platform and OS provided by Zoom Node to provide backup PSTN connectivity through an on-premises SBC with an integrated carrier.
For more information, refer to the section on available later in this document.
Zoom Phone supports cloud paging with select , allowing authorized users to broadcast one-way announcements or alerts to supported devices across multiple locations. This feature is notably useful in environments like warehouses, schools, hospitals, retail stores, or large office buildings where instant communication and emergency notifications are essential to standard business operations.
Refer to Zoom's support center for more information on for your account.
Provisioning Templates simplify the process of setting up and configuring IP desk phones within the Zoom Phone system. With Provisioning Templates, Zoom Phone admins can create custom settings for IP phones that can be applied to users from multiple levels, ranging from the entire account to individual or multiple Sites, a group of desk phones, or a single desk phone.
Refer to Zoom's support center for more information on .
Select Outbound Caller ID
Hide Outbound Caller ID
Personal Audio Library
Allow Music on Hold Customization
Allow Voicemail and Message Greeting Customization
Personal Voicemail & Videomail
Allow Videomail
Allow User to Download Their Own Videomail / Voicemail
Allow User to Delete Their Own Videomail / Voicemail
Allow User to Share Their Own Voicemail
Allow Virtual Background for Videomail / Video Greeting
Voicemail / Videomail Transcription
Voicemail / Videomail Notification By Email
Include Voicemail / Videomail File
Include Voicemail / Videomail Transcription
Forward Voicemail to Email
Shared Voicemail / Videomail Notification by Email
Restricted Call / SMS Hours
Allowed Call / SMS Locations
Check Voicemails Over Phone
nces for Redirected Calls
Display End-of-Call Experience Feedback Survey
Obfuscate Sensitive Data During a Call
Incoming Call Notification Options
Automatic Call Recording
Access Member List
Ad-Hoc Call Recording
Access Member List
Allow User to Access Their Own Recording
Download
Delete
Allow Call Recording Transcription
International Calling
Manage Country / Region
Call Queue Pickup Code
Exempt List
Zoom Phone on Mobile
Allow Calling and SMS / MMS functions on Mobile
Zoom Phone on Progressive Web App (Google Chrome Web App)
SMS
SMS Templates
End-to-End Encryption
Call Handling & Forwarding
Restrictions
Allow Users to Edit Call Handling Settings
Call Overflow
Restrictions
Enable Users to Allow Their Calls to Reach an Operator
Allow Users to Forward Their Calls Outside of Their Own Site
Call Transferring
Restrictions
Elevate a Call to a Meeting
Call Park
Expiration Period
When a Parked Call is Not Picked Up
Call Park Location Assignment
Hand Off to Room
Mobile Switch to Carrier
Delegation
Audio Intercom
Call Screening
Block Calls Without Caller ID
Block External Calls
Advanced Encryption
Call Queue Opt-Out Reason
Auto Delete Data After Retention Duration
Call Logs
Ad-Hoc Recordings
Auto Call Recordings
Set Caller ID Viewing Prefere
Default Overflow for Closed Hours
Default Holiday Hours
Default Overflow for Holiday Hours
AES-256 Encryption for Supported Devices
Audio Prompt Language
Default Audio Prompt
Hot Desking Session Timeout
Templates
Dial by Name Directory
Private Directory
Additional Outbound Caller ID for User and Common Area Phones
Call Queue Numbers (For Members)
Shared Line Group Numbers (For Members)
Auto Receptionist Numbers (All users and Common Area Phones)
Customized Numbers
Show Outbound Caller ID for Internal Calls
Desk Phone General Settings
Web Interface
Admin Password
Desk Phone Firmware Update Rules
Don't Route Emergency Calls to PSAP
Route Emergency Calls to Internal Safety Response Team
To PSAP and Internal Safety Response Team Simultaneously
To Internal Safety Response Team First, then to PSAP After Max Holding Time
Nomadic Emergency Services
Emergency Address
Emergency Address Management
Allow User to Manage Own Emergency Address
Location Management
GPS Coordinates
Custom Call Handling for Emergency Service Numbers
Hold Music
Supported
Unsupported
Wrap-Up Time
Supported
Unsupported
In this example, both an SLG and Call Queue are capable of meeting the firm's needs, but it is up to the firm to decide which of the two is best-aligned with their intended goals for their callers and business.
Voicemail
Play a message, then disconnect
User
Zoom Room
Common Area Phone
Cisco/Poly Room
Auto Receptionist
Call Queue
Shared Line Group
Interactive Voice Response (IVR) Menu
External Contacts
Phone Number
Voicemail Access
Voicemail Transcription
Voicemail Notification by Email
SMS
SMS Templates
Call Screening
Block Calls Without Caller ID
Customizable Greeting Prompt
Business Hours
Holiday Hours
Time Zone
Communication Content Storage Location
Audio Language Prompt
Extension Number
Voicemail
Cost Center Assignment
User
Zoom Room
Common Area Phone
Cisco/Poly Room
Auto Receptionist
Call Queue
Shared Line Group
External Contact
Phone Number
Current Extension
User
Auto Receptionist
Call Queue
Shared Line Group
Call Distribution
Simultaneous
Sequential
Rotating
Group Rotating
Longest idle
Overflow—Route to:
Voicemail
Play a message, then disconnect
User
Customizable Greeting Prompt
Audio While Connecting
Music on Hold
Business Hours
Holiday Hours
Time Zone
Communication Content Storage Location
Audio Language Prompt
Extension Number
Voicemail
Cost Center Assignment
Receive Calls While on A Call
Max Wait Time
Wrap-up Time
Max Calls in Queue
Voicemail Access
Voicemail Transcription
Voicemail Notification by Email
Automatic Call Recording
Allow Ad-Hoc Call Recording
Call Queue Pickup Code
SMS
SMS Templates
Call Screening
Block Calls Without Caller ID
Call Queue Opt-Out Reason
Chat Channel
Extension Number
Department Assignment
Cost Center Assignment
Audio Prompt Language
Business Hours
Holiday Hours
Timezone
Voicemail
PIN Code
Communications Content Storage Location
Allow members to prevent others from picking up a held call, and using whisper, barge, or take over (if configured)
Voicemail Access
Voicemail Transcription
Voicemail Notification by Email
Check Voicemails Over Phone
Call Screening
Block Calls Without Caller ID
Call Distribution
Simultaneous, Sequential, Rotating, Idle
Simultaneous
Waiting Queue
Queue Until Overflow or Max Wait Time
Overflow When Full
Reporting
Supported
Unsupported
Customizable Greeting Prompt
Supported
Unsupported
Videomail
SMS / MMS
After Retention Duration
Soft Delete Data
Permanently Delete Data
Common Area Phone
Cisco/Poly Room
Auto Receptionist
Call Queue
Shared Line Group
Interactive Voice Response (IVR) Menu
External Contacts
Phone Number
Disconnect
The following diagrams demonstrate the core data processing pathways and functional architecture of each feature.
The following diagram illustrates the dataflows behind most of Zoom AI Companion's features, organized by Content Resources that provide inputs to these AI services:
Static Artifacts 📦: Artifacts that are stored at rest, such as post-meeting transcripts, Zoom Team Chat messages, text messages, voicemail, etc.
Real-Time Artifacts ⚡: Artifacts that are considered “live” and ongoing in real-time, such as a live transcript from a meeting or phone call or an active chatbot conversation. Keep in mind that after the live session completes, if these records are retained, they will transition to Static Artifacts⚡.
Data Sources 🤖: Third-party artifacts (email, calendar, and/or files) indexed in a retrieval-augment generated module for improved AI capabilities, if the account setting is enabled. For example, emails and calendar events users can search for with AI Companion.
On-Demand Artifacts 💥: Information that is processed in real-time during active user sessions within the Zoom Workplace app, exclusively for providing contextual input to AI services without any persistent storage or indexing. These artifacts are dynamically pulled from local sources only when needed for immediate workflow context. For example, responding to an ongoing email thread with the Email Compose feature will temporarily include previous emails in the payload to the third-party service directly from the Zoom Workplace app's local access—not the host server—providing context that helps shape the response. A list of On-Demand artifacts may include but are not limited to:
Zoom Team Chat Messages
Zoom Docs
In conjunction with the content resources, each feature falls into one of three categories based on how it uses contextual information, as shown in the Context Table:
Context-Dependent Features: Features that always utilize a relevant, contextual artifact for delivering an AI service. For example, Live Transcripts are used to produce Meeting Summaries.
Context-Possible / Context-Conditional Features: Features that can use relevant, contextual artifacts for delivering an AI service, depending on the context or user actions. For example, responding to an ongoing email thread with Email Compose will use a contextual artifact, while using Email Compose in a brand new email will not.
User-Input Features: Features that always require user input to function. For example, generating a virtual background based on the user’s input.
By combining the Content Resources and the Context Table into the following unified table, you can see which data types each feature uses, as each feature is labeled with the appropriate symbol to indicate the content source it relies on.
For example, within the AI Companion Panel section are a list of features broken down by being Context-Dependent, Context-Possible, and User-Input. In the Context-Dependent section is Smart Scheduling, with the content resources Static Artifacts 📦, On-Demand Artifacts💥 , and Data Sources 🤖 in the column next to it. Together, these reveal that this feature can use artifacts from all three sources, if they are available (note that these features may work in a diminished capacity if not all context sources are available. ).
Alternatively, under the User-Input section is General Knowledge Queries. Because this feature does not intrinsically depend on any context, except for user-inputs, there are no content resources listed.
Warning
The following tables account for standard artifact use cases. The diagram and table cannot account for user-provided files paired with requests. Readers should assume users may upload files at any time with any feature unless . Additionally, some features may combine multiple artifact types for optimal results. If certain data sources are unavailable, features automatically adapt to deliver the best possible experience with remaining resources. For example, Context-Aware Follow-Ups creates more detailed responses when third-party Data Sources 🤖 are accessible, while still providing valuable follow-ups without them.
The following diagram outlines typical dataflows for AI Companion when used with third-party meeting services.
The following diagram illustrates how Zoom generates virtual background generation with AI Companion.
The following diagram illustrates how Sentence Completion works within the Zoom Workplace app.
In-App Contextual Awareness
Static Artifacts 📦 On-Demand Artifacts 💥 Data Sources 🤖
Provides intelligent, context-aware assistance that adapts responses based on your current location and activity within the Zoom Workplace application.
Post-Meeting Transcript Querying
Static Artifacts 📦
Enables users to ask natural language questions about meeting content and receive instant responses from meeting transcripts.
Smart Scheduling
On-Demand Artifacts 💥 Data Sources 🤖
Searches colleagues' calendars to find and schedule meeting times that work for both parties.
Context-Possible
Agenda Creation
Static Artifacts 📦 On-Demand Artifacts 💥 Data Sources 🤖
Generates structured agendas leveraging insights from meeting preparation to ensure attendees are aligned on discussion topics.
Prompt Assistance
On-Demand Artifacts 💥
Helps users craft better AI prompts by providing guidance on how to phrase queries for optimal results.
Meeting Preparation
Static Artifacts 📦 On-Demand Artifacts 💥 Data Sources 🤖
Synthesizes data from various sources to provide personalized summaries, key discussion points, and relevant context before meetings.
User-Input
General Knowledge Queries
None
Provides definitions, explanations, and contextual insights by leveraging built-in LLM knowledge or conducting web-based searches.
Virtual Background Generation
None
Creates custom AI-generated backgrounds for meetings using generative AI based on user text prompts.
Quick Scheduling
On-Demand Artifacts 💥 Static Artifacts 📦
Allows users to schedule meetings directly from chat interface by automatically suggesting available times based on participants' schedules.
Sentence Completion
On-Demand Artifacts 💥
Assists users by offering AI-generated suggestions to finish sentences as they type based on conversation context.
Voicemail Prioritization
Static Artifacts 📦
Automatically identifies and prioritizes voicemail messages that match predefined topics or intents.
Voicemail Tasks
Static Artifacts 📦
Analyzes voicemail content and automatically suggests tasks based on key details to help users stay organized.
Create Zoom Doc
Static Artifacts 📦
Creates a collaborative Zoom doc using the Call Summary.
Follow-Up Tasks
Real-Time Artifacts ⚡
Automatically identifies and suggests follow-up actions based on conversation details to ensure issues are addressed.
Smart Compose
Static Artifacts 📦
Helps agents refine their messaging by providing AI-generated suggestions for copyediting, rephrasing, and tone adjustments.
Smart Compose
None
Quickly generates content for event descriptions, session details, speaker bios, and lobby announcements based on user prompts.
Context Type
Feature
Content Resource
Description
Context-Dependent
Chat Summaries & Search
Static Artifacts 📦 On-Demand Artifacts 💥
Summarizes recent messages in active chat channels and helps locate specific conversation points users may not clearly remember.
Context-Aware Follow-Ups
Static Artifacts 📦 On-Demand Artifacts 💥 Data Sources 🤖
Generates personalized follow-up messages based on meeting transcripts to ensure accuracy and relevance in post-meeting communication.
Data Analysis
On-Demand Artifacts 💥 Data Sources 🤖
Allows users to upload datasets and quickly generate summaries of key findings, patterns, and trends.
Context Type
Feature
Content Resource
Description
Context-Dependent
In-Meeting Questions
Real-Time Artifacts ⚡
Allows participants to discreetly ask AI Companion questions about the meeting using real-time transcript analysis.
Meeting Summary
Real-Time Artifacts ⚡
Automatically generates structured summaries capturing key discussion points, decisions, and action items after meetings conclude.
Context Type
Feature
Content Resource
Description
Context-Dependent
Smart Recording
Static Artifacts 📦
Enhances cloud recorded meetings by automatically generating structured summaries, highlighting key moments, and identifying action items.
Voice Recorder
Real-Time Artifacts ⚡
Brings the power of AI Companion to in-person conversations by capturing, transcribing, and summarizing live discussions through the Zoom Workplace mobile app.
Context Type
Feature
Content Resource
Description
Context-Dependent
Thread Summary
On-Demand Artifacts 💥 Static Artifacts 📦
Provides AI-generated summaries of all messages within a thread, highlighting key points, decisions, and action items.
Document Summary
On-Demand Artifacts 💥 Static Artifacts 📦
Provides AI-generated summaries of attached text-based files or Zoom docs.
Context-Possible
Chat Compose
On-Demand Artifacts 💥 Static Artifacts 📦
Uses AI to assist users in drafting messages by analyzing conversation context and offering suggestions for tone, topics, or length.
Context Type
Feature
Content Resource
Description
Context-Dependent
Call Summary
Real-Time Artifacts ⚡
Generates AI post-call summaries capturing key details such as dates, names, discussion points, and action items.
Call Questions
Real-Time Artifacts ⚡
Answers user questions using the live transcript as context.
Team SMS Thread Summary
Static Artifacts 📦
Generates AI summaries of Team SMS conversations for Call Queue and Auto Receptionist members.
Context Type
Feature
Content Resource
Description
Context-Dependent
Agent Talk Metrics
Real-Time Artifacts ⚡
Provides real-time insights into agent speaking speed and speech length during customer engagements.
Consumer Sentiment Analysis
Real-Time Artifacts ⚡
Provides real-time insights into customer sentiment during messaging and voice interactions using AI analysis.
Conversation Summary
Real-Time Artifacts ⚡
Provides agents with AI-generated summaries of previous conversations when receiving transferred engagements.
Context Type
Feature
Content Resource
Description
Context-Dependent
Zoom Tasks
Real-Time Artifacts ⚡
Captures action items and follow-ups directly within Zoom Workplace, automatically generating tasks from meeting summaries or Contact Center interactions.
Context Type
Feature
Content Resource
Description
Context-Dependent
Email Summary
On-Demand Artifacts 💥
Provides AI-generated summaries of emails.
Context-Possible
Email Compose
On-Demand Artifacts 💥
Helps users draft emails more efficiently by providing AI-generated suggestions based on email thread context or specific user inputs.
Context Type
Feature
Content Resource
Description
Context-Possible
Content Generation
Static Artifacts 📦
Enables users to generate ideas, refine existing content, and add visual elements to whiteboards with AI assistance.
Context Type
Feature
Content Resource
Description
Context-Possible
Content Generation and Revision
Static Artifacts 📦
Assists users in creating and refining documents by offering suggestions for new content, generating summaries, and revising existing content.
Sentence Completion
On-Demand Artifacts 💥
Assists users by offering AI-generated suggestions to finish sentences as they type based on conversation context.
Context Type
Feature
Content Resource
Description
Context-Possible
Chat Compose
Static Artifacts 📦
Allows users to quickly craft professional and contextually-aware responses within event lobbies.
User-Input
Email Compose
None
Helps users create email content for event communication including email bodies, subject lines, and call-to-action text.
Image Generation
None
Creates custom images for events including headers, session images, and expo images using AI-generated content.
Context Type
Feature
Content Resource
Description
Context-Dependent
Ask Questions
Static Artifacts 📦
Queries user selected documents for information and provides AI-generated responses using information from the selected artifacts.


