Feature Request

Business problem: As a marketer, I want the ability to track different Click-To-Chat (CTC) ads performances and their conversion rates directly on the Respond.io platform, so that I can effectively measure and optimize my chat marketing campaigns. Desired outcome: Integrated tracking for CTC ad performance Conversion rate measurement for each CTC ad Real-time analytics dashboard Use Cases: Measure the effectiveness of different CTC ads in real-time Optimize chat marketing strategies based on conversion data The current workaround: Creating a workflow automation that uses CTC ads as a trigger, captures the CTC ad variables, and logs them into a Google worksheet

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: Businesses that primarily use the WhatsApp Business App face limitations when trying to scale their customer interactions. Currently, they cannot connect their WhatsApp Business App to our platform and utilize our advanced features while retaining their WhatsApp Business App and phone number. This restriction hinders their ability to efficiently manage and scale customer communications, impacting overall customer service and engagement. Desired Outcome: Enable businesses to use the WhatsApp Business App and access Cloud API solutions concurrently. This co-existence would allow businesses to leverage Cloud API-enabled tools to connect with their customers at scale, while still maintaining the continuity of their WhatsApp Business App and phone number. This dual capability would enhance their operational efficiency and customer service capabilities.

Business Problem The business needs specific files to be filled out or signed in a PDF file. Platform Problem Currently, does not support any files in Snippets. Desired Outcome Allow files to be attached to a snippet.

Business problem: As a manager, I want to restrict call capabilities for agents and align incoming call menu visibility with agent user restrictions so that I can ensure compliance and improve call handling efficiency. Desired outcome: Ability to configure call permissions per agent role Incoming call menu visibility aligns with agent restrictions Improved control over call-handling capabilities Use Cases: Managers restrict outbound calls for certain agents Agents only see call options relevant to their permissions The current workaround: N/A

Business problem: As a user, I want to see reports and insights on my call logs and activities so that I can track performance, identify trends, and make data-driven decisions. Desired outcome: Visual reports with call metrics (e.g., duration, volume). Insights into call patterns and customer behavior. Exportable reports for analysis and sharing. Log table with details on each call (direction, duration, user, etc..) Use Cases: Monitoring team productivity and call efficiency. Identifying peak call times and optimizing resource allocation. The current workaround: N/A

Enable to receive inbound calls on the respond.io platform.

Business Problem: Currently, Users cannot edit HubSpot fields directly within respond.io . This limitation forces teams to switch between platforms, leading to inefficiencies, inconsistent data, and fragmented workflows. Desired Outcome: Direct HubSpot Field Editing: Enable users to edit HubSpot contact fields directly from respond.io . Improved Data Consistency: Ensure changes made in respond.io are reflected in HubSpot Use Cases: Seamless HubSpot Updates: A sales rep updates a customer's status directly in respond.io , and the change syncs instantly with HubSpot. The Current Workaround: Manually switching between respond.io and HubSpot to edit contact details.

Business Problem: Currently, Users cannot edit Salesforce fields directly within respond.io . This limitation forces teams to switch between platforms, leading to inefficiencies, inconsistent data, and fragmented workflows. Desired Outcome: Direct Salesforce Field Editing: Enable users to edit Salesforce contact fields directly from respond.io . Improved Data Consistency: Ensure changes made in respond.io are reflected in Salesforce Use Cases: Seamless Salesforce Updates: A sales rep updates a customer's status directly in respond.io , and the change syncs instantly with Salesforce. The Current Workaround: Manually switching between respond.io and Salesforce to edit contact details.

Business Problem: As a sales representative, I want a dedicated tab in the contact side drawer to view all call-related activities and events, so that I can quickly access and manage call information without sifting through unrelated data. Desired Outcome: Simplify access to call-related activities. Improve efficiency in managing contact interactions. Provide a streamlined view for better decision-making. Use Cases: Quickly review all past and scheduled call activities for a contact. Identify and follow up on missed calls or call notes efficiently. The Current Workaround: Look through the existing "activities" tab or scroll through conversation history.