Feature Request

Business problem: Currently, there is no direct way to import contacts from HubSpot into respond.io . Users have to manually export contacts from HubSpot and then import them into respond.io , which is inefficient and prone to errors. Desired outcome: Implement a feature within the HubSpot integration that allows users to import contacts directly into respond.io ideally during onboarding stage. Enable options for manual selection of contact lists to be imported. Use Cases: Selective Import: Users can manually select specific contacts or contact lists in HubSpot to import into respond.io for targeted messaging campaigns. Data Consistency: Regular synchronization keeps contact details consistent across both platforms, improving the effectiveness of marketing and support efforts. The current workaround: Users currently export contacts from HubSpot as CSV files and then manually import them into respond.io . This process is time-consuming, labor-intensive, and increases the risk of data inconsistencies due to human error.

Business Problem: Currently, there is no native option to trigger respond.io actions (e.g. sending messages) directly from within HubSpot Workflows. This limitation forces teams to rely on external integration platforms or manual steps to initiate conversations or actions in respond.io , complicating their automation ecosystem and increasing the risk of delays or data inconsistencies. Desired Outcome: Native respond.io Workflow Action: Introduce a dedicated respond.io action type in HubSpot Workflows. This allows HubSpot users to seamlessly initiate respond.io actions—such as sending a WhatsApp message, assign the contact and etc. Unified Automation Ecosystem: Enable users to maintain a single automated workflow environment, eliminating the need for third-party connectors or manual updates. This ensures consistent data handling, reduces complexity, and streamlines cross-platform communication. Use Cases: Sales Handoffs: When a HubSpot contact reaches a new lifecycle stage (e.g., from Lead to MQL), a HubSpot Workflow could automatically trigger a personalized WhatsApp or SMS message via respond.io . This ensures timely engagement without manually switching tools or exporting contact data. Event & Campaign Triggers: Suppose a contact registers for a webinar or completes a form. HubSpot Workflows can immediately prompt respond.io to send a confirmation message or provide next steps, ensuring immediate, automated customer communication. Current Workaround: Users must rely on third-party integration tools (like Zapier or Make.com ) to trigger the respond.io actions based on HubSpot trigger. This adds complexity, creates additional costs, and is prone to errors or delays.

Business Problem: Currently, there is no direct integration between respond.io and HubSpot to automatically capture and log all respond.io activities on the corresponding HubSpot contact’s timeline. Without this centralized, automated recording of key interaction details, users must manually transfer information—leading to data discrepancies and communication gaps. Desired Outcome: Seamless Activity Sync: Automatically log all respond.io activities and messages to the HubSpot contact record. Comprehensive Interaction Details: Include critical data points such as the date and time of messages, when conversations were opened or closed, who opened or closed them, who assigned them to team members, and any conversation summaries or categories. Use Cases: Sales Handoffs: A sales representative can review a HubSpot contact record and instantly see all recent respond.io conversations, including timestamps, participants, and conversation summaries, before making a follow-up call or sending a proposal. Marketing Insight: Marketers can analyze the automatically logged activity data in HubSpot to identify communication patterns, conversation categories, and engagement trends. This insight informs campaign targeting, messaging strategies, and overall customer journey improvements. Operational Efficiency: Managers can track conversation handling times, assignment patterns, and resolution notes directly in HubSpot, reducing the need to switch platforms or search multiple systems for complete customer interaction histories. Current Workaround: At present, users rely on third-party integration tools such as Zapier or Make.com to sync activity data into HubSpot.

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, there is no native action step in respond.io workflows that can directly interact with HubSpot. Users need a streamlined way to push updates, create records, or log activities in HubSpot as part of their automated workflows. Desired Outcome: Direct HubSpot Action: Introduce new Workflow Steps (actions )in respond.io that allows users to interact directly with HubSpot objects within the respond.io workflow builder. Flexible HubSpot Actions: Support essential HubSpot operations, such as creating or updating contacts, adding notes or activities, logging conversation histories and etc. Use Cases: Lead Generation: When a prospect reaches out on WhatsApp or Facebook Messenger, a respond.io workflow could automatically create or update a corresponding HubSpot contact record and log the initial conversation as an activity—streamlining the lead qualification process. Sales Nurturing: If a contact expresses interest in a product, the workflow can instantly update their lifecycle stage in HubSpot and add a note summarizing the conversation, enabling the sales team to follow up with relevant information and timely proposals. Current Workaround: Users currently rely on third-party integration platforms like Zapier or Make.com to bridge the gap between respond.io and HubSpot.

