The Salesforce admin Contact/ Lead property mapping tab (tabs 3 and 4) is designed to manage contact and lead properties, including lead statuses and ownership mappings. This feature enables you to map Salesforce contact properties to Aloware's default and custom contact fields. Aloware can read from, write to, or synchronize with Salesforce contact properties.
You can configure data pulling and field mapping for both Leads and Contacts, with customizable priorities and behavior settings. This involves mapping Salesforce Lead/Contact fields to your Aloware system fields (e.g., city to mailing City).
Lead property mapping
Contact property mapping
Important notes
Some fields are specific to Leads (e.g., Company), while others are specific to Contacts (e.g., Mailing Address). Always save your changes to activate the field mappings. Warning messages will appear if any required mappings are missing or unsaved, guiding you to correct them.
You can specify which Salesforce properties Aloware can read from or write to, and similarly, which Aloware properties Salesforce can read from or write to.
A common practice suggests Salesforce as the primary data source, with Aloware primarily reading information from it.
Disconnecting and reconnecting the Salesforce integration will reset default settings for contact owner mapping.
Legends for mapping icons
A locked 🔒 icon signifies that the mapping is disabled for modifications.
A prohibited 🚫 icon means the property is already selected and cannot be mapped multiple times.
A wastebasket 🗑️ icon allows you to delete a contact/lead property mapping.
Types of attributes
Default locked fields - these fields are fixed and cannot be removed or modified (e.g., phone Number and email).
Default open fields - these fields can be removed or modified (e.g., First Name).
Special fields
Contact ownership mapping - the contact owner field in Aloware is mandatory and fixed. It can be mapped to any property of your choice in Salesforce, with the existing Salesforce Owner ID being the most common mapping.
Synchronization is available in multiple directions: bi-directional, one-way (Aloware to Salesforce →), and one-way (Salesforce to Aloware ←). This contact property mapping cannot be deleted.
The contact owner field's behavior in the contact property mapping tab respects the contact/lead update direction set in the sync tab:
If contact/lead update in the sync tab is 'inbound-only (←)', changes to contact owner in Aloware will not push to Salesforce, even if the Property Mapping is set to Bi-directional.
Updates will only push to Salesforce when both contact/lead update in the sync tab and the property mapping are set to bi-directional (↔).
Users can configure property mapping settings to toggle between sync methodologies (outbound 'right, →', inbound 'left, ←', or bi-directional 'both, ↔'), providing flexibility based on operational preferences.
Here are examples of contact owner mapping directions:
Contact owner ↔ Owner ID - ownership changes from Aloware are sent to Salesforce and vice versa.
Contact owner → Owner ID - only ownership changes originating in Aloware are sent to Salesforce. No ownership changes occur from Salesforce to Aloware, even when the “Sync with Salesforce“ button is used in the JIT card.
Contact owner ← Owner ID - only ownership changes from Salesforce are sent to Aloware. No ownership changes are sent from Aloware to Salesforce.
Contact owner ↔ in Salesforce - ownership changes from Aloware map to the selected custom field in Salesforce. When updating a custom mapped property in Salesforce, you must click the “Sync with Salesforce“ button in the JIT card for the owner update to reflect in Aloware.
If the Salesforce integration is disabled and then re-enabled, the Contact owner mapping will default to appear below the Email mapping, with 'Contact Owner ← (inbound) Owner ID' (default in Salesforce).
Sync direction control
Users can control which fields are synchronized and in which direction:
← - Salesforce to Aloware
→ - Aloware to Salesforce
↔ - Bi-directional
Some properties have fixed directions once added, as they are part of established best practices for updates between Salesforce and Aloware. For example, Phone Number is typically set to 'Both'.
Number formatting
When 'Contact Update' (in the Sync tab) is set to 'Inbound-only (←)', Salesforce will not update the phone number format to international when other Aloware contact properties (like First Name, Last Name, Timezone, etc.) change.
Only when 'Contact/Lead Update' is set to 'Bi-directional (↔)' will Salesforce update the phone number format when any Aloware contact/lead property is modified.
For detailed documentation of each field, refer to the Salesforce Default/Custom Fields documentation.