--- title: Why RingEX by RingCentral Creates Duplicate Contacts in HubSpot and How to Fix It description: Learn why RingEX by RingCentral creates duplicate contacts in HubSpot, what “Caller +[number]” contacts mean, and how to detect, merge, and prevent duplicates with Koalify. image: https://koalify.io/hubfs/What%20Does%20%E2%80%9CCaller%20+1...%E2%80%9D%20Mean%20in%20HubSpot.png --- [Skip to content](https://koalify.io/blog/ringcentral-duplicate-contacts-hubspot#main-content) [![rectangle\_long\_koala\_with\_name\_bold\_200\_125\_white](https://koalify.io/hubfs/rectangle_long_koala_with_name_bold_200_125_white.png)](https://koalify.io) - Products Show submenu for Products - [Deduplication](https://koalify.io) - [Email Validation](https://koalify.io/hubspot-email-validation) - Pricing Show submenu for Pricing - [Deduplication](https://koalify.io/pricing) - [Email Validation](https://koalify.io/hubspot-email-validation-pricing-koalify) - [Partners](https://koalify.io/partners) - [Blog](https://koalify.io/blog) - Knowledge base Show submenu for Knowledge base - [Deduplication](https://koalify.io/knowledge-base) - [Email Validation](https://koalify.io/email-validation-knowledge-base) - Products Show submenu for Products - [Deduplication](https://koalify.io) - [Email Validation](https://koalify.io/hubspot-email-validation) - Pricing Show submenu for Pricing - [Deduplication](https://koalify.io/pricing) - [Email Validation](https://koalify.io/hubspot-email-validation-pricing-koalify) - [Partners](https://koalify.io/partners) - [Blog](https://koalify.io/blog) - Knowledge base Show submenu for Knowledge base - [Deduplication](https://koalify.io/knowledge-base) - [Email Validation](https://koalify.io/email-validation-knowledge-base) ![menu-toggle](https://21645388.fs1.hubspotusercontent-na1.net/hubfs/21645388/menu-toggle.svg) ![menu-close](https://21645388.fs1.hubspotusercontent-na1.net/hubfs/21645388/menu-close.svg) [Get Started Free](https://api.koalify.io/hubspot/install?utm_source=koalify&utm_medium=website&utm_campaign=navigation) [HubSpot Data Quality](https://koalify.io/blog/tag/hubspot-data-quality), [HubSpot Integration Duplicates](https://koalify.io/blog/tag/hubspot-integration-duplicates) # Why RingEX by RingCentral Creates Duplicate Contacts in HubSpot and How to Fix It [By \- Jonas,](https://koalify.io/blog/author/jonas) Apr 23, 2026 ![ Featured Image](https://koalify.io/hs-fs/hubfs/What%20Does%20%E2%80%9CCaller%20+1...%E2%80%9D%20Mean%20in%20HubSpot.png?width=425&height=262&name=What%20Does%20%E2%80%9CCaller%20+1...%E2%80%9D%20Mean%20in%20HubSpot.png) 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. ![Why Does RingCentral Create Duplicates in HubSpot](https://koalify.io/hs-fs/hubfs/Why%20Does%20RingCentral%20Create%20Duplicates%20in%20HubSpot.png?width=400&height=501&name=Why%20Does%20RingCentral%20Create%20Duplicates%20in%20HubSpot.png) ## 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. ![What Does “Caller +1...” Mean in HubSpot](https://koalify.io/hs-fs/hubfs/What%20Does%20%E2%80%9CCaller%20+1...%E2%80%9D%20Mean%20in%20HubSpot.png?width=400&height=247&name=What%20Does%20%E2%80%9CCaller%20+1...%E2%80%9D%20Mean%20in%20HubSpot.png) ## 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](https://knowledge.hubspot.com/workflows/format-phone-numbers-using-workflows) 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 ![Compare phone numbers across multiple fields](https://koalify.io/hs-fs/hubfs/Compare%20phone%20numbers%20across%20multiple%20fields.png?width=1218&height=536&name=Compare%20phone%20numbers%20across%20multiple%20fields.png) ## 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. ![Set non-RingCentral contacts as the primary record](https://koalify.io/hs-fs/hubfs/Set%20non-RingCentral%20contacts%20as%20the%20primary%20record.png?width=800&height=418&name=Set%20non-RingCentral%20contacts%20as%20the%20primary%20record.png)   ### 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. ![Merge RingCentral duplicates automatically with Koalify](https://koalify.io/hs-fs/hubfs/Merge%20RingCentral%20duplicates%20automatically%20with%20Koalify.png?width=800&height=588&name=Merge%20RingCentral%20duplicates%20automatically%20with%20Koalify.png)   ### 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.   ## FAQ about RingCentral duplicates in HubSpot ###### Why does RingCentral create duplicate contacts in HubSpot? RingCentral can create duplicate contacts when it can’t find a clean match for the caller in HubSpot. If no usable match is found, the integration creates a fallback contact like **Caller +\[phone number\]** and logs the call there. If your team later creates the real contact separately, you end up 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. ###### Are “Caller +1…” contacts always duplicates? No. They are not always duplicates. But they are a strong signal that the record was auto-created by the RingCentral integration and should be reviewed, especially if another contact exists with the same phone number and more complete CRM data. ###### Why does RingCentral create a new contact even when the person already exists in HubSpot? The most common reasons are phone-number formatting differences, the number being stored in the wrong field, or the integration not finding a single clean match at the time the call is logged. ###### What is the best way to detect RingCentral duplicates? The best starting point is to look for contacts whose names begin with **Caller +** and then compare phone numbers across multiple HubSpot phone fields, not just one. ###### Can HubSpot automatically merge RingCentral duplicates on its own? Not in this workflow. HubSpot can help with lists, formatting, and review, but **workflow-based automatic merging for this setup is something you’d handle with Koalify**. ###### How can Koalify help with RingCentral duplicates? Koalify helps by identifying duplicates across multiple phone fields, applying fuzzy matching for phone-format differences, choosing the better primary record, and automatically merging lower-quality fallback contacts through workflows. ###### Category - [HubSpot Data Quality](https://koalify.io/blog/tag/hubspot-data-quality) - [HubSpot Revenue Operations](https://koalify.io/blog/tag/hubspot-revenue-operations) - [HubSpot Integration Duplicates](https://koalify.io/blog/tag/hubspot-integration-duplicates) - [HubSpot Email Validation](https://koalify.io/blog/tag/hubspot-email-validation) - [HubSpot Associations](https://koalify.io/blog/tag/hubspot-associations) - [HubSpot Deduplication](https://koalify.io/blog/tag/hubspot-deduplication) ###### Popular Post - [HubSpot best practices for contacts that leave a company](https://koalify.io/blog/hubspot-best-practices-for-contacts-that-leave-a-company) - [How to Bulk Merge HubSpot Duplicates: Contacts, Companies, Deals and More](https://koalify.io/blog/how-to-bulk-merge-hubspot-duplicates-contacts-companies-more) - [How to Merge Companies in HubSpot (Safely, Manually or in Bulk)](https://koalify.io/blog/how-to-merge-companies-in-hubspot-manual-or-in-bulk) - [HubSpot Deduplication: How to Find, Manage, and Remove Duplicates in HubSpot](https://koalify.io/blog/hubspot-deduplication-the-ultimate-guide-to-zero-duplicates-in-hubspot) - [How to Merge Duplicate Contacts in HubSpot Without Losing Data](https://koalify.io/blog/how-to-merge-contacts-in-hubspot-manual-or-in-bulk) ### Similar Blogs ![Why Aircall Creates Duplicate Contacts in HubSpot and How to Fix It](https://koalify.io/hs-fs/hubfs/Aircall%20new%20contact.png?width=352&name=Aircall%20new%20contact.png) #### [Why Aircall Creates Duplicate Contacts in HubSpot and How to Fix It](https://koalify.io/blog/how-to-detect-and-merge-aircall-duplicates-in-hubspot) By [Jonas](https://koalify.io/blog/author/jonas) 10 April 2025 If you use Aircall with HubSpot, you may have seen duplicate contacts appear when calls are logged.... [READ MORE](https://koalify.io/blog/how-to-detect-and-merge-aircall-duplicates-in-hubspot) ![Why ZoomInfo Creates Duplicates in HubSpot and How to Merge Them](https://koalify.io/hs-fs/hubfs/Tighten%20ZoomInfo%20export%20settings.png?width=352&name=Tighten%20ZoomInfo%20export%20settings.png) #### [Why ZoomInfo Creates Duplicates in HubSpot and How to Merge Them](https://koalify.io/blog/merge-zoominfo-duplicates-hubspot) By [Jonas](https://koalify.io/blog/author/jonas) 2 April 2026 If you are a HubSpot admin and use ZoomInfo, you have probably heard some version of this: [READ MORE](https://koalify.io/blog/merge-zoominfo-duplicates-hubspot) ![Why CallRail Creates Duplicate Contacts in HubSpot and How to Fix It](https://koalify.io/hs-fs/hubfs/Look%20for%20@call.com%20email%20addresses.png?width=352&name=Look%20for%20@call.com%20email%20addresses.png) #### [Why CallRail Creates Duplicate Contacts in HubSpot and How to Fix It](https://koalify.io/blog/callrail-duplicate-contacts-hubspot) By [Jonas](https://koalify.io/blog/author/jonas) 27 March 2026 If you use CallRail with HubSpot, you may have seen duplicate contacts appear when calls are logged. [READ MORE](https://koalify.io/blog/callrail-duplicate-contacts-hubspot) ## Koalify HubSpot deduplication and email validation - - [Review us on HubSpot](https://app-eu1.hubspot.com/l/marketplace/listing/koalify-io/write-review?eco_review_source=external-button) [![SOC 2 Logo](https://koalify.io/hs-fs/hubfs/SOC%202%20Logo.webp?width=70&height=70&name=SOC%202%20Logo.webp "SOC 2 Logo")](https://trust.koalify.io/) [![gdpr](https://koalify.io/hs-fs/hubfs/gdpr.png?width=70&height=70&name=gdpr.png "gdpr")](https://trust.koalify.io/) ## Company [Product](https://koalify.io) [Pricing](https://koalify.io/pricing-usd) [Knowledge Base](https://koalify.io/knowledge-base) [Blog](https://koalify.io/blog) [Partners](https://koalify.io/partners) ## Blog [HubSpot Deduplication](https://koalify.io/blog/hubspot-deduplication-the-ultimate-guide-to-zero-duplicates-in-hubspot) [Merge HubSpot Contacts](https://koalify.io/blog/how-to-merge-contacts-in-hubspot-manual-or-in-bulk) [Merge HubSpot Companies](https://koalify.io/blog/how-to-merge-companies-in-hubspot-manual-or-in-bulk) [Merge HubSpot Deals](https://koalify.io/blog/how-to-merge-deals-in-hubspot-manual-or-in-bulk) [Bulk Merge HubSpot](https://koalify.io/blog/how-to-bulk-merge-hubspot-duplicates-contacts-companies-more) ## Security [Trust Center](https://trust.koalify.io/) [Terms of Service](https://koalify.io/terms-of-service) [Privacy Policy](https://koalify.io/privacy-policy) [Data Processing Addendum](https://koalify.io/data-processing-addendum) [Security](https://koalify.io/security) © 2026 Koalify. All rights reserved. ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Jonas", "url" : "https://koalify.io/blog/author/jonas" }, "dateModified" : "2026-05-28T11:46:33.189Z", "datePublished" : "2026-04-23T12:34:25.000Z", "headline" : "Why RingEX by RingCentral Creates Duplicate Contacts in HubSpot and How to Fix It", "image" : [ "https://koalify.io/hubfs/What%20Does%20%E2%80%9CCaller%20+1...%E2%80%9D%20Mean%20in%20HubSpot.png" ], "mainEntityOfPage" : { "@id" : "https://koalify.io/blog/ringcentral-duplicate-contacts-hubspot", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://koalify.io/hubfs/koalify_rectangle_100px.png" }, "name" : "Koalify" } } ```