Jacada Intelligent Agent Engagement vs NICE Robotic Automation comparison

"The initial setup was fairly straightforward."

"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 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."

"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."

"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."

"The deployment of NICE Robotic Automation is easy."

"Provides good automation features."

"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."

"They need to create a workflow 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..."

"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."

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

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

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

"[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."

"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."

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