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
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
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
Increase Character Limit for Custom Reactions
Increase the character limit for custom reactions from the current 45 characters to approximately 100 characters.
💡 Feature Request
Increase Character Limit for Custom Reactions
Increase the character limit for custom reactions from the current 45 characters to approximately 100 characters.
💡 Feature Request
Send Chat Messages Without Leaving an Active Call
Enable users to send messages to users or groups while staying in an ongoing audio/video call.
💡 Feature Request
Send Chat Messages Without Leaving an Active Call
Enable users to send messages to users or groups while staying in an ongoing audio/video call.
💡 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
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
Multi-Select Poll Options
Customers need the ability to create polls that allow respondents to select multiple options instead of just one. This would support use cases such as asking users to choose multiple preferences e.g., “Select up to 3 options from the list”
💡 Feature Request
Multi-Select Poll Options
Customers need the ability to create polls that allow respondents to select multiple options instead of just one. This would support use cases such as asking users to choose multiple preferences e.g., “Select up to 3 options from the list”
💡 Feature Request
Single API to Bulk Delete All Messages
Introduce a dedicated API that allows deleting all messages across all conversations within an app in a single request. This would simplify message cleanup workflows, eliminate the need to iterate through conversations using the Reset Conversations API, and provide a more efficient and intuitive way to permanently remove messages at scale.
💡 Feature Request
Single API to Bulk Delete All Messages
Introduce a dedicated API that allows deleting all messages across all conversations within an app in a single request. This would simplify message cleanup workflows, eliminate the need to iterate through conversations using the Reset Conversations API, and provide a more efficient and intuitive way to permanently remove messages at scale.
💡 Feature Request
Admin/Moderator Control to Remove Participants from Ongoing Calls
Support for admin or moderator control to remove participants from an ongoing call.
💡 Feature Request
Admin/Moderator Control to Remove Participants from Ongoing Calls
Support for admin or moderator control to remove participants from an ongoing call.
💡 Feature Request
Admin/Moderator Ability to Disable Participant Camera or Microphone During Calls
Support for controls that allow admins or moderators to disable a participant’s microphone or camera during an ongoing call.
💡 Feature Request
Admin/Moderator Ability to Disable Participant Camera or Microphone During Calls
Support for controls that allow admins or moderators to disable a participant’s microphone or camera during an ongoing call.
💡 Feature Request
Admin or Moderator Controls for Locking and Moderating Call Rooms
Support for admin or moderator control that allows them Lock or Moderating ongoing call rooms.
💡 Feature Request
Admin or Moderator Controls for Locking and Moderating Call Rooms
Support for admin or moderator control that allows them Lock or Moderating ongoing call rooms.
💡 Feature Request
Admin control to Mute or Unmute participants during call
Support for admin or moderator controls that allow them to mute or unmute participants during ongoing calls.
💡 Feature Request
Admin control to Mute or Unmute participants during call
Support for admin or moderator controls that allow them to mute or unmute participants during ongoing calls.
💡 Feature Request
Add Filter Options and Display Message IDs in Chat Logs
Admins should be able to filter chats in the dashboard chat logs using filter options. Additionally, each message should display its message ID
💡 Feature Request
Add Filter Options and Display Message IDs in Chat Logs
Admins should be able to filter chats in the dashboard chat logs using filter options. Additionally, each message should display its message ID
💡 Feature Request
Support for Logging Message Reactions in Chat Logs
Admins should be able to view message reactions in the chat logs on the CometChat dashboard.
💡 Feature Request
Support for Logging Message Reactions in Chat Logs
Admins should be able to view message reactions in the chat logs on the CometChat dashboard.
💡 Feature Request
Windows App Support in Flutter Plugin
Currently, the CometChat Flutter plugin does not provide official support or documentation for Windows applications. This limits developers who want to build cross-platform Flutter apps with Windows desktop support using CometChat. We request official Windows support, along with clear documentation and examples, to enable seamless integration and consistent behavior across all Flutter-supported platforms.
💡 Feature Request
Windows App Support in Flutter Plugin
Currently, the CometChat Flutter plugin does not provide official support or documentation for Windows applications. This limits developers who want to build cross-platform Flutter apps with Windows desktop support using CometChat. We request official Windows support, along with clear documentation and examples, to enable seamless integration and consistent behavior across all Flutter-supported platforms.
💡 Feature Request
Enable Group Ownership Transfer and Owner Removal via CometChat Dashboard
Currently, the CometChat Dashboard does not provide an option to transfer group ownership or remove the existing owner from a group. This limitation creates challenges for scenarios such as organizational changes, role transitions, or when the original group owner is no longer part of the team. We request the ability to: Transfer group ownership to another member (Admin or Moderator) directly from the CometChat Dashboard. Remove or demote the current owner after ownership has been successfully transferred. Ensure appropriate permission checks and audit handling during ownership transfer. This feature would significantly improve group management flexibility and reduce dependency on workarounds or manual intervention.
💡 Feature Request
Enable Group Ownership Transfer and Owner Removal via CometChat Dashboard
Currently, the CometChat Dashboard does not provide an option to transfer group ownership or remove the existing owner from a group. This limitation creates challenges for scenarios such as organizational changes, role transitions, or when the original group owner is no longer part of the team. We request the ability to: Transfer group ownership to another member (Admin or Moderator) directly from the CometChat Dashboard. Remove or demote the current owner after ownership has been successfully transferred. Ensure appropriate permission checks and audit handling during ownership transfer. This feature would significantly improve group management flexibility and reduce dependency on workarounds or manual intervention.
💡 Feature Request
RTL Support in Flutter UIKit
Add native Right-to-Left (RTL) language support to the Flutter UIKit by CometChat. The UI should automatically adapt based on locale, including correct alignment and mirroring of chat bubbles, message lists, composer, navigation elements, and icons for RTL languages like Arabic and Hebrew. This will improve usability and reduce the need for custom UI overrides.
💡 Feature Request
RTL Support in Flutter UIKit
Add native Right-to-Left (RTL) language support to the Flutter UIKit by CometChat. The UI should automatically adapt based on locale, including correct alignment and mirroring of chat bubbles, message lists, composer, navigation elements, and icons for RTL languages like Arabic and Hebrew. This will improve usability and reduce the need for custom UI overrides.
💡 Feature Request
Idea
Unread Message Count Should Exclude Deleted Messages in Conversations
When a message is deleted using the Delete Message API, it should no longer be included in the Conversations API. Accordingly, the value of the unreadCount key should decrease to show only the remaining unread messages.
💡 Feature Request
Idea
Unread Message Count Should Exclude Deleted Messages in Conversations
When a message is deleted using the Delete Message API, it should no longer be included in the Conversations API. Accordingly, the value of the unreadCount key should decrease to show only the remaining unread messages.
💡 Feature Request
Idea
Automatic Transcription for Audio & Video Calls
Enable automatic transcription for audio and video calls, providing both live and post-call transcripts. Transcripts should be searchable, downloadable, and directly linked to the corresponding recorded session for easy reference and review.
💡 Feature Request
Idea
Automatic Transcription for Audio & Video Calls
Enable automatic transcription for audio and video calls, providing both live and post-call transcripts. Transcripts should be searchable, downloadable, and directly linked to the corresponding recorded session for easy reference and review.
💡 Feature Request