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).
Lead sync
Contact sync
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, a priority setting is required to manage duplicate records based on phone numbers. This ensures Aloware treats one record as primary if both a lead and a contact share the same phone number. You must select your preferred priority between Leads and Contacts, and the system will disregard duplicate records based on the chosen priority. Saving your CRM module selection is necessary to activate all syncing functionality.
One-time operations (Push and Pull)
These operations are designed for specific data synchronization needs and should primarily be used for troubleshooting or emergencies, not as regular practices. To ensure that Aloware remains in sync with Salesforce, there may be instances where a one-time data pull or push is necessary.
The system displays the latest update information for these operations, such as "Last push contact: Jul 10, 2024, 6:38 PM PDT".
Available one-time operations include:
Push contacts/leads - this function sends Aloware contacts/leads to Salesforce, updating corresponding records in Aloware based on CRM data.
Pull contacts/leads - this function retrieves Salesforce contacts/leads into Aloware, noting that this action may incur LRN lookup charges.
Pull lead statuses - this function imports Salesforce lead statuses into Aloware, mapping them as contact disposition statuses.
For more detailed information on Contact/Lead Synchronization and Creation, refer to the dedicated documentation section.
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.