Nintex RPA Reviews

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.

Areas, where I see some room for improvement would be the use of reading details from an Excel file. Most of the time, it's difficult when I say looping through a huge data set, and it's very difficult for the bot to interact with those data sets unless it starts offering the Excel file. As of today, from the reports I've worked with, I noticed that most reports are empty columns and two rows. So if Kryon can associate with that and extract those deposits into a variable, and the tools can easily fit out to column dash and two rows and columns, it will be nice. But as of today, the bot doesn't have the functionality to detect variables. We have to do it on the Excel file itself.

I also noticed that when it comes to the use of bots, not everyone has the same knowledge, and it can be difficult to do certain research unless you have advanced knowledge of what you need to do. I also noticed that in the community, most people don't use it, and it's quite difficult when you need certain support.

We started using it about a year ago, in 2022. The version we use is 22.3.1.

Based on how we use it, it has no breakdowns. It's very stable. I mean, it's been months since we encountered any breakdowns.

Everyone has access to it, so around ten people are using Kryon RPA in our organization.

We have contacted the customer service and support team before. We were facing some issues with the console, which is the administration page where we see expenses, expanded entries, bots, and successfully run lines. At some point, we were unable to connect to the page, so we had to contact the support team. They came in and resolved the issue.

The support was good, but our relationship with Kryon's support team is very good. So I would rate it as good.

Positive

I have in-depth knowledge of Kryon RPA and other similar tools. I have used Ui Path and Blue Prism in the past, and I find Kryon to be similar and easy to use.

I have a good understanding of all the action blocks and how to use them, which makes it easy for me to set up and use Kryon.

I would say the installation is not complex. When we did our own installation for a vendor due to some permissions and restrictions, it took us around two to three days. But normally, if we don't have those issues, I can say the installation is quick and straightforward. It didn't even take me a full day to install and set up the solution.

The price is affordable. The license is based on the number of bots and users.

We had some back and forth using the setting tools of the RPA solution and noticed that other RPAs were costly. We found that Kryon RPA was cost-effective and had features other apps didn't have.

I would give Kryon RPA an eight. As a developer, I find it easy to use. The codes are written in a language that is understandable. They also have documentation available on their website that explains how the tools work. The way the tools are built is simple to understand. The steps can be split into different parts, and there can be more than one step for a particular bot. The fundamental aspects of the process build are easy to understand. Additionally, the build has current and account notes explaining what each step does. 

Overall, Kryon RPA is easy to understand, which is why I gave it an eight. I would definitely recommend using the solution. 

We only use unattended bots right now. We build processes to help business departments in our company to improve processes through automation of pretty easily "bot-able" ideas.

We have a bot that creates a proposal using a request-for-proposal template that people fill out. We then create the proposal, based on that information, on our internal site. Another one is where we mail out payroll files that come in by reading a portion of the file to get payroll dates and the like. Those are two of our really big ones. The payroll bot saved 15,000 hours last year. For the other one, while I don't have specific metrics on total time saved, it went from a 30-minute, manual prep process to an eight-minute bot process.

It has helped us to find and prioritize processes that are ripe for automation, when we go searching for ideas. We just haven't been able to reach every department in our company yet because we're a big company and there's only so much time.

Our business users love it. Those 15,000 hours saved are a fantastic result and we're at a 99 percent success rate. Our bots very rarely fail, and if they do, most of the time it's because something is wrong with one of the websites that we are using and an unexpected error pops up. But they are loving it.

Finally, it has helped to reduce employee errors.

We do have bots where we use .NET plugins to make some of them faster, but other than those, I have built most of the bots that we have. Even though I'm in IT, I'm a business analyst. As a business user, it's so easy to use. With the recording of the processes, we didn't need to hire a specific developer. We do have one now because there was only one of me, but we are able to build most of our processes without having to develop the actual development skillset. It's nice to have that skillset here, because we can scale by using .NET, but the simplicity is the biggest win.

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. They also came and trained us a little bit so that helped.

There are some known defects that are on our list for the next release, but that happens. It's technology. They're aware of them and they're working on them.

The stability has been great. We've had one incident in a year-and-a-half, where we were down for about four or five hours. It affected everybody, not just our company. As far as I know there was a hotfix that they had to put out. But in all that time there has only been that one day.

The scalability has been good because of the .NET aspect. If it wasn't for that, they wouldn't scale.

For example, we had one bot that we built which needed to run every day to download documents off a website. It had to go download a lot, sometimes up to 500 documents a day. It never finished because the website wasn't stable enough to run for hours and hours. The bot would end up failing because it took hours. Now, we download one document now from the website and use .NET to split out the PDF files for each separate document that we need. Instead of downloading one at a time on the website, we use .NET to download one, and separate all 300 of them. If we didn't have .NET they wouldn't be able to scale.

