Feature Request

Business Problem: Currently, the AI Agent: Collect Information feature asks a confirmation question after gathering details such as name, email address, and phone number. While this ensures accuracy, it often results in drop-offs when Contacts or Customers fail to respond, causing the AI to withhold the collected information from being passed to respond.io , and proceed to ELSE branch. Desired Outcome: Introduce an option to disable the "Confirmation" step in the AI Agent. This will allow the AI to automatically pass collected information to respond.io for data storage even if the Contact did not confirm with AI, reducing drop-offs and ensuring seamless data capture.

Business problem: As a business owner, I want to trigger conversations with the Get Started Event, so that I can engage users promptly at the beginning of their journey. Desired outcome: Automatically initiate conversations when users first interact with the channel. Use this event to open a conversation or as a workflow trigger Seamlessly integrate this event into existing workflows. Use Cases: Welcome message delivery to first-time users. Gathering initial user preferences or data. The current workaround: N/A

Business problem: As a channel manager, I want an auto alert feature to let me know my channel token has expired so that I can refresh the token and minimize operational disruption. Desired outcome: Automatic notification upon token expiration Seamless token refresh process Use Cases: Alert channel managers before token expiration to prevent service interruptions Provide a direct link or method for quick token refresh The current workaround: Manual checking of the channels

Here’s the rephrased message: Business Problem: The variable created within the workflow is not case-sensitive, but spaces can cause the branch step to malfunction. Desired Outcome: Have a preview list of variables within the same workflow to reduce the effort of copying and pasting from previous steps.

Lead Ads allow for collecting more information from the Contact which can be added on Respond.io By clicking on the lead ad, contacts will see a form that’s conveniently pre-filled with the info they’ve already shared with Facebook—like their name, number, or email. Workaround: Utilize either the Zapier template or the Make.com template to automate creating or updating a contact in respond.io when they submit the Facebook Lead Ads form. Zapier Template: Link Make.com Template: Link

Business problem: Character limit: Comments are restricted to 1000 characters, which is frequently exceeded, requiring users to split comments into multiple pieces. In contrast, normal messages support up to 2500 characters. No dedicated links: Comments lack dedicated links, making it impossible to direct colleagues to a specific comment. Only conversations have dedicated links currently. Generic customer notes: There is no functionality for creating pinned, customer-specific notes relevant only to a specific customer. Desired outcome: Enhance the functionality of comments to align with normal messages on the platform. Specifically: Increase the character limit for comments to match the 2500-character limit of normal messages. Add fixed links to individual comments for easy referencing and collaboration. Introduce a pinned note feature for customer-specific comments to track relevant details Workaround: Users currently rely on splitting comments into multiple entries, using external platforms for file sharing, and referencing conversation links instead of specific comments. These workarounds are inefficient and disrupt workflows.

Business Problem: Currently, AI Agent and AI Assist occasionally fail to retrieve accurate information from knowledge sources, even when the information exists. These challenges arise due to: Knowledge Source Formatting: Improperly formatted sources may lead to retrieval errors. Users can follow guidelines here to improve formatting. Non-English Knowledge Sources: Information in languages other than English is not consistently handled by the system. In some cases, the AI may still fail to retrieve accurate information despite correct formatting and content due to technical limitations inherent to AI technology. Desired Outcome: Enhance the knowledge source retrieval system to address these two core issues: Improve AI handling of non-English knowledge sources. Mitigate dependency on perfect formatting by refining retrieval methods. This enhancement would lead to higher accuracy and reliability in AI Agent and AI Assist responses, reducing errors and improving user satisfaction.

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.

A must required feature for a company having sales agents who are provided with access to this platform, since agents are assigned with defined contact addition and conversation targets. At current, Agent level access doesn't have a contact count to check how many contacts are added in total and as per the filter selection. Would be helpful if can get this small feature added on priority.

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.