When Salesforce is connected to Aloware, account properties are mapped between the two systems. This mapping determines how account data such as ownership, address, and activity details are stored and synchronized.
Each field belongs to a category that defines whether it is required, editable, or system-controlled, and how it syncs between Aloware and Salesforce.
This article explains field categories, sync behavior, default and configurable fields, and how these mappings support daily operations and reporting.
Field categories
Fields are categorized based on behavior and restrictions:
Locked (🔒) fields cannot be edited or removed
Prohibited (🚫) fields have restricted configuration and fixed sync direction
Deletable (🗑️) fields can be edited or removed based on business needs
Sync direction
Each field has a defined sync direction that determines how updates move between Aloware and Salesforce:
Bidirectional ↔ - updates sync between Aloware and Salesforce
Aloware → Salesforce (→) - updates are sent from Aloware to Salesforce only
Aloware ← Salesforce - updates are sent from Salesforce to Aloware only
Default fields on accounts
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 | Account Owner | Lookup(User) |
Default open fields (Bidirectional ↔ / Configurable sync → / ←)
Field Name (Aloware) | Field Name (Salesforce) | Field Label (Salesforce) | Field Type (Salesforce) |
First Name | Name | Account Name | Text |
Lead Source | AccountSource | Account Source | Picklist |
City | Billing City | Billing Address | Address |
State | Billing State/Province | Billing Address | Address |
Country | Billing Country | Billing Address | Address |
Zipcode | Billing Zip/Postal Code | Billing 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 |
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) |
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) |
DNC | Custom in Salesforce | DNC | Checkbox |
Line Type | Custom in Salesforce | Line Type | Picklist |
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) |
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 |
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: 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 |
Additional activity tracking fields (Aloware → Salesforce only)
Field Name (Aloware) | Field Name (Salesforce) | Field Label (Salesforce) | Field Type (Salesforce) |
First inbound call date/time | Custom in Salesforce | First inbound call datetime | Date/Time |
First outbound call date/time | Custom in Salesforce | First outbound call datetime | Date/Time |
First inbound text message date/time | Custom in Salesforce | First inbound text message datetime | Date/Time |
First outbound text message date/time | Custom in Salesforce | First outbound text message datetime | Date/Time |
First inbound engagement date/time | Custom in Salesforce | First inbound engagement datetime | Date/Time |
First outbound engagement date/time | Custom in Salesforce | First outbound engagement datetime | Date/Time |
Last inbound text message date/time | Custom in Salesforce | Last inbound text message datetime | Date/Time |
Last outbound text message date/time | Custom in Salesforce | Last outbound text message datetime | Date/Time |
Last inbound call date/time | Custom in Salesforce | Last inbound call datetime | Date/Time |
Last outbound call date/time | Custom in Salesforce | Last outbound call datetime | Date/Time |
How this supports account data
Mapped account properties ensure that account records remain consistent and complete. Ownership, contact details, and activity data are reflected in both systems, which supports accurate reporting and reduces manual updates.
Configuration approach
Admins configure account mapping by selecting the fields to include and defining how each field syncs. Standard fields are typically kept as is, while custom fields can be added to support specific workflows.
After mapping is set, testing confirms that updates are reflected correctly in both systems.