With that capability I don't see any limitation to that scalability. .NET has been a lifesaver.

We had another one that we had to change recently because it took the bot six to eight minutes to do the whole process the way the business users were doing it. We needed to do 900 in a day. Even running it on two different servers, it wasn't going to get everything done in the time that we needed it done. Instead of throwing it away saying, "Sorry, we can't use it," we changed the process for the business users and said, "Hey, can we do it this way?" and used .NET. There is a little more front-end work that the users have to do if there are errors, but not very often. Most of the time it goes through. With .NET, it does the process in 30 seconds.

We use the. NET plugin everywhere that we can because it makes things faster.

Their tech support is pretty good. The people I've worked with have been good. The time zone issue sometimes was difficult at first, but they've fixed that with a USA support team now. It's gotten much better.

In terms of customer service, everyone that I've worked with is great. Ryan is our guy and he's very good. Whenever we've had to escalate things — we've had some issues with bugs and things that we weren't expecting — he has done all of the escalations for us. 

They came out here and gave us a four-day-long training but it just wasn't going to work for us to go to them in September or October when they were going to have more training. So instead of us going, they offered to come to our office and have a mini-training session with just us. That was awesome. That was part of their standard service.

We did not have a prior solution.

I was not included in our initial setup. That was done before I was brought onto the team. But I am familiar with upgrades. 

The first upgrade that we did was not fun at all. It took seven or eight hours. The second time, when we upgraded to the 19.1 version, it was an hour-and-a-half, both because we got better and because they provided better documentation. We also got a QA environment, which we didn't have before. When we installed our QA environment, I don't think it even took half a day.

Part of the difficulty with the upgrades was that we didn't know any steps that we should have taken, because their documentation wasn't step-by-step. So we were on the phone with them, walking through the upgrade the first time. We missed steps because the documentation wasn't there. But the second time, the documentation was great. We knew exactly what to do. Our app engineer had all the setup stuff done before we had our meeting with Kryon, and we just walked through it. It was awesome.

There were two of us, from our organization, involved in the upgrades. Kryon had people on the phone but they weren't doing anything. They were just watching us.

In terms of maintaining the solution, there's one person who handles all the bot servers and there's one admin on Kryon but he's super-part-time. It takes maybe five percent of his time. I haven't had to talk to him for weeks. And there are two of us on the team who handle the support and the bot building. There are six departments that we have built bots for, and I don't know how many people are in those departments, but they don't handle anything with them. They don't have access to Kryon. We handle everything.

The OCR reader, to help read non-digital PDFs, has a separate charge. We don't have that plugin. The only other cost that I know was separate, at the time, is the Process Discovery. I don't know if that's included in a bundle now.

We evaluated Automation Anywhere and Blue Prism. I wasn't involved in all of that process, but the biggest thing in our decision to go with Kryon was that IT didn't need to own it. Although our IT has it right now, a process improvement team could have actual business users building processes. It can't just be them, because we have to have oversight with the .NET stuff. But with the easiness of it, we just had to go with Kryon.

The biggest lesson we've learned through our time using it is the .NET component for scaling. One of our biggest lessons is to use that wherever possible because it makes things so much quicker. Also, if you look at some of our old bots that we built versus some of the bots we build today, it's crazy that we even knew what we were doing. The process flows and understanding what can and can't be bot-able, have gotten way better.

My advice would be to have a team. Make sure there's a developer so you can do plug-in things and make sure that you understand the setup and the admin tool. That was a huge lesson learned for us, going back. The way we did the setup was incorrect so we had to re-record all of our bots the first time, and that was a disaster. We didn't have it set up right because nobody told us how to do it. We didn't have that support at the front-end, for the setup pieces, for everything we were doing. 

And always have a QA environment first. We did not have a QA environment. When we first went live we didn't know it was an option, and I don't know if it was an option at the time. I imagine it's standard now. We have a QA environment now, but we don't have any data set up or any automation to set data up so we can't test bots in QA. We have to test them in production because we didn't go through that work. Testing was a mess. That's no longer true for our current bots, the ones we're building today, but it was a mess for all of our old production bots, anytime changes were needed. So always have a QA environment or a Dev environment.

It's been hard to get it off the ground. We have a really small team, so there are not very many examples. We have quite a few bots that have saved a lot of time, but I know that we could have way more. We just need a team, and I think we're going to get one, although not right this second. Kryon hasn't helped our workforce embrace the digital transformation of our organization because we only have that small team right now. People are seeing things and say, "Yeah, that's awesome," but we can only move so fast because we're so small. So people are not super-excited about it yet. They still need more exposure to it. We have about 15 bots in production right now, but it's pretty much focused on one section of our organization, and we're a huge organization. We have plans to increase our usage of the solution. There's a whole new process improvement team coming. Once we get out there more, I'm sure it will expand.

