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 : 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, 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 platform currently lacks the ability to trigger workflows based on keywords or phrases within contact messages, limiting automation capabilities. Desired Outcome: Enable triggers to start workflows based on the contact's messages containing specific keywords or phrases, ensuring it also applies to open conversations. Use Cases: Keyword/Phrase-Based Triggers: Enable workflows to be triggered based on specific keywords or phrases in messages, such as automatically sending predefined responses based on certain keywords. Workaround: Filter by incoming message using the Branch step. https://help.respond.io/l/en/broadcasts/workflow-based-on-broadcast-response

Business problem: Currently, AI Agent does not have the capability to process images from messages. This feature would help platform users handle objective queries where the contact sends an image, AI Agent will not be able to process it answer based on the image that the contact is enquiring about. Desired outcome: Allow AI to process images based on the image from messages. Specific use cases: Identify brands of items of the image and provide a response on said brand / product Identify issues from images and provide a response based on knowledge sources (i.e. image of a malfunctioning device of a specific brand) Process an image of a form, receipt, etc Use case (Capture, Convert, Retain): This feature spans multiple phases: Capture: Visually engage users early in the journey—think visual search or product discovery via images. Convert: Streamline image-based product matching and upselling in chat. Retain: Use visual input to reduce back-and-forth and solve problems faster.

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: Right now, Respond AI Agents can't interact with external systems in real time — limiting their ability to trigger workflows, fetch dynamic data, or complete transactions. Without the ability to make HTTP calls, the AI is cut off from countless integrations and use cases that require external API access, forcing handoffs to humans or third-party automations. Desired Outcome: An AI Agent capability to make HTTP requests (GET, POST, PUT, DELETE) to external endpoints. This would allow AI Agents to fetch live data, update CRM records, trigger automations, check order statuses, submit forms, or interact with custom services based on the conversation flow. This unlocks endless possibilities for customization, automation, and AI-driven execution. Use Case (All Lifecycle Phases) * Capture : Call a lead enrichment API to personalize outreach. * Convert : Check shipping costs or create orders via third-party services. * Retain : Fetch ticket status or update records in real-time. With HTTP support, Respond AI transforms from a chat assistant into an action engine — fully capable of reading, writing, and reacting across your ecosystem in real time ⚙️🌐🚀

Problem Statement: Currently, our AI features can’t send images or files to customers. This is a major roadblock for both sales and support teams, who often need to share product images, brochures, guides, or troubleshooting documents to give customers the full context or help them solve problems. Without this, customer interactions are less effective and require manual intervention for something as simple as sending a file. Desired Outcome: AI should be able to recognize when an image or file is needed and send the appropriate material automatically, based on the conversation. This would allow customers to get complete answers and resources instantly, boosting satisfaction, speeding up resolutions, and letting teams focus on more complex tasks—without having to jump in just to attach a file.

Business Problem: Our platform currently lacks a personalized product recommendation feature. This absence limits our ability to guide customers towards products that best suit their needs and preferences, potentially leading to missed sales opportunities and reduced customer satisfaction. Desired Outcome: Implement a new AI Agent objective that suggest relevant products based on Contact's conversation. This objective should improve user experience by offering tailored suggestions, increasing the likelihood of purchases, enhancing customer engagement and able to capturing intent after recommending products. Use case (Convert): This feature clearly shines in the Convert phase. You're already engaging the customer—they’ve reached out or responded—and now it's time to seal the deal. The AI doesn’t just inform; it persuades. It uses the context of the chat to: Recognize buying signals Suggest products that align with the customer’s use case Help the customer make a confident, informed buying decision So, you're not just solving for engagement—you’re solving for revenue.

Business Problem: Currently, agent availability must be managed manually, which makes it difficult to plan ahead for shift coverage—especially for businesses that operate 24/7 or have rotating schedules. This results in missed handovers, delayed responses, and inefficient workload distribution. Desired Outcome: Enable a built-in calendar or scheduling feature that allows admins or managers to define agents’ availability in advance (weekly or monthly). Based on the schedule, the platform should automatically: Mark agents as available/unavailable. Trigger relevant automation (e.g. shift-based routing or task reassignment). Use Cases: Customer support teams with rotating shifts (e.g. morning, evening, overnight). Service businesses operating in multiple time zones. Automatically adjust assignment logic based on agent availability without manual intervention.

Desired outcome Allow for granular or custom user level access. A user may have the same role, but with different level of permission from other users. Have one access level that is higher than Agent, but lower than Manager, in which they can access Dashboard, Contacts, Messages, Snippets, Settings: Users & Teams (but NOT workflows and most of the settings). Business use case: Some customers are online stores and they have an operation team. The agent will transfer contact to operation team for feedback (write comments to agent) then they will return back to the agent. Some operation teams may give read only mode with reply to contacts, just to search and review history if requested from his manager etc Some agents want to disable voice notes to customers, only to reply in text So if possible to add permissions to each user: Enable/Disable reply to contacts (Read only) Only they will use comments between teams and agents: Enable/Disable Send files Enable/Disable send survey Enable/Disable record voice notes It's an internal process flow between teams, where customer care will assign contact to operation team for feedback. They should document their response as comment and return back to agent to discuss the feedback with contact. The operation team does not have responsibility to answer contact direct, so we need to disable the reply to prevent the human mistakes.