No more typing reviews! Try our Samantha, our new voice AI agent.

Rootly vs Salesforce Service Cloud comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Rootly
Ranking in IT Alerting and Incident Management
5th
Average Rating
8.0
Reviews Sentiment
5.6
Number of Reviews
4
Ranking in other categories
No ranking in other categories
Salesforce Service Cloud
Ranking in IT Alerting and Incident Management
12th
Average Rating
8.4
Reviews Sentiment
6.9
Number of Reviews
58
Ranking in other categories
CRM Customer Engagement Centers (2nd), Help Desk Software (9th), Knowledge Management Software (6th)
 

Mindshare comparison

As of August 2026, in the IT Alerting and Incident Management category, the mindshare of Rootly is 3.1%, down from 10.0% compared to the previous year. The mindshare of Salesforce Service Cloud is 2.1%, up from 0.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Alerting and Incident Management Mindshare Distribution
ProductMindshare (%)
Rootly3.1%
Salesforce Service Cloud2.1%
Other94.8%
IT Alerting and Incident Management
 

Featured Reviews

Luis Vasconcelos - PeerSpot reviewer
System Architect at CI&T
Centralized incident workflows have improved visibility and streamlined communication across teams
Rootly helps me handle those issues by using a predefined template to define roles inside the workflow and utilizing a basic flow, which is very short in its lifecycle. The most powerful feature of Rootly is its visibility; we can create a dashboard and integrate with Slack and Jira, for example, automating many steps in the follow-up process, which helps to centralize all communications around issues. The best features Rootly offers include communication capabilities, particularly the integration with Slack, which stands out for me because it allows for very clean and direct communication with all clients and even with the resolution area. The Slack integration helps my team by creating a specific resolution group and an automation channel inside Slack once an incident is opened in Rootly, ensuring that everyone knows when a new incident arises. It is not just a notification; we create a group where all the relevant people can help solve the issue quickly. The workflow capability of Rootly to create flows is another key feature for our operation, allowing us to establish specific rules for incidents in Jira or manage the metrics we need during the incident lifecycle, effectively automating many manual processes. Rootly has positively impacted my organization, and we have measured its impact by analyzing the number of incidents we handle over a period. With the strategic approach of putting everyone in a Slack group to resolve incidents, we have reduced the percentage of incidents created in a month by thirty percent during the first three months of using Rootly. Other positive outcomes include time savings and improvements in collaboration; the groups inside Slack enable people to communicate across different areas and work directly with client operations, creating synergy and a strong integration between teams.
ManchikatlaShravani - PeerSpot reviewer
Salesforce Consultant at BYTENET
Omni-channel routing has transformed case handling and now supports complex field operations
From my experience, we might need queue-based alignment in Omni-Channel routing. Assignment rules should be defined at the flow level. The challenge with SLA creation is evident in escalation rules, which should include a field flagging feature that is lacking in the current setup. Einstein Bot, linked with Omni-Channel messaging, is complex to define, with a need for all related information in one place, making the process cumbersome. Understanding which bot is associated with specific messaging apps requires manual searching, and this can be improved.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Rootly has positively impacted our organization because, in comparison to ObsGenie, the tool we used before Rootly, it is much more user-friendly, including the user interface and the whole approach to alerting and routing these alerts."
"Rootly has positively impacted my organization by allowing us to receive the on-call alerts successfully, whereas before Rootly, we had issues missing alerts."
"Rootly has positively impacted my organization by saving time with manually adding timelines, as they are already built in when timelines are added in Slack through integration."
"With the strategic approach of putting everyone in a Slack group to resolve incidents, we have reduced the percentage of incidents created in a month by thirty percent during the first three months of using Rootly."
"Salesforce Service Cloud is a user-friendly and flexible CRM tool that provides good accessibility and security."
"Our users are satisfied with the product, and they spend less time on this tool, but create more opportunity and other data."
"I don't have the specific details, but I'm aware that Salesforce is used for campaigns, decision-making processes, and order submissions. I'm currently in the learning phase and not familiar with all the details."
"The complexity of the solution is very less."
"Salesforce accelerates time to market and streamlines workflows through automation. Integrating with other software systems, such as HR or ERP platforms, allows for seamless data exchange and enhances efficiency."
"The plug-ins that work with other standard systems have made the product industry-ready."
"The built-in, ready-to-go package of case management, email management and social media management with a knowledge base helps to speed up the implementation time."
"I would rate the support received from Salesforce of the highest caliber, as they are very responsive and helpful and even sent a Product Director on-site to work with us on a particularly difficult issue."
 

