Feature Request

Business Problem: As a sales agent using Respond, I want to see the correct contact name when a Contact is created via an echo message (a message sent from the WhatsApp Business App), so I don’t have to rely on the generic name. Currently, contacts created this way display a generic name instead of the actual contact’s name, making it harder to engage personally and efficiently. Desired Outcome: Auto-create the contact with the actual name when the contact is created via an outgoing message from the WhatsApp Business App Current Workaround: Manually ask the customer for their name or check WhatsApp Business App, then update the contact info manually. Important Note: This is a known limitation due to Meta’s platform policy. We are actively working with Meta to explore solutions and will update this request if the policy changes or alternatives become available.

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.

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: 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

Make creating new WhatsApp Templates easier by allowing them to be created by AI prompt. Also use AI to predict if the template will be categorized as Utility or Marketing.

Business Problem Businesses often have several sales people converting leads. Knowing which sales person has the best conversion rates allows business owners to learn the tactics of the best sales people. Knowing the sales person with the worst conversion metrics allows business owners to help those sales people to improve.

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.

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: If I connect my WhatsApp Business App to respond.io , I want to enable WhatsApp calling within the platform, so that my team can handle calls without switching apps and maintain full visibility over communication. Desired outcome: Enable calling for WhatsApp Business App on respond.io Support Respond.io calling features for WhatsApp Business App channels. Use Cases: Support agents taking calls directly from platform using WhatsApp Business App Companies wanting to log calls made via WhatsApp Business App The current workaround: This feature is only available on the native WhatsApp Business App and not on respond.io due to Meta limitation

Business Problem For many businesses after the lead has made their first sales there is repeat business. Business owners would also like to know the conversion rates for the repeat business. Some of examples of this could be: Customer comes back to buy an additional product or service Customer inquires about a new service and an appointment needs to be booked Business Owners would like to know the following How many new opportunities from existing customers do they have each day/week/month How many of those opportunities were converted