Should Salesforce acquire RingCentral?

Every few years, the SaaS world dusts off a favorite bar-stool question:
should Salesforce buy RingCentral? Back in 2016, SaaStr founder
Jason Lemkin’s answer was basically, “interesting idea, but nah” mostly
because RingCentral looked too SMB and too far away from Salesforce’s
enterprise center of gravity at the time.

Fast-forward to 2025 and the landscape looks very different. Salesforce has
swallowed Slack, Tableau, MuleSoft and (pending approvals) Informatica,
and is busy turning itself into an AI-first customer platform.
RingCentral, meanwhile, has grown into a multi-billion-dollar
communications-as-a-service (UCaaS/CCaaS) leader with deep partnerships
across the industry and a mature integration with Salesforce CRM.

So is it time for a different answer? Let’s look at how both companies have
evolved, what a deal would actually buy Salesforce, and whether the upside
justifies the pain (and the price tag).

From “too downmarket” to serious contender

In the original SaaStr Q&A, Lemkin argued that while RingCentral was a
solid, fast-growing company (then around $300 million in revenue), it sat
below Salesforce’s sweet spot. Salesforce was leaning into larger
enterprise deals and strategic platforms, not buying pure-play phone
systems for SMBs.

Since then, RingCentral has done some growing up:

• By full year 2024, RingCentral posted roughly $2.4 billion in
  revenue, with about 9% year-over-year growth and subscription
  revenue making up more than 95% of the total.
• In Q4 2024, revenue reached $615 million with free cash flow margins in
  the high teens, and guidance for 2025 calls for mid-single-digit revenue
  growth with improving operating margins.
• S&P Global recently upgraded RingCentral’s credit rating to
  BB+, citing steady mid-single-digit growth and expanding
  free cash flow.

That’s not hyperscale startup growth anymore, but it’s a meaningful, sticky
subscription business with real cash generation exactly the kind of
profile that can interest an acquirer like Salesforce when it’s thinking
about accretive M&A.

Where Salesforce is heading: AI, data, and the customer graph

To understand whether Salesforce should acquire RingCentral, you
have to understand what Salesforce is optimizing for in 2025.

Historically, Salesforce used acquisitions to bolt on strategic clouds:
MuleSoft to connect data and systems, Tableau
for analytics, and Slack as the “digital HQ” for enterprise
collaboration.
The recently announced $8 billion acquisition of Informatica
doubles down on data management and AI readiness: Salesforce wants to own
more of the data plumbing that feeds Einstein and its Agentforce AI agents.

In other words, Salesforce’s North Star right now is:
“Every customer interaction becomes AI-ready data inside Customer 360.”

Voice calls, SMS, and contact center interactions are a big piece of that
puzzle which is exactly why RingCentral looks tempting.

How RingCentral and Salesforce already fit together today

Before we jump to mergers and acquisitions, it’s worth remembering that
Salesforce and RingCentral already play very nicely together.

• RingCentral for Salesforce embeds calling, texting, and
  call logging directly inside Salesforce, letting reps click-to-dial,
  capture notes, and auto-log interactions without leaving the CRM.
• RingCentral RingCX for Salesforce Voice integrates with
  Service Cloud Voice, pulling telephony into the same console agents use
  for cases and chats.
• On the UCaaS/CCaaS side, RingCentral also powers cloud solutions for
  Avaya and Mitel, and integrates with
  Microsoft Teams and Zoom which gives it reach into huge existing
  enterprise footprints.

For customers, that means many can already get an end-to-end experience:
Salesforce as the system of record, RingCentral as the communications
fabric, and an AppExchange integration doing the glue work.

Arguments for a Salesforce–RingCentral deal

1. A stronger answer to Microsoft and Zoom

Microsoft has an increasingly tight story: Dynamics 365 + Teams +
Azure AI. Zoom is pushing deeper into contact center, phone, and
productivity. A Salesforce + Slack + RingCentral combo
would give Salesforce:

• A full-stack customer engagement platform from CRM to contact center.
• Native voice, video, and messaging across sales, support, and success.
• Richer conversational data for AI models and analytics.

Instead of “We integrate with your phone system,” Salesforce could
credibly say, “We are your phone system, your digital HQ, and your
customer data brain.”

2. Unified data for Einstein and Agentforce

RingCentral generates enormous volumes of structured and unstructured data:
call metadata, recordings, transcripts, SMS threads, voicemail, and more.
Plug all of that directly into Salesforce’s Customer 360 graph and good
things happen:

• Sales coaching based on actual call transcripts, not just CRM notes.
• Support automation that “listens” to real conversations, not only tickets.
• AI agents that can act on nuance: tone, intent, sentiment, and the
  actual words customers used on calls.

