Skip to main content

Aloware-HubSpot property mapping: Call dispositions

Sync HubSpot call disposition options to Aloware and map outbound call dispositions (Aloware → HubSpot) for consistent call logging.

Written by Laarni D

To maintain consistent call logging across both platforms, Aloware displays the call disposition options that are defined in your HubSpot account.

This ensures agents use the same standardized call outcomes, such as Left voicemail, Connected, or No Answer, when logging calls.


What agents see in Aloware

When agents log a call in Aloware Talk, the available call disposition options are pulled directly from HubSpot.

These options are marked with a 🔐 icon to indicate that they originate from HubSpot and cannot be edited in Aloware. This helps maintain consistent terminology and reporting across both platforms.


Import call disposition options from HubSpot

Before importing call disposition options, ensure your HubSpot integration is already connected.

  1. In Aloware, navigate to Integrations menu> Integrations > HubSpot.

  2. Open the Sync tab.

  3. Click Pull Call Outcomes to import the call disposition options from HubSpot.

  4. Click Save to apply the changes.

Once saved, the imported HubSpot call disposition options become available in Aloware Talk for your agents to use.


Map the call disposition property

If you want the call disposition selected by an agent in Aloware to be stored in a HubSpot contact property, configure a contact property mapping. This mapping supports outbound synchronization only (Aloware → HubSpot).

  1. Log in to Aloware admin.

  2. Navigate to Integration > HubSpot Settings > Contact Property Mapping > Default Fields.

  3. Click + Add Mapping.

  4. Select Last Outbound Call Disposition as the Aloware field.

  5. Map it to the appropriate HubSpot property.

  6. Click Save.

Note: Mapping the contact property is separate from importing the available call disposition options.

Importing the options controls what agents can select in Aloware, while property mapping determines where the selected value is stored during synchronization.

For more information about contact property mappings, see the Contact Property Mapping guide.

Did this answer your question?