The Kryon Process Discovery is not included in our license right now. We just haven't done it yet. We've looked into it but we haven't done it yet because it's pretty complex. With the version that we saw originally — it might be different now — when it first came out, you needed special computers for it which we would have had to buy and deploy for the users who use the processes. It wasn't something that we were going to do at the time. It's not something that we have thrown off the table, but at the moment we're not using it.

Just learning what bots do, what RPA does, what I can and can't do, has been part of it. I can go to any business unit, now that I've built bots, and say, "Yeah, I can do that," or "That's not a good idea." I know exactly what I can and can't do in Kryon. I don't know if any other tool can do things better because I've never seen any other tool, but I know what I can and can't do in Kryon.

The original training that we got was a week long and we were trying to build bots in that same timeframe. So we didn't get a whole lot at that time. When we took their training classes online and had them come to us and train us in more in-depth, it helped a lot.

Everything that we do use, that we know how to use, works nicely. I love it but I'm not going to give it a ten out of ten because there are issues. I would go with an eight. They've gotten so much better at all their stuff. The tech support was part of our issues for a long time, but it has gotten a lot better. They're getting all the training classes online and they keep those pretty updated. They have a community now. They're learning and growing and they always ask us for feedback on every aspect. They put that in their backlog for future prioritization. They're listening to us.

We manage customer accounts: their orders, modifications, account cancellations, and back office stuff. For example, our clients are network marketing teams. Therefore, they will have accounts for multi-level marketing (MLM). They want their orders and accounts modified. For some of them, we want to change their subscriptions or cancel their accounts. These are all submitted as requests through online forms. Then, we will take them and do the modifications. We do this process automatically through Kryon.

All our bots are actually licensed for unintended, but we are not able to use them. So, we have currently 15 bots and all of them are attended only.

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.

We are able to cope with our clients's demands. No matter how much volume they throw at us, we are able to get it done quickly. That is where we see the biggest returns.

If a client gives us a new task, and it is a recurring volume, procedure, or SOP, then we are able to automate it within approximately a week. Then, they will be up and running with that automation. 

If it's a very simple task, we can automate it within about a week. If it's complex, then it will maybe be a couple of weeks to three weeks at most. We mostly differentiate simple and complex tasks by the number of steps involved. Sometimes, we need to cross check multiple accounts for a single request. We need to ensure all the information comes back correctly and that the logical calculations are done correctly. The more number of steps, the more complicated task that we will consider it to be.

We do code level modifications, which are already prewritten, and everything is with us. We don't use any of the advanced features of Kryon.

The simplicity of it: Kryon was very easy to learn and implement. The learning curve was very small. It didn't take a lot of time to set up or go live.

It is easy for business users to utilize. Mostly, it is a visual based tool. You don't need any expert coding knowledge. Even if you don't know anything about coding, a couple of weeks training should do the trick, as long as you are able to identify the logic behind whatever task you're going to automate.

While it does help reduce manpower, we still do require manpower because there are some processes and steps that we cannot do with automation. It may be too sensitive to be done by automated processes. In those cases, we still need manpower.

It does help to identify which tasks can be automated based on Kryon functionality, until you have close to 50 multiple tasks from one client. As soon as we automate any one of our top volume drivers, we try to understand how we can automate the next one orthe next highest volume driver. We have tried to use Kryon's functionality to the max, but still there are some limitations that don't allow us to automate all the tasks. E.g., anything that involves free form text is a major drawback. We use forms which get their data from our customers along with their account details. So, their form details are always the same. They don't change the fields, only the values are different. If it were an email, every customer would use their own words to describe the problem. It's difficult to write simple logic that is common for all types of words. I think free form text requires artificial intelligence. However, the lack of AI is not a big issues.

Another major drawback is OCR. We are not able to read scanned documents correctly in a reliable way. There is always some margin of error. Some of the processes require us to read scanned documents, and you need to ensure that it is 100 percent accurate. Without that level of assurance, you can't automate such tasks.

Our client uses Citrix NetScaler Unified Gateway. It is a virtual machine. All the tools that we use run from the client's location and through a virtual machine called Citrix. It is projecting the remote screen onto our screen. Kryon is not able to identify individual applications behind Citrix. All it makes is a screen by taking the image. So, Kryon's functionality is limited to screen reading. Because of this, we are not able to take advantage of the Windows functionality or web server functionality. like browsers. They are not able to identify whether it's a browser, etc. It can just read from the screen. Being able to identify applications inside Citrix would be a huge advantage for our processes.

Their logging features are minimal. 