Salesforce’s recent moves with Informatica show how serious it is about
controlling data pipelines. Owning RingCentral would extend that control to
one of the most important data sources of all: the customer’s voice.

3. Revenue and margin synergy

RingCentral has shifted from a “grow at all costs” mindset toward
profitable growth, with expanding operating and free cash flow margins.

If Salesforce can:

• Cross-sell RingCentral into its own enterprise base, and
• Use its scale to reduce overlapping G&A and go-to-market costs,

then the acquisition could be financially attractive, especially if done
at a reasonable multiple versus historical high-growth SaaS valuations.

4. Simplified buying for customers

Ask any CIO what they like less than surprise AWS bills, and they’ll say
“more separate contracts.” A combined Salesforce–RingCentral stack could:

• Consolidate vendors and billing under a single master agreement.
• Offer unified SLAs for CRM + contact center uptime.
• Make procurement, compliance, and renewals less of a headache.

For large, global customers, that is a very real selling point.

Arguments against the acquisition

1. It distracts from Salesforce’s AI and data strategy

Salesforce is re-entering “big deal” territory with Informatica after a
period of discipline under pressure from activist investors.
Its story to Wall Street is about focus: tighten expenses, drive margins,
and invest where AI and data give Salesforce a durable moat.

RingCentral is, at its core, a communications network and UCaaS platform.
Owning it would mean:

• More capex-heavy infrastructure to manage.
• Regulatory and telecom complexity in multiple regions.
• A new set of competitors (telcos, UCaaS vendors) to worry about.

That’s a lot of operational brain space to spend on something that
Salesforce can already access via integrations.

2. Ecosystem and channel conflict

Today, RingCentral partners deeply with Avaya and Mitel, and integrates
with Microsoft Teams and Zoom.
That ecosystem works precisely because RingCentral is (relatively)
vendor-neutral.

If Salesforce bought RingCentral, several awkward questions appear:

• Do Avaya and Mitel really want their strategic UCaaS partner owned by a
  CRM vendor that also competes for wallet share?
• Does Microsoft keep leaning into Teams + RingCentral integrations if
  RingCentral is part of a major competitor to Dynamics?
• How do other telephony and CCaaS partners on the Salesforce AppExchange
  feel about Salesforce suddenly favoring its own in-house solution?

One of Salesforce’s big strengths has always been its ecosystem.
Buying a major UCaaS player risks spooking that ecosystem and driving
partners toward neutral alternatives.

3. Investor optics and “one more giant deal” fatigue

After the expensive Slack acquisition and years of integrating multiple
large purchases, Salesforce faced serious pushback from activist
investors, who questioned whether big-ticket M&A was really paying off
in operating leverage and growth.

Dropping another multi-billion-dollar deal on RingCentral, while still
digesting Informatica and optimizing Slack and Tableau, would be a hard
sell unless the strategic rationale and financial model were
crystal clear.

4. The “good enough” factor of today’s integration

For a large chunk of customers, the current Salesforce–RingCentral
integration is already “good enough”:

• Click-to-dial inside Salesforce.
• Automatic call logging and activity creation.
• Screen pops with customer details for inbound calls.

Many buyers don’t actually need Salesforce to own the phone
system; they just need it to work, be stable, and feed data into reports
and AI models. That’s an integration and partnership problem, not
necessarily an M&A problem.

What customers really care about

Talk to line-of-business leaders and you’ll notice something: very few wake
up asking, “Has Salesforce bought my phone vendor yet?” They care about:

• Agent productivity – fewer clicks, fewer tabs, faster
  wrap-up time.
• Data quality – every customer interaction logged
  correctly and searchable later.
• Insights – call analytics, coaching, churn risk, and
  opportunities surfaced automatically.
• Reliability – calls don’t drop, queues behave, and SLAs
  are met.

All of that can be delivered via tight integration, shared product
roadmaps, and co-innovation without necessarily combining balance
sheets.

The middle path: deeper partnership instead of acquisition

There’s a strong argument that the best move for Salesforce and RingCentral
is not a full acquisition, but a “more than partner, less than
merger” relationship.

That could look like:

• Even tighter Service Cloud Voice and RingCentral
  alignment, with AI-driven routing and analytics built jointly.
• Revenue-sharing or co-selling agreements for strategic enterprise
  accounts.
• Technical roadmaps coordinated so RingCentral features are “Salesforce
  first” in terms of APIs, objects, and AI hooks.
• Possibly a minority investment from Salesforce to
  signal long-term commitment without triggering a full takeover.

This keeps the ecosystem open, lets RingCentral maintain neutral
partnerships with players like Avaya and Mitel, and still gives Salesforce
the deeply integrated voice layer it wants for Customer 360 and Einstein.

