Understanding sync settings
The HubSpot admin sync tab manages contact data synchronization between Aloware and HubSpot. It offers automated data syncing. By default, Aloware serves as the data receiver, but you can configure syncing based on your specific needs.
To ensure successful data synchronization, it is important to configure property mapping and validate property types. Property types in HubSpot should match the data formats sent from Aloware, such as ensuring datetime fields are aligned appropriately.
Your sync settings consist of two (2) main operations:
Contact creation
When new contacts are added to either system, you can control how they flow between platforms:
Bi-directional sync (↔) - contacts created in Aloware are pushed to HubSpot, and contacts created in HubSpot are created in Aloware.
Inbound sync (←) - contacts created in Aloware are not sent to HubSpot, but HubSpot-created contacts are created in Aloware.
Contact update
When existing contact information changes, you can determine how updates are handled:
Bi-directional sync (↔) - contact updates from Aloware are reflected in HubSpot, and contact updates from HubSpot are reflected in Aloware.
Inbound sync (←) - contact updates in Aloware will not be sent to HubSpot, but HubSpot contact updates will be reflected in Aloware.
To enable seamless updates across both platforms, it’s imperative to also configure property mapping within the Contact Property Mapping tab to ensure no critical data discrepancies occur during the sync process.
Recommended configuration
The default configuration supports bi-directional contact creation, allowing both systems to add new contacts.
However, for updates and new contact entries, configuring for bidirectional sync is recommended to ensure continuous data flow between Aloware and HubSpot. To mitigate the risk of unintended overwrites, maintain clear property mapping and field validation.
One-time operations (Push and Pull)
One-time pulls or pushes should not be regular practices. These operations are designed for initial setup or troubleshooting scenarios. Each button displays the latest update information (e.g., "Last push contact: Jul 10, 2024, 6:38 PM PDT").
Contacts management
To ensure that Aloware remains in sync with HubSpot, there may be instances where a one-time data pull or push is necessary.
Push contacts - this operation sends Aloware contacts to HubSpot, updating the contacts in HubSpot based on Aloware data.
Pull contacts - this operation imports HubSpot contacts into Aloware. Note that this action incurs LRN lookup charges.
If synchronization issues arise during these operations, ensure that the property types match across both platforms and that all mapped fields are correctly configured. Troubleshooting might also involve rechecking integration settings or consulting Aloware support for further assistance.
Data synchronization
Pull lead statuses - imports HubSpot lead statuses into Aloware as contact disposition statuses.
Pull call outcomes - imports HubSpot call outcomes into Aloware as call disposition statuses.
When the HubSpot integration is enabled, only call and contact dispositions that are synced from HubSpot will be displayed within the application. This ensures that users only interact with relevant data associated with their HubSpot account.
Pull activity types - imports HubSpot call and meeting types to utilize in the Aloware Talk Dialer following the end of a call.
For more information on this feature, refer to our detailed documentation: HubSpot call and meeting types in Aloware.
Call and meeting types in HubSpot
HubSpot activity types pulled to Aloware
Pull deals - retrieves HubSpot deals into Aloware, including basic deal information (amount, pipeline and stage). This allows you to manage your contacts in Aloware based on the deal owners identified in the IVR system.
Deals Information in the integration card
IVR Settings > Route to HubSpot Deal Owner