NICE Robotic Automation vs Nintex RPA comparison

"Through interfaces called Callout (created with HTML code) it is possible to create a strong interactivity with the user. These interfaces can be extremely dynamic in relation to the behavior of a local or remote robotic flow."

"NICE is one of the only vendors that does attended and unattended out-of-the-box. Using the unattended processes we've been able to build a "feature library." We break each process down into workable chunks that we can save into a big library. The next time we come to automate a task, we already have chunks of that automation built."

"It is easy to deploy. To do the automation in NICE, you really need to use your programming expertise. There are no inbuilt features in it, and you have to create all the required features, which can be very interesting for a programmer."

"What we've done with the RTI client is that we've brought it into a bit more of a 21st-century feel. Our agents have the ability to move around when they want, click into stuff. They use it according to how their conversations go with the customer."

"It is a kind of desktop automation. Its licensing model is a little bit different. It tends to be individual automation specific to a role. It excels at that."

"Provides good automation features."

"The deployment of NICE Robotic Automation is easy."

"The most valuable features for our organization are the automatic processes which save main power in the back office."

"Once I decide a process is suitable as a Kryon solution, the cycle of automation is quite quick. I learn about the manual process and I'm one of the two guys who program the Kryon environment. It's relatively simple. There are many details, but once you understand the concept it is quite easy."

"It has been helpful in reducing the manpower and error rate since we are able to run tasks 24/7 without interruptions. As humans definitely take breaks and there may be absenteeism that is unexpected, the solution provides continuous work. Humans tend to make errors once in a while, but the solution has almost zero percent errors."

"Attended automation has diverted 34 percent of training calls to our tech support centers."

"[One of the valuable features] is the triggers. It's relatively simple to activate it. You can activate it via Control-M or via email. It has a lot of built-in triggers which enable us to easily activate the jobs."

"The bot is typically about twice as fast as a person and more accurate, as long as the data going in is good. That is the biggest advantage."

"The initial setup process is easy."

"All our users have no technical background. But Kryon is really simple and intuitive. Our business adapted very quickly and easily. This is the main thing and it's why we love the system so much. It's why we are always trying to put more processes into the system and make more use cases: because of the simplicity and the intuitive nature of the system."

"The one thing I'd like to see, and NICE is already heavily investing in it, is improvement in the user interface itself. They call it the Designer and it's what the developers use. It is a bit clunky; that is the polite way to put it. I'd like to see it be a bit more user-friendly, a bit more intuitive, and to move to something a bit more web-based..."

"The solution is not as intuitive as it could be and integrating took a lot of time."

"We haven't found it to be as powerful as some of the other platforms. From a true RPA perspective, it is pretty far behind some of the other solutions. It has emerged as a more desktop automation kind of tool, but it lacks a lot of enterprise features. It is not really a true RPA because of its licensing, which is kind of user-initiated. It would be nice it can be deployed at a more enterprise licensing model versus a user-based model. It didn't have autonomous automation so far, and they have just released this feature. They have kind of hodgepodged a bunch of products together to get there, but it is not as seamless as other solutions."

"There is a need for NICE robotics to be more user-friendly."

"There are a few areas for improvement in the installation phase"

"Its connectivity with other applications should be improved. In the version that I was using, it would just stop interacting with the other application. Its graphical interface should also be improved. It should have a user-friendly interface. Sometimes, people find it very difficult to understand. One of the obstacles that I faced while programming was that if I needed any kind of help, there wasn't much content on the internet. It can be very difficult to find a solution for a particular issue."

"[During the upgrade] any issues, where it couldn't remotely connect to upgrade, I needed the floor plan so I could go to that PC and have a look at it. Often it was either that the PC was switched off or had a bug or some other application needed to be reset."

"The only unstable part is Studio where you build this stuff. In our version, the 5.25. It has a memory leak. If you leave it open for too long, eventually it just freezes. Saving your work, closing, and opening it just once a day is all it takes. However, this is a bug that I have noticed about the stability of the actual tool."

"Often, it's difficult to loop through a large data set unless the bot has access to the Excel file with specific settings and shortcodes."

"Kryon could be easier to use, especially in comparison to UiPath."

"There are limitations on integrations with other platforms like ServiceNow. There are some issues integrating. It's not a really an open system. The product, its design, etc., is really good, but they have to look at the openness, how to integrate with other products which are available in the market, as well as with our own solutions. You can do integration but it is not so easy."

"Further simplifying the low-code development process can attract a broader user base by making automation accessible to those with minimal technical skills."

"We need stronger governance to know, when a transaction is done, whether it worked or failed; strong logging. That would be helpful."

"It could be more reliable in spying HTML."

"At first, we had problems with the object detection but in this latest release it has been better, and I think it keeps getting better."

"As per my understanding, UiPath has a much lesser cost than NICE, but I am not sure."

"We have been able to alleviate two FTEs, which was a big savings for us. We were able to reuse those resources in other locations. It is over 5000 hours a year in total savings."

"The product has reasonable pricing."

"Licensing costs are about $100,000 a year without any additional costs."

"It is very cheap. I would rate the pricing a three out of ten, with ten being expensive."

"They license per robot and we have 25 robots. You get so many robot licenses and can allocate those licenses to either attended, unintended, or Process Discovery bots. If you have 25 licenses, for example, you could have 20 automation bots and five process discovery. This allocation is flexible. There are also maintenance costs."

"Kryon is slightly more expensive compared to UiPath."

"We're paying in the neighborhood of about $66,000 a year. The cost is fairly similar to its competitors' costs. It might have been a little bit more reasonable than the others, and that cost was with Process Discovery in addition."

"In addition to the standard licensing costs, there are manpower costs."