A visitor submits a website enquiry and calls the office a few minutes later. HubSpot now contains two apparently independent leads, and the team sends duplicate follow-up messages.
Connecting those interactions requires identity evidence and a shared workflow reference. Similar wording or close timestamps are not enough to merge people safely.
Decide which relationship you are trying to establish
You may need to link a call to an existing enquiry, associate both with a verified contact, or simply show staff that the records might be related. Those outcomes have different confidence requirements.
| Signal | Appropriate interpretation |
|---|---|
| Verified enquiry reference | A specific candidate interaction |
| Confirmed email or phone | Input to the approved identity policy |
| Similar message | Possible context, not identity proof |
| Nearby timestamps | Supporting chronology only |
For a fictional quote request, the receptionist can ask whether the caller has the reference from the submitted form. Verify that reference within the authorised account boundary before exposing its contents.
Preserve source interactions instead of erasing them
The form and phone call may contain different information. Keep their original references and attach the relationship rather than replacing both with a single generated summary.
If the caller corrects the address during the call, mark which value is current and why. The earlier form remains useful evidence, but it should not overwrite the correction through a delayed automation.
The email-correction guide covers a related versioning problem.
Coordinate follow-up across channels
Decide whether a newly confirmed phone booking should suppress a generic form-response sequence. Apply that decision from a verified state transition, not merely from the fact that a call occurred.
Message operations need their own identities and delivery status. A failed call should not cancel a useful response unless the business has approved that behaviour.
If the relationship is uncertain, present it for review rather than letting both workflows rewrite the same contact automatically.
Test the cases that look similar but are different
Use fictional enquiries from two employees at one company, one person with two unrelated requests, a shared household number, and an invalid reference. Include a delayed form event arriving after the call.
Inspect associations, current fields, and outgoing messages. The desired outcome is not always fewer records; it is a traceable relationship without lost context or incorrect merges.
The shared-line article explains why a familiar company number cannot settle individual identity.
Cross-channel questions
Should close timestamps trigger automatic merging?
No. Use an approved identity and interaction-linking policy.
Must the original form be deleted after a call?
Usually the relationship is more useful than deleting the source evidence.
What should staff see?
Show the linked interactions, current verified details, and active follow-up in the CRM review.