Feature Request

The official WhatsApp API currently doesn't support Group Chats. Other platforms supporting WhatsApp Groups use unofficial APIs that often break. We will consider building this feature once it is released officially for WhatsApp API. 🔴 Important Note : As of February 2026, Meta has released native Group Chat support through WhatsApp cloud API. However, there's significant restrictions at this time: It is not available for Coexistence users yet Because of this, once Meta expands eligibility and releases full documentation for all account types, we can consider to move forward. This is NOT a limitation on respond.io . This is a limitation set by Meta's team to all WhatsApp API accounts.

I would like to be able to delete or edit a message that I sent by mistake on the Messages module, and for it to also be removed for edited rom the recipient's device. 🔴 Important Note: This is NOT a limitation on respond.io . This is a limitation set by Facebook's team to all WhatsApp API accounts.

Business Problem: When a business connects their WhatsApp Business App (WABA) to the WhatsApp Cloud API, existing conversations are not imported into the new environment. This creates a disjointed experience for users who expect to see their past chats, leading to confusion, loss of context, and operational inefficiencies for support and sales teams. Desired Outcome: Allow import of existing conversation history from the WhatsApp Business App when transitioning to the Cloud API, allowing users to continue conversations seamlessly without losing prior message context.

Business Problem: Currently, users can only be assigned to one team within a single space on respond.io . This limitation restricts flexibility for users who need to participate in multiple teams, such as Customer Support and Sales, but not Management. Desired Outcome: Allow users to belong to multiple teams within a single space on respond.io . For example, a user could simultaneously be part of both the Customer Support and Sales teams while not being assigned to the Management team, enabling better collaboration and access to relevant resources.

Currently, we can insert steps at any point easily. However, we can't delete the step easily as sometimes it will cause all the steps below it to be deleted.

Business Problem: The current role-based permissions structure (Agent, Manager, Admin) does not provide enough flexibility for organizations with complex operational workflows. Many businesses — especially those with multiple internal departments — require fine-grained control over what each user can view, edit, or do inside the platform. This leads to risks such as accidental customer replies, unauthorized data edits, or exposing sensitive information to users who should not have access. Desired Outcome Introduce a granular permission system that allows workspace admins to customize access levels per user or per role. This should include the ability to enable or disable specific actions, modules, or permissions, such as: Access to Dashboard, Contacts, Messages, Snippets, Users & Teams (but not Workflows or advanced settings) Read-only access to conversations Restricting ability to reply to contacts Restricting ability to send files, surveys, or voice notes Allowing comments only for inter-team collaboration Use Cases Multi-Team Operational Workflows Some customers (e.g., online stores) have an operations team that reviews cases internally. The desired flow: Customer care assigns a contact to the operations team Operations team reviews history Leaves internal comments Contact is returned to the agent However: The operations team should not reply directly to the customer Replies must be text-only for some agents Operations team should have limited permissions (no surveys, no attachments, no voice notes) Restricting Access to Sensitive Contact Fields Currently, contact fields marked as hidden are only collapsed behind a dropdown — but are still accessible and editable. Organizations need stronger control over field visibility to protect internal or confidential data. View-only fields: Users (at least agents) should be able to see certain fields but not edit them. Fully hidden fields: Some fields should be completely invisible to certain roles (not displayed anywhere in the interface). This is important for companies storing sensitive customer data (financial info, internal IDs, CRM-synced fields, etc.), where only a subset of users should have access or edit rights.

Sometimes I want to mark messages as unread so I can get back to it later.

Business Problem: Businesses face challenges in efficiently handling meeting and appointment scheduling through chat. Key components of the issue include: Allowing contacts to easily schedule meetings or appointments via chat. Providing businesses with tools to manage availability, meeting durations, and other appointment settings. Sending appointment confirmations and reminders via chat to ensure contacts are informed about upcoming meetings. Enabling contacts to reschedule appointments directly through chat when needed. This lack of an integrated solution forces businesses to rely on external tools, leading to inefficiencies and potential friction in the user experience. Desired Outcome: Implement an integrated appointment scheduling feature within the platform. This feature should include: Seamless scheduling of meetings or appointments directly through chat. Customizable business settings for availability, meeting durations, and appointment preferences. Automated confirmation and reminder notifications via chat. Easy rescheduling options for contacts to adjust appointment times when necessary. Use Cases: Customer Support Appointments: Enable customers to book service or support sessions directly during chat interactions. Sales Meetings: Allow prospects to schedule demos or sales calls in real-time through chat. Automated Reminders: Ensure customers receive timely reminders and confirmations to reduce missed appointments. Workaround: Businesses currently use third-party applications like Calendly for appointment scheduling and share booking links with contacts. However, this adds extra steps and disrupts the seamless chat experience.

Business problem: As a user, I would like to automatically send a public reply from respond.io to contacts who comment on my Instagram posts or Reels, so that I can capture and engage leads while their interest is at its peak. Desired outcome: Auto-reply to comments publicly Boost engagement and conversion in real time Use Cases: A user comments on a Reel and receives an public reply A follower asks a question and gets a public + private response The current workaround: N/A

Business Problem Organizations with multiple agents operating simultaneously or across various time zones and shifts face a challenge in monitoring their activities. As a manager, I seek the capability to oversee and analyze the activities of my agents. Platform Problem Presently, the platform lacks an option to comprehensively track agents' activities beyond assignment and closure times. Desired Outcome To have a connection time report on the agents: Duration of online/offline periods Specific timing of online/offline sessions Timing and duration of breaks taken