T1 · T1-R01 · Zoom Workplace
What Zoom Workplace names
Read the company and the product family as two layers. Wikipedia describes Zoom Communications, Inc., formerly Zoom Video Communications, Inc., founded in 2011 by Eric Yuan, with the software launched in January 2013. That history is not a dial plan. It tells you which company publishes the pages you are about to trust.
Learn it in 5 minutes
- Wikipedia's article, opened as Zoom Communications, calls the company a communications technology company in San Jose, known primarily for the videoconferencing platform Zoom.
- The blog that opened is titled Say Hello to Zoom Workplace, an Evolution in the Zoom Platform Experience.
- The same Zoom navigation lists Meetings, Chat, Phone, Mail and Calendar, Scheduler, Whiteboard, Clips, and Rooms under Zoom Workplace.
- Zoom Contact Center sits under a Zoom CX heading on that navigation, beside Workforce Management, Quality Management, and Virtual Agent.
- A marketing URL for Zoom Phone returned HTTP 404 in this session. The Phone name is still on the navigation and on the developer docs.
Visual
Count the boxes: 4. Each label is a name from a page or a study label marked on the drawing.
Flow
What is going on
Read the company and the product family as two layers. Wikipedia describes Zoom Communications, Inc., formerly Zoom Video Communications, Inc., founded in 2011 by Eric Yuan, with the software launched in January 2013. That history is not a dial plan. It tells you which company publishes the pages you are about to trust.
Zoom Workplace is the name on the blog and in the product navigation. The developer API reference groups Workplace items (Meetings, Chat, Phone, Mail, Calendar, Scheduler, Rooms, Clips, Whiteboard, Conference Room Connector) separately from Zoom CX (Contact Center, Virtual Agent, Quality Management, Workforce Management). Treat those as names on a page, not as a promise that every account owns every module.
The API reference also lists a section titled AI Companion (retired). Confirm the current assistant name on a Zoom page for your account before you teach it as a live product.
Worked example
Open the Workplace blog and the API reference side by side. Write two columns: names under Workplace, names under Zoom CX. If a name is only in a menu, write menu. If a paragraph defines it, write defined. Phone is in the menu and in the developer guide. A consumer Zoom Phone product URL was not verified here.
Quiz
1. The blog title that opened names Zoom Workplace.
True. The title is Say Hello to Zoom Workplace, an Evolution in the Zoom Platform Experience.
2. This lab verified a public Zoom Phone marketing URL.
False. Several Zoom Phone product paths returned HTTP 404. The name remains on the navigation and the developer docs.
Ecosystem
Sister pieces sit on the ecosystem page: the glossary, the mind map, the integration map, and the bridges.
- Zoom Workplace — The product-family name on the Zoom blog and navigation that opened in this session.
- Zoom CX — The navigation group that lists Contact Center, Virtual Agent, Quality Management, and Workforce Management on the pages that opened.
Config. In a study note, copy the menu names you saw. Do not add a SKU.
Troubleshooting. If a teammate cites a Zoom Phone URL that 404s, use the developer Phone page that did open, and mark the marketing URL confirm.
Bridge. Phone is the voice name inside Workplace. Contact Center is the CX name beside it. They are both on the navigation. That does not prove they share one dial plan.
Mind map, sister technologies, and future hooks live on the ecosystem page.
Sources and go deeper
Opened 2026-10. A row marked confirm has no link, because that page was not verified.
- Zoom. Say Hello to Zoom Workplace last checked 2026-10
- Zoom. Zoom API reference last checked 2026-10
- Zoom. Zoom Contact Center product page last checked 2026-10
- Wikipedia. Zoom Communications last checked 2026-10
- Zoom. Official Zoom Support last checked 2026-10
- Confirm. Zoom Phone consumer product page. confirm. Requests for several /products/zoom-phone paths returned HTTP 404. last checked 2026-10