Business Problem: Currently, the HubSpot integration with respond.io only supports the Contact object, limiting the ability to track and manage sales opportunities. Businesses using HubSpot Deals to monitor their sales pipeline lack visibility within respond.io , leading to fragmented sales data, as deal-related insights are only available in HubSpot. Desired Outcome: Support for HubSpot Deals Object: Enable users to sync, view, and update HubSpot Deals within respond.io . Use Cases: Sales Follow-Ups: A sales rep chatting with a prospect on WhatsApp can instantly check their associated deal and update the deal stage in respond.io .

Business Problem: Currently, respond.io does not allow users to customize which contact fields are displayed when integrating with HubSpot. This limitation forces teams to switch between platforms, leading to inefficiencies and fragmented workflows. Desired Outcome: Custom Field Selection: Allow users to choose which contact fields are visible on respond.io for a more streamlined interface. Use Cases: Personalized Contact View: Users can customize which contact details appear in respond.io to focus on relevant information. The Current Workaround: Manually switching between respond.io and HubSpot to view all contact fields.

Business Problem: Currently, contact information between respond.io and HubSpot does not sync bidirectionally. Changes made in one platform do not automatically reflect in the other, leading to: Data inconsistency, where outdated or mismatched contact details exist across platforms Desired Outcome: Configurable Contact Sync: Allow users to define how contact data syncs between respond.io and HubSpot: One-way sync (HubSpot → respond.io ): Changes made in HubSpot are reflected in respond.io One-way sync ( respond.io → HubSpot): Updates in respond.io are pushed to HubSpot Two-way sync: Changes made in either system update the other automatically. Use Cases: Seamless Updates: A sales rep updates a contact's lead status in HubSpot, and the change is instantly reflected in respond.io . Current Workaround: At present, users must: Manually update contact details in both respond.io and HubSpot. Use third-party automation tools like Zapier or Make.com to sync

Business Problem: Currently, if a contact exists in HubSpot but not in respond.io , there is no automated mechanism to create the new contact in respond.io . This results in fragmented customer data, manual duplication efforts, and the risk of misalignment between platforms. Desired Outcome: Automated One-Way Sync: When a contact is found in on HubSpot but not respond.io , the system should automatically create a corresponding contact in the missing platform. Real-Time Data Alignment: Ensure that both platforms remain continuously and accurately synchronized, providing teams with up-to-date contact records wherever they work. Use Cases: Unified Sales & Support Operations: When a new lead is captured through a HubSpot, that contact is automatically created in respond.io . The support team can then immediately follow up via messaging channels without any manual data entry. Current Workaround: At present, you must rely on third-party integration platforms like Zapier or Make.com to detect when a contact exists in one system but not the other and then create it accordingly.

Business Problem Many respond.io users require a straightforward way to access their CRM data within our platform to improve response times and customer interaction quality. Without integration, users must switch between systems, leading to inefficiencies and potential data inconsistencies. Platform Problem Currently, respond.io does not offer a direct integration with HubSpot CRM that allows for pulling and displaying essential contact information within the user interface. Desired Outcome Core/Simple CRM Integration: Establish a foundational integration with HubSpot to pull and display contact data directly in respond.io . This basic integration should include: Displaying contact names, phone numbers, email addresses, and customer lifecycle stages within respond.io . Allowing users to view recent contact interactions and notes from HubSpot without leaving the respond.io interface.