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:
- duplicate contacts for the same person
- split call history
- messy reporting
- manual cleanup after reps create the “real” contact later
In this guide, we’ll cover:
- why RingCentral creates duplicate contacts in HubSpot
- what Caller +1... contacts mean
- how to detect RingCentral duplicates
- how to merge them safely
- how to prevent more duplicates in the future
Quick answer
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.
Why Does RingCentral Create Duplicates in HubSpot?
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.
What Does “Caller +1…” Mean in HubSpot?
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:
- Caller +15551234567
- Caller +1[company number]
- Anonymous
that’s often a sign the integration created a fallback contact instead of using a normal existing record.
Common Reasons RingCentral Creates Duplicates in HubSpot
1. No usable match is found
This is the most direct cause.
RingCentral’s auto call logging follows a simple matching flow:
- if the call has a single match, it logs to that record
- if the call has multiple matches, it logs to the last modified matched contact
- if there is no match, it creates a new contact named Caller + [phone number in E.164 format]
- if the call is anonymous, it creates or uses an Anonymous contact
That means duplicates can appear anytime RingCentral fails to find the right existing contact.
2. Phone-number formatting gets in the way
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.
3. A rep creates the actual contact later
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.
How to Detect RingCentral Duplicates in HubSpot
The easiest way to find these duplicates is to look for the patterns RingCentral creates.
Step 1: Search for contacts named “Caller +”
Start by looking for contacts whose name begins with Caller +. Those are often the fallback records created by the integration.
Step 2: Normalize phone numbers before comparing them
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.
Step 3: Compare phone numbers across multiple fields
Don’t just check one phone property.
Compare across:
- Phone Number
- Mobile Phone Number
- WhatsApp Phone Number
- secondary phone fields
- custom phone properties
How to Merge RingCentral Duplicates Automatically
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.
Step 1: Set non-RingCentral contacts as the primary record
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:
- have an email address
- do not contain
Caller +
That gives you a much cleaner surviving record after the merge.
Step 2: Merge RingCentral duplicates automatically with Koalify
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:
- the name starts with Caller +
- Koalify Duplicate Rules matches one of your phone-based rules
- Koalify is Primary Duplicate is
False
That way, Koalify can merge the lower-quality fallback record automatically.
Step 3: Test before automating fully
Before turning on auto-merge across the board, test on a smaller segment first, especially for:
- shared business numbers
- internal lines
- company main numbers
- anonymous or spam calls
How to Prevent Future RingCentral Duplicates
A few simple changes can reduce duplicate creation:
- review whether RingCentral is set to auto log calls
- keep phone-number formatting consistent
- store key phone numbers in standard HubSpot phone fields
- compare duplicates across multiple phone properties
- test merge logic before rolling it out widely
Koalify Tips for RingCentral Duplicates
If you want to handle this pattern more systematically in HubSpot, Koalify is a strong fit.
A practical setup looks like this:
Duplicate Rules
- compare Phone Number, Mobile Phone Number, WhatsApp Number, and custom phone fields
- don’t rely on a single phone property
Fuzzy Rules
- ignore spaces, dashes, brackets, and punctuation
- reduce false negatives caused by formatting differences
Primary Duplicate Rules
- prefer records that do not start with Caller +
- prefer records with a real contact name, owner, lifecycle stage, and more activity history
Workflow Automation with Koalify
- use Koalify’s Merge Duplicate Record action for automatic merging
- enroll contacts where the name starts with Caller +
- only merge records marked as non-primary duplicates
- test carefully before applying the workflow broadly
Final Thoughts
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:
- identify Caller + contacts
- improve phone-based matching
- choose better primary-record logic
- automate merging carefully with Koalify
Once those pieces are in place, RingCentral duplicates become much easier to manage.
