Hello,
TL/DR: If there is anyone who has successfully integrated 3CX with HubSpot and has any advise on how to properly reformat the callerID and how the phone numbers should be saved in HubSpot, it would be greatly appreciated.
We have successfully integrated 3CX with HubSpot. However whenever a call comes in it will create a new contact even when there is an existing contact. We have reviewed the contact matching strategy, but are still having trouble.
By default we had caller ID's coming in as 11-digit numbers (ex. 1##########). In HubSpot we also had the phone numbers saved in a similar fashion (ex. 1##########); at least that's how they are displaying. So there were no parenthesis or dashes. When a call would come in it would create a new contact, which would display a phone number that was exactly matching. We would then call again and it would create a second new contact, again with a matching phone number. I would have though at the very least it should match with the new contact that was generated. This makes me think HubSpot is saving the number in a way that is not how it is displayed.
The contact matching strategy suggested we try using E.164 format, so we attempted that. First we attempted to just add the "+" to the beginning of the string (ex. +1##########). This would also generate a new contact, and repeated calls would also create new contacts. In HubSpot it displayed the phone number with parenthesis and dashes like so +1 (###) ###-####.
So we tried matching the format so I reformatted the CallerID to +1 (###) ###-####, I used the following source: "1(XXX)(XXX)(XXXX)" and replace: "+1 (\1) \2-\3", which did result in the desired Caller ID, which did save properly in HubSpot. However the same results occurred.
Thank you,
Philip
TL/DR: If there is anyone who has successfully integrated 3CX with HubSpot and has any advise on how to properly reformat the callerID and how the phone numbers should be saved in HubSpot, it would be greatly appreciated.
We have successfully integrated 3CX with HubSpot. However whenever a call comes in it will create a new contact even when there is an existing contact. We have reviewed the contact matching strategy, but are still having trouble.
By default we had caller ID's coming in as 11-digit numbers (ex. 1##########). In HubSpot we also had the phone numbers saved in a similar fashion (ex. 1##########); at least that's how they are displaying. So there were no parenthesis or dashes. When a call would come in it would create a new contact, which would display a phone number that was exactly matching. We would then call again and it would create a second new contact, again with a matching phone number. I would have though at the very least it should match with the new contact that was generated. This makes me think HubSpot is saving the number in a way that is not how it is displayed.
The contact matching strategy suggested we try using E.164 format, so we attempted that. First we attempted to just add the "+" to the beginning of the string (ex. +1##########). This would also generate a new contact, and repeated calls would also create new contacts. In HubSpot it displayed the phone number with parenthesis and dashes like so +1 (###) ###-####.
So we tried matching the format so I reformatted the CallerID to +1 (###) ###-####, I used the following source: "1(XXX)(XXX)(XXXX)" and replace: "+1 (\1) \2-\3", which did result in the desired Caller ID, which did save properly in HubSpot. However the same results occurred.
Thank you,
Philip
