RingCentral Salesforce Integration: Setup, Features and Limits (2026)

What a RingCentral Salesforce integration does

Without it, reps dial from a desk phone or the RingCentral app, then type the call into Salesforce, or don’t. Managers can’t see activity, and the next rep who opens the account has no idea who called last.

A working integration does five jobs:

• Click-to-dial. Phone fields in Salesforce become links that start the call through RingCentral.
• Screen pop. On an incoming call, Salesforce searches the number and opens or lists the matching record.
• Call logging. Each call becomes a Task on the right Contact, Lead, Account, Opportunity or Case, with duration, result, notes and a recording link.
• SMS. Reps text from Salesforce, and conversations are logged to the record.
• Reporting. Calls are Salesforce data, so you can report on activity per rep, team, campaign or pipeline stage.

If you are still choosing a phone system, our Salesforce CTI integration guide compares RingCentral with other vendors. This page assumes you run RingCentral and want it wired into Salesforce properly.

RingCentral’s Salesforce apps in 2026

RingCentral sells two phone products, and each has its own Salesforce package. Pick the one that matches the RingCentral product your team uses.

RingCentral for Salesforce (RingEX)

This is the app most people mean by “RingCentral Salesforce integration”. RingCentral builds and maintains it, and you install it from AppExchange (now AgentExchange) or the RingCentral App Gallery, into a sandbox or production org. After install, the App Launcher shows two apps: RingCentral for Lightning for users and RingCentral Admin for Lightning for setup.

RingCentral ships updates often. As of October 2026 the current version is 6.49.2, and recent releases added:

• Smart Notes for all users and SMS actions triggered from Salesforce flows (version 6.45, March 2026).
• A shared SMS inbox that syncs to Salesforce (it needs an SMS Booster license) and SMS opt-out handling (6.47, May 2026).
• Screen pops on outgoing calls, switched on in RingCentral’s Integration Console (6.49, July 2026).
• An updated connected app security model to meet current Salesforce requirements (6.48, June 2026).

Requirements

• RingCentral plan: RingEX Advanced or Ultra. RingCentral’s pricing page lists CRM integrations from Advanced up; Core doesn’t include them. As of October 2026, the list prices are $25 and $35 per user per month billed annually, or $35 and $45 billed monthly.
• Salesforce edition: Professional, Enterprise or Unlimited, according to RingCentral’s admin guide. RingCentral’s FAQ adds that orgs without Apex can’t complete the connection and an API add-on won’t fix it, so confirm with RingCentral if you run Professional.
• Users: not compatible with community licenses. Each user is assigned to the call center and needs access to the package’s Visualforce pages.
• Interface: Lightning Experience; the Sales Engagement (formerly High Velocity Sales) features work only in Lightning.
• Browser and network: RingCentral recommends a current browser, at least 8 GB of RAM and network latency under 150 ms. The softphone is a WebRTC phone, so a weak laptop or VPN shows up as call quality problems.

RingCX for Salesforce

RingCX is RingCentral’s contact center product, and its Salesforce package is separate, with its own release notes.

In 2025 and 2026 RingCentral added click-to-SMS from contact and lead phone fields, Salesforce lead uploads into the RingCX outbound dialer, automatic Do Not Call sync, customizable matching, screen pops and logging, and an Agent Assist panel with real-time transcripts and AI coaching.

RingCX also offers a Service Cloud Voice (bring your own telephony) option, which Salesforce now calls Salesforce Voice with Partner Telephony. Calls then arrive through Salesforce Omni-Channel and are stored as VoiceCall records; since March 2026, RingCX queue callbacks are presented that way too. This path needs Salesforce Voice licenses on top of RingCX, and Salesforce Voice is where Salesforce points customers after Open CTI.

The Open CTI question

The RingEX package is built on Salesforce Open CTI. You can see it in the setup: the wizard creates a call center, users are assigned to it, and admins add the Open CTI Softphone to each Lightning app’s utility bar.

RingCentral for Salesforce runs on Open CTI, and that framework has an end date. Salesforce’s Trailhead module on the migration says Open CTI has been in maintenance mode since 2020, has not been offered to newly created Agentforce Service orgs since February 16, 2026, and retires for all orgs on February 28, 2028.

After that, call center adapters, softphone layouts and custom screen-pop logic built on Open CTI stop working. Salesforce points customers to Salesforce Voice (Partner Contact Center or Agentforce Contact Center).

As of October 2026, RingCentral’s public release notes for the RingEX app don’t describe what replaces its Open CTI adapter, and customers are asking about it in RingCentral’s community forum. What that means in practice:

• Existing orgs: the app keeps working until the retirement date. No reason to rip it out now.
• New Agentforce Service orgs: check with RingCentral before you buy, because Open CTI isn’t available there.
• Renewals: before you sign a RingEX contract that runs past February 2028, get RingCentral’s plan in writing, including whether it will need Salesforce Voice licenses.
• Custom code: don’t build new logic on the Open CTI JavaScript API. Put custom work on the RingCentral and Salesforce APIs instead.

Your options compared

Which option fits you?

Four questions about who calls, what Salesforce needs to show, which RingCentral product you pay for and who builds integrations. The answer points to RingEX, RingCX, an iPaaS or a custom build.

How the data flows

RingCentral is the system of record for calls, recordings and messages. Salesforce is the system of record for people, accounts and deals, and it gets a Task for each call or conversation with a link back to RingCentral.

What gets logged where

The package installs a Task layout with its own fields. This is the mapping to plan around:

Two details catch most admins. First, a call logs to the Contact or Lead plus one related record. If managers expect calls on Opportunities, reps must dial from the Opportunity or pick it in Related To.