So… should Salesforce acquire RingCentral?

If you love clean narratives, the answer “yes” is tempting. The idea of
Salesforce owning CRM, collaboration (Slack), analytics (Tableau), data
integration (MuleSoft, Informatica), and communications (RingCentral) makes
for a great conference slide.

But when you factor in Salesforce’s current AI-and-data focus, partner
ecosystem dynamics, investor expectations, and the strength of the existing
integration, the more realistic answer at least right now is:

No, Salesforce probably shouldn’t acquire RingCentral today.

This doesn’t mean the idea is permanently off the table. If the UCaaS/CCaaS
market consolidates, if voice and contact center become the clear bottleneck
in Salesforce’s AI strategy, or if RingCentral’s valuation and trajectory
align perfectly with Salesforce’s M&A appetite, the discussion could
look very different.

For the moment, though, a deeper strategic partnership is
likely the smarter play: customers get tighter integration, Salesforce
stays focused on AI and data, RingCentral keeps its ecosystem reach, and
everyone avoids yet another multibillion-dollar digestion project.

Practitioner experiences: what real teams have learned

It’s one thing to sketch strategy on a whiteboard; it’s another to live it
in a real-world rollout. Here are composite experiences (based on common
patterns from Salesforce–RingCentral deployments) that reveal what actually
matters on the ground.

1. The mid-market SaaS company that chased “one throat to choke”

A mid-market SaaS provider with a few hundred employees wanted to simplify
its tech stack. The CIO’s dream was “one throat to choke” one vendor for
CRM, collaboration, and telephony. On paper, that sounded great. In
practice, the team discovered a few wrinkles:

• Their sales team already lived in Salesforce and Slack, but the support
  team used a mix of voice tools and legacy on-prem PBX hardware.
• When they tried to standardize on a single communications provider, they
  underestimated how tightly voice workflows were tied to day-to-day
  operations (particularly in support queues and escalation paths).
• The project bogged down not because of vendors, but because change
  management around call flows and staffing wasn’t planned deeply enough.

The lesson they drew later: logo consolidation matters less than workflow
design. Whether Salesforce ever owns RingCentral is secondary to whether
the integration is configured around how reps actually sell and support.

2. The global retailer that went “integration first”

A global retailer with operations in North America and Europe took the
opposite approach. Instead of standardizing on a single vendor, they
decided first to standardize on a data and process model in
Salesforce:

• One global lead and account model.
• Unified case taxonomy and escalation rules.
• Common reporting definitions for sales and support KPIs.

Only after that did they roll out RingCentral integrated into Salesforce
for their contact centers. Because the data model was aligned up front, the
integration felt almost invisible to agents. Calls popped with the right
context; activities and cases were logged consistently; and analytics
actually matched what leadership saw in their dashboards.

When executives later heard industry chatter about a hypothetical
Salesforce–RingCentral deal, their reaction was basically: “As long as
someone keeps these APIs online and our agents don’t lose their screen-pops,
we’re fine.” Ownership was a distant second to stability and clear
responsibilities.

3. The startup that underestimated voice complexity

A fast-growing startup decided to “turn on phones in Salesforce” using a
cloud telephony provider. They assumed it was a weekend project. Then they
ran into:

• Regulatory rules on call recording in different states and countries.
• Routing logic that had to respect time zones, skills, and VIP customer
  tiers.
• The need for robust disaster-recovery plans if call centers in one region
  went offline.

Their post-mortem conclusion: voice is its own craft. The idea of folding a
full UCaaS/CCaaS provider into a CRM company sounds neat, but the
operational realities are intense. For them, a strong specialized partner
deeply integrated with Salesforce was preferable to Salesforce trying to
reinvent telephony in-house.

4. A Slack lesson that still lingers

Many Salesforce customers watched the Slack acquisition with interest.
Internally, a common sentiment emerged: “Slack as part of Salesforce is
powerful, but culture and product fit take time.” Some features shipped
fast; others required long integration cycles and changes to how teams
worked.

That experience colors how they think about any future mega-deal. When you
ask them, “Should Salesforce acquire RingCentral?” they don’t immediately
say yes. Instead, they ask:

• Will my agents see a better console this year, or in three years?
• Do I lose options if I don’t like the combined roadmap?
• Will pricing stay predictable, or will it be bundled into a giant SKU?

For many practitioners, the “integration first, ecosystem friendly” path
feels safer than a giant merger that might introduce years of flux.

Taken together, these experiences support a pragmatic view: the real value
is in aligned roadmaps, deep integrations, and clear accountability
for outcomes. Whether or not Salesforce owns RingCentral’s stock
certificate matters far less than whether Salesforce customers get
reliable, AI-ready voice data and smooth workflows.