Want to request a feature?

Create a new request and help us improve CometChat!

Add Sensitive Data Masking (Phone & Email) Support in New Moderation System

We are currently using the new Moderation system and observed that the Contact Details Filter and Email Filter only block messages when phone numbers or email addresses are detected. In the earlier Legacy Data Masking feature, there was an option to mask sensitive information (such as phone numbers and email addresses) while still allowing the message to be delivered. However, this masking capability does not appear to be available in the new Moderation system. Current Behavior: Messages containing phone numbers or email addresses are completely blocked. Expected Behavior / Requirement: The message should be delivered successfully. Sensitive information such as phone numbers and email addresses should be automatically masked instead of blocking the message. Example: Phone: 9876543210 → 98XXXXXX10 Email: john.doe@gmail.com → jo***@gmail.com

💡 Feature Request

Include detailed violation “Reasons” in moderation_engine_blocked Webhook Payload

Description: Moderation is functioning correctly, and the CometChat Dashboard displays comprehensive Violation Details → Reasons whenever a message is blocked. However, the moderation_engine_blocked webhook payload currently only includes rule metadata such as: rule_id rule_name revision action blockedAt The payload does not include the detailed “Reasons” explanation that is visible in the dashboard. Problem Statement: Since the webhook does not expose the violation reason, client applications can only show a generic message like “Message blocked” to end users. This limits transparency and negatively impacts user experience. Requested Enhancement: Enhance the moderation_engine_blocked webhook JSON payload to include a detailed violation_reasons (or similar) field, matching the Violation Details → Reasons shown in the dashboard.

💡 Feature Request

CometChat – Blocked State Messages Should Not Update Delivery Status After Unblock

We have identified an issue related to message delivery status behavior in CometChat when users are blocked and later unblocked. Scenario: User A logs in on Device 1 User B logs in on Device 2 User A blocks User B User B sends messages to User A (messages correctly show single tick) User A unblocks User B User B sends a new message after being unblocked Current Behavior: Messages that were sent by User B while blocked initially show a single tick (correct behavior). However, once User A unblocks User B, those old messages are automatically updated to double blue ticks, even though they were never delivered to User A at the time they were sent. Expected Behavior: Messages sent while the sender was blocked should permanently remain in a single tick (undelivered) state, even after the unblock action. Only messages sent after the unblock event should follow the normal delivery and read receipt lifecycle.

💡 Feature Request

Archive Conversation Feature in Flutter CometChat UIKit

Request to add an Archive Conversation feature in the CometChat UIKit. Currently, there is no built-in support for archiving chats. Users should be able to archive conversations (primarily groups, but ideally both group and one-to-one chats) directly from the conversation list. Archived conversations should be moved out of the main list and accessible in a dedicated Archive section, with an option to unarchive them.

💡 Feature Request

Ability to Customize Group Action System Messages

Currently, when a user is removed from a group, the system automatically displays the message “System kicked user.” For a business-to-business application, the term “kicked” may come across as informal and unprofessional. We would like the ability to modify or customize group action system messages specifically the wording used when a user is removed from a group.

💡 Feature Request

Support for Picture-in-Picture mode

We would like to request support for Picture-in-Picture (PiP) mode during ongoing audio and video calls within the application. The PiP mode should allow users to: Minimize the active call screen into a floating window. Ability to chat during ongoing audio/video calls(video and chat working simultaneously) Drag and reposition the PiP window freely across the screen for better usability and visibility.

💡 Feature Request

Enable Push Notifications for Bot Extension Messages (Reminder Bot)

Currently, the CometChat Bot Extension does not support push notifications for bot-generated messages, including Reminder Bot messages. As a result, users do not receive push alerts for reminder messages when the app is in the background or terminated. We request support for push notifications for bot extension messages to ensure users receive timely reminder alerts, similar to regular user messages. This enhancement would improve user engagement and ensure important bot-triggered reminders are not missed.

💡 Feature Request

Real-Time Events for Tag Updates on Conversations + Local Caching Support

Currently, when tags are added to or removed from a conversation, the Conversation List does not update in real time. There are no dedicated events or listeners for tag added or tag removed actions. Because of this limitation, developers must manually refresh or re-fetch the conversation list to reflect updated tags. This leads to unnecessary screen reloads and negatively impacts user experience, especially during navigation. Additionally, there is no local caching mechanism for conversation tags. Due to the absence of caching, tag updates require a fresh API call, which affects performance and prevents seamless UI updates. We request the following enhancements: Real-time events/listeners for: Tag Added to Conversation Tag Removed from Conversation Local caching support for conversation tags, so that: Tag updates reflect instantly in the conversation list UI remains in sync without requiring manual refresh Performance is improved by reducing redundant API calls These improvements would significantly enhance real-time behavior, performance optimization, and overall developer experience while maintaining UI consistency.

