Feature Request

Business problem: As an agent on the go, I want to handle support Channel calls such as WhatsApp, Messenger, etc. directly from the mobile app, so that I can provide seamless customer service without being tied to a desktop. Desired outcome: Allow agents to initiate and receive calls via the mobile app. Use Cases: Agents resolving customer issues while traveling. Field agents managing customer calls during site visits. The current workaround: N/A

Business Problem: Currently, respond.io supports integration with platforms like Zapier and Integromat, but there is no direct integration with n8n.cloud ( n8n.io ). Many businesses prefer n8n due to its lower costs and flexible workflow automation capabilities. Without a native integration, users must rely on workarounds or custom scripts, making automation more complex. Desired Outcome: Enable integration with n8n.cloud ( n8n.io ) to allow seamless automation of workflows. If a full integration is not immediately possible, ensuring that webhook support is available would already help users connect respond.io with n8n efficiently.

Business Problem: The current AI model has limitations, including a restricted space for creating custom AI personas and challenges with understanding synonyms, leading to ineffective customer interactions. Desired Outcome: Integrate the ChatGPT API to enhance the AI's capabilities and allow the creation of customized GPTs for a more tailored conversational experience. Details of the Potential Feature and Use Case: Utilize better versions of ChatGPT and custom GPTs. Improve understanding of varied customer responses, such as synonyms (e.g., "auto" for "car"). Enable seamless access to a customized AI persona via the ChatGPT API, connected with Respond.io for optimized customer interactions.

It helps the agents automatically close the conversation after 30 minutes duration. It enables the agent to save extra time a lot.

Business Problem Currently, respond.io supports calls accross channel like WhatsApp Meesener (Beta), Telneyx (soon), but there is only one default ringtone available for all. Desired Outcome: Enable the ability to upload custom audio files and offer a wider selection of ringtones for better customization.

Business Problem: Currently, customers have no way to track or verify how many CAPI (Conversions API) signals are being sent to Meta from the platform. Moreover, there is no visibility into which individual contacts these signals are associated with. This lack of transparency makes it difficult for customers to reconcile performance data and understand signal effectiveness within Meta Business Manager. Desired Outcome: This enhancement will empower customers to better monitor their data sharing with Meta, validate conversions, and align insights with metrics available in Meta Business Manager. The total number of CAPI signals sent. A breakdown of signals by individual contacts (e.g., contact ID or name). Status indicators showing whether each signal was successfully delivered.

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 : This is NOT a limitation on respond.io . This is a limitation set by Facebook's team to all WhatsApp API accounts.

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.

Business Problem Businesses are seeking to proactively engage with users by initiating conversations through Instagram Direct Messages (DMs) whenever users comment on their Instagram posts. Desired Outcome The goal is to channel commentators towards DMs for further engagement, by implementing two key features: Instagram Private Replies: This feature would enable businesses to respond to comments on their posts with a private message sent through Instagram Direct. Automatic DMs for Commenters: This would automatically send a Direct Message to users who comment on posts, facilitating immediate and personalized engagement.

Business problem: As a customer service agent using Respond, I want to automatically see the contact's name when they message via Messenger / Instagram / WhatsApp Business App, so that I can avoid asking for it again and create the Contact and address the Contact accurately Desired outcome: Auto-populate contact name from Meta Reduce manual contact data entry Improve customer experience and personalization Use Cases: Avoid toggling between Meta Inbox and Respond Avoid asking Contact for their name The current workaround: Manually ask for the name or check Meta Inbox and update manually Important note footer: This is a limitation from Meta due to policy. We are working with Meta closely to help address this issue. Refer to the official documentation here .