Today the “Automatically link calls to associated objects using HubSpot AI” setting is all or nothing. When it is on, the call-to-deal AI model can attach any deal in the account. When it is off, you lose AI linking for contacts, companies and tickets as well. There is no way to keep the feature and require that the deal it picks has some connection to the company or contact actually called.
Please add that option: a setting where AI call-to-deal linking may only attach a deal that is associated with the called company or contact, that company’s parent or child companies, or another company sharing the same parent.
Why? Between 1 May and 22 September 2026 we had 1,717 calls placed to a company where HubSpot set a primary deal. In 1,649 the deal belonged to the company called or its parent. In 68 it belonged to an entirely unrelated company, spread across ten users. In one example the call went to a company in one US state and the deal HubSpot attached belonged to a company 700 miles away in another, with no association between the two records.
The pattern is consistent. In 65 of the 68, the company called had no open deal of its own at the time of the call, against 91 per cent of the correctly linked calls where it did. In 67 the deal chosen was open, and in 56 it belonged to the user who made the call. So when there is no plausible deal on the company called, the model reaches across the account and tends to land on one of the caller’s other open deals.
Support confirmed on ticket 48652340334 that the AI linking feature made the link on every example call we submitted, that the model’s per-call reasoning is not exposed, and that no setting currently restricts it to related deals.
The consequences are not cosmetic. The wrong deal gets the call’s activity, so “last contacted” and activity counts move on deals nobody has worked, which distorts pipeline hygiene reports and any workflow keyed on activity dates. Our call-coaching integration copies each call’s deal onto the notes and tasks it writes, so a rep opens a note about one account filed against a different account’s deal. Nothing in the interface flags the link as AI-generated or low confidence, and it is applied part way through the call, so there is nothing for the rep to notice at the time.
We expect this to hit hardest in any portal holding many similarly named company records: branch networks, franchises, regional sites and multi-site organisations under a shared parent. Our own database contains 16 companies sharing one identical name and 11 sharing another, each a separate site of a different organisation.
Our choice at the moment is to accept roughly 13 wrong links a month or switch off a feature that also produces around 19 correct ones. A relatedness constraint would keep the benefit and remove the failure mode. A confidence threshold, or simply labelling AI-made associations on the call record so they can be reviewed and reported on, would also help.