Cons

"The integration process could be easier, perhaps with the addition of AI to facilitate smoother integrations with other applications, especially since those who manage integrations often need technical knowledge about web services and single sign-on processes, which can be challenging for non-technical users."
"Regarding Rootly's AI capabilities, we had one incident when we lost alerting generally because Rootly crashed, and we did not like it."
"There are a few areas where Rootly can be improved."
"There are elements of Service Cloud which cannot be smoothly migrated from sandbox environments to production, leading to manual steps in a deployment."
"The solution could continue improving its artificial intelligence capabilities."
"I'm not deeply engaged with this team, so I don't have extensive experience with it. As you mentioned, I haven't used it much yet, so my experience is limited."
"The product should be capable of delivering complex reports as per company requirements without the need for a Tableau license."
"There's an issue where creating a repetitive appointment creates two appointments on the first occurrence."
"UI/UX has always proven difficult to keep up with. Salesforce, in general, requires a continued training effort to keep people up to speed and to encourage adoption in the tools."
"Einstein Bot, linked with Omni-Channel messaging, is complex to define, with a need for all related information in one place, making the process cumbersome."
"The documentation could be improved."
 

Pricing and Cost Advice

Information not available
"Salesforce is not a cheap product. It can be expensive."
"We pay a yearly licensing fee for Salesforce Service Cloud, which is expensive."
"The price of the solution depends on how many users need access to it"
"The solution is priced at 50 dollars a month per user."
"The licensing is flexible. Companies pay for what they use. However, a company with very small needs might find it difficult to justify the cost. Overall, it's in the medium price range."
"Only enterprise businesses can afford the solution, and small companies cannot afford it."
"I believe that in our country, Colombia, we utilize this platform for the Latin American region. In terms of expenses, it's somewhat higher compared to other products. I would rate it as expensive and nine out of ten."
"Salesforce Service Cloud is a bit expensive."
report
Use our free recommendation engine to learn which IT Alerting and Incident Management solutions are best for your needs.
909,725 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Performing Arts
28%
Comms Service Provider
7%
Financial Services Firm
7%
Transportation Company
7%
Financial Services Firm
14%
Outsourcing Company
11%
Construction Company
8%
University
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business21
Midsize Enterprise13
Large Enterprise26
 

Questions from the Community

What is your experience regarding pricing and costs for Rootly?
Regarding my experience with pricing, setup cost, and licensing, we got a license for one year. Generally, it is great and the price is great, and that is the reason we chose Rootly. The only thing...
What needs improvement with Rootly?
There are a few areas where Rootly can be improved. More customization options for postmortem templates and reports would be helpful. Enhancing search functionality to make it easier to locate hist...
What is your primary use case for Rootly?
I use Rootly every day to manage the end-to-end incident lifecycle. When a critical incident is reported, I create or join an incident on Rootly, assign the appropriate severity, and engage the req...
What is your experience regarding pricing and costs for Salesforce Service Cloud?
I do not have knowledge of the setup cost as I do not look into pricing. Once the customer and my team discuss everything, I configure the system, but I do not have an idea about the pricing.
What needs improvement with Salesforce Service Cloud?
From my experience, we might need queue-based alignment in Omni-Channel routing. Assignment rules should be defined at the flow level. The challenge with SLA creation is evident in escalation rules...
What is your primary use case for Salesforce Service Cloud?
Currently, I work exclusively with Salesforce CRM and have not had the opportunity to work with HubSpot on any projects. I work with Sales and Service. I have more than five years of experience wit...
 

Also Known As

No data available
Service Cloud
 

Overview

 

Sample Customers

* **Atlassian** * **Cisco** * **Databricks** * **DigitalOcean** * **Google Cloud** * **IBM** * **JetBlue** * **LinkedIn** * **Lyft** * **Microsoft** * **MongoDB** * **Netflix** * **Pinterest** * **Qualcomm** * **Red Hat** * **Salesforce** * **Spotify** * **Square** * **T-Mobile** * **Twitter** * **Uber** * **VMware** * **WeWork** * **Workday** * **Xerox** * **Zoom**
Stanley Black & Decker, Coca-Cola, Activision, Wells Fargo, Spotify, Aldo, Philips, The Red Cross, Blue Shield of California, Sprouts Farmers Market, Direct Energy Solar, Inspirato, Kiva
Find out what your peers are saying about Rootly vs. Salesforce Service Cloud and other solutions. Updated: August 2026.
909,725 professionals have used our research since 2012.