Second, if a rep creates a Lead after an inbound call, RingCentral’s FAQ notes the earlier Task isn’t relinked automatically; the rep has to associate it from call history.

How to set it up, step by step

Most of the work is deciding logging rules and wiring the softphone into every app; the install itself is quick. Labels in the RingEX package change between versions, so take the exact clicks from RingCentral’s admin guide.

1. Check plans and decide the rules firstConfirm RingEX Advanced or Ultra for every rep and a supported Salesforce edition. Write down which calls should log (all, connected only), when (ringing or answered), which records calls should attach to, and which outcomes reps must pick.
2. Install in a sandboxOpen the RingCentral for Salesforce listing on AppExchange, click Get It Now and choose Sandbox on RingCentral’s page. Install for admins only or for the profiles that will use it. Check it under Installed Packages and in the App Launcher.
3. Run the install wizardOpen RingCentral Admin for Lightning. The wizard can create the call center for you if the org has none; otherwise download the XML definition and import it under Call Centers in Setup, then click Verify Call Center. The XML is specific to one org, so don’t reuse a sandbox file in production.
4. Assign users to the call centerAdd each rep under Manage Call Center Users. A user who isn’t in the call center won’t see the phone. Check that their profiles can open the package’s Visualforce pages; a missing OpenCTIIndex page is RingCentral’s most common “insufficient privileges” cause.
5. Add the softphone to every Lightning appIn App Manager, edit each app reps use (Sales, Service Console, any custom app). Add the Open CTI Softphone as a utility item and save. Skipping one app is why a rep says the phone “disappears” on some tabs.
6. Set softphone layouts and screen popsCreate a softphone layout per role (each user gets one, assigned by profile). Choose the objects to search on incoming calls, including custom objects if you need them, and what happens on no match, one match and several matches.
7. Configure logging in the Admin UISet the matching strategy and whether call logs are auto-created on ringing or answered. Then set auto SMS logging (off by default), the disposition field and the log fields reps see. Add the Call Recording, Call Result and Call Duration fields to every Task layout in use, and check field-level security.
8. Turn on extras deliberatelyDo Not Call settings, Sales Engagement dispositions if you use cadences, RingCentral Video global actions, mobile actions and screen pops on outgoing calls. Share the Cloud Phone Report and Dashboard folders with managers.
9. Test real callsInbound from a known contact, from a number on two records and from an unknown number. Outbound from a Lead, an Opportunity and a Case. Then a missed queue call, a voicemail, an SMS thread and a recorded call. Check the Task, its links and who owns it.
10. Pilot, then repeat in productionRun one team for a week or two, adjust layouts and logging rules, then install in production and repeat the configuration. Brief reps on what logs automatically and what they still pick by hand.

Run the integration under named users, not a shared login: each rep authorizes RingCentral with their own extension, so Tasks are owned by the right person. If you add a server-side sync or custom code, give it a dedicated Salesforce integration user.

Built by Gilzor

Results we’ve shipped

70+products launched

98%delivered on time

85%clients come back

Aviation33%faster baggage weigh-inWeb and Mobile application for Airlines→Healthcare+30%lab test ordersMedical Lab Web and Native Mobile Applications→Retail · Startup700+stores aggregatedMobile application for Grocery shops→

Talk to the people who build it. Tell us about your project and get a free estimate of scope, timeline and cost.

See how we’d approach yours →

Pitfalls and how to fix them

When a custom integration makes sense

The RingCentral app is the right default for calling and logging. Custom work starts to pay off when:

• You need call data in custom objects or a data model the Task can’t carry: call legs, queue times, transfers, talk-to-listen ratios.
• You want transcripts or AI summaries stored in Salesforce fields for scoring, coaching or Agentforce, not just a link.
• Calls must sync even when no rep has Salesforce open, for example missed calls, IVR outcomes or calls from desk phones.
• You run several Salesforce orgs or several RingCentral accounts, or you need the same data in a warehouse.
• You want to cut your dependency on Open CTI before 2028.

A typical build is a small service that subscribes to RingCentral webhooks for call and message events. It reads the call log and recordings through the RingCentral REST API, matches numbers against Salesforce, and writes records through the Salesforce REST or Composite API. For an in-Salesforce phone, RingCentral’s Embeddable widget and its App Connect framework are the vendor’s building blocks.

Respect the limits on both sides. RingCentral’s developer guide sets default limits per user and app, by API group. As of October 2026, that is 10 requests a minute for Heavy calls, 40 for Medium and 50 for Light, with a 60-second penalty when exceeded, so bulk call-log pulls need queues and backoff.

On the Salesforce side, batch writes and watch your daily API allocation. Our Salesforce API integration guide covers that part in detail.

Pushing missed calls into a custom object is a one-way job; keeping calls, contacts and dispositions in step both ways is a two-way sync. The API integration cost guide behind these ranges breaks down what drives each. Comparing phone vendors? See our Zoom Salesforce integration and CloudTalk Salesforce integration guides, and the Salesforce integration guide for the wider picture.

Go-live checklist

Before reps lose their desk phones, check the list below. Don’t skip the last item: it decides whether this setup still works after Open CTI retires.

FAQ

Where Gilzor fits

Because Open CTI is retiring, a RingCentral setup chosen today should keep working after the cutoff. Gilzor is a software development company in Poland and Cyprus that builds and maintains Salesforce integrations.

We can agree call and SMS logging rules with your sales and ops leads, configure the RingCentral app, plan the move off Open CTI, or build a custom integration on the RingCentral and Salesforce APIs. We also support it after launch; see Salesforce integration services for how a project is scoped.