Understanding contact property mapping settings
Contact property mapping in Aloware controls how contact data flows between Aloware and HubSpot, allowing you to connect any HubSpot contact property (default or custom) to corresponding Aloware fields.
This system determines what data gets synchronized, in which direction, and under what conditions the sync occurs, ensuring data consistency and automated synchronization across your platforms.
Accessing and understanding the interface
The mapping interface is in your Aloware admin panel and provides visual indicators to help you understand the status and capabilities of each field mapping: for 🔒 locked mappings, 🚫 for fields already mapped, and 🗑️ for removable mappings.
Core mapping principles
Unlike basic integrations, Aloware-HubSpot property mapping follows specific rules and behaviors that are important to understand:
Best practice: HubSpot as source of truth
For optimal data consistency, HubSpot should serve as your primary data repository. This means:
Most data flows from HubSpot into Aloware
Changes in HubSpot automatically update Aloware
Your team maintains consistent data across platforms
Reduces data conflicts and synchronization issues
Three (3) types of field mapping categories
Default locked fields - these are essential, permanent mappings that form the backbone of the integration:
Include core contact properties like email and phone
Cannot be modified or removed
Automatically sync based on preset rules
Marked with a 🔒 in the interface
Default open fields - pre-configured mappings that offer flexibility:
Can be modified or removed as needed
Include properties like Last Call Dispositions
Allow customization of sync direction
Support your specific workflow needs
Custom fields - user-defined connections between systems:
User-created mappings
Connect custom properties between systems
Maximum flexibility in configuration
Configuring your contact property mappings
After understanding the basic principles, your property mapping configuration involves several key components that maintain data consistency between Aloware and HubSpot. Each component serves a specific function in ensuring proper data flow between systems.
Default field mappings
These are often automatically established and adhere to the best practice of HubSpot serving as the primary source of data, meaning Aloware primarily reads this information. Verify these mappings are present. Modifications are typically not allowed or recommended.
Special field types
Contact disposition status
A contact disposition in Aloware (or lead status in HubSpot) shows the stage of a contact interaction, like New Lead, In Progress, or Contacted.
This field is flexible: it syncs outbound from HubSpot to Aloware (→) by default. When set to bi-directional (↔), it can also sync inbound from Aloware to HubSpot (←).
What your agents see in Aloware Talk
In Aloware Talk, your agents will only see Lead Statuses that are available and synced from your HubSpot account. These options are marked with a 🔐 icon to indicate their HubSpot origin.
If you ever disconnect and reconnect the HubSpot integration, this mapping automatically resets to HubSpot → Aloware, which is its permanent fixed direction.
Contact ownership mapping
Contact ownership mapping determines which user is assigned as the owner of a contact in both systems. This mapping requires configuration of both field selection and sync direction.
For field selection, you can map Aloware's contact owner field to either:
HubSpot's standard contact owner field
A custom text field you've created in HubSpot
The sync direction offers three (3) configurations:
Bi-directional sync: Contact owner (Aloware) ↔︎ Contact owner (HubSpot)
Changes in either system update the other automatically.
Aloware to HubSpot: Contact owner (Aloware) → Contact owner (HubSpot)
Only Aloware changes update HubSpot. HubSpot changes won't affect Aloware, even with integration card sync.
HubSpot to Aloware: Contact owner (Aloware) ← Contact owner (HubSpot)
Only HubSpot changes update Aloware. This is the default if the integration is reset.
Mapping Aloware's contact owner to a HubSpot custom field
When using a custom HubSpot field for contact owner mapping, updates require manual synchronization. Users must click the Sync with HubSpot button on the contact's integration card in Aloware to reflect HubSpot changes.
User list for contact owner selection
When setting up contact owner mapping in Aloware, the dropdown list of users available for selection will only show users who are properly synced between Aloware and HubSpot. Users not synced with the CRM will not appear in this list.
Mapping modification rules
The contact owner mapping cannot be deleted, though you can modify its field connection and sync direction. When selecting contact owners in Aloware, only users properly synced between both systems will appear as options.
Red indicates locked (non-editable), green indicates unlocked (editable)
HubSpot contact properties used in Aloware integration
These properties allow Aloware and HubSpot to synchronize contact information and communication activity. Depending on the field, synchronization may occur in both directions or only from Aloware to HubSpot.
Default locked fields (Bidirectional ↔)
These fields are core identifiers required for synchronization. Their mapping and sync direction cannot be modified.
Aloware Field | HubSpot Property | Label | Type |
Phone Number | phonenumber | Phone Number | Phone |
Special Fields (Configurable direction ↔, →, ←)
These fields are managed by HubSpot but can synchronize with Aloware depending on configuration.
Aloware Field | HubSpot Property | Label | Type |
Contact Owner | hubspot_owner_id | Contact Owner | HubSpot User |
Contact Disposition Status | lead_status | Lead Status | Radio Select |
Lifecycle Stage | lifecyclestage | Lifecycle Stage | Radio Select |
Note: Lifecycle stage is typically managed within HubSpot through imports, forms, or workflows.
Default open fields (Flexible ↔, →, ←)
These fields store standard contact details and can be customized or mapped differently if needed.
Aloware Field | HubSpot Property | Label | Type |
First Name | firstname | First Name | Single-line text |
Last Name | lastname | Last Name | Single-line text |
Company Name | company | Company Name | Single-line text |
Address | address | Street Address | Single-line text |
City | city | City | Single-line text |
State | state | State / Region | Single-line text |
Country | country | Country / Region | Single-line text |
Zipcode | zip | Postal Code | Single-line text |
Website | website | Website URL | Single-line text |
Date of Birth | date_of_birth | Date of Birth | Single-line text |
Time Zone | timezone | Time Zone | Dropdown Select |
Aloware custom fields (Configurable ↔, →, ←)
These fields are created by the Aloware integration in HubSpot and can synchronize in either direction depending on configuration.
Aloware Field | HubSpot Property | Label | Type |
Lead Source | custom | Lead Source | Custom |
Incoming Number | custom | Incoming Number | Custom |
Custom Field 1 | custom | Custom Field 1 | Custom |
Custom Field 2 | custom | Custom Field 2 | Custom |
TCPA Approved | custom | TCPA Approved | Checkbox |
Aloware Contact Link | custom | Aloware Contact Link | Multi-line text |
Aloware Contact ID | custom | Aloware Contact ID | Single-line text |
Compliance fields (Aloware → HubSpot only)
These fields are used for communication compliance and phone classification and are populated automatically by Aloware.
Aloware Field | HubSpot Property | Label | Type |
DNC | custom | Do Not Call | Checkbox |
Line Type | custom | Line Type
Possible Line Type values:
| Dropdown Select |
Messaging activity fields (Aloware → HubSpot only)
These fields track SMS activity associated with a contact.
Aloware Field | HubSpot Property | Label | Type |
Last inbound text message | custom | Last inbound text message | Multi-line text |
Last outbound text message | custom | Last outbound text message | Multi-line text |
Total inbound text messages | custom | Total inbound text messages | Number |
Total outbound text messages | custom | Total outbound text messages | Number |
Last inbound text message date | custom | Last inbound text message date | Date picker |
Last outbound text message date | custom | Last outbound text message date | Date picker |
Last inbound text message date/ time | custom | Last inbound text message date/ time | Date & time picker |
Last outbound text message datetime | custom | Last outbound text message datetime | Date & time picker |
Call activity fields (Aloware → HubSpot only)
These fields store call metrics and call outcomes.
Aloware Field | HubSpot Property | Label | Type |
Total inbound calls | custom | Total inbound calls | Number |
Total outbound calls | custom | Total outbound calls | Number |
Last inbound call date | custom | Last inbound call date | Date picker |
Last outbound call date | custom | Last outbound call date | Date picker |
Last inbound call date/ time | custom | Last inbound call date/ time | Date & time picker |
Last outbound call date/ time | custom | Last outbound call date/ time | Date & time picker |
Call and message tracking fields (Aloware → HubSpot Only)
These fields track interaction outcomes and message timestamps.
Aloware Field | HubSpot Property | Label | Type |
Last inbound call time | custom | Last inbound call time | Single-text line |
Last outbound call time | custom | Last outbound call time | Single-text line |
Last inbound message time | custom | Last inbound message time | Single-text line |
Last outbound message time | custom | Last outbound message time | Single-text line |
Last call disposition | custom | Last call disposition | Single-text line |
Last inbound call disposition | custom | Last inbound call disposition | Single-text line |
Last outbound call disposition | custom | Last outbound call disposition | Single-text line |
Engagement tracking fields (Aloware → HubSpot Only)
These fields provide a consolidated view of contact interactions across calls and messages.
Aloware Field | HubSpot Property | Label | Type |
Last inbound engagement | custom | Last inbound engagement | Date & time picker |
Last outbound engagement | custom | Last outbound engagement | Date & time picker |
Last inbound and outbound engagement | custom | Last inbound and outbound engagement | Date & time picker |
First activity tracking fields (Aloware → HubSpot Only)
These fields capture the first recorded interaction with the contact.
Aloware Field | HubSpot Property | Label | Type |
First inbound call date & time | custom | First inbound call | Date & time picker |
First outbound call date& time | custom | First outbound call | Date & time picker |
First inbound text message date/ time | custom | First inbound SMS | Date & time picker |
First outbound text message date/ time | custom | First outbound SMS | Date & time picker |
First inbound engagement date/ time | custom | First inbound engagement | Date & time picker |
First outbound engagement date/ time | custom | First outbound engagement | Date & time picker |
Synchronizing call disposition options from HubSpot
To ensure consistency in call logging, Aloware dynamically displays the list of call dispositions (e.g., "Left voicemail," "Connected," "No Answer") that are defined and managed within your HubSpot account.
What agents see in Aloware Talk
When logging a call, the disposition options available for selection by agents in Aloware are directly sourced from HubSpot. These options are often marked with a 🔐 (lock icon) to indicate they are synced from HubSpot, ensuring standardized terminology across platforms.
