Feature Request

Reporting api to allow connection to looker sudio or power bi

We’d like to request an enhancement for the workflow trigger options. Specifically, having a trigger for incoming messages or the ability to send tags when using a webhook would be incredibly helpful. This would streamline our processes significantly and reduce the heavy use of operations in Make.com . Looking forward to your feedback!

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, AI Agent does not have the capability to process images. 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 and respond based on the image. 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

Please connect to TikTok if such an API exists.

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 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: Currently, closing notes on Respond.io require manual input, which can be time-consuming and inconsistent. Users have no automated way to categorize or summarize conversations effectively. This lack of automation hinders the ability to analyze trends, sentiments, or outcomes across conversations, leaving a gap in actionable insights. Desired Outcome: Implement an AI-driven system for closing notes that: Automates Categorization: Suggests or selects categories (e.g., "Resolved," "Escalated," "Follow-Up Needed"). Generates Summaries: Provides concise, AI-generated summaries of the conversation when a conversation is closed. Exportable Data: Stores categorized notes, summaries, and sentiments in a table for Data Export. This enables users to view trends in conversation outcomes and sentiments across the platform. By introducing this feature, Respond.io can: Save users time by automating closing note tasks. Improve data consistency for more accurate insights. Empower businesses with actionable analytics to enhance customer interactions and team performance.

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

Business Problem: Duplicate contacts are created when numbers added lack an area code following the country code. This occurs despite initial contact through a WhatsApp template. Use Case: For contacts from Mexico, if the number added after the country code "+52" does not include the area code digit "1", the system creates a duplicate contact, even after a WhatsApp template is sent. Desired Outcome: Implement a feature to automatically verify and append the necessary area code after the country code when a new contact is added. Example: For contacts in Mexico, the system should automatically check for the presence of the digit "1" after the country code "+52". If absent, it should automatically insert the digit "1". This adjustment aligns with WhatsApp's requirements for Mexican numbers. Workaround: Manually append the appropriate area code to each number during import. The final format should consistently follow the pattern: +(country code)(area code) without the "1" after +52.