Reporting-wise, there are some reporting options, but I don't think they are very practical from the point of developers.

We haven't had any instability. It is very stable.

So far, the upgrade process has been smooth, but it does take a few hours. The upgrade process could be better. Right now, it takes a few hours for them to set it up. We must wait to have a shared meeting. They have to wait for us, and we have to wait for their availability. It would be better if we don't have to wait for them, and similarly, they don't have to wait for our availability.

Everything is managed by our console and the Kryon admin. All we had to do is get a license, add the system name, and the bot is simultaneously up and running. So, stability is very simple.

We have two types of roles: developer and tester. Developer does the coding work and shows new tasks are deployed. Once they are deployed, the tester's work would be to ensure the tasks are running correctly. We have a license for an unattended bot. However, because of the Citrix issue, we still need to have at least one person on the floor to monitor the bots in case anything gets stuck, the tool is not responding correctly, or ground does not direct the total Windows, etc. 

We have seven people covering all the shifts 24/7. Apart from developers, we have four testers. One developer is enough for development and maintenance, but we still have three to ensure that all of our shifts are covered. Thus, we can work on multiple task at the same time.

The customer service is pretty good. The only problem is availability. Because of our high transaction volume, we have to give a scheduled time to them. Similarly, their experts also need to schedule among other customers. So, there is no dedicated support, but I know they are available and very helpful. It just takes a bit of time to contact them with both of us trying together. On average, it takes three or four days to schedule something with the customer services. 

If it is an emergency that makes our bots go down, they will make special arrangements with us. They make sure that they are available immediately. We haven't had downtime for more than 24 hours, so far. The customer service is great in supporting us.

This is our first RPA solution. We did try automation with Visual Studio, like encoding, but it was a failure. We thought RPA would be a better solution: easier to implement and error free. It made sense at the time, and it's still helping us out.

The initial setup was straightforward. 

The deployment took a couple of days: One day to set it up and one day to review.

We just have one environment with multiple bots. We straight away went into production. We didn't have a testing environment or equivalent.

There were Kryon people who took care of everything. They just had to arrange the requirements. Once that was done, they were able to take up a remote connection and set up everything. They were helpful, ensuring everything was properly working and up and running.

At the beginning, we had fewer bots. So, we just went straight into it without a plan. We asked the Kryon team to set up a server, and they did. From there, they licensed us the bots. Once that was done, we started coding and straight away implemented them. Anytime that we have required an upgrade, we will just add additional bots.

If they need to upgrade the version, they will let us know that a version is available. We give them a suitable time and they will schedule a meeting to upgrade it remotely.

Error rate and manpower has been reduced. The error rate has been reduced almost to zero. Though, sometimes, some of the tasks are done better with humans than Kryon.

We are not exactly saving money at this stage, because we have invested a lot in Kryon. Our transaction volume and cost that we are receiving has not yet equated in a profitable way. We are moving to a more profitable way going forward, but it will take a bit more time. In maybe another year or so, we will see some improvement and ensure that this solution is profitable.

It saves our business analysts a couple hours per day.

Our workforce management (WFM) team is managing the licensing costs.

Kryon was our choice. Our project manager brought in Kryon team for a demo. Once we saw the features, we did a test with their training specialist, then we were convinced that we could utilize this for our requirements. We didn't look at any other options at that time.

It is a good solution if you're not using any virtual machines, like Citrix. 

It would be better if you get a demo or automate a simple task using Kryon. Get them to show you a proof of concept so you can understand what other challenges that you will have rather than blindly implementing it. Definitely, get a demo to see how efficient it is. Seeing it in action helps a lot.

We are not completely moving to a digital transformation. Even our management doesn't agree with 100 percent digitized solutions. They still want some level of human involvement, as well as for auditing.

The humans in our company have been concern about the robots taking over their roles. The robots take up most of the redundant tasks and focus on those. This ensures that our agents do the more complex ones or the low volume drivers. The agents do all the ones that require more logical reasoning, installation processes, or secure processes. We train our agents on these tasks and reassign their skill sets. We give them more training, giving them more complicated tasks. We aren't trying to lose our agents, even though manpower reduction is there. We just trying to retain them, but for different types of tasks, ones that require more human involvement and thinking.

We don't use Kryon Process Discovery or any of their web related services.

Automation takes up most of the walling that we get from our clients. Ground is being used extensively. However, the limitations are caused by Citrix, which is making us rethink our strategy sometimes as to whether we will be able to increase with the product. We want it to be faster and more reliable. We want to ensure that with any errors which occur, it is able to identify those errors, and it's able to rectify them or at least log of them. We want to take a look at them or notify people. Currently, only because of the Citrix issue, we are constrained. We might need to take a look at another software that supports Citrix more efficiently. Currently, there's no plan to increase usage, but it is part of our major usage as of now.

