If you use RingEX by RingCentral with HubSpot, you may have noticed duplicate contacts showing up when calls are logged. This usually happens when RingCentral can’t match the call to an existing HubSpot record. If there’s one match, it logs the call there. If there’s no usable match, RingCentral creates a new contact like “Caller + [phone number]” and logs the call under that record.
That fallback behavior helps preserve call activity, but it can also create duplicate contacts in HubSpot.
Over time, this often leads to:
In this guide, we’ll cover:
RingCentral duplicates in HubSpot usually happen when the integration can’t find a clean match for the caller, so it creates a fallback contact named Caller +[number]. If your team later creates the actual contact separately, you end up with duplicate records and split call history.
RingCentral supports auto call logging. When that setting is turned on, calls are logged automatically after they end. RingCentral tries to log calls against an existing HubSpot record. If it finds one matching contact, it uses that record. If there are multiple matches, it may use the last modified matched contact. But if it can’t find a usable match, it creates a new fallback contact instead.
That’s the core issue.
A contact may already exist in HubSpot, but if RingCentral can’t match it correctly, it may create a second record like Caller +15551234567. Later, your team may create or update the real contact separately, leaving you with duplicates.
A contact named Caller +[number] usually means RingCentral created that record automatically because it couldn’t match the call to an existing HubSpot contact.
So when you see contacts like:
that’s often a sign the integration created a fallback contact instead of using a normal existing record.
This is the most direct cause.
RingCentral’s auto call logging follows a simple matching flow:
That means duplicates can appear anytime RingCentral fails to find the right existing contact.
A common reason is incorrect phone number formatting.
If the number in HubSpot doesn’t match the format RingCentral expects, the integration may miss the existing contact and create a new one instead. Even when the same phone number exists in HubSpot, inconsistent formatting can make matching less reliable.
RingCentral can match phone numbers stored in different common formats, but inconsistent formatting can still make matching and duplicate review harder. Standardizing numbers in E.164 format is usually the safest option.
This is one of the most common duplicate patterns.
RingCentral creates a fallback Caller +1... contact first, then later an SDR or sales rep creates the real contact with the same phone number. That leaves you with two records for the same person.
The easiest way to find these duplicates is to look for the patterns RingCentral creates.
Start by looking for contacts whose name begins with Caller +. Those are often the fallback records created by the integration.
Phone-based matching works much better when numbers are stored consistently. If the same number appears in different formats, duplicates are much easier to miss.
If you want to align more closely with HubSpot’s phone validation model, E.164 is the cleanest option. You can also use HubSpot’s native phone-number formatting workflow action to standardize values.
Don’t just check one phone property.
Compare across:
Once you’ve identified the duplicates, the next step is deciding which record should stay.
In most cases, the best record to keep is not the RingCentral-created fallback contact. It’s usually the real HubSpot contact with the better name, richer history, owner assignment, and cleaner source data.
A good rule of thumb is to avoid keeping RingCentral-created Caller + records as the surviving contact when a more complete HubSpot record already exists.
If you’re using Koalify Primary Duplicate Rules, the primary-record logic should favor records that:
Caller + That gives you a much cleaner surviving record after the merge.
If you want to automate the merge, this is where Koalify comes in.
Workflow-based automatic merging is not a native HubSpot feature in this setup. A practical approach is to use Koalify’s Merge Duplicate Record workflow action after Koalify has identified the duplicate and decided which record is primary.
A common setup is to enroll contacts where:
FalseThat way, Koalify can merge the lower-quality fallback record automatically.
Before turning on auto-merge across the board, test on a smaller segment first, especially for:
A few simple changes can reduce duplicate creation:
If you want to handle this pattern more systematically in HubSpot, Koalify is a strong fit.
A practical setup looks like this:
Duplicate Rules
Fuzzy Rules
Primary Duplicate Rules
Workflow Automation with Koalify
If RingEX by RingCentral is creating duplicate contacts in HubSpot, the issue usually comes from the matching logic and the fallback behavior when no match is found.
When that happens, RingCentral creates a Caller +[number] contact and logs the call there. If your team later creates the real contact separately, you end up with duplicate records and split call history.
The fix is usually straightforward:
Once those pieces are in place, RingCentral duplicates become much easier to manage.