💡 Feature Request

UX Suggestion – Voice Recorder Outside Click (Idle State)

Current Behaviour Once the voice recorder is opened, it cannot be closed by clicking outside of it. This behaviour applies to all states, including: Active recording Audio preview available Idle state (no recording in progress and no recorded audio) Proposed Enhancement Allow the voice recorder to close on outside click only when: No recording is currently active, and No recorded audio or preview is present (e.g., after deleting a recording). Expected Behaviour Idle state: Outside click should dismiss/close the recorder. Recording or preview state: Keep the current protected behavior during recording and preview states.

💡 Feature Request

Add “Recent Emojis” to React UI Kit Emoji Picker

We would like to request the addition of a “Recently Used” section to the Emoji Keyboard in the React UI Kit. Most modern messaging platforms and emoji libraries include a Recent category that automatically displays emojis selected by the user. This significantly improves usability by allowing quick access to frequently used emojis without navigating through multiple categories each time.

💡 Feature Request

Increase multipleReceivers Limit for Large Scale Messaging

We currently use CometChat’s multipleReceivers parameter to send a single message to multiple users. As our platform has grown, several clients now need to send messages to hundreds of users in one operation. Iterating in small batches of 25 users is no longer scalable or efficient, even with pagination and queuing. We would like to request a higher limit for the number of UIDs allowed in multipleReceivers.

💡 Feature Request

Admin-Level Option to Clear Channel Conversation for All Participants

Feature Request Description Currently, CometChat allows clearing chat history only at an individual user level, where messages are removed from the current user’s view. Additionally, the existing Reset Group Conversation API is limited to groups with up to 10 participants. We request an admin-level capability to clear or delete a channel/group conversation for all participants, regardless of group size. Use cases: Channel moderation and policy enforcement Removing sensitive or mistakenly shared information Resetting conversations for temporary or event-based channels Better administrative control over large groups and channels

💡 Feature Request

Convert 1:1 Chat to Group Chat (Add Participants to Existing Conversation)

Description Currently, CometChat treats 1:1 (direct) chats and group chats as separate entities. To include additional participants in an ongoing 1:1 conversation, a new group must be created manually, which results in losing the existing conversation context and history. We would like to request a native feature that allows converting an existing 1:1 chat into a group chat by adding more participants — similar to how platforms like LinkedIn allow users to expand an ongoing conversation. Expected Behavior Ability to add one or more users to an existing 1:1 chat. The conversation should seamlessly transition into a group chat. Existing message history should remain intact and visible to all participants (with proper permissions). System message indicating when users are added (e.g., “Rohit added John to the conversation”). Use Cases Customer support workflows where a manager or specialist needs to be added mid-conversation. Collaboration tools where discussions organically grow from 1:1 to multi-user. Sales or onboarding flows where stakeholders join an ongoing thread. Why This Matters This feature is critical for collaboration and support scenarios. Without it: Developers must create a new group and manually migrate context. Users lose conversational continuity. The experience feels fragmented compared to modern messaging platforms. Requested Scope Should be available via: Core SDKs (REST + Mobile/Web SDKs) UI Kits (prebuilt UI support) Optional Enhancements Ability to choose whether past history is visible to newly added users. API method like: convertDirectChatToGroup(conversationId, userIds[])

💡 Feature Request

Open Chat at First Unread Message Instead of Latest Message

Description We would like to request support for a feature that allows a conversation to automatically open and scroll to a user’s unread messages instead of defaulting to the latest message in a group or one-to-one chat. Currently, when a user opens a conversation that contains unread messages, the UI Kit scrolls directly to the most recent message. As a result, users must manually scroll upward to locate their unread messages, which can be time-consuming and unintuitive—especially in active group conversations with a large number of new messages. Proposed Enhancement When a logged-in user opens a conversation with unread messages: Detect the first unread message for the user using read receipts or message delivery state. Automatically scroll the chat view to that unread message. Clearly indicate unread messages (for example, using a divider such as “Unread Messages” or visual highlighting). If no unread messages exist, the chat may continue to open at the latest message as it does today. Additionally, provide developer-level control through: An API or configuration option to enable or disable this behavior. A method to manually set or override the unread message reference. An optional callback or event confirming that the scroll-to-unread action was completed successfully. Why This Feature Is Valuable Allows users to immediately focus on messages they have not yet seen. Eliminates the need for manual scrolling in busy group conversations. Matches the behavior of widely adopted messaging platforms, improving familiarity. Enhances usability and productivity for both consumer and enterprise use cases. Expected Impact This feature would significantly improve the chat experience by ensuring users are automatically taken to the most relevant point in the conversation—their unread messages. It streamlines navigation, reduces friction in active chats, and provides a more intuitive and user-friendly messaging experience.

💡 Feature Request