ServiceNow was chosen as replacement for Microsoft Project , due to better licensing model, more flexible configuration of the project stages and components, better API with Azure DevOps. Also ServiceNow is best in the area of Incident and Service management systems and the …
I've used Freshservice which is very similar to ServiceNow. I can definitely say ServiceNow performs better in a larger environment. Freshservice is usually used in smaller organization or less complx environment. Plus the ServiceNow reporting and dashboard features are more …
I used ConnectWise previously as a ticketing module prior to a company acquisition where our new parent company moved us from ConnectWise to ServiceNow Now Platform because it was the tool they were using. All of our core functionality remained in moving between the tools, …
The ServiceNow Now Platform is more customizable to meet your organization's specific needs and expectations. However, if you need a system that is already specialized for a specific application, you may choose something else like IBM solution. A good price offer or partnership …
After running with the BMC platform for over a decade, we switched to ServiceNow Now Platform for multiple reasons. It's placement over BMC in the Gartner Magic Quadrent, it's ease of use and development were among the top reasons. In my opinion, BMC has not aged/grown well …
ServiceNow is by far a better tool over Remedy. Its ability to integrate so seamlessly to so many tools allows for plenty of opportunity to streamline and improve processes. Servicenow has intuitive flows that allow you to quickly pivot if process change. Its adaptiveness is …
When I assumed my territory (Brazil) at Nuvolax, ServiceNow Now Platform was already implemented, so I haven't had the choice to participate in the selection of the tool. Still, I can compare with other tools I had to use in my previous companies. With ServiceNow Now Platform, …
In the past, I've used Remedy and the organization was using Spiceworks for years. I was so used to those platforms that when we started the search, I was honestly, completely biased towards those two. After comparing features side by side, going through user trials and …
Using it in the application support team is worth it as it is capable of carrying a lot of information. But using it for a Service Desk operation might not be of much use as it won't be used up to its full potential and will be costly as compared to other alternatives available in the market.
Providing admins/devs with easier mechanisms for providing businss stakeholders with self-service admin capabilities across the platform
Tutorials on how to be the best at reporting in servicenow
Guided tour functionaltiy is a bit rigid and could use more workflow capabilities
Making it easier to push form variables to the user so there is more context when providing an approval. The out of box approval UI/form is terrible in my opinion.
While we are very likely to renew, we are also assessing if we should renew all of what we currently subscribe to as we try to reduce costs. Some parts of the business feel there may be a better tool out there to fit their process requirements. We are currently working with them to identify what those requirements are to see if it makes sense while also pointing out a reduced cost of tooling is not always the best fit if we have an increased cost of customization and maintenance between tools.
ServiceNow is a web platform that does not require any installation on a customer's computer. It is very easy to use and it is user-friendly. The customer started to open incidents very fast without investing time and money in training. Customer loves the dashboard at the startup where they can see all their open incidents or look at KB articles for any issue.
The platform is provided as a SaaS solution and support from the vendor has been good. There are regular software releases with bug fixes, new features and enhancements, and furthermore we are given the opportunity to fully test these before rolling these new releases out into the production environment to minimise the risk of business disruption
We went through a re-implementation last year with a partner and were very pleased with the outcome. We looked at several partners and chose one that was able to provide an entire scope and cost upfront of what would be required to complete our requirements. We worked very closely with the dedicated team assigned to our project throughout the process and they fully delivered on all of our requirements that we presented in the initial scope.
ServiceNow was chosen as replacement for Microsoft Project , due to better licensing model, more flexible configuration of the project stages and components, better API with Azure DevOps. Also ServiceNow is best in the area of Incident and Service management systems and the proof of concept with Jira and incident.io were not successful and we kept relying on ServiceNow. ServiceNow is much more scalable than MS Project for constantly growing enterprise companies for both employee and external contractor type personas.
The biggest positive impact ServiceNow has made to our organization is reduced IT support cost. When we didn't use ServiceNow, we needed a bigger support team. Now we don't need as many support employees.
The other positive impact that I've noticed is faster solutions to any problems. ServiceNow makes very easy to resolve IT issues, in a efficient way. The tickets are organized in a way that the higher priority tickets get worked on quicker.
The dashboard has also made the job easy to find a recurring problem from its core and fixing it forever so that we don't repeatedly get the same issues again and again