Salesforce is starting to talk about IT service management (ITSM). References to ITSM are now showing up in Service Cloud messaging and its “Agentforce” artificial intelligence (AI)-building platform positioning. So far, it has been relatively low-key in my opinion: a Dreamforce announcement (that created a buzz), a few posts, a video, and a landing page that feels more like a placeholder than a full strategy.
It looks less like a bold announcement and more like a quick response to ServiceNow’s move into customer relationship management (CRM). The question is whether Salesforce’s entry into ITSM will have a real impact.
Messaging That Misses the Mark
Stephen Mann has already called out Salesforce’s “What is ITSM?” page on LinkedIn for missing basic concepts. After all, who’s heard of the “4 stages of ITSM processes” described on this Salesforce page?
That lack of clarity, and I think this is describing it kindly, signals inexperience. Buyers notice (or at least, should notice) when a vendor doesn’t demonstrate a genuine understanding of the space.
Would you risk your organization’s IT service delivery and support on a vendor that states the “4 stages of ITSM processes” are:
- Incident management
- Problem management
- Change management
- Release management?
Whoever (or whatever) wrote the Salesforce “What is ITSM?” page must have slept through the last 36 years of ITIL (or framework-agnostic ITSM best practices).
Yes, Salesforce can quickly bring in ITSM expertise. However, credibility takes time to establish, and currently, Salesforce has little history in ITSM.
Why Salesforce ITSM Could Still Gain Ground
Despite this, Salesforce brings two major advantages:
- Scale and brand power – Millions of customers and a marketing engine that can quickly put ITSM in front of executives.
- The CFO conversation – For organizations already heavily invested in Salesforce, the argument “Why pay for another tool if we can extend Salesforce?” will carry weight, especially under budget pressure.
As Ian Aitchison and Barclay Rae mentioned in their Enterprise Digital podcast, this opportunity (or distraction) sets up internal conflict. Finance leaders may push for tool consolidation, but IT teams will question whether Salesforce can match the capabilities of tools like ServiceNow.
The Risk for Enterprises
If cost consolidation drives the decision, organizations risk trading mature ITSM capabilities for a tool that may not yet be ready for enterprise use. This could result in reduced service quality, frustrated end-users, and increased operational costs in the long run. Effectively costing an organization more than it originally saved.
What Comes Next with Salesforce ITSM
Salesforce has the reach and resources to secure early adoption, particularly with existing customers. However, whether they can establish enough credibility and capability to compete with established ITSM players (such as those listed here) remains an open question.
This move could become a genuine market disruptor, or it could be remembered as another vendor expanding into ITSM without the depth of knowledge and expertise needed to succeed.
What’s your view on Salesforce ITSM? Real disruption, or just noise? Please let me know in the comments.
Sophie Danby
Sophie is a freelance ITSM marketing consultant, helping ITSM solution vendors to develop and implement effective marketing strategies.
She covers both traditional areas of marketing (such as advertising, trade shows, and events) and digital marketing (such as video, social media, and email marketing). She is also a trained editor.
One Response
🚨 Salesforce just entered ITSM.
But here’s the real question:
Why are we still calling it IT Service Management at all?
Service is not an IT thing.
It’s an enterprise thing.
HR, Finance, Facilities, Customer Service — they all manage incidents, changes, and requests. Slapping “IT” on the front just guarantees more silos, more tool wars, and more confusion.
Maybe Salesforce should stop chasing IT’s rabbit hole of complexity…
…and start asking business stakeholders what they really need from service management.
That’s where the real value is created.
And that’s why the future isn’t ITSM.
It’s USM — Unified Service Management.
One system.
One language.
For the entire enterprise.