RingCentral ↔ Salesforce integration

Calls and messages from RingCentral are logged on Salesforce records by themselves, missed calls become tasks, and the rep dials from the record with the client's card already open

The sales team talks to clients through RingCentral and keeps deals in Salesforce, but the two do not know about each other: after each call the rep writes a note by hand, missed calls live only in the phone log, and the manager cannot see which opportunities have had no contact for a month. The RingCentral ↔ Salesforce pair writes every call and text message to the right lead, contact or opportunity, turns a missed call into a task for the owner, and lets the rep dial straight from the record. Below: what exactly moves, which scenarios we cover and which capabilities of both systems we rely on.

Request an integration System page: RingCentral →System page: Salesforce →

What moves between the systems

RingCentral → SalesforceEvery finished call is written to Salesforce as a completed activity on the lead, contact or opportunity found by the phone number: direction, duration, the rep and a link to the recording if it exists.
RingCentral → SalesforceA missed inbound call from a known number becomes an open task for the record owner with a due date, so it is called back rather than forgotten.
RingCentral → SalesforceA call from an unknown number creates a new lead in Salesforce with the number and the time, so a first-time caller is not lost.
RingCentral → SalesforceText messages sent and received through RingCentral are attached to the same record as a thread, so the conversation is visible next to the calls.
Salesforce → RingCentralThe rep starts a call from the lead or contact page in Salesforce, and RingCentral dials from their own extension; the call is logged back the moment it ends.
Salesforce → RingCentralNames and companies from Salesforce are shown to the rep on an inbound call, so they greet the client by name before picking up.

What we connect

We agree on the rules: which records a call is matched to when a number belongs to both a lead and a contact, who owns a lead created from an unknown number, and which calls are not logged (internal, shorter than a few seconds).
The Salesforce administrator registers the exchange as an external client app with access only to activities, leads, contacts and opportunities; the rep's own login is not used.
In RingCentral the administrator adds the exchange as an application with rights to read call logs, recordings and messages and to place calls on behalf of the users who opted in.
We map RingCentral extensions to Salesforce users, so each call lands on the right rep and the manager's reports show who talked to whom.
We set the rhythm within RingCentral's per-minute request ceilings: call logs are read in batches every few minutes, and the exchange waits exactly as long as RingCentral asks when a ceiling is reached.
We test in a test copy of Salesforce with two reps and a day of real calls, check the activities with the sales lead, and only then switch to the production org.

Automation scenarios

Notes written from memory

Before the rep makes twenty calls a day and logs six of them in Salesforce, from memory, in the evening.

After every call is on the record within minutes with duration and recording, and the rep only adds a line about what was agreed.

Missed call, lost deal

Before a client calls back about a quote, nobody picks up, and the missed call sits in the phone log until Monday.

After the missed call is a task on the opportunity for its owner with a due date today, and the manager sees it on the dashboard.

«Who is calling?»

Before the rep sees only a number, picks up, asks the client to repeat the company name, and then searches Salesforce.

After the name, company and open opportunity appear with the ringing call, and the record is open before the greeting.

Report with no calls in it

Before the sales lead counts calls from RingCentral and deals from Salesforce in two windows and cannot connect them.

After calls are activities on opportunities, and one Salesforce report shows calls per rep, per stage and per week.

How it works technically

For those who want to check: each point links to the official documentation page it comes from.

Every method of RingCentral's interface belongs to one of several request groups, so the platform can better distribute load and protect itself.
Source: developers.ringcentral.com ↗ checked 2026-09-25
Default ceilings per group, per user per minute: Light 50, Medium 40, Heavy 10, and Auth (signing in) just 5 — each with its own 60-second penalty window.
Source: developers.ringcentral.com ↗ checked 2026-09-25
Going over the ceiling returns a Too Many Requests error, and the exact number of seconds to wait before trying again is stated right in the response.
Source: developers.ringcentral.com ↗ checked 2026-09-25
REST API gives programmatic access to Salesforce records, metadata and search without using the Salesforce interface itself.
Source: developer.salesforce.com ↗ checked 2026-09-25
Access is authorised through OAuth 2.0 via a Connected App or External Client App; since Spring '26, creating new Connected Apps is restricted and Salesforce recommends External Client Apps instead (existing Connected Apps keep working).
Source: developer.salesforce.com ↗ checked 2026-09-25
Open CTI, Salesforce's built-in telephony integration layer, is in maintenance mode and scheduled for retirement in February 2028; Salesforce recommends moving new development to Salesforce Voice.
Source: developer.salesforce.com ↗ checked 2026-09-25

Limits

The limits come from both systems. RingCentral meters requests per user per minute by groups, and sign-in attempts are metered most strictly, so call logs are read in batches and a large team is spread over several minutes; a call therefore appears on the record within minutes, not at the same second. A call from a number kept in Salesforce in a different format is matched only after numbers are normalised, which we do at setup. The on-screen pop-up for inbound calls is built outside the retiring Open CTI layer, so it keeps working after 2028. Recordings stay in RingCentral; Salesforce receives a link, not the file.

How to start

Three steps from a first message to work on your project.

01
Leave a request
Describe the task in the form — in text or by voice. Budget and timing are optional.
02
We review and estimate
A developer studies the brief, asks about anything unclear and sends an estimate.
03
We start
Once scope and price are agreed, the work begins.

Leave a request

or write to info@coreviaflow.space

Live project We built and run Gemalli — a B2B export platform with producer pages, a CRM and a deal chat. Read the case →

Questions

RingCentral has its own Salesforce app. Why build anything?

Often nothing needs building: if the vendor app covers your rules, we set it up and stop there. We build only the parts it does not do for you: your own matching rules, tasks from missed calls with your due dates, leads from unknown numbers with your ownership rules, and reports the way your sales lead reads them.

Can we log calls only for the sales team, not for support?

Yes. The exchange works per extension: only the extensions mapped to Salesforce users are read, other extensions of the company are not touched.

Does the rep need to install anything?

No. Calls are logged on the server side regardless of the device the rep uses. Dialing from the record and the inbound pop-up are added to the Salesforce page itself and open the RingCentral app the rep already has.