The Salesforce admin sync tab facilitates data synchronization between Aloware and Salesforce for contacts and leads. These settings ensure a consistent data flow and operational efficiency.
Lead sync, contact sync, and combined sync
The integration supports distinct synchronization options: configuring data flow specifically for leads (lead sync), for contacts (contacts sync), or for both simultaneously (contacts + lead sync).
Aloware and Salesforce Lead sync
Aloware and Salesforce Contact sync
Aloware and Salesforce lead and contact sync
Data sync direction
This setting determines how data updates and creations are handled between Aloware and Salesforce. Aloware serves as the default data receiver. By default, both Salesforce and Aloware can update contact and lead information, though it is recommended that Aloware not create new contacts or leads in Salesforce.
For contact/lead creation, two directions are available:
Bi-directional sync (↔) - contacts created in Aloware are pushed to Salesforce, and contacts/leads created in Salesforce are also created in Aloware.
Inbound sync (←) - contacts created in Aloware are not sent to Salesforce; only Salesforce-created contacts/leads are created in Aloware.
Similarly, for contacts/lead update operations:
Bi-directional sync (↔) - contact updates from Aloware are reflected in Salesforce, and updates from Salesforce contacts/leads are reflected in Aloware.
Inbound sync (←) - contact updates in Aloware will not be sent to Salesforce, but Salesforce contacts/leads updates will be reflected in Aloware.
Admins can specify the data sync direction based on preferences: 'inbound' (←) indicates data flow from Salesforce to Aloware, while 'both' (↔) signifies bidirectional data flow.
Sync leads and contacts with phone number prioritization
When both leads and contacts are enabled for synchronization, you must set a priority to manage duplicate records with the same phone number. Aloware will treat the selected record type as primary and ignore the duplicate.
This preference also applies when:
Importing lists from Salesforce into Aloware (via Import List or Broadcast)
Using the Push button, which will only create records in Salesforce as either Contacts or Leads, based on your chosen priority
Example: If you set Leads as the priority and a phone number exists as both a Lead and a Contact, only the Lead will sync or be created.
One-time operations
Aloware supports synchronization of contact data and properties with integrated platforms like Salesforce, HubSpot, and HighLevel. Synchronization can be configured as one-way or two-way, depending on your mapping settings.
There are two main ways data updates occur:
Automatic sync - this runs in the background when related events happen (such as sending an SMS), and manual push/pull, which is triggered by the user through the One-time operations: Contacts/Leads section.
Manual sync - this forces records to update immediately, bypassing the usual schedule, and should only be used in emergency situations such as testing, fixing discrepancies, or showing real-time updates.
Available one-time operations include:
Push/Pull contacts/leads – This function either pushes Aloware contacts and leads into Salesforce (if bi-directional sync is enabled) or pulls Salesforce contacts and leads into Aloware. Pulling records may generate LRN lookup charges.
Pull lead statuses – This function imports Salesforce lead statuses into Aloware and maps them as contact disposition statuses.
For routine operations, it is best to rely on automatic synchronization to keep systems aligned.
Sync users button
The sync users button manages the connection between Aloware users and Salesforce owners via email. It pulls in unsynchronized Salesforce owners, resolves mapping issues, and connects users without creating new Aloware accounts.
During this process, the system automatically cleans up outdated mappings. A User Mapping will be removed if the Aloware user is deleted, inactive/suspended, an extension/destination, or if the Salesforce Owner does not exist, is deactivated, or does not match the Aloware user.
Save changes
It is crucial to explicitly save any mandatory settings. Unsaved changes may affect other configuration aspects of the integration, such as Contact Property Mapping.