Support for Picture-in-Picture (PiP) Mode & “Tap to Return to Call” Experience
Requesting support for Picture-in-Picture (PiP) mode and a “Tap to return to call” experience similar to Google Meet. This would allow the call to remain active when the app is minimized or runs in the background, with a floating PiP window for quick access and the ability to instantly return to the full call screen.
💡 Feature Request
Support for Picture-in-Picture (PiP) Mode & “Tap to Return to Call” Experience
Requesting support for Picture-in-Picture (PiP) mode and a “Tap to return to call” experience similar to Google Meet. This would allow the call to remain active when the app is minimized or runs in the background, with a floating PiP window for quick access and the ability to instantly return to the full call screen.
💡 Feature Request
Custom actor attribution for group actions without permission dependency
Provide an option in group management APIs to set the actor name for action messages independently of permission checks. Currently, using onBehalfOf enforces user permissions, while omitting it defaults the actor to “System.” A flag or parameter to control only the display name (without tying it to permissions) would help support server-side operations while maintaining accurate user attribution in UI messages.
💡 Feature Request
Custom actor attribution for group actions without permission dependency
Provide an option in group management APIs to set the actor name for action messages independently of permission checks. Currently, using onBehalfOf enforces user permissions, while omitting it defaults the actor to “System.” A flag or parameter to control only the display name (without tying it to permissions) would help support server-side operations while maintaining accurate user attribution in UI messages.
💡 Feature Request
Enhancement Request: Server-Side Call Lifecycle Control, Recording Management, and Advanced Webhook Insights in CometChat
We request enhancements to the CometChat calling infrastructure to support robust backend-driven control and visibility over call sessions. While the current React Native SDK enables basic calling functionality, there are several limitations from a backend perspective that restrict advanced use cases such as monitoring, compliance, and centralized session management. We propose the following enhancements: A. Server-Side Call Lifecycle APIs APIs to fetch detailed call session data (status, participants, timestamps, termination reasons) Ability to monitor and manage active calls in real-time B. Force Call Termination API Backend API to terminate active calls programmatically Support for use cases like moderation, time limits, and system-triggered disconnects C. Server-Side Recording Management APIs to start/stop recordings from backend Support for configurable formats (audio/video), resolution, and layouts Synchronous or callback-based recording access D. Enhanced Webhook Events Detailed call termination reasons Network-related events and failure diagnostics User-level disconnect causes E. Custom Metadata Support Ability to attach custom metadata to call sessions Metadata accessible via webhooks and APIs for backend-driven workflows Expected Impact: These enhancements would enable: Better observability and debugging of call sessions Stronger compliance and governance controls Advanced backend-driven workflows and automation Improved overall flexibility for enterprise-grade applications We believe these capabilities are essential for building scalable, compliant, and fully managed calling solutions using CometChat.
💡 Feature Request
Enhancement Request: Server-Side Call Lifecycle Control, Recording Management, and Advanced Webhook Insights in CometChat
We request enhancements to the CometChat calling infrastructure to support robust backend-driven control and visibility over call sessions. While the current React Native SDK enables basic calling functionality, there are several limitations from a backend perspective that restrict advanced use cases such as monitoring, compliance, and centralized session management. We propose the following enhancements: A. Server-Side Call Lifecycle APIs APIs to fetch detailed call session data (status, participants, timestamps, termination reasons) Ability to monitor and manage active calls in real-time B. Force Call Termination API Backend API to terminate active calls programmatically Support for use cases like moderation, time limits, and system-triggered disconnects C. Server-Side Recording Management APIs to start/stop recordings from backend Support for configurable formats (audio/video), resolution, and layouts Synchronous or callback-based recording access D. Enhanced Webhook Events Detailed call termination reasons Network-related events and failure diagnostics User-level disconnect causes E. Custom Metadata Support Ability to attach custom metadata to call sessions Metadata accessible via webhooks and APIs for backend-driven workflows Expected Impact: These enhancements would enable: Better observability and debugging of call sessions Stronger compliance and governance controls Advanced backend-driven workflows and automation Improved overall flexibility for enterprise-grade applications We believe these capabilities are essential for building scalable, compliant, and fully managed calling solutions using CometChat.
💡 Feature Request
Support for Exact Phrase Match in Message Search
Currently, message search uses fuzzy matching and returns results for partial or related keywords when searching for a phrase (e.g., searching “add member” returns results for “add” and “member” separately). We request the ability to perform exact phrase searches so that only messages containing the complete phrase are returned. This will help improve search precision and user experience.
💡 Feature Request
Support for Exact Phrase Match in Message Search
Currently, message search uses fuzzy matching and returns results for partial or related keywords when searching for a phrase (e.g., searching “add member” returns results for “add” and “member” separately). We request the ability to perform exact phrase searches so that only messages containing the complete phrase are returned. This will help improve search precision and user experience.
💡 Feature Request
intergration with MS-teams calling
is it posible to intergrate with MS-Teams calling? The use-case is that when a customer calls (through a regular phone) the phonecall is picked up by CometChat and an AI voice gives a response to the customer.
💡 Feature Request
intergration with MS-teams calling
is it posible to intergrate with MS-Teams calling? The use-case is that when a customer calls (through a regular phone) the phonecall is picked up by CometChat and an AI voice gives a response to the customer.
💡 Feature Request
Message Pinning via REST APIs
We would like to request support for message pinning and unpinning through REST APIs in CometChat. Currently, message pinning is only available via the Pin Message Extension and is not accessible through REST API endpoints. This limits use cases that rely on backend-driven workflows and server-side control. We propose adding endpoints to pin and unpin messages (e.g., POST /v3/messages/{messageId}/pin and DELETE /v3/messages/{messageId}/pin) so developers can manage pinned messages programmatically.
💡 Feature Request
Message Pinning via REST APIs
We would like to request support for message pinning and unpinning through REST APIs in CometChat. Currently, message pinning is only available via the Pin Message Extension and is not accessible through REST API endpoints. This limits use cases that rely on backend-driven workflows and server-side control. We propose adding endpoints to pin and unpin messages (e.g., POST /v3/messages/{messageId}/pin and DELETE /v3/messages/{messageId}/pin) so developers can manage pinned messages programmatically.
💡 Feature Request
Unread Thread Indicator on Message Bubbles
Add support for displaying unread indicators on message bubbles that contain threads (e.g., “12 replies”). The indicator can either show the unread count or a simple unread marker.
💡 Feature Request
Unread Thread Indicator on Message Bubbles
Add support for displaying unread indicators on message bubbles that contain threads (e.g., “12 replies”). The indicator can either show the unread count or a simple unread marker.
💡 Feature Request
Idea
User List Export from Dashboard
Request to add an export option in the CometChat dashboard to download active and inactive user lists directly. This would improve ease of access and reduce reliance on API calls for basic data retrieval.
💡 Feature Request
Idea
User List Export from Dashboard
Request to add an export option in the CometChat dashboard to download active and inactive user lists directly. This would improve ease of access and reduce reliance on API calls for basic data retrieval.
💡 Feature Request
Idea
Add Local Caching Mechanism to Improve Chat Load Performance in CometChat React Native UI Kit
Opening a conversation in the CometChat React Native UI Kit currently triggers a full reload of messages from the server each time, resulting in slower load times and a less responsive user experience. In a real-time chat application, users expect conversations to open instantly with previously viewed messages readily available. The lack of a local caching mechanism leads to repeated network calls and unnecessary data fetching, even for recently accessed chats. Introducing a local caching mechanism to store recent conversations and messages on the device would allow chats to load instantly while syncing with the server in the background. This would significantly improve performance, reduce latency, and provide a smoother and more seamless user experience, especially in low or unstable network conditions.
💡 Feature Request
Idea
Add Local Caching Mechanism to Improve Chat Load Performance in CometChat React Native UI Kit
Opening a conversation in the CometChat React Native UI Kit currently triggers a full reload of messages from the server each time, resulting in slower load times and a less responsive user experience. In a real-time chat application, users expect conversations to open instantly with previously viewed messages readily available. The lack of a local caching mechanism leads to repeated network calls and unnecessary data fetching, even for recently accessed chats. Introducing a local caching mechanism to store recent conversations and messages on the device would allow chats to load instantly while syncing with the server in the background. This would significantly improve performance, reduce latency, and provide a smoother and more seamless user experience, especially in low or unstable network conditions.
💡 Feature Request
Idea
Retry or Re-upload Option for Failed Media Uploads Due to Network Issues
Currently, when a media or image upload fails due to poor or unstable network connectivity, there is no option for the user to retry or re-upload the file directly. We propose adding a retry or re-upload option for failed media uploads, allowing users to easily attempt the upload again without restarting the entire process. This enhancement would improve usability and provide a smoother experience in cases where uploads fail due to temporary network issues.
💡 Feature Request
Idea
Retry or Re-upload Option for Failed Media Uploads Due to Network Issues
Currently, when a media or image upload fails due to poor or unstable network connectivity, there is no option for the user to retry or re-upload the file directly. We propose adding a retry or re-upload option for failed media uploads, allowing users to easily attempt the upload again without restarting the entire process. This enhancement would improve usability and provide a smoother experience in cases where uploads fail due to temporary network issues.
💡 Feature Request
Idea
Support for video resolution configuration using UI or programmatically
Support for video resolution configuration using UI or programmatically
💡 Feature Request
Idea
Support for video resolution configuration using UI or programmatically
Support for video resolution configuration using UI or programmatically
💡 Feature Request
Idea
Support Multiple Group GUIDs in Get Messages API
Currently, the GET /groups/{guid}/messages API supports fetching messages for only a single group GUID per request. Customers who need messages from multiple groups must make separate API calls for each GUID. A feature enhancement is requested to allow multiple group GUIDs to be passed in a single request (e.g., 10–15 GUIDs) and return the messages for all those groups in one response.
💡 Feature Request
Idea
Support Multiple Group GUIDs in Get Messages API
Currently, the GET /groups/{guid}/messages API supports fetching messages for only a single group GUID per request. Customers who need messages from multiple groups must make separate API calls for each GUID. A feature enhancement is requested to allow multiple group GUIDs to be passed in a single request (e.g., 10–15 GUIDs) and return the messages for all those groups in one response.
💡 Feature Request
Idea
Support for Message Forwarding and Multi-Message Selection in React Native UIKit
Feature request for message forwarding and multi-message selection in the React Native UIKit. This feature would allow users to select single or multiple messages within a conversation and perform bulk actions such as Forward, Delete, and Copy. Additionally, users should be able to forward selected messages to one or multiple users or groups directly from the chat interface. Providing this functionality in the React Native UIKit would help developers implement a more advanced and user-friendly chat experience, similar to popular messaging applications like WhatsApp, and would significantly improve message management within conversations.
💡 Feature Request
Idea
Support for Message Forwarding and Multi-Message Selection in React Native UIKit
Feature request for message forwarding and multi-message selection in the React Native UIKit. This feature would allow users to select single or multiple messages within a conversation and perform bulk actions such as Forward, Delete, and Copy. Additionally, users should be able to forward selected messages to one or multiple users or groups directly from the chat interface. Providing this functionality in the React Native UIKit would help developers implement a more advanced and user-friendly chat experience, similar to popular messaging applications like WhatsApp, and would significantly improve message management within conversations.
💡 Feature Request
Idea
Expose CometChat Dashboard Metrics via API for CRM Integration
We have a use case where customers want to display CometChat dashboard metrics directly inside their internal CRM or applications. Currently, while messaging events can be captured using webhooks, there is no API available to programmatically fetch dashboard-level metrics (such as message counts, usage analytics, user activity, etc.). Providing an API or endpoint to access these metrics would allow teams to automatically sync CometChat analytics with their internal systems and display them in custom dashboards for stakeholders such as brokers, admins, or support teams. This enhancement would enable better reporting, automation, and deeper integration of CometChat analytics into external platforms like CRMs and internal business tools.
💡 Feature Request
Idea
Expose CometChat Dashboard Metrics via API for CRM Integration
We have a use case where customers want to display CometChat dashboard metrics directly inside their internal CRM or applications. Currently, while messaging events can be captured using webhooks, there is no API available to programmatically fetch dashboard-level metrics (such as message counts, usage analytics, user activity, etc.). Providing an API or endpoint to access these metrics would allow teams to automatically sync CometChat analytics with their internal systems and display them in custom dashboards for stakeholders such as brokers, admins, or support teams. This enhancement would enable better reporting, automation, and deeper integration of CometChat analytics into external platforms like CRMs and internal business tools.
💡 Feature Request
Idea
Add Full RTL Support in Web Widget and UI Kits for Arabic Localization
Currently, Arabic localization is not fully supported in our Web Widget and UI Kits because Right-to-Left (RTL) layout support is not yet implemented. Arabic requires proper RTL handling across the UI, including message layouts, navigation elements, alignment, and component structure. Adding full RTL support would enable proper Arabic language localization and improve accessibility for applications targeting Arabic-speaking users. This feature would allow developers to implement Arabic translations while ensuring the UI renders correctly in an RTL layout. Implementing RTL compatibility across the UI Kits will help expand usability in regions where Arabic is widely used and make localization more flexible for developers.
💡 Feature Request
Idea
Add Full RTL Support in Web Widget and UI Kits for Arabic Localization
Currently, Arabic localization is not fully supported in our Web Widget and UI Kits because Right-to-Left (RTL) layout support is not yet implemented. Arabic requires proper RTL handling across the UI, including message layouts, navigation elements, alignment, and component structure. Adding full RTL support would enable proper Arabic language localization and improve accessibility for applications targeting Arabic-speaking users. This feature would allow developers to implement Arabic translations while ensuring the UI renders correctly in an RTL layout. Implementing RTL compatibility across the UI Kits will help expand usability in regions where Arabic is widely used and make localization more flexible for developers.
💡 Feature Request
Idea
Add Full RTL Support in UI Kits for Arabic Localization
Currently, Arabic localization is not fully supported in our UI Kits because Right-to-Left (RTL) layout support is not yet implemented. Arabic requires proper RTL handling across the UI, including message layouts, navigation elements, alignment, and component structure. Adding full RTL support would enable proper Arabic language localization and improve accessibility for applications targeting Arabic-speaking users. This feature would allow developers to implement Arabic translations while ensuring the UI renders correctly in an RTL layout. Implementing RTL compatibility across the UI Kits will help expand usability in regions where Arabic is widely used and make localization more flexible for developers.
💡 Feature Request
Idea
Add Full RTL Support in UI Kits for Arabic Localization
Currently, Arabic localization is not fully supported in our UI Kits because Right-to-Left (RTL) layout support is not yet implemented. Arabic requires proper RTL handling across the UI, including message layouts, navigation elements, alignment, and component structure. Adding full RTL support would enable proper Arabic language localization and improve accessibility for applications targeting Arabic-speaking users. This feature would allow developers to implement Arabic translations while ensuring the UI renders correctly in an RTL layout. Implementing RTL compatibility across the UI Kits will help expand usability in regions where Arabic is widely used and make localization more flexible for developers.
💡 Feature Request
Idea
Native Unread Thread Reply Indicator in Message List (iOS UI Kit)
Currently, in CometChat iOS UI Kit v5, threaded messages only display the total number of replies for a parent message in the message bubble. However, there is no native indicator to show when a thread has unread or newly received replies. This limitation makes it difficult for users to quickly identify which message threads have new activity without manually opening each thread. A customer recently requested the ability to visually indicate new or unread thread replies directly in the message list, similar to unread indicators used for conversations.
💡 Feature Request
Idea
Native Unread Thread Reply Indicator in Message List (iOS UI Kit)
Currently, in CometChat iOS UI Kit v5, threaded messages only display the total number of replies for a parent message in the message bubble. However, there is no native indicator to show when a thread has unread or newly received replies. This limitation makes it difficult for users to quickly identify which message threads have new activity without manually opening each thread. A customer recently requested the ability to visually indicate new or unread thread replies directly in the message list, similar to unread indicators used for conversations.
💡 Feature Request
Idea
Sending Bot Messages to Specific Agentic Conversations via Send Bot Message API
Currently, the Send Bot Message API does not support sending bot messages within agentic conversations. Use Case: In some implementations, backend systems may perform actions (e.g., executing a tool, completing an external workflow, or retrieving data) whose results need to be communicated back to the agent. Ideally, developers should be able to send a bot message tied to the specific agentic conversation. Requested Enhancement: Allow the Send Bot Message API to send messages for agentic bots.
💡 Feature Request
Idea
Sending Bot Messages to Specific Agentic Conversations via Send Bot Message API
Currently, the Send Bot Message API does not support sending bot messages within agentic conversations. Use Case: In some implementations, backend systems may perform actions (e.g., executing a tool, completing an external workflow, or retrieving data) whose results need to be communicated back to the agent. Ideally, developers should be able to send a bot message tied to the specific agentic conversation. Requested Enhancement: Allow the Send Bot Message API to send messages for agentic bots.
💡 Feature Request
Idea
Remove Android Support Library Dependencies from CometChat Android SDK to Enable Jetifier Disablement
The customer would like to disable Jetifier in their Android project; however, the current CometChat Android SDK still depends on legacy Android Support libraries, which forces Jetifier to remain enabled. When attempting to manually exclude these transitive dependencies, the application crashes during SDK initialization due to the missing class android.arch.lifecycle.ProcessLifecycleOwnerInitializer. The customer noted that this dependency could be replaced with the AndroidX equivalent androidx.lifecycle.ProcessLifecycleOwnerInitializer. They are requesting that the CometChat Android SDK update its dependencies to fully adopt AndroidX and remove legacy support library references so that projects can safely disable the deprecated Jetifier option.
💡 Feature Request
Idea
Remove Android Support Library Dependencies from CometChat Android SDK to Enable Jetifier Disablement
The customer would like to disable Jetifier in their Android project; however, the current CometChat Android SDK still depends on legacy Android Support libraries, which forces Jetifier to remain enabled. When attempting to manually exclude these transitive dependencies, the application crashes during SDK initialization due to the missing class android.arch.lifecycle.ProcessLifecycleOwnerInitializer. The customer noted that this dependency could be replaced with the AndroidX equivalent androidx.lifecycle.ProcessLifecycleOwnerInitializer. They are requesting that the CometChat Android SDK update its dependencies to fully adopt AndroidX and remove legacy support library references so that projects can safely disable the deprecated Jetifier option.
💡 Feature Request