The Salesforce contact property mapping feature allows Aloware to connect specific contact fields with their corresponding fields in Salesforce. These fields define what contact information is shared between the two systems.
Default fields represent common customer details, ownership information, and communication activity records. When these fields are mapped, contact data can remain consistent between Aloware and Salesforce depending on the configured sync direction.
Understanding these fields helps admins maintain accurate contact records and ensure that important information such as contact details, ownership, and engagement history is available in both platforms.
Types of contact fields
Contact properties available for mapping are grouped into several categories based on how they behave in the integration.
Default locked fields are standard identifiers used by both systems. These fields cannot be removed or modified because they are required for identifying contacts like a phone number and an email.
These fields are synchronized bidirectionally (↔), meaning updates in either system can reflect in the other.
Default open fields store standard contact information. Unlike locked fields, these properties can be customized or removed depending on business needs.
Default fields on contacts
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 | Contact Owner | Lookup(User) |
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) |
Lead Source | LeadSource | Lead Source | Picklist |
City | MailingCity | Mailing City | Address |
State | MailingState | Mailing State / Province | Address |
Country | MailingCountry | Mailing Country | Address |
Zipcode | MailingPostalCode | Mailing Zip / Postal Code | Address |
Date of Birth | Birthdate | Birthdate | Date |
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 |
Aloware Contact Link | Custom in Salesforce | Aloware Contact Link | URL(255) |
Aloware Contact ID | Custom in Salesforce | Aloware Contact ID | Text(40) |
Default open fields (Additional fields) (Bidirectional ↔ / Configurable sync → / ←)
Field Name (Aloware) | Field Name (Salesforce) | Field Label (Salesforce) | Field Type (Salesforce) |
Home Phone | HomePhone | Home Phone | Phone |
Mobile Phone | MobilePhone | Mobile | Phone |
Fax | Fax | Fax | Fax |
Other Phone | OtherPhone | Other Phone | Phone |
Default open fields - Outbound tracking fields (Aloware → Salesforce only)
Field Name (Aloware) | Field Name (Salesforce) | Field Label (Salesforce) | Field Type (Salesforce) |
DNC | Custom in Salesforce | DNC | Checkbox |
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 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) |
Mapping time fields - Outbound tracking fields (Aloware → Salesforce only)
For time fields, always use Text(40) instead of Salesforce's native time field. Salesforce converts times to UTC automatically, which can make local times confusing. Using Text(40) keeps the time exactly as it happened, including the correct time zone.
Example:
Text(40):
08:33:16-07:00- shows local time correctlyTime:
(08:33:16 + 07:00 = 15:33:16.000Z)- converted to UTC, may not match your local time
This ensures agents see accurate times for calls, messages, and engagement history.
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 directions
Each field can be configured with a synchronization direction that determines how data moves between systems.
Aloware ↔ Salesforce - syncs both directions between Aloware and Salesforce
Aloware → Salesforce - can be configured to sync from Aloware to Salesforce.
Aloware ← Salesforce - can be configured to sync from Salesforce to Aloware.
Field legends
🔒 Locked – indicates a default locked field that cannot be changed.
🚫 Prohibited – indicates a field already mapped and unavailable for multiple mappings.
🗑️ Delete – allows the removal of an existing 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.