Feature Request

Business problem: Updating lifecycle manually limits automation. Additionally, without proper webhooks and triggers for Lifecycle, users cannot build automations around Lifecycles of Contacts Desired outcome: Allow the ability to change Lifecycle via automation, such as workflow step. Triggers and webhooks would also help users create automations when Lifecycle changes for contacts. This could help automations with other integrations such as GSheet, HTTP calls, etc.

Business problem As a business owner, I want to create structured interactions for business messaging using WhatsApp Flows, so that I can provide customers with a more organized and seamless communication experience. Desired outcome A feature that allows businesses to define, configure, and customize messages with rich interactions using WhatsApp Flows. Use Cases Customers can utilize Flows to schedule appointments, browse products, gather customer feedback, generate new sales leads, or engage in any other scenario where structured communication enhances the natural and comfortable interaction with customers. Businesses can use WhatsApp Flows to automate customer onboarding processes, guiding customers through a series of structured messages to collect necessary information and provide a smooth onboarding experience. The current workaround Currently, businesses can try to simulate a similar experience using the respond.io workflow builder, webhooks, APIs, and integrations like Zapier and Make.com .

I would want to have a click-to-call feature to make a voice call directly on respond.io platform (e.g. using SIP)

Business Problem The platform serves as a hub for customer interactions, with users dedicating substantial time to it. Introducing an option that is gentler on the eyes would enhance comfort and elevate the overall user experience. Platform Problem Currently, the desktop web platform does not offer the dark mode option. Use Case To allow users to choose which mode (light or dark) suits their way of working accordingly.

Desired outcome Allow to receive WhatsApp calls. At least allow only one user at a time can be allowed to receive WhatsApp calls, if it's complicated to allow multiple user using the same WhatsApp.

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.

Desired Outcome: Make all URLs clickable in messages, regardless of whether they have http or https prefixes, aligning with the web app behavior. Business Problem: Users currently need to copy and paste URLs without http or https prefixes, which disrupts their workflow and impacts usability. Platform Limitation: The mobile app doesn’t currently recognize URLs without http or https as clickable links.

Business problem: As a WhatsApp user, I want balance cards for unused WABAs to be removed from my view, so that I can focus on active WABAs that require top-up. Desired outcome: Display only active WABAs requiring top-up. Automatically hide/archive balance cards for deactivated or unused WABAs. Use Cases: Quickly identify WABAs needing top-up to ensure uninterrupted service. Maintain a clutter-free WABA balance management pagr The current workaround: Must manually locate and ignore unused WABA balance cards.

Sometimes broadcasts are sent accidentally. An option to stop an in progress broadcast would help solve this problem if it occurs.

It would be great to be able to manage Linkedin Chats & Comments inside respond.io .