I have been using it for a few clients and office stations, including banking, insurance, and a major internet provider. 

The most valuable features of Kryon RPA include exceptional in-build management, simple transcription management, and deployment features. 

The user-friendly environment allows for easy learning, and the end-to-end workflow management is excellent. Additionally, the maintenance and management costs are comparatively low in terms of licenses, and the adaptability is also noteworthy. Overall, they have developed good features.

There are a few areas that can be improved. Firstly, Kryon RPA needs to enhance the robustness of its multi-board architecture to ensure the availability of bots on multiple machines. 

Secondly, Kryon RPA should focus on improving document extraction. When compared to other integrated products, such as those offered by its competitors, its document extraction capabilities need more attention. 

Additionally, Kryon RPA should work on enhancing the allocation response for multiple bots to maximize their utilization.

These are the key aspects that require improvement, along with the inclusion of a high availability feature. While I hope the data is stored in the cloud, I'm not entirely certain. However, it's crucial to ensure seamless integration with third-party vendors to enhance the usage of the product console.

The security aspect of Kryon RPA is good, which is why several banking and financial institutions are using it. As for stability, it ultimately depends on meeting the expectations of the individual customers.

I would rate the scalability a seven out of ten.

The support provided by Kryon, along with the learning academy and online forums, has been quite responsive.

The initial setup of Kryon RPA can be considered moderate. It is neither overly complex nor extremely easy. However, the configuration deployment and client version setup are relatively more user-friendly compared to other products.

Initially, the deployment was mostly on-premises as we explored the project's capabilities and conducted proofs of concept (POCs). This was during a period when the organization was also using AWS and Azure. However, gradually, we migrated to the cloud to leverage the product's features and capabilities. Initially, on-premises deployment was necessary for testing purposes. Now, the implementation and deployment process has been simplified, and we primarily use cloud apps.

The initial setup itself only took a few days. However, the duration of implementation and deployment depends on the complexity of the project or process being automated. Once the implementation is completed, the migration to the production environment is usually quick, taking only a few hours or days, but in some cases, it can take a few weeks.

The implementation timeframe varies based on the complexity of the specific use case we are working on.

The pricing is moderate compared to other products, and I would consider it to be economical.

The licensing features are very good, including the option for shareable licenses. The overall cost is moderate and economical.

Overall, I would rate the solution a seven out of ten. 

Our primary use case is two back-office processes from a specific area, an area which was very complicated. In the credit card world, there is a process called a chargeback, when the customer says he didn't do a specific transaction, or it's not the right amount. This process has a very long, complicated and regulated process behind the scenes, after the conversation with the customer. We used a robot to automate a lot of the process, to make it shorter, easier, and to save a lot of agents working on the process.

Every week or two weeks we are bringing on a new process with the robot. We are still in the middle of the automation move; we have a very big roadmap for what comes next. We are still on this trail.

The process I noted above is a main business area with a lot of very specific processes inside - we have now more than 15 specific processes in this business area. All of them, as of now, have saved us almost six FTEs. That's a lot of money. The savings are great and they will increase every month.

In the last month, we achieved 11,000 activities done by robot. Before Kryon, we did 500 each month. When we started with automation ten months ago we did a few hundred. Each month we have added more and more processes and more and more activities. It's quite dramatic, because we took a very complex business area, and every activity in it which can be done automatically is being replaced by the robot instead of people working on them.

In terms of Kryon helping us embrace digital transformation, we are very advanced in this area. More than 70 percent of our interactions with customers are digital. But Kryon helped us with some of the processes which are more complicated, where we had people doing things in the back-office after the digital process. Now we can do more of them automatically. It's another step in the same direction for us.

What we are lacking is OCR, the ability to read text. We would like it to have the ability to take a page which is free text and analyze it, and then for the robot to know what to do next. This ability does not exist in Kryon products, so our company is now trying another tool which has this specific feature - an IBM tool which combines RPA and OCR together.

Also, when the robot stops working for any reason - it doesn't matter if it's something in our systems or our infrastructure - it does not know to go back to the same point it was at when it stopped. We have to start from the beginning or to delete the report. It cannot continue from the same point. We would like the robot to know how to continue.

It's quite stable. Most of the difficulties are coming from the changes on our side.

The scalability has been good enough for our needs.

Prior to Kryon, we didn't work with another solution. But we are now starting to work with another solution because of OCR.

On the technical side, the setup was done mostly by HMS. The issues we dealt with were mostly to do with the connection to our organization's system. The authorization issue was difficult for the system and many other aspects, but I know part of it was from our side. We also had some information-security issues. I don't think it was too complicated, but it took us about a month-and-a-half, to do the first at set up, and then it was much easier.

