Products · Meeting communications compliance requirements
Communication Compliance

Chat Etiquette

An employee pastes an account number or passport details into chat, Zoom stops the message or asks for confirmation. The administrator sets the rules, the check runs on the device.

What it is

The Chat Etiquette Tool is a set of rules in the Zoom account that check a message before it is sent. A rule describes keywords or a regular expression, for example the format of a bank card, a tax ID or a passport number. When a rule fires, the message is either blocked or the user sees a warning and confirms sending themselves.

The rules apply in Team Chat, in meeting chat, in webinar chat and in webinar Q&A. Zoom Events has its own tool of the same kind.

The check runs on the client side. Zoom states it plainly: the tool sends no text, metadata or events to the administrator, to Zoom or to third parties. It is protection against an employee's slip, not a surveillance system.

What a rule can describe
  • Keywords and their variants
  • Regular expressions: card, account and document numbers
  • Block the message
  • Or ask to confirm sending
  • Up to 50 policies per account

An employee's mistake does not become an incident

Leaks happen more often through carelessness than malice. Copied the wrong thing, pasted it in the wrong place, sent it.

Caught before sending

The rule fires at the moment Send is pressed. A message with a card number does not reach the shared channel.

The person stays in the loop

In warning mode the employee sees what worried the rule and decides. False positives do not block work.

Nothing leaves the device

The check is on the device. The administrator sets the rules but gets no copy of the conversation. Easier to agree with staff and with lawyers.

Capabilities

What you get from the Chat Etiquette Tool

Rules, coverage and modes

Keywords

A list of words and phrases that must not appear in chat: project names under NDA, internal code names, rudeness.

Regular expressions

Patterns for structured data: card and account numbers, tax IDs, passports, contract numbers. One pattern covers every way of writing it.

Blocking

The message is not sent, the user sees the reason. For data that must never be passed in chat under any circumstances.

Confirmation

The message is held, the user confirms sending. For cases where the rule may be wrong.

Wherever there is Zoom chat

Team Chat, meeting chat, webinar chat, webinar Q&A. Zoom Events has its own tool with the same rules.

Account and groups

Policies are set at account level or for a user group. Accounting and support can have different lists.

Up to 50 policies

Up to 50 policies can be created at account level. Each with its own words or expressions and its own action.

Checked on the client

No text, metadata or events are sent to the administrator, to Zoom or to third parties. The tool protects against mistakes, it does not watch.

Requirements and availability

Pro, Business, Education or Enterprise plans, owner or administrator rights. The Zoom app from version 5.6.0 for chat and from 5.11.0 for webinar Q&A. No separate licence.

Scenes

Where it works

Wherever chat might receive something that belongs in a protected system

01

Banking and finance

Customers' card and account numbers must not land in chat. A regular expression catches any format.

02

Personal data

A passport, a tax ID, a customer's date of birth: the rule reminds that the CRM is for this, not the shared channel.

03

Customer support

An agent pastes a reply from a template and accidentally grabs another customer's data. The warning stops it.

04

Projects under NDA

Project code names and customer names in the word list. They do not show up in open channels.

05

Webinars for an external audience

Webinar chat and Q&A under the same rules. The presenter will not send the audience an internal link or a price.

06

Deployment with RightConf

The rule list is drawn up together with security and legal, patterns are tested on real examples, modes are chosen per group. Then support in Russian.

How it worked for others

An example deployment

Hedge fund

Financial institution

They urgently needed to close the data-leak gap in meetings and set up archiving.

  • Zoom APIs were used to connect third-party solutions and meet regulatory requirements
  • Information barriers and Chat Etiquette were configured straight from the Zoom admin portal, with no development
  • Archiving was connected via the Archiving API

What you need to get started

Requirements
  • A paid Zoom license with access to policies
  • Administrator rights in the web portal
  • A list of rules agreed with legal

Try Zoom today

We'll give you a remote demo Monday to Friday, 10:00–16:00 Moscow time, answer all your questions and provide trial access so you can explore the system yourself.

Please note: we work with legal entities only.

Leave a request

Our specialists will find the right solution for your needs.

We reply within one business day By sending this form you agree that we may contact you at the phone number and email you provided. See our privacy policy for how we handle your data.
Made on
Tilda