RingCentral for Hubspot (Chrome extension): Match call to existing Hubspot record when NOT in e.164 format
RingCentral for Hubspot: Match call to existing Hubspot record when NOT in e.164 formatIn some cases a match can be found when not in e.164 format, it depends. However, if the contact has a +1 and also parenthesis and dashes - no match is found.When Hubspot integration is not finding a match, the app is creating a new contact named “Caller + phone number in e164 format” and logging the call under the new contact.per Customer: "All these "junk" contacts are being generated in Hubspot every time our users call via Ring Central IF the number doesn't have the +1(and the phone number) format. And we have many records with phone numbers that don't have that format."See video for replicated issue: the RC call is initiated from a "Deals" record, to an existing Hubspot contact. User has "auto log calls" enabled. The problem, Hubspot integration is seemingly not finding a match, the app is creating a new contact named “Caller + phone number in e164 format” and logging the call under the new contact.For the issue we replicated: the contact had a +1 and also parenthesis and dashes. One of those is causing an issue with matching. The root problem is the format for making a call is not in a traditional e164 format. Customers format should work and engineering needs to look and see why it's not working. see case: https://rc.lightning.force.com/lightning/r/Case/500Hr00001Xba3mIAB/view