We learned a lot. We learned what we need to prepare for each process so the process will be the most effective and quick. We learned about the abilities of the tool and that helped us in thinking about the next processes and how to do things more efficiently.

We are also using BI to help us with more complex business logic. Instead of doing it in the robot, we are doing it in BI and giving the robot more direct reports to work on. It makes our process much smarter and efficient.

In terms of deployment and maintenance, we have one full-time employee working on it, and one of our business persons, a project manager, is working on it half-time. He's involved in building the business process, deciding what will be the next step, and helping close all the details on our side.

The maintenance is not high. It's just that each time the system is changing, we need to teach the robot the process from the beginning. This is the only maintenance we have. The other work is really to in developing the next process each time.

We have a supplier doing the implementations for us, HMS. They are more involved in the technical details and issues. But next month, we are planning to do Kryon's course. We are bringing it here, and then eight people, both business and tech people from our organization, will learn the tool and then we will be able to use it by ourselves.

Our experience with HMS has been very good. We like working with them. We are continuing with them but from a budget point of view we would also want to learn to be more independent. But we'll definitely continue working with them.

Now that the process is cheaper for us, we have been able to change our business rules a little bit and save more money by automating. To give a simple example, if it was worthwhile for us to do a specific activity only if it was more than 50 shekels, now, when the robot is doing it and it's cheaper for us, we're doing it from the first shekel. We are saving more money by changing the business rules because the process is costing us less money.

It has also helped to reduce employee errors. This is also very important. And it has helped us in terms of monitoring because we need to do less monitoring of the employees. That's another area of savings, another improvement. In the beginning, we did need to monitor the automated process, but after seeing it and becoming comfortable with it, we were able to reduce our monitoring of employees.

The first robot was very expensive.

For us, there are the additional implementation costs that we paying to HMS.

We have a lot of people coming to us to learn from our process, so we've been providing advice already. First of all, it's important to do a very smart business analysis, from the business side, and not automate exactly the way it was done before. Really think about ways you can improve and make the business logic, the business rules behind the scenes, more effective. This is very important.

It's also important to look at becoming independent with the solution from the beginning. We have only started to plan for that now.

The authorization issues within our company also took a lot of time, so I would suggest getting those dealt with in advance.

Part of the difficulty in embracing the tool is on our side, due to bureaucratic issues that we have in our organization. Every change we make which results in a new version of the system the robot is working on means we need to teach the robot from the beginning to do the process.

For example, when we would have a new version of the system, we would ask our people, "Has anything changed?" They would say, "No. Nothing is new." Only after would we find out that something moved from the right to the left. Just one button. For the employees, it didn't matter. For the robot, of course, it does. And then we needed to teach the robot to do it again. So we have learned to prepare ourselves better before a new version is released. We receive all the screens. We teach the robot to do everything again. We're checking ourselves. We test more. These are things we learned along the way, "on-the-job learning." We wasted a lot of time on this because we did not prepare for it properly.

In terms of the prioritization process, we are working with a business analyst to decide exactly what the next process should be, what has the biggest number of activities per month and that the business case is important. We also look, from an implementation point of view, at whether we can do it. Is it accessible for us and not something very complicated which will not be possible? We take all of this into account and we decide which process to put in next. We already did the main business area and now we're continuing to another business area and doing the same process. One of the things on our roadmap is to optimize part of our monitoring processes.

From a business-analyst point of view, we are using a lot of analytics to make it very smart and efficient. So it's not saving us money in business analytics, it's the opposite. But it's worthwhile for us. The discovery process in our methodology is very important because each case is a little bit different, so we need to find the right rules, the logic.

The first process was the most difficult. We needed to learn how to work with it. But by using it more and more, we have achieved a very easy and quick process. The delivery time, now, is very good for us. We are adding a new process every two weeks. Now it's good, but the first time was more difficult.

We're predominantly focused on the contact centre because that's our primary core business, and a lot of RPA use cases are in the back offices. The challenge for contact centres over the years for all RPAs has been that it's hard to establish the business case. The complexity of that environment includes determining and prioritizing which process you want to automate first.

We have done quite a number of back office stuff, but our vision is to link the back office to the front office in terms of customer experience. We are a speech analytics company, and we specialize in that area. We have challenges with corporates because every vendor comes in with a return on investment equation, but there's only so much that our customers will do. We saw that combining our capability with what RPA can do would really help with the business case for automation.

The full-service automation aspects and the process discovery are the most valuable features of Kryon RPA. The process discovery is where you spend most of your time in RPA. We're not a big professional services company and don't want to build a massive team. So, the more we can automate on the front end, the better it will be for us.

