Consultant at a comms service provider with 1,001-5,000 employees
Real User
Top 5
Nov 10, 2025
If I compare the interface of ServiceNow Orchestration with Boomi, it is easier to use Boomi than ServiceNow Orchestration. Boomi is an ESB with orchestration features to integrate and exchange data between applications, and it provides a more user-friendly experience than ServiceNow Orchestration.
Service Manager at a tech vendor with 1,001-5,000 employees
Real User
Top 10
Mar 28, 2025
The third-party integrations are challenging when the tools are not from ServiceNow ( /products/servicenow-reviews ) partners. This presents issues when integrating solutions from other vendors.
I remember last time I said there is no need for improvement. It's fine. Due to the limited scope, I cannot comment further. However, it should be integrated with AI and messaging or chatting features, which would be better.
ServiceNow Consultant at a tech services company with 1-10 employees
Reseller
Top 10
Jul 9, 2024
There is a lot of complexity in the platform, but that comes with the scalability. It is a highly complex platform to work on. There are changes in their workflow technology, and the flow technology improvements have introduced more complexity, in my view.
Solutions Architect at a financial services firm with 5,001-10,000 employees
Real User
Top 5
May 24, 2024
There is room for improvement in pricing. The initial setup is a bit challenging, only due to getting incorrect information from the client team. That’s the only issue, possibly. You have to read through your stuff because once the organization starts moving people around, management changes follow. The tools were set up to look up an organization that works a certain way. Now, you have to reset it to look up the new organization.
ServiceNow Orchestration needs to improve multiple aspects in which their event monitoring system is one. The solution lacks event monitoring systems which makes them non-competitive. They need to include improvements in a similar manner that they did in Sweden.
The automatic remediation needs enhancement, particularly integrating ServiceNow with tools like SolarWinds and Logic Monitor. It is functional, but it needs improvement.
Information Technology Specialist at a tech services company with 1-10 employees
Real User
Feb 13, 2023
I am not going to say dashboards as they are working significantly on it at the moment. They made huge strides for the last three versions in enhancing the workspace concept. With the new UI, enabling workspaces and dashboards is going to become much easier for all the modules. I am sure installation will follow that part. You can already spin up AWS servers, Azure, and VM services. From my space, the only thing that I can say is the spinning up with Google Cloud Services. I haven't personally tried it, so I don't know if it is working.
The solution is a bit rigid because it requires the completion of five steps in one direction. If you do not follow that order, you will not succeed. There is no flexibility when it comes to customer requirements. Orchestrations are very expensive and the cost overall needs to come down. The flow rate for releases and updates is very, very slow and does not meet customers' objectives for scalability. For example, changes in model numbers or products are not enabled for six months to a year because they are included only with new releases.
Business Manager, Cybersecurity & Network Practices at a computer software company with 1,001-5,000 employees
Real User
Oct 6, 2022
We have found some gaps in integration because all of our customers require niche tools. Different companies have different needs - I guess it's difficult to cover every use case.
The interface could always be improved. I would like a user experience module to be added. With different services that they are reporting, how can that be measured and what analysis can be done on the user experience? The cost could be lower.
Senior Manager - Retail Sales at a computer software company with 10,001+ employees
Real User
Jan 26, 2022
There is still room for more integrations. Or, it would be nice to bundle multiple products together rather than selling everything as a model as that turns out to be a bit costly.
When it comes to automation, to basic windows activity, there is room for adding some features. Even in the areas that relate to publishing there could be increased efficiency in areas such as helping with editing portals. Other areas where there might be improvement is in terms of handling specific sequence based activities. In these areas, ServiceNow could extend beyond Orchestration and come up with some bots of RPAs and all. We had a few use cases where we couldn't find solutions in Orchestration and had to go with the publishers to solve them.
Principal Consultant at a computer software company with 10,001+ employees
Real User
Mar 16, 2020
This solution should be more developer-friendly. This is what my team has been telling me. The connectors need to be updated because certain connectors for third-party tools are not up to date, and our customers are having problems synchronizing data with some of these tools. There should be connectors to cover at least the top industry applications, and they should be easier to configure in a plug-and-play fashion. The price of this solution needs to be a little bit lower. Technical support could be improved by decreasing the time required to resolve issues.
ServiceNow is the fastest-growing enterprise cloud software company in the world above $1 billion (2018 revenue was $2.6 billion, up 36% year over year). We deliver digital workflows that create great experiences and unlock productivity to approximately 5,400 enterprise customers worldwide, including almost 75% of the Fortune 500.
If I compare the interface of ServiceNow Orchestration with Boomi, it is easier to use Boomi than ServiceNow Orchestration. Boomi is an ESB with orchestration features to integrate and exchange data between applications, and it provides a more user-friendly experience than ServiceNow Orchestration.
The third-party integrations are challenging when the tools are not from ServiceNow ( /products/servicenow-reviews ) partners. This presents issues when integrating solutions from other vendors.
I remember last time I said there is no need for improvement. It's fine. Due to the limited scope, I cannot comment further. However, it should be integrated with AI and messaging or chatting features, which would be better.
There is a lot of complexity in the platform, but that comes with the scalability. It is a highly complex platform to work on. There are changes in their workflow technology, and the flow technology improvements have introduced more complexity, in my view.
There is room for improvement in pricing. The initial setup is a bit challenging, only due to getting incorrect information from the client team. That’s the only issue, possibly. You have to read through your stuff because once the organization starts moving people around, management changes follow. The tools were set up to look up an organization that works a certain way. Now, you have to reset it to look up the new organization.
ServiceNow Orchestration needs to improve multiple aspects in which their event monitoring system is one. The solution lacks event monitoring systems which makes them non-competitive. They need to include improvements in a similar manner that they did in Sweden.
The automatic remediation needs enhancement, particularly integrating ServiceNow with tools like SolarWinds and Logic Monitor. It is functional, but it needs improvement.
We cannot perform GUI automation using the tool.
I am not going to say dashboards as they are working significantly on it at the moment. They made huge strides for the last three versions in enhancing the workspace concept. With the new UI, enabling workspaces and dashboards is going to become much easier for all the modules. I am sure installation will follow that part. You can already spin up AWS servers, Azure, and VM services. From my space, the only thing that I can say is the spinning up with Google Cloud Services. I haven't personally tried it, so I don't know if it is working.
The solution is a bit rigid because it requires the completion of five steps in one direction. If you do not follow that order, you will not succeed. There is no flexibility when it comes to customer requirements. Orchestrations are very expensive and the cost overall needs to come down. The flow rate for releases and updates is very, very slow and does not meet customers' objectives for scalability. For example, changes in model numbers or products are not enabled for six months to a year because they are included only with new releases.
We have found some gaps in integration because all of our customers require niche tools. Different companies have different needs - I guess it's difficult to cover every use case.
The interface could always be improved. I would like a user experience module to be added. With different services that they are reporting, how can that be measured and what analysis can be done on the user experience? The cost could be lower.
There is still room for more integrations. Or, it would be nice to bundle multiple products together rather than selling everything as a model as that turns out to be a bit costly.
When it comes to automation, to basic windows activity, there is room for adding some features. Even in the areas that relate to publishing there could be increased efficiency in areas such as helping with editing portals. Other areas where there might be improvement is in terms of handling specific sequence based activities. In these areas, ServiceNow could extend beyond Orchestration and come up with some bots of RPAs and all. We had a few use cases where we couldn't find solutions in Orchestration and had to go with the publishers to solve them.
This solution should be more developer-friendly. This is what my team has been telling me. The connectors need to be updated because certain connectors for third-party tools are not up to date, and our customers are having problems synchronizing data with some of these tools. There should be connectors to cover at least the top industry applications, and they should be easier to configure in a plug-and-play fashion. The price of this solution needs to be a little bit lower. Technical support could be improved by decreasing the time required to resolve issues.