Feature Request

Business Problem The current Voice AI Agent does not offer a native Castilian Spanish (Spain) voice. Available Spanish voices typically sound Latin American or non-local, which can negatively impact customer trust, comfort, and perceived service quality for businesses operating in Spain. Desired Outcome Provide Voice AI Agent support for Spanish (Spain – Castilian) with a native accent.

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, check product availability, 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 ⚙️🌐🚀

Business problem: As a mobile app user, I want the app to ring for incoming calls even when it is in the background or closed, so that I don’t miss calls while I’m on the go. Desired outcome: Play an audible ringing sound for incoming calls when the mobile app is in the background or closed Reduce missed calls on mobile Improve reliability of mobile call handling for on-the-go users Use cases: A sales agent receives an inbound call while the app is in the background and needs to answer immediately A support agent has the app closed but still needs to be alerted by a ringing sound for incoming calls Mobile-first users who rely on calls as their primary channel while moving between locations Current workaround: Users rely on push notifications only Calls are often missed and only seen as missed calls afterward

Business Problem: Digital marketing teams running Google Ads face challenges connecting ad performance directly to messaging outcomes. While Google Ads supports Click-to-WhatsApp CTAs, attribution is unreliable because WhatsApp does not allow referrer tracking. Without proper attribution, businesses cannot measure ROI accurately, optimize campaigns, or connect Google Ads conversions to lifecycle reporting. Desired Outcome: Provide clear source and campaign attribution for leads entering via Google Ads Click-to-WhatsApp campaigns. Surface Google Ads campaign performance in lifecycle reporting alongside other marketing channels. Use Cases: A retail business runs Google Ads campaigns with Click-to-WhatsApp buttons. Each incoming lead is automatically tagged with campaign source for accurate ROI measurement. A company wants to optimize ad spend by sending conversion goals (e.g., qualified leads, closed deals) back to Google Ads for smarter bidding. Marketing teams can view Google Ads contribution directly in lifecycle reports

Business Problem: Right now, Respond.io ’s AI Agent doesn’t have “conversation event” context—meaning it isn’t aware of important state changes like a conversation being closed and then reopened by a new inbound message. Because of this, the AI Agent often behaves as if nothing significant changed, even when the platform clearly shows the conversation has re-entered an open state. A common scenario looks like this: An issue is resolved and the conversation is closed. Shortly after, the contact sends a final acknowledgement like “Ok thank you” or “👍”, which reopens the conversation. The message does not indicate a new request; it’s simply a closing remark. The AI Agent should recognize this as a reopen caused by a polite follow-up and re-close the conversation automatically. Instead, the conversation stays open unnecessarily, which creates inbox clutter, adds extra triage work for human agents, and introduces noise in reporting (reopen counts, resolution time, and backlog). There’s a second related behavior: when the AI Agent has already called a tool earlier in the conversation, it tends to avoid calling that same tool again later—even when it’s perfectly valid and necessary because the conversation state has changed (for example, after a reopen event). This “one-and-done” tool behavior reduces reliability in event-driven flows. Desired Outcome: AI Agent should be able to understand and use conversation events—especially closed → reopened transitions—so it can make state-aware decisions. When a conversation is reopened and the new inbound message is clearly an acknowledgement with no new intent, AI should confidently re-close the conversation to keep the inbox clean and prevent unnecessary follow-ups. In addition, conversation events should act as a strong signal that prior actions may need to be repeated. AI Agent should be allowed (and encouraged) to call tools again when an event indicates a new state, rather than treating a previously-called tool as “off-limits” for the rest of the thread. This helps the Agent behave more like a dependable operator: aware of what just happened, and comfortable repeating the correct action when conditions warrant it.

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 October 2025, Meta has released native Group Chat support through WhatsApp cloud API. However, there's significant restrictions at this time: Group chat support is currently limited to businesses with at least 100,000 monthly business-initiated conversations 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.

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: As a user, I want the option to decide whether an Instagram Story reply opens a new conversation in my inbox, so that I can focus on leads coming from Story replies only during active campaigns. Desired outcome: Control inbox behavior for Story replies Filter and prioritize conversations from campaign-specific Stories Reduce noise from non-campaign interactions Use Cases: Only open new chats from Story replies during a product launch Ignore Story replies outside of active lead-gen campaigns The current workaround: N/A

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.

Native integration with Zoho.