Nintex RPA Reviews

We use it to automate a lot of data entry or do manipulation in regards to our ERP system.

We are still pretty new with the solution. We have maybe a dozen wizards right now. Some of them are different variants of similar wizards. For the most part, it is used all around our ERP system. E.g., if we have a new product that we're going to make, we take the information from marketing and engineering. That gets handed off to the bot, then the bot enters that information into our ERP. This is a pretty intensive manual entry process.

Everything that we use is on-premise.

Our company has seen crazy growth over the last 10 to 12 years. We have been up 20 percent year-over-year for that amount of time. Without some of this automation, we would not have the time to invest in developing a full solution or custom applications to handle some stuff because things are changing so quick. It's not worth the investment or there is not enough time to keep up. Constantly hiring more people isn't always an option either. It's sort of a necessity with the growth that we've seen to use this to help with some of the pain points that we have just around growth challenges. Especially at the higher levels of the organization, they see quite a bit of value in the solution.

It has really helped us with efficiency and accuracy. We literally have teams of people just sitting in front of a computers typing in data from Excel sheets all day. That is all they do. We have so many other roles and new challenges associated with our business growth that we could use those bodies. People who have been with the organization a while that we can take those people and say, "Instead of just manually keying all this stuff, go work on something that's a value-add. You know the business and you're familiar with our systems, so go do this instead." That is the biggest win, especially with our state's unemployment being pretty low and filling jobs can be a challenge when finding good people. We want to take the people that we have and leverage them for the things which really help the organization.

It is still a small footprint. In the last 30 days, we've automated 216 hours of work. That is not a lot. However, when you talk about how many people hours that is, it's probably double, if not more than that. So, it is not a huge impact, but in the couple of places that we've deployed it, it has been nice to be able to just send an email in and have it turned around to you from the bot. Within 10 to 15 minutes, the task is done instead of having to send it to a person and rely on them to do it, then get back to you, or they might be on a lunch break, etc. Some of these are critical areas where there's not a lot of time. It's definitely been a benefit to those departments.

I don't think it saves any time from the analyst or IT side. It is an investment upfront to build this stuff and to dig in and find where the opportunities are. We just installed the Kryon Process Discovery service, but we haven't really used it a whole lot yet. Therefore, I can't speak to its efficacy. Hopefully, it will help in this area. 

They make it pretty easy to use this solution for the full-cycle of automation from the discovery of processes to turning on the automation and scaling it up. We just installed Process Discovery. In theory, that should work quite well. It recommends what processes if identified are best for automation versus those that are highly complicated or have a lot of bearings. We haven't gotten the value out of that yet because it's brand new. 

We use it for rapid process automation, but we also have Process Discovery. We use it for billing and collections, business administration, and insurance.

We have some idea of what we wanted to start with. We have been able to expand on that since embracing Kryon a bit more. We originally went into this solution knowing there were some processes which were extremely manual and wanted to take on automating. Once we got into using more of the advanced commands, we got through with some of our first, second, and third wizards, then we were able to take a step back, and say, "Here are all the functions that I've now learned to work with. I want to put them into higher level of development." We were able to expand the idea of something very simplistic, a three or four-step process, then move it over to a 50 or 60-step process. Because of those advanced commands, we could condense them down, which was something we didn't know at the time would be a reality.

Kryon has helped our existing workforce embrace the digital transformation of our organization. We now have people who are more interested than ever in moving over to digital processing. We are able to focus on key components of the business which can't be processed through automation.

We have seen some significant drops in employee errors. However, your data is only as good as what you receive. Errors have reduced by 80 percent based on the processes that we have automated by the sheer fact that we don't have people touching so many of them.

We have been able to streamline some processes just by using RPA. That has improved them.

We use it for unattended automation and attended automation.

We are working on automating a lot of the support processes that we do within our call centers which are very repetitive. In addition, there are rates and pricing in another area where we have introduced automation. We have some automated processes running multiple times a day to evaluate rates, provide reporting, and perform rate updates, as needed, without human intervention.

We are also looking at streamlining some areas on our franchise side, where we are building properties out in our systems and updating their property information. Therefore, we are looking at those components, as well as the onboarding of new hotels.

It has benefited our organization through automated rates and pricing. We built an automated rate system that runs four times a day. Our initial analytics coming back from that rate system for a single two-day period in July performed over 25,000 individual rate changes across just under 600 hotels. 

With this volume of activity, there is no way that we could hire enough revenue managers to perform those volume of rate changes. This rate system has allowed us to be more responsive and competitive with our rates with less human involvement. It is leaving our revenue managers free to work with properties, identify special events where things might want to be increased, etc., rather than spending their time updating rates. Instead, they can now just submit a special event and what they want the rates to be, then the system will adopt these into the existing strategy that is being implemented automatically.

It has been straightforward and smooth to use this solution for the full-cycle of automation from the discovery of processes to turning on the automation and scaling it up. We have three dedicated environments: development, UAT, and production. We build things out, then test them in development. It is very easy for us to transition them out of development into user acceptance testing. Once our users are happy, it is a very easy, seamless process for us to transfer that into production, enable the triggers, and turn it on. The ease of being able to bring things into production and through the development cycle is quite straightforward.

This solution has helped our existing workforce embrace the digital transformation of our organization. We have multiple departments currently coming up to us, and saying, "Hey, when can we meet and talk about things? We have things we want to automate." We have other departments starting to to reach out and show an interest in having parts of their processes streamlined or automated. For example, one of the processes that we are working on automating would be a hotel room type of change. So, if a hotel has a bunch of rooms in their hotel, and they want to transform them into a different room type, it is a very long, slow process. It's very monotonous and repetitive. This is a really good candidate for automation. Right now, we are working with that department to automate that specific process. For them to do it by hand right now, it takes them almost a full seven days to perform, but with automation, we can do it in almost half that time. These type of requests happen regularly. Therefore, there are more of them to do than there are people. This automation will allow us to perform the requests that we have faster, but also keep up with future requests.