Kryon RPA's automation, process discovery, exit deployment, bots management, and change control management are really good.

The process discovery tool of Kryon RPA could be improved because of its limitations. I'm looking forward to the new release, which will fix these limitations.

I have been working with Kryon RPA for about three years.

Kryon RPA has decent stability. Once you've built your bot, they run really well. With RPA, you're always a victim of what the client does. The biggest challenge in RPA is managing the customer. A customer might do a version upgrade on something that's out of our control. However, from what we can control, Kryon RPA is a stable solution.

I rate Kryon RPA an eight out of ten for stability.

Most of my deployments have been pretty small. On average, they're about 50 users at the end of the solution. We don't have thousands of users sitting at the end of these things. The console that manages all the bugs you deploy is really good. The chances of our company getting involved in a big telco are very, very small. We're using Kryon RPA mainly for organizations with 200 users and below based on per division. Kryon RPA is well suited and well priced for organizations with 200 users and below based on per division.

Currently, the two customers that use Kryon RPA are in maintenance mode with us regarding change control and management. Our clients are medium sized businesses.

Based on my experience with other RPA products, I rate Kryon RPA an eight out of ten for scalability.

Kryon RPA’s technical support is very good.

Positive

I rate Kryon RPA a six or seven out of ten for its initial setup.

The pilot phase we did the first time went really well. The deployment with Kryon RPA is ongoing, and there are always improvements. We are pleased that we were able to deal with the security aspects of managing and dealing with customer data. We're dealing with tier-one organizations in terms of managing their data and getting through security.

Compared to its competitors, Kryon RPA's pricing is very competitive. We've priced Kryon RPA based on the use cases that we're getting and the return on investment. Its list price is one dollar, but we got it for 30 cents because the pricing was negotiated.

Along with licensing, we paid Amazon to set up the Amazon infrastructure to support the software. We also got the whole environment certified as an ISO-certified environment. Additionally, there are resourcing costs because we set up a fully managed service proposition around it.

We had to pay about 30% additional cost in addition to the standard licensing fees while using the solution.

I rate Kryon RPA a four out of ten for pricing.

The reason we selected Kryon RPA was because of the automation capability of the process discovery. It's a little bit immature, but the new release will fix a few bugs in the product. The product has the potential to speed up the discovery process. The new version will overcome some of the solution's limitations and make it a better product. The automation capability or the RPA aspects of the solution are pretty much the same as what I've found in most RPA tools. It all depends on the environment you're integrating into.

Kryon's gone through some changes because they got acquired by Nintex. In that period of acquisition by Nintex, it's been a bit uncoordinated in terms of support and other things. But Nintex is getting its act together and integrating the product into its portfolio. That's a natural thing that happens following an acquisition.

Overall, I rate Kryon RPA a seven out of ten.

We're automating a lot of shared services tasks within our homegrown system: payroll, billing, and things like that.

As a company that places temporary employees, we have talent globally. In the UK there are GDPR requirements. Before Kryon, when one of our field employees reached out to us saying that we needed to remove their records, that was all done manually. Now, that’s something done by the robot, giving people time back and reducing possible entry mistakes. It’s the same thing with fee entries within our system. That is something that might take somebody ten hours, whereas a robot will be able to take that off somebody’s hands and ideally reduce the time to complete.

In terms of embracing the digital transformation, there is the question of whether people are going to be accepting of tasks being taken away from them and what they're going to do with that time. But a lot of people have really embraced it, especially people who were taking ten hours to put fees into our system and who will be able to use that time for more productive and less mindless tasks.

The advanced Excel functionalities are really convenient because we work a lot with spreadsheets. It’s also easy to use the HTML selectors on most major sites. It’s just a click and it picks it up. There’s not a lot of no hard-coding with it.

While I have some technical background, everything is self-taught. I'm not necessarily a developer myself, but picking up the tool, with the training they provided, has been pretty easy. I’m currently the only person using the tool in our company.

We use Google Drive a lot. If somebody sends us a spreadsheet or a document, it's going to be in Google’s format. It's not going to be in Microsoft Office format. But currently, there's no integration with Google’s documents. That would be a huge plus to have.

The same goes for, using Chrome natively. There's an extension but it doesn't necessarily always work. We have to close Chrome and reopen it to get it to pick things up sometimes, depending on the page and the IFrames and things like that.

I’m not sure yet what I think about the stability of Kryon because we haven't been able to get things constantly running and working. We initially had the server issue. And then, there have been issues with Chrome crashing and the extension.

Right now our usage of Kryon is limited to our shared services team. We're taking care of those processes first. But we have plans to automate as many processes as we can get on our plate and get through.

We have room to grow. We just have to figure out where we need to go from where we're at now. Right now it's a waiting game to get things fixed and running.

