The Salesforce lead property mapping feature in Aloware helps you keep your lead information accurate and consistent across both platforms. By synchronizing details like phone numbers, email addresses, lead sources, and ownership, your team can rely on up-to-date records without manual updates.
Step 1: Set up integration
Follow the integration guide to connect Salesforce with Aloware.
Select Leads as the object module for synchronization.
Ensure that email addresses match between both platforms for successful updates.
Note - you can only sync one object module at a time, either Leads or Contacts. To sync contacts, refer to the contact mapping guide.
Step 2: Configure field mapping
Identify the fields you want to sync, such as phone number, email, and lead source.
Customize default open fields according to your organization’s needs.
Step 3: Synchronize leads
Click the sync leads button to initiate synchronization.
Step 4: Verify data
Review synchronization logs and validate updates.
Check that fields like lead owner and lead source are correctly mapped.
Understanding field types
Lead fields are grouped by attribute type, which determines how they behave in the integration.
Default locked fields are core identifiers such as phone number and email. These fields are fixed and cannot be modified because they are required to identify leads.
Default open fields store standard lead information such as lead source and zipcode. These fields are flexible and can be customized, added, or removed depending on business needs.
Default field on leads
Default locked fields (Bidirectional ↔)
Field Name (Aloware) | Field Name (Salesforce) | Field Label (Salesforce) | Field Type (Salesforce) |
Phone Number | Phone | Phone | Phone |
Special fields (Bidirectional ↔ / Configurable sync → / ←)
Field Name (Aloware) | Field Name (Salesforce) | Field Label (Salesforce) | Field Type (Salesforce) |
Contact Owner | OwnerId | Lead Owner | Lookup(User) |
Note: Even for Leads, the Aloware property name remains Contact Owner.
Default open fields (Bidirectional ↔ / Configurable sync → / ←)
Field Name (Aloware) | Field Name (Salesforce) | Field Label (Salesforce) | Field Type (Salesforce) |
First Name | FirstName | First Name | Text(40) |
Last Name | LastName | Last Name | Text(80) |
Company | Company | Company | Text(255) |
Lead Source | LeadSource | Lead Source | Picklist |
City | City | Address | Address |
State | State | Address | Address |
Country | Country | Address | Address |
Zipcode | PostalCode | Address | Address |
Website | Website | Website | URL(255) |
Incoming Number | Custom in Salesforce | Incoming Number | Custom |
Custom Field 1 | Custom in Salesforce | Custom Field 1 | Custom |
Custom Field 2 | Custom in Salesforce | Custom Field 2 | Custom |
TCPA Approved | Custom in Salesforce | TCPA Approved | Custom |
DNC | Custom | DNC | Checkbox |
Aloware Lead Link | Custom in Salesforce | Aloware Lead Link | URL(255) |
Aloware Contact ID | Custom in Salesforce | Aloware Lead ID | Text(40) |
Default open fields (Additional fields) (Bidirectional ↔ / Configurable sync → / ←)
Field Name (Aloware) | Field Name (Salesforce) | Field Label (Salesforce) | Field Type (Salesforce) |
Mobile Phone | MobilePhone | Mobile | Phone |
Fax | Fax | Fax | Fax |
Default open fields – Outbound tracking fields (Aloware → Salesforce only)
Field Name (Aloware) | Field Name (Salesforce) | Field Label (Salesforce) | Field Type (Salesforce) |
Last inbound text message date | Custom in Salesforce | Last inbound text message date | Date |
Last outbound text message date | Custom in Salesforce | Last outbound text message date | Date |
Last inbound text message | Custom in Salesforce | Last inbound text message | Long Text Area |
Last outbound text message | Custom in Salesforce | Last outbound text message | Long Text Area |
Total inbound text messages | Custom in Salesforce | Total inbound text messages | Number |
Total outbound text messages | Custom in Salesforce | Total outbound text messages | Number |
Last inbound call date | Custom in Salesforce | Last inbound call date | Date |
Last outbound call date | Custom in Salesforce | Last outbound call date | Date |
Total inbound calls | Custom in Salesforce | Total inbound calls | Number |
Total outbound calls | Custom in Salesforce | Total outbound calls | Number |
Last inbound call time | Custom in Salesforce | Last inbound call time | Text(40) or Time |
Last outbound call time | Custom in Salesforce | Last outbound call time | Text(40) or Time |
Last inbound message time | Custom in Salesforce | Last inbound message time | Text(40) or Time |
Last outbound message time | Custom in Salesforce | Last outbound message time | Text(40) or Time |
Last call disposition | Custom in Salesforce | Last call disposition | Text(40) |
Last inbound call disposition | Custom in Salesforce | Last inbound call disposition | Text(40) |
Last outbound call disposition | Custom in Salesforce | Last outbound call disposition | Text(40) |
Last inbound and outbound engagement | Custom in Salesforce | Last inbound and outbound engagement | Date/Time |
Last inbound engagement | Custom in Salesforce | Last inbound engagement | Date/Time |
Last outbound engagement | Custom in Salesforce | Last outbound engagement | Date/Time |
Mapping time fields – Outbound tracking fields (Aloware → Salesforce only)
When creating lead time fields in Salesforce, it is recommended to use Text(40) instead of the native Time field type.
Salesforce automatically converts time values to UTC, which can change how the time appears when viewed in different time zones. Using Text(40) preserves the original time format exactly as it was recorded, including its time zone information.
Example:
Field Type | Value Stored | Result |
Text(40) | 08:33:16-07:00 | Displays the recorded local time with its time zone |
Time | 08:33:16 +07:00 | Converted to 15:33:16.000Z (UTC) |
Using text fields helps keep call and message timestamps consistent with the time they actually occurred.
Field Name (Aloware) | Field Name (Salesforce) | Field Label (Salesforce) | Field Type (Salesforce) |
Last inbound call time | Custom in Salesforce | Last inbound call time | Text(40) / Time |
Last outbound call time | Custom in Salesforce | Last outbound call time | Text(40) / Time |
Last inbound message time | Custom in Salesforce | Last inbound message time | Text(40) / Time |
Last outbound message time | Custom in Salesforce | Last outbound message time | Text(40) / Time |
Synchronization fields
Field mappings also define how data moves between Aloware and Salesforce. The selected synchronization direction controls which system can update the field.
Aloware ↔ Salesforce - data updates can sync in both directions between the two systems.
Aloware → Salesforce - updates are sent from Aloware to Salesforce only.
Aloware ← Salesforce - updates are sent from Salesforce to Aloware only.
Field legends
The mapping interface uses icons to show the status of each field.
🔒 Locked - Indicates a default field that cannot be modified.
🚫 Prohibited - Indicates the field is already mapped and cannot be mapped again.
🗑️ Delete - Removes an existing field mapping.
How agents benefit from contact mapping
With Aloware and Salesforce synced, agents always see the most up-to-date contact information. Ownership changes, phone numbers, emails, and other mapped fields are automatically updated across both platforms, eliminating manual work.
This ensures agents work with accurate, consistent contact records, letting them focus on customer interactions instead of correcting data errors. Updates in one system immediately reflect in the other, providing a clear view of ownership and engagement history at all times.
How this integration works with other tools
This integration works seamlessly with Aloware’s broader CRM ecosystem, including CRMs like HubSpot and Pipedrive. By keeping contact data synchronized across systems, agents can manage customer interactions more efficiently, without worrying about discrepancies or missing information.
For more guidance on tracking communications, agents can refer to our SMS/MMS logging and call logging guides, which complement this integration by ensuring engagement history is complete and accurate.
Key configurations
To make the integration work effectively, a few important settings should be confirmed:
Mapping fields - make sure the Aloware contact owner field is correctly mapped to Salesforce’s OwnerId (Contact Owner or Lead Owner).
Synchronization direction - decide whether updates should flow both ways or in a specific direction, based on your workflow.
Integration setup - verify API configuration and permissions in both Aloware and Salesforce to ensure smooth data flow.
These configurations help agents maintain accurate contact records and ensure engagement history is consistently tracked across platforms.