When we approach the departments about automation, we put a high stress that the solution is complimentary and will elevate the human workforce. This way they can do the more important things while not having to worry about filling out an Excel spreadsheet with 600 fields. Most of them, when they hear that they won't have to fill out all those fields anymore and they'll just have to worry about the more important aspects of it, they typically end up pretty happy. They seem to be pretty receptive to it. However, you'll always run into a few people who will have the concern that automation might take their jobs, but it hasn't happened so far.

With any of the processes that we have deployed, the accuracy and rate of errors coming back is much lower than what we would typically see. There have been a lot less things going through the automation that we need to adjust, fix after the fact, or touch manually.

We use Kryon in a number of use cases. We have done a lot of work in the insurance industry, especially client-onboarding. We are also working on AML, anti-money laundering. Another use case is data extraction from invoices, using the Kryon platform.

To give you an example, we worked on a client-onboarding scenario. Client-onboarding, when run manually, was typically taking about 45 minutes for just one customer, because the process is so lengthy and because of the amount of information required. In addition, it was updating four systems and there was work done to match the systems, which required a migration piece. Now, with automation, we capture it once, in one system, and then onboard this information to two or three other systems. It now takes a maximum of about eight minutes, compared to the 45 minutes of work when it was done manually.

It has definitely also helped our workforce embrace digital transformation. We have implemented this with onboarding processes, email processes, and the like. It has now spread to multiple LOBs and they're talking to us, including HR, finance, and more.

The bots result in a lot of effort saved and that means we don't need to hire people to do certain jobs. It's saving money on FTEs. I estimate that when we run a business use case, the typical savings are four to five FTEs per month. In terms of business analysts' time, out of eight hours, typically four hours are saved. Operational efficiency has increased more than 50 to 60 percent. Finally, it saves us time when launching new automation processes, by about 30 percent.

We mainly use it for creating automated processes from previously manual processes, to make existing processes faster, better quality and more efficient. We currently have three processes implemented in production and the fourth is going live next week. It's not heavily used, so far.

The first one is small. It just enters the US dollar currency into our ERP system. It's a daily task each morning. The second one involves an external, third-party systems from which we export a report and import it into one of our systems. It used to be done on a daily basis by an employee and now it's being done automatically. The third one is an automated delivery note. One of our suppliers, provides our tobacco products with paper delivery notes. So now they send us a daily report and the robot enters the delivery notes into the operations system. The fourth one which will go live next week, will upload bank notes of returned payments into our financial system. That was another manual process that will be automated.

The currency automation saves us around five minutes per day, but it has to be done every day. For this one, the amount of time is irrelevant. It's more that there are many processes that rely on the currency. So if it hasn't been done or is done late, it can delay other processes. So the value here is more than how much time it saves us. The second one saves us approximately five to ten minutes per day. The third one, the delivery note process, is more difficult to calculate since we have approximately 200 points of sale. Each one has one to two deliveries per week and it takes five to 10 minutes for each point of sale to create these delivery notes manually. So it saves us 2,000 minutes, about 1.5 times a week. The last one, the one that is going live next week, is more significant. It will save approximately a day per week for an employee.

As for operational efficiency, the automatic delivery notes is most significant. From the 200 managers, the bit of feedback that I have gotten is very positive. From the others, I have to admit that it's more minor.

Of course it has helped to reduce employee errors, especially with the delivery notes, since the correct number is very important. If you enter "11" instead of "one," a type-o, it's very significant because it is an expensive product. Definitely, in terms of user-error, we have improved on that a lot. Before Kryon, there were one to two errors per day, or about 50 per month. We found most of them later on and then someone had to remediate them. It has saved us significant man-hours.

Once I decide a process is suitable as a Kryon solution, the cycle of automation is quite quick. I learn about the existing 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.

We're looking to discover routine processes that our users do and ultimately automate those processes and deploy them to robots.

We've really been looking at just about any of processes. We've initially used it for processes that update invoices or update data on our system. We've used it for processes to send emails such as notification emails. We've used it to run scripts and to run data updates, and as a scheduling tool as well.

We've already automated about 40 hours' worth of weekly savings. It has definitely helped us to implement some of the workflows that I've shared with you and to take that work away from our partners so they can focus more on other, more valuable work.

We use Nintex RPA in a complex environment and for working with legacy systems as well as with open systems and outside the company environment. We use the tool in order to do daily tasks that replace employees. 

It has improved operational efficiency, reduced manual workloads, and increased accuracy in repetitive tasks. The platform’s user-friendly design and automation capabilities contribute to streamlining processes and achieving overall productivity gains.

The solution can be good, but suffers from some unexpected flows. Sometimes it sticks or stops - which requires some manual intervention. In newer versions it will likely work better. 

Initially, it improved operational efficiency, reduced manual workloads, and increased accuracy in repetitive tasks. The platform’s user-friendly design and automation capabilities contribute to streamlining processes and achieving overall productivity gains. 

We use it to automate some processes that require no human intervention. Currently, we have three projects: dispute resolution, settlement reconciliation, and consolidation.

I find it very easy to use and customize. The bot can be configured dynamically to use dynamic values, and we can use attended bots to interact with the flow of the bot. Also, it's very seamless to interact with Excel files and web app pages. So far, we have not encountered any issues while building using the action blocks.

We have also used its functionality to call REST services and SOAP services, and we can make use of JavaScript or Python scripts. There are a lot of functionalities that we can leverage.