We performed a comparison between JIRA Service Management and Salesforce Service Cloud based on real PeerSpot user reviews.
Find out in this report how the two Help Desk Software solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."This service management solution has a good user interface. It helps improve your IT request requirements and makes tracking requests easier."
"JIRA SD also helps for much better feedback on the work being done. All colleagues can see what is happening."
"The platform is easy to use."
"There are two things that I value very much about this product. One is the service levels management – the SLA agreement management part of it – and knowledge management."
"I like the precise ticket management capabilities. JIRA Service Management is easy to use as well."
"Its integration is most valuable. It is pretty open for integration."
"Easily integrates with other tools."
"The links between the help desk and Jira issues and between Confluence and Jira issues are most valuable. I can write requirements in Confluence and link them to user stories in Jira and test cases. I can see my test coverage and all that kind of stuff. The integration between these three is very useful. It is pretty customizable, and it integrates well. There are a lot of add-ins and a lot of connectors to third-party products. In my last company, we used Test Royal for managing all the tests, and it integrated perfectly with that. For any issue or bug, we could see what tests have been run and the complete history of the tests."
"We use Salesforce Service Cloud for lead management and opportunity management."
"The strength lies in its ability to work cohesively with other systems, creating a centralized hub that enhances efficiency and collaboration across various functionalities within our organization."
"It's a cloud tool, so it is easy to set up."
"The product's initial setup phase was straightforward."
"The most valuable feature of Salesforce Service Cloud is its ease of use."
"The three major pillars of Salesforce Service Cloud are the SSL, Chatter, and the Dispatcher Console, which routes calls to the technicians."
"It’s feasible to configure the platform according to the specific processes utilised. Customization of the platform could be carried out based on the techniques we employ."
"The plug-ins that work with other standard systems have made the product industry-ready."
"SaaS version for large organizations (more than 2000 users) is not available."
"If we can have an easier way to deploy this solution without the help of a consultant and a more reliable way of deploying procedures, it would be quite helpful."
"The documentation needs improving, it's difficult to find specific procedures."
"It would be useful to be ale to link tickets across different gantt charts in Jira and Confluence."
"The solution needs to be integrated better with Office X5."
"Every time there's a problem with JIRA Service Management, you have to have a look at how to solve it, and there's always a feature request or the feature request on the solution is too large and the development cycles are too slow."
"The way it handles subtasks can be improved. We would really like the ability to have different types of subtasks. If we have a user story for a feature, we would like to have a subtask for documentation, a subtask for requirements, a subtask for development, and a subtask for testing. Right now, we just make four subtasks, but there is no way to specify their type, so we have to add a custom field to specify what type of work is this. It just means you've got to look at more data. For logging time or time tracking, we would like to have something using which we can define the work type we're doing. We would like to log whether we're working on a bug, a new development, scope change, or rework. We've got a user story for which we do the dev, and then we have to do more dev. It is the same story, but some of it could have been a scope change, and some of it could be a rework because we either screwed up the first time or missed something obvious. Currently, we have to have a custom field and track that separately. It would be nice to have some kind of work type for logging time."
"The product could improve its asset management."
"The product should be capable of delivering complex reports as per company requirements without the need for a Tableau license."
"There is room for improvement in pricing."
"The integrations with other solutions can be improved."
"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 main concern for me revolves around the speed of certain integrations."
"The product's high price is an area of concern where improvements are required."
"Salesforce should include maps as a default offering so that, as a customer, I can view where the technician is on the geographical map."
"The documentation could be improved."
JIRA Service Management is ranked 2nd in Help Desk Software with 73 reviews while Salesforce Service Cloud is ranked 9th in Help Desk Software with 38 reviews. JIRA Service Management is rated 8.2, while Salesforce Service Cloud is rated 8.6. The top reviewer of JIRA Service Management writes "Customizable, stable, and integrates well". On the other hand, the top reviewer of Salesforce Service Cloud writes "High scalability with good plugins and excellent customer visibility". JIRA Service Management is most compared with ServiceNow, ManageEngine ServiceDesk Plus, BMC Helix ITSM, Freshdesk and HaloITSM, whereas Salesforce Service Cloud is most compared with ServiceNow, Microsoft Dynamics CRM, Vlocity, BSI and BMC Helix ITSM. See our JIRA Service Management vs. Salesforce Service Cloud report.
See our list of best Help Desk Software vendors.
We monitor all Help Desk Software reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.