The HubSpot Deals Integration connects Aloware with HubSpot deals so that calls and SMS made through Aloware are logged on every deal associated with the contact or company involved.
Agents can also open the Aloware Messenger and Dialer directly from inside a HubSpot Deal record, which keeps conversations and Deal context in the same place.
This article walks through what the integration does, how to connect it, how IVR routing resolves the right owner, how SMS and call logging behaves across Deals, and how agents send messages from inside a Deal.
What the HubSpot deals integration does
The integration covers four behaviors that together give a complete picture of communication tied to a Deal.
First, it pulls HubSpot Deals into Aloware.
When a contact is opened in Aloware Talk, the Integration Card shows every Deal associated with that contact, including Deal Name, Amount, Pipeline, and Stage.
Second, it routes inbound calls through IVR to the right owner.
Aloware looks up the most recently updated Deal linked to the caller's contact, identifies the Deal Owner, and routes the call to that agent. If no valid Deal Owner is found, the call falls back to the Contact Owner.
Third, it logs SMS and calls on every related Deal automatically.
When a message or call is sent or received, Aloware creates an activity entry on all Deals associated with the contact or company tied to that phone number.
Fourth, it surfaces the Aloware Messenger and Dialer inside the HubSpot Deal view.
Agents working a Deal can send SMS or start a call without leaving HubSpot. When a Deal has multiple contacts, a picker shows which ones are eligible to receive messages through Aloware.
Prerequisites for SMS logging to reach deals
A few conditions need to be in place for SMS logging to actually land on a Deal:
Active HubSpot integration - HubSpot must be connected and authorized in Aloware before any Deal-level feature is available.
Deal sync enabled - the pull deals sync must have been run so that Deal information is available for the integration card and for Deal Owner lookups.
Phone number match - the phone number used in the conversation must resolve to at least one HubSpot Contact or Company that is associated with one or more Deals.
Setting up the HubSpot deals integration
Connecting HubSpot and enabling Deal sync populates the Integration Card in Aloware with Deal information for each contact. Once enabled, agents can see Deal Name, Amount, Pipeline, and Stage inside Aloware Talk without opening HubSpot.
Steps to connect HubSpot and pull Deals
Log in to your Aloware Admin account.
Navigate to Integrations > HubSpot.
Click Connect HubSpot and authorize with your HubSpot account credentials.
Open the Sync tab and click Pull Deals under One-time Operations.
Open a test contact in Aloware Talk and confirm the Integration Card shows the expected Deals, Pipelines, and Stages.
The Sync with HubSpot button inside the integration card can be used any time Deal information looks outdated and needs a manual refresh.
Configuring IVR routing to the deal or contact owner
IVR routing sends inbound callers to the owner of the most recently updated Deal linked to their contact. If that owner is not valid in Aloware — for example, they are inactive or do not have an Aloware seat — the system falls back to the Contact Owner. If no valid owner is available, the call routes to a fallback ring group.
Steps to configure Deal or Contact Owner routing
Go to Lines > Settings > Routing & IVR.
In the IVR Menu Options section, add or edit a menu key option.
In the action dropdown, select Route to HubSpot Deal/Contact Owner.
Select the HubSpot Pipeline that should be used to scope the Deal Owner lookup.
Set a fallback ring group for cases where no resolved agent is available.
Save the IVR flow and run a test call from a number linked to a HubSpot Contact that has associated Deals.
The IVR step will show Invalid Step until both the pipeline and fallback ring group are configured.
How deal owner resolution works
When an inbound call reaches Aloware, the system needs to decide which agent should receive it. Instead of assigning calls randomly or relying only on the contact owner, Aloware prioritizes the most relevant Deal Owner based on recent activity.
This same logic is used in both standard IVR and AloAi IVA flows, so routing remains consistent regardless of how the call is handled.
When a call comes in, Aloware:
Identify the caller - The system matches the incoming phone number to a HubSpot contact.
Look up related deals - It retrieves all deals associated with that contact, limited to the selected pipeline used in the IVR configuration.
Prioritize recent activity - The deals are sorted by their most recent update (
notes_last_updated), so the most actively worked deal is considered first.Build the routing order - The system creates a list of potential owners:
First: Deal Owners (starting from the most recently updated Deal)
Last: Contact Owner (as fallback)
Select the first available agent - Aloware goes through the list and routes the call to the first owner who:
Is active in Aloware
Has a valid seat/license
If no valid deal owner is found, the system automatically falls back to the contact owner. If neither is available, the call is routed to the configured fallback ring group.
The table below summarizes how different situations resolve:
Scenario | Outcome |
Multiple deals linked to the contact | The deal owner of the most recently updated deal is prioritized. |
No deals linked to the contact | The call routes to the contact owner. |
Deal owner differs from contact owner | The deal owner takes precedence, as long as they are valid in Aloware. |
No valid deal owner is found in Aloware | The contact owner is used. |
How SMS and call logging works on deals
Every call made or received and every SMS sent or received through Aloware is logged as an activity on all HubSpot Deals associated with the contact or company involved. No extra action or setting is required once the integration is active.
For inbound calls and SMS, the activity is logged on every deal tied to the contact or company that owns the matching phone number.
For outbound SMS and calls, whether sent from the Aloware contact view or from the HubSpot Deal view, the activity is logged on every eligible deal.
Steps to verify SMS and call logging on deals
Pick a contact that has one or more associated HubSpot deals.
Send or receive an SMS and make or receive a call with that contact through Aloware.
Open HubSpot and navigate to one of the associated deals.
In the deal's activity timeline, make sure Calls and SMS are selected in the filters.
Confirm the call or SMS activity appears with the correct timestamp and direction.
Repeat on another Deal linked to the same contact or company to confirm every deal receives the log.
Open the contact record as well and verify the SMS also appears on the contact timeline.
Logging limits and constraints
The following limits apply to multi-entity logging. They exist so logging stays performant on large HubSpot accounts.
Parameter | Limit | Notes |
Deals logged per contact | 10 | The first 10 deals (by HubSpot association order) are logged. Any additional Deals are skipped. |
Deals logged per company | 10 | The same cap applies to Company-associated Deals. |
Duplicate contact records | 5 | When one phone number maps to multiple contact records, logging targets a maximum of 5. |
Timeline events | Contacts only | Deals and companies receive engagement-level logs; full timeline entries are written to contacts only. |
Deal data modification | Never | Aloware creates activity logs only.
Deal name, stage, owner, and custom fields are not modified. |
Duplicate activity prevention | Enforced | The system avoids creating duplicate activity entries, even when the same contact is linked to multiple Deals. |
HubSpot dialer consideration
Call logging on deals is supported by the new Aloware HubSpot Dialer, also known as the In-CRM CTI. Teams using the legacy dialer need to migrate to the new CTI to enable Deal-level call logging alongside SMS logging.
SMS logging does not depend on the new CTI. It works as long as the HubSpot integration is active and Deal sync has been completed.
How the deals integration works with other Aloware tools
The deals integration builds on several existing Aloware and HubSpot capabilities rather than replacing them. The table below maps those relationships.
HubSpot companies Integration
The Deals integration builds on the multi-entity model introduced with Companies. Deals associated through a Company are included in SMS logging. A message sent to a Company phone number is also logged on that Company’s Deals.
HubSpot multi-entity contacts
Multi-entity contact support allows contacts to be synced per phone number. The Deals integration extends logging from Contacts to include Deals and Companies.
New HubSpot Dialer (Aloware CTI)
The new in-CRM dialer supports call logging on Deals under certain conditions. SMS logging ensures both channels remain consistent. Teams using the legacy dialer need to migrate to the new CTI to enable deal-level call logging.
IVR and AloAi IVA
The same Deal Owner resolution logic is used across both systems. The most recently updated Deal Owner is prioritized, followed by the Contact Owner as fallback. This behavior is consistent in standard IVR and in the AloAi IVA post-conversion flow.
Aloware workflows and automations
Deal-level timeline events and engagement logs can be used as triggers in HubSpot Workflows. Only Contact records receive full timeline events. Deals and Companies receive engagement-level logs only.
How the deals integration helps teams
For admins and supervisors
Deal-level logs keep reporting and audits consistent across calls and SMS. IVR routing to the Deal Owner reduces the need for call transfers. Pipeline-based routing allows each IVR line to focus on the correct pipeline.
For agents
Deal context is available in the Integration Card within Aloware Talk. The Messenger and Dialer can be accessed directly from the HubSpot Deal view. All conversations are logged automatically on every related Deal, so no manual updates are required to keep timelines accurate.