What does the HubSpot call outcome and call type sync do?
The HubSpot call outcome sync and HubSpot call type sync ensure that call results selected in Aloware are aligned with the call properties configured in HubSpot.
When the HubSpot integration is enabled in Aloware:
HubSpot call outcomes are pulled into Aloware as call dispositions.
HubSpot activity/meeting types are pulled into Aloware as HubSpot call type.
Agents select both fields during call wrap-up.
Selected values are synced to HubSpot immediately after the call is completed.
Admins can enable force HubSpot call type disposition to require call type selection before allowing call completion.
This ensures that HubSpot activity logs always contain structured, accurate call data.
Important note: Mobile app limitation
HubSpot call type selection is not currently supported in the Aloware Mobile App.
If force HubSpot call type disposition is enabled:
Agents are required to select a HubSpot call type before finishing a call.
The HubSpot call type dropdown does not appear in the mobile app.
Mobile users may be unable to complete wrap-up.
Recommendation:
Enable force HubSpot call type disposition only if your team primarily uses:
Aloware Talk (desktop)
HubSpot widget (Talk2)
Power dialer
How HubSpot call outcome and HubSpot call type work inside Aloware
When a call ends in Aloware whether it was a manual call or part of a power dialer session the system opens the wrap-up panel. This is where the agent logs the result of the conversation before completing the call.
In this wrap-up view, agents will see two separate fields. Although both come from HubSpot, they serve different purposes.
Call disposition (mirrors HubSpot call outcome)
The call disposition field captures the result of the call itself. This dropdown reflects the call outcomes configured in HubSpot. Examples include:
Busy
Connected
Left voicemail
No answer
Wrong number
Any custom outcomes created in HubSpot
These options are imported into Aloware when an admin runs pull call outcomes in the HubSpot integration settings.
When an agent selects a call disposition:
The result is saved to the call record in Aloware.
The same outcome is written to the HubSpot activity record.
HubSpot reporting uses this value for outcome-based tracking.
This ensures the call result selected in Aloware matches exactly what appears in HubSpot.
HubSpot call type (mirrors HubSpot activity/ Meeting type)
The HubSpot call type field is used to categorize the purpose of a call, rather than its outcome. It allows agents and teams to specify why the call was made, helping both Aloware and HubSpot track and report on call activity accurately.
The dropdown displays Activity or Meeting types configured in HubSpot, including:
Default HubSpot types
Custom types such as sales, customer support, onboarding, or follow-up
These values are imported into Aloware when an admin runs Pull Activity Types, so agents always have the latest options during call wrap-up.
When an agent selects a HubSpot call type:
The selection defines the purpose of the call.
It is saved in the Aloware call record.
The same value is synced to the corresponding activity in HubSpot.
HubSpot can group and filter calls by type, helping teams track call volume and performance by department or function.
Linking call type in Aloware with HubSpot ensures every call is consistently categorized across both systems, providing accurate and reliable reporting.
Prerequisites
Before configuring HubSpot call type enforcement in Aloware, make sure the necessary HubSpot fields are properly set up.
Create custom call outcomes in HubSpot
Navigate to HubSpot → Call settings.
Add any custom outcome labels your team requires (e.g., “No Answer,” “Left Voicemail”).
Save changes.
These outcomes will appear in Aloware after running pull call outcomes. For more details, see create custom call outcomes in HubSpot.
Create call and meeting types in HubSpot
Navigate to HubSpot → Activity/Meeting type settings.
Create or edit call and meeting types (e.g., sales, customer support, onboarding, follow-up).
Save and publish.
These types will appear in Aloware after running pull activity types.
Step-by-step configuration (Admin setup)
Step 1: Enable HubSpot integration
Go to Aloware → Integrations → HubSpot.
Confirm integration is enabled.
If disabled, HubSpot-related dropdowns will appear greyed out and sync operations will not function.
Step 2: Sync HubSpot outcomes and call types
To make HubSpot call outcomes and activity/meeting types available in Aloware, you need to import them through the integration settings:
Go to HubSpot Integration Settings → Sync tab → One-time Operations.
Click Pull Call Outcomes to import all HubSpot call outcomes.
Click Pull Activity Types to import all HubSpot call and meeting types.
After the initial import, Aloware automatically updates these values hourly, ensuring agents always see the latest options during call wrap-up.
Step 3 (optional): Enforce HubSpot call type selection
Go to Account → Calling settings.
Locate force HubSpot call type disposition and toggle ON.
Key details:
Default is OFF; the setting must be turned on manually.
Only admins can enable or disable this requirement.
Agents cannot bypass it, calls cannot be completed without selecting a HubSpot call type.
Enforcement follows the same logic as Force call disposition, maintaining consistency with existing wrap-up rules.
How agents use HubSpot call outcome and call type
Agents use HubSpot Call Outcome and Call Type consistently across all call types, including manual inbound/outbound calls, Power Dialer sessions, and calls made through the HubSpot widget.
Step-by-step workflow:
Complete the call
When the call ends, Aloware automatically opens the wrap-up panel.Select call disposition (Outcome)
The agent chooses the result of the call from the HubSpot-synced dropdown (e.g., connected, left voicemail, No answer).
Select HubSpot call type
The agent selects the purpose of the call from the Activity/Meeting type dropdown (e.g., sales, customer support, onboarding). If enforcement is enabled, this selection is required before completing the call.
Complete wrap-up
Once both fields are selected, the agent finishes the wrap-up process.Automatic sync to HubSpot
The call outcome and type are immediately recorded in HubSpot. Agents can see the activity reflected on the contact’s timeline, ensuring accurate categorization for reporting and analysis.
HubSpot sync
Aloware Talk sync
This workflow ensures that every call, whether manual or automated, is consistently categorized in both Aloware and HubSpot, reducing errors and maintaining reliable reporting.
Required field enforcement (if enabled)
When force HubSpot call type disposition is turned ON, agents must select a HubSpot call type before completing a call. This ensures every call is fully categorized, preventing incomplete data and improving reporting accuracy in both Aloware and HubSpot.
Using enforcement in Aloware Talk (desktop dialer)
After the call ends, the wrap-up panel automatically opens.
The agent must select a HubSpot call type from the dropdown.
Until a selection is made, the Finish button remains disabled.
Once a call type is selected, the agent can complete the wrap-up normally.
This prevents calls from being logged without proper categorization and ensures accurate activity data.
Using enforcement in power dialer sessions
After each call, the wrap-up screen requires HubSpot call type selection.
The dialer cannot move to the next contact, and the session cannot resume until the required field is completed.
Once the agent selects a call type, the workflow continues to the next call.
This guarantees every call in a campaign is properly logged before the session progresses.
Verifying sync in HubSpot
After wrap-up is completed:
The call outcome appears in the HubSpot activity timeline.
The HubSpot call type is categorized correctly.
All data matches the selections made in Aloware.
Sync occurs immediately upon wrap-up completion.
Agents do not need to perform additional steps; Aloware handles the real-time update automatically.
How this relates to other Aloware tools
HubSpot call logging
This feature builds on Aloware’s existing Pull Call Outcomes functionality. Once a call is completed, the outcome and type are synced in real time to HubSpot, ensuring activity logs are always accurate and up-to-date.
Power dialer
Required-field enforcement applies consistently across Power Dialer sessions. Agents cannot skip mandatory wrap-up fields, which ensures every call is fully categorized. This maintains structured reporting across dialing campaigns, preventing gaps in data and supporting reliable campaign analytics.
HubSpot widget (Talk2)
The integration works seamlessly within the HubSpot widget, providing the same enforcement and synchronization as the desktop dialer. If the integration is disabled, the relevant fields are automatically hidden to avoid confusion. This also prevents conflicts when multiple CRM integrations, such as Salesforce and HubSpot, are active.
Key configurations to review
Before enabling force HubSpot call type disposition, make sure the following are in place:
HubSpot integration is active.
Pull call outcomes has been run to import call outcomes.
Pull activity types has been run to import call and meeting types.
The team does not rely primarily on the mobile app, since enforced fields are not yet supported there.
Reviewing these configurations ensures enforcement works as expected and all calls are properly logged in both Aloware and HubSpot.