Skip to main content

Salesforce-Aloware integration: Lead and Contacts simultaneous sync

Laarni D avatar
Written by Laarni D
Updated this week

Two-way sync for contacts and leads

This feature enables data to be synchronized from Salesforce to Aloware, and from Aloware to Salesforce, for both Contact and Lead records. When updates or new records are created in Salesforce, they are reflected in Aloware, and vice versa. This reduces manual data entry and minimizes discrepancies. Personal Identifiable Information (PII) such as first name, last name, email, and phone numbers are synchronized. The phone number serves as a unique identifier for records in Aloware.

Sync with Contacts and Leads at same time (with prioritization for contacts in this example)

Sync only with leads

Sync only with contacts


Synchronization timing

Updates synchronize records in near real-time. For instance, if a contact is created in Salesforce, it will sync to Aloware shortly after the Aloware user interface loads and the integration is active. The same applies to updates for existing contacts.


Data integrity and unique identifiers

The system uses the phone number as a unique identifier in Aloware to prevent data redundancy, ensuring that there are no duplicate phone numbers or emails between Salesforce and Aloware.


Configuration for admins

Initial setup and configuration

Before you begin, ensure your Salesforce package is updated. To connect Salesforce and Aloware, follow this guide.

Enable sync modules

Enable the toggles of lead and contact.

Set sync priority

Define which object (lead or contact) has precedence when both exist with the same identifier in Salesforce. This addresses scenarios where Leads and Contacts might share the same phone number in Salesforce.

Configuring sync direction

Set the direction for record creation and updates as Bi-directional (↔) or Inbound (←, from Salesforce to Aloware).

Mapping fields

Access the "Contact Property Mapping" or "Lead Property Mapping" tabs to align Salesforce fields with Aloware fields. This ensures accurate data transfer. Visually indicated fields are either disabled or already mapped. For full details on field mapping, check our lead property mapping guide, and contact property mapping guide.

Lead property mapping tab

Contact property mapping tab

One-time sync operations

Within the "One-time operations: Contacts / Leads" section, admins can initiate a manual pull of records directly from Salesforce. This function is designed for specific instances where an immediate, on-demand data refresh is required, rather than for continuous or scheduled synchronization.


How synchronization behaves

With the setup complete, let's understand how data moves between Salesforce and Aloware.

Two-way data Flow

This feature allows for the automatic exchange of data. Updates or new records created in Salesforce are reflected in Aloware, and changes made in Aloware are pushed back to Salesforce (if bi-directional sync is configured). This minimizes manual data entry and reduces inconsistencies.

Unique identifier

The phone number is the primary unique identifier used by Aloware to match and manage records. This helps prevent duplicate entries.

Prioritization for conflicts

If both a Lead and a Contact in Salesforce share the same phone number, the system will respect the priority you set during configuration (either Lead or Contact takes precedence) to ensure a single, consistent record in Aloware.

Near real-time updates

Data updates synchronize quickly. For example, if a contact is created in Salesforce, it will appear in Aloware shortly after the Aloware user interface loads and the integration is active.
​


Daily use for team members

Once the synchronization is configured by an administrator, regular users will experience a consistent data environment.

What You Can Do:

  • Access unified records - view contact and lead records in Aloware that are automatically populated from Salesforce.

  • Update records - if bi-directional sync is enabled, any changes you make to contact details in Aloware will be reflected back in Salesforce.

  • Track communications - when you make calls or send messages through Aloware, these activities (Call Detail Records and Message Detail Records) are automatically logged as tasks in the corresponding Salesforce Lead or Contact record. Call recording links are also included.

    Contact sync:

    Lead sync:

  • Direct Salesforce access - you can typically find direct links from Aloware contact pages to the corresponding Salesforce Lead or Contact record for quick access.


Testing the synchronization

To verify the synchronization is working as expected, you can perform these actions:

  1. Create a new contact in Aloware - after creation, check Salesforce to see if the contact appears as a Lead or Contact, respecting your configured priority.

  2. Initiate communication - make a call or send a message from Aloware. Then, confirm that the communication log appears as a task on the corresponding Salesforce record.

  3. Update contact information - change a contact's name, email, or other details in Aloware. Verify that these updates are reflected in Salesforce (if bi-directional sync is enabled).

  4. Observe conflict resolution - (For admins or during testing) Create both a Lead and a Contact in Salesforce with the same phone number. Observe which entity appears in Aloware based on your set priority.

  5. Test lead conversion - convert a Lead to a Contact in Salesforce. Validate that the synchronization behaves correctly and that communication history remains associated.


How this connects with other Aloware features

The Salesforce integration is foundational and connects with Aloware's core communication capabilities:

  1. Calling and messaging - use Aloware to make calls and send SMS/MMS to your synchronized contacts and leads.

  2. Comprehensive tracking - all call and message activities, along with notes, are tracked within Aloware and simultaneously synchronized as tasks in Salesforce, providing a complete communication history in both systems.

Did this answer your question?