Before diving into your questions, here’s the key distinction:
RingEX = RingCentral’s unified communications platform for everyday business calling, SMS, voicemail, and messaging. Think of it as a business phone system for sales reps and general employees.
RingCX = RingCentral’s full contact center platform — built for support queues, agent routing, omnichannel interactions (voice + 20+ digital channels), quality management, and supervisors.
Both integrate natively with HubSpot, delivering value to sellers, marketers, and agents — but they serve distinct user roles and use cases. RingCentral
Your Questions Answered
1. Can the same HubSpot users use both integrations?
Yes, but with important caveats. RingEX handles communication activity logging and contact synchronization, while RingCX adds contact center data including agent interactions across digital channels. They are separate apps installed from the HubSpot Marketplace, and a user can technically have both active. However, in practice, the integrations serve different roles — RingEX is for sales/general staff making outbound calls, while RingCX is for contact center agents handling queued interactions. A user trying to use both simultaneously may encounter UI conflicts. At least one user has noted using CX and RX together, flagging that the widget “pops up in front of everything as soon as the phone rings” and some functions are less straightforward than before. ZoomInfoHubSpot
2. Will setting up RingCX break outbound calling via RingEX in HubSpot?
It shouldn’t break it outright, but there is real risk of interference. The two integrations each embed their own dialer widget inside HubSpot. RingCX for Salesforce and RingCX for HubSpot now include customization, allowing admins to tailor the integration to their workflows — but this requires deliberate configuration. Without careful setup, both widgets may compete for control of the calling interface. Best practice: test outbound RingEX calling in a sandbox or staging environment before enabling RingCX in production for your full user base. RingCentral
3. Could adding RingCX affect existing RingEX call logging, SMS logging, call recording, or call summaries?
Potentially yes. The integrations log activities independently, but they write to the same HubSpot contact timeline. Call recordings are referenced in the HubSpot activity log, but the audio files themselves are stored in RingCentral — the HubSpot activity record may include a link to the recording that opens in RingCentral for playback. Since both integrations use overlapping data objects (call logs, contact records), misconfigured logging rules could cause RingCX to interfere with or overwrite RingEX-logged activities. SMS logging and call summaries from RingEX should remain unaffected as long as each integration’s logging scope is clearly defined during setup. ZoomInfo
4. How do RingCX calls get logged in HubSpot — can we tell which integration logged an activity?
Yes, in most cases. Each integration logs activities under its own “call provider” label in HubSpot’s activity timeline. The RingEX integration handles communication activity logging and contact synchronization, while the RingCX integration adds contact center data including agent interactions across digital channels — these are logged as distinct activity types. RingCX activities tend to be tied to contact center interactions (with queue/agent metadata), while RingEX activities reflect direct calling. Admins can also use HubSpot’s activity filters to segment by integration source. That said, without enforced naming conventions or custom properties, distinguishing them at scale requires proactive configuration. ZoomInfo
5. Is there a risk of duplicate call activities?
Yes — this is one of the most commonly reported issues when running both integrations. If a call passes through both the RingEX system and is also handled by a RingCX agent (e.g., a transferred or warm-handoff call), both integrations may independently log the same interaction to the same contact record. What happens if a caller has no matching contact in HubSpot depends on the integration configuration — the native connector can create a new HubSpot contact when an unmatched phone number is detected, or log the call without associating it to a contact record. The duplicate risk is highest when: ZoomInfo
- The same phone number is used across both systems
- Both integrations are configured to auto-log all calls
- There’s no deduplication logic or call source filtering in place
Mitigation: configure each integration to only log activities from its designated call type (e.g., RingCX logs only queued/inbound contact center interactions; RingEX logs only direct outbound calls).
6. Known limitations and config requirements to be aware of?
Here’s a consolidated list of the most important ones:
Licensing: RingCX requires a subscription starting at $65/user/month on annual billing, on top of existing HubSpot and RingEX costs. Make sure you account for this before rolling out to agents. ZoomInfo
Admin access required on both sides: Setting up the native integration requires admin access on both platforms — in RingCentral you need admin rights to authorize the HubSpot connection, and in HubSpot you need Super Admin or integration-specific permissions to install the connector. ZoomInfo
Call activity is one-way: Call activity flows one way — from RingCentral into HubSpot. HubSpot deal data, pipeline stages, and marketing engagement history do not flow back into RingCentral. ZoomInfo
Mobile limitations: There is no way to automatically log RingCentral calls received on mobile devices into HubSpot unless the call is handled within the RingCentral app — forwarding calls to a mobile device outside the RingCentral app will not trigger auto-logging. HubSpot
Email address matching is critical for RingEX: The email on your RingCentral account must be exactly the same as your HubSpot account for SMS activities and workflows to log correctly. Marketingallday
Video and team messaging don’t sync: Video meeting data and team messaging content from RingCentral do not flow into HubSpot automatically. ZoomInfo
API rate limits matter at scale: RingCentral enforces tier-based limits (50 requests/minute for Light, 10 requests/minute for Heavy operations), and HubSpot enforces 100–190 requests per 10 seconds depending on subscription tier. High call volumes can hit these limits.