Feature Request

Business Problem: Currently, the lifecycle management feature is primarily designed for desktop use. This limitation creates two significant issues: Mobile app users have restricted access to lifecycle management functions. Information updated on the desktop version is not readily available to those who exclusively use the mobile app. Desired Outcome: Integrate the lifecycle feature into the mobile app, allowing users to view, update, and analyze contact lifecycle stages directly from their mobile devices.

Business Problem: Contacts typically have a lifecycle status that defines their current engagement or sales progress with the business. Currently, tracking and managing a contact's lifecycle status within the platform is challenging. Furthermore, the existing open and closed conversation statuses are inadequate for lead management. Contacts in the sales pipeline often remain in open conversations rather than being closed, as sales agents still need to follow up with them. This has led to clutter in the open conversation list, causing some contacts to be overlooked for follow-up and resulting in lost leads. Desired Outcome: It would be good if we could track and manage the lifecycle status of contacts within the platform directly and organize the conversations based on the lifecycle status to enhance conversation management. Additionally, generating insights to monitor lifecycle metrics, such as conversion rate would be valuable for monitoring the sales process and making data-driven improvements. Workaround: Create a custom field and custom inboxes to track the lifecycle status.

Business Problem: Currently, there is only a receipt generated for WhatsApp Fees Top Up and no other information, such as company name and address are displayed in the receipt. Desired Outcome: It would be good if users can get the receipt for each top up that includes: Respond.io name and address User's company name and address Top up amount

Desired outcome: It would be good if ChatGPT can read the messages received and propose a few responses. The user would be able to edit suggestions before responding to the contacts.

Currently, the time format of Business Hours in the Date & Time step is HH:MM in 24 hours clock. Hence, the maximum End Time users can input for the Business Hours is 23:59 only which there is a minute between 23:59 to 00:00 that cannot be selected to use in the Business Hours. It will be good if the time of the Business Hours in the Date & Time step can cover until the end of the day (00:00). It is very useful for midnight shift transfer, for example, I have a workflow for the evening shift team to transfer the conversations to the morning shift team from 23:00 to 01:00 of the next day.

Business problem: As a digital marketing team, we want to implement the Conversions API in our platform to create a direct connection between our marketing data and the systems that help optimize ad targeting, decrease cost per result, and measure outcomes across Meta technologies, so that we can improve our marketing efficiency and ROI. Desired outcome: Direct integration with Meta's technologies for optimized ad targeting. Decreased cost per result. Enhanced measurement of marketing outcomes. Use Cases: Improve accuracy in ad targeting by leveraging first-party data. Measure ad performance across Meta's platforms more effectively. The current workaround: N/A

The platform supports only one conversation language per Agent (the primary language field). In this case, when a chatbot is multilingual, the platform can't support several languages. Consequently, the user can't choose a preferred language in a chatbot from the start or during a conversation.

Business Problem: Our current AI Agent Workflow Step occasionally encounters queries that it cannot answer, either due to their complexity or because they fall outside its programmed knowledge base. In these instances, the AI lacks a clear pathway to handle such unanswered queries effectively, potentially leading to customer dissatisfaction. Desired Outcome: Introduce a new branch to handle cases where the AI cannot provide a response to a query. Users can configure the handover using the branch.

Sometimes you may want to give access to some functions in the Settings Panel but not others. Granular permissions should allow you to set these permissions at a more granular level.

I use a custom Respond field to track my users' birthdays, many of which are before 1975. Can we get years further in the past? Thank you.