Customer service gets a rating of 100 percent. They’re fantastic. They're always really quick to respond. If we have a problem or if we put in a ticket that is more high-priority, our rep will jump on it and get things escalated. They’re happy to work through issues and take as much time as needed to resolve everything.

The Kryon team has definitely helped prioritize processes that are ripe for automation. It's an ongoing process, but they give us a good understanding of what to expect and how to figure those processes out; what can and can't be automated. It was mostly through the training. Going through that with them gave us a better understanding of what sorts of processes make sense.

We didn’t have a previous solution. We went with Kryon because of

• the ease of use
• the user interface seemed a lot better, more usable
• some advanced features that others didn't have
• the price - can't beat the price.

We had somebody within our department doing the initial setup, although I was on the calls. It was a little bit complex, because there were some issues we ran into with Server 2016. When we tried to run an unattended bot on there it wasn't working so we had to switch operating systems. We've had to go back and forth to get things truly set up and ready to go. We're still working on the deployment, but that's not necessarily because of Kryon issues. It took some time to figure out the issue with the server, going back and forth with screen-sharing, etc.

And it seems that the size of the virtual machine that they provided with us might not be enough. We're trying to figure that out. Chrome keeps crashing on us. Once that is resolved, we have three or four processes that are pretty much ready to go. I just have to get through the actual testing of the running the unattended bots on the virtual machines.

In terms of an implementation strategy, we are working with our shared services teams to identify the processes. We have a daily “stand-up” and a weekly planning session to figure out and prioritize our processes. Then it's just a matter of building and testing and getting them out.

I expect that Kryon will save us money. It's too early to tell, but I would say that once it starts running there are going to be cost savings.

There are different pricing levels for every bot or unattended bot. You can buy however many you want. You'll need an additional virtual machine for it to work on. You can get multiple attended bots if you have users who have Windows machines. You can run those locally on their machines.

Automation Anywhere was one of the solutions we looked at. There were others but it’s been a while since we went through all of them.

Make sure that you have your processes in a good place and that you have them written out. Make sure that you have your stakeholders onboard. And make sure that your bot works on the right server.

We don't use the process-discovery functionality of the tool. We're identifying our own processes by polling various stakeholders to see which processes make sense to automate. But it seems like it's pretty easy. We've hit a couple of snags with our virtual machines and the OS they are running and with the Chrome Extension. We're doing everything with unattended bots since we're primarily a Mac-based company. We're not able to run them on people's local machines other than the machine I use to create the Wizards.

In terms of operational efficiency, it might be a little too early to tell because we're stuck right now. But in the big picture, not only are we identifying processes, but we're also figuring out how to improve the processes, whether somebody is currently still manually doing them or a bot is doing the improved process.

Our company buys products from vendors and sells services to end-users. Most of the RPA processes done in Kryon are related to order raising, as well as retrieving reports. We have automated processes involve SAP, Pegasus, ITSM tool, Words, and Excel.

It takes a lot of work and time to complete the business processes manually. When the users utilize the Kryon solution, it cuts off more than 50 percent of the processing time as the logic has been pre-built. There are less orders being delayed. Adopting Kryon solution has significantly improved the turnaround time.

The image recognition in recording actions is very helpful. It runs stably as long as the graphics on the applications are not changed.

The environment of storing the variables could be defined as local, which will only be accessible within the wizard itself and cannot be read by the embedding wizard.

It will be good if Kryon has a function to find/replace the keywords and collapse/expand the groups.

We did encounter some issues regarding to trigger often but our support team is able to resolved it later. Other than that, it is quite stable.

It is very scalable. All we need to do is to set up the robot accounts and assign the access to it. Once it is done, we have to configure the trigger for the robot. Scaling up and down can be done in just a few steps.

The customer support is outstanding. They are very responsive and will accommodate with our schedules.

No, we started with Kryon.

Setup for Studio and Robot is pretty straightforward. We have to install the Studio and Robot on the machines, create accounts for the users and assign access rights. Then login Studio to develop wizards and Robot to run the wizards.

The initial setup of server was done together with vendor. Subsequently, vendor team came down to help us with the upgrade. They are very helpful and knowledgeable.

I am not too sure how much cost was saved. But there are a few people in the department were redeployed when one of our processes is up and running fine.

I am not involved in any of those.

We are using UiPath in conjunction with Kryon. I feel that Kryon has a better image recognition than UiPath.

I have tried a few solutions and Kryon is the most user-friendly.

The solution is easy to use. Although I felt the solution is a little restricted sometimes as I could not call any external libraries, I am able to use the advance commands, which are the built-in functions in Kryon, to program the RPA solution by changing my initial idea. It makes me think out of the box and test how good my logical thinking is.