Chat messaging is one of the most useful features in video conferencing applications. When developers build meeting bots, collaboration tools, or AI assistants using the Zoom Meeting SDK, they often need the ability to send and receive chat messages programmatically.
The Zoom Meeting SDK provides built-in chat capabilities that allow applications to interact with meeting participants through public or private messages.
In this guide, you will learn how the Zoom Meeting SDK chat system works, how to implement message sending, and how to receive chat events inside your application.
Understanding In-Meeting Chat in Zoom
Zoom meetings support real-time chat communication between participants. Users can send messages to everyone in the meeting or privately to a specific participant depending on the host’s settings.
For developers, the Zoom Meeting SDK exposes chat functionality through a chat controller that allows applications to interact with the meeting chat system. Instead of using the REST API, in-meeting chat messaging must be handled directly through the SDK.
Typical use cases include:
- Meeting bots that respond to commands
- Automated assistants that send reminders
- Collaboration tools that integrate meeting chat data
- AI systems that analyze meeting conversations
With the SDK, your application becomes a participant in the meeting and can exchange chat messages like a normal user.
Key Components of Zoom Meeting SDK Chat
To implement messaging functionality, you need to understand a few core SDK components.
Chat Controller
The chat controller manages sending and receiving messages in a meeting session. Developers typically retrieve it after joining the meeting through the meeting service.
Example concept:
IMeetingChatController* chatController =
meetingService->GetMeetingChatController();
This controller allows your application to:
- Send chat messages
- Receive message notifications
- monitor chat status
Chat Message Object
The SDK represents messages using chat message objects that contain information such as:
- message content
- sender user
- receiver user
- timestamp
- message ID
These objects help applications identify who sent the message and whether it was public or private.
Sending Chat Messages with the Zoom Meeting SDK
Sending messages through the SDK involves constructing a chat message and delivering it through the chat controller.
Most SDK implementations require a message builder or message object that contains the message content and recipient.
For example, in Android implementations developers create a message using a ChatMessageBuilder, set the message content, and define the receiver before sending it.
Conceptual workflow:
- Create a chat message object
- Set message text
- Define recipient (everyone or specific user)
- Send message through the chat controller
Example concept:
ChatMessageBuilder message = new ChatMessageBuilder();
message.setContent("Hello everyone!");
message.setReceiver(0); // send to all
The receiver ID determines who receives the message. If the receiver value represents everyone, the message becomes a public meeting message.
Sending Private Messages
Zoom meetings also support direct messaging between participants.
To send a private chat message:
- Retrieve the user ID of the target participant
- Assign that ID as the receiver
- Send the message through the SDK
Private messages appear only in the conversation between those two participants. Meeting hosts cannot view private chats unless they are part of that conversation.
This functionality allows developers to create features like:
- private bot responses
- moderation tools
- AI assistants that respond to individual participants
Receiving Chat Messages with the SDK
Sending messages is only one part of the system. Applications must also listen for incoming messages from meeting participants.
Zoom provides event callbacks for chat notifications.
To receive messages:
- Register a chat event listener
- Implement the message notification callback
- Process incoming message content
Developers typically implement an interface that listens for events such as onChatMsgNotification.
When someone sends a message during the meeting, the SDK triggers this callback so your application can read the message data.
Example workflow:
- Participant sends chat message
- SDK triggers message event
- Bot receives message
- Application processes message content
This mechanism enables automated bots and assistants to respond dynamically to chat messages.
Thread and Event Handling Best Practices
One common challenge when implementing Zoom chat messaging involves thread management.
The Meeting SDK requires chat operations to run on the main thread or UI thread. Attempting to send messages from background threads can cause failures or unexpected behavior.
To avoid these issues:
- Handle message sending on the main thread
- Forward background events to the main event loop
- Use proper dispatch or message queues
This ensures reliable communication between the SDK and your application.
Example Workflow for a Chat Bot
A typical Zoom meeting bot that interacts with chat messages might follow this process:
Step 1: Join Meeting
The application joins the Zoom meeting using the Meeting SDK.
Step 2: Initialize Chat Controller
After joining, the app retrieves the chat controller to manage messaging.
Step 3: Register Chat Listener
The application registers an event listener to receive incoming messages.
Step 4: Process Incoming Messages
When a participant sends a message, the event callback captures it.
Step 5: Send Response
The bot generates a response and sends it through the chat controller.
This workflow allows developers to build interactive meeting bots and automation systems.
Common Use Cases for Zoom SDK Chat Messaging
Developers use Zoom chat messaging in a variety of advanced applications.
AI Meeting Assistants
Bots that answer questions during meetings.
Command-Based Bots
Participants send commands such as:
/help
/summary
/record
The bot processes these commands and responds automatically.
Customer Support Meetings
Support agents can automate instructions or share links via chat.
Meeting Moderation
Bots can monitor chat messages and flag inappropriate content.
Troubleshooting Chat Messaging Issues
Developers sometimes encounter problems when implementing SDK chat functionality.
Messages Not Appearing
If messages are not visible in the meeting chat, verify:
- correct receiver ID
- proper message construction
- host chat permissions
Chat Event Not Triggered
If message callbacks do not trigger:
- confirm event listener registration
- ensure correct SDK interface implementation
Background Thread Errors
If chat sending fails, move message operations to the main thread to comply with SDK requirements.
Best Practices for Zoom SDK Chat Integration
To build a reliable messaging system:
Validate Chat Permissions
Meeting hosts can restrict chat functionality. Always check meeting settings.
Handle Both Public and Private Messages
Bots should support both message types for flexible interactions.
Log Incoming Messages
Logging messages helps debugging and improves bot behavior analysis.
Design Clear Bot Responses
Bots should provide concise and useful responses to participants.
Conclusion
The Zoom Meeting SDK allows developers to build powerful meeting integrations by enabling programmatic access to chat messaging.
By using the SDK’s chat controller, registering message event listeners, and sending messages through the correct thread, applications can interact seamlessly with meeting participants.
Whether you are building a Zoom meeting bot, AI assistant, or automation tool, the ability to send and receive chat messages unlocks a wide range of possibilities.
With proper implementation and event handling, developers can transform simple meeting chats into intelligent, interactive communication systems.