Automation Anywhere Reviews

We use it for our refund department. We use it to initialize payments and everything else that is a repetitive process. 

We use Automation Anywhere to automate financial processes, invoices, billing, etc. 

Because it reduced the time duration of our processes, our costs went down.

Right now, we have Automation Anywhere integrated with artificial intelligence (AI).

I am certified in the Automation Anywhere University as a developer. It is a good tool. It goes topic-by-topic with real-time examples.

The product has a lot of options and visibility.

I just came to understand that there is a cloud attached to it. I would like to see how the cloud is going to work, because every application is coming out with a cloud version. If you are not on-premise, then you will need to have Citrix automation. 

It took one month to scale to the amount of bots which we are currently using.

Initially, the setup is not complex; it is straightforward.

We used a consultant for the deployment.

This product is really useful for me. I recommend Automation Anywhere as a solution.

The bot creation process is good, though it depends on the use case.

I don't use Citrix.

It is our RPA platform. It is the main platform that we use for backups.

It has helped us a lot with our digitized work.

We have automated a lot of the bank's processes.

My team has taken courses through the Automation Anywhere University. The courses have been good. They have helped us, but it could improve some things, like how the courses are designed.

It is pretty stable, but we have experience issues.

We are working on scaling it now.

We use it with more than 17 applications. So, we work it on a very large scale.

The technical support is good. 

It took us two years to scale it from the pilot it to our current number of bots. The process was too much work.

We have saved 53 minutes through automation.

It is a very good product.

It is for my partner development. We primarily work in the insurance business. So, we do a lot of insurance back office operations. These are the types of processes that we have automated.

We previously had a lot of manual processes. With the bot, we were able to automate them. Therefore, we are able to see the real-time value in our business area.

We have multiple developers on our team. With its user-friendly user interface, our developers are able to quickly pick it up. The ease of use is really good.

Bot creation is a cool feature. It allows the developer to do complex things. 

There are some places where Automation Anywhere needs improve a lot, especially from an integration perspective. We have had to build our own scripts to make this happen, building a bot in Automation Anywhere, along with some scripts. However, we have not yet implemented the Automation Anywhere MetaBots. So, once the MetaBots are implemented in our area, we should be able to achieve more.

If the bots become more stable, we can completely avoid using our additional scripts.

I would like to see the record management, data tracking, and database feature. Some of these have been implemented in the version 11. I have not used the latest release, version 11. Also, if some various cable features which come out with it, that will be really helpful.

I would not give stability good marks. There are a lot of negative things stability-wise. These things need to be improved, especially regarding reliability. When we have a huge end user process or need to automate a a huge volume, the failures are high.

The product is more stable versus older versions.

We face issues when we need to increase volumes. Currently, it is failing for some reason, and we don't know the reason. It fails or stops, then we need to see what is going on. We have to fix that, then our developers need to rerun it. These are mostly practical challenges for our team who uses it on daily basis.

Timing is a problem with the technical support. A person will be assigned, but that tech support person may only be available during our morning hours. In the morning, we might be in a meeting, not able to respond when the tech support reaches us, then when we try to reach them back, the tech support person may be on a call or not in the office. This is a challenge.

The initial setup was complex.

To scale from pilot to production takes a long time because the initial setup process is complex.

I am the consultant who does the deployments.

The ROI is really good. We have saved time and money.

We evaluated Automation, Kryon, and Blue Prism. Of those, we felt Automation Anywhere was more user-friendly. On the developer side, we received feedback that development was quick in Automation Anywhere, which is why we shortlisted them.

Since using Automation Anywhere, I might be inclined towards using another product.

Automation Anywhere is currently a good product. The RPA market is growing.

The integration with other applications is good. There are some complications. With some specific applications, it may not work. We are facing some specific issues, but we have found workarounds.

I am certified in Automation Anywhere University.

I have not personally used the IQ Bot nor have I used any trial version, but the features look really good.

I do not use Citrix automation.

The primary use case is to save hours for all the manual stuff which is going on.

Things are not overly complicated now. We can streamline processes.

Its ease of use is the most valuable feature. It is easy to train developers and find the right people, then use them to build the tool.

I liked the Automation Anywhere University. It was easy and simple. I hoped that it wouldn't take too much of my time, and it didn't, which was good.

I like the bot creation process, because it is very simple. If the process is not complicated, then the bot is really easy to create.

We had initial hiccups, like any new process. It took us six to eight months to sort the product out. It has been two years, and we know what we are doing and which use case work better for us.

We would like to use the mobile feature and give access to our users, but we don't know how.

The technical support is pretty good.

Everything was previously manual. We determined by going with an RPA solution that we would save time.

The initial setup was complex.

Automation Anywhere helped us with the deployment.

We measure ROI as in the number of hours saved not performing manual activities.

We evaluated a few vendors.

We have integrated Automation Anywhere with a few other application, but there is still more work to be done.

We have done some work with documentation, but not a whole lot. We are still exploring other features.

The primary use case is for optimizing processes.

It helps with the speed on improving processes and the results of those processes.

They could improve the learning curve.

The product is scalable.

We are measuring ROI through quality: Reducing errors, saving time, and saving money.

It is a good product.

it's not as complex as running a new computer language, but it is also not as simple as connecting EPL dots. Therefore, it is a medium level of complexity on the learning curve.

My team has taken course on the Automation Anywhere University. Their feedback was good. I have not taken any courses on it.

There are multiple use cases. Primarily, we are looking at finance and accounting. So, we have been deploying bots, specifically in the area of account payable and cash applications.

Bots add a lot of productivity and value to our business, because a robot can work for 24/7. They work a lot better, as compared to a human being, specifically for tasks which are repetitive in nature. Therefore, we are seeing a lot of business value being derived from these bots.

There have been a lot of challenges in terms of interfacing with the customer ERPs. So, we have been building tools and interfaces using bots to write back into these custom ERPs. Specifically, in the area where I work, this has been very helpful.

I have not seen bots working efficiently in the area of reporting.

The time it takes to scale bots depends process to process, how complex the process is and if you're talking about a specific process. It may takes anywhere from around three weeks to 15 weeks, depending upon the complexities, the number of bots which we are deploying, and the problem these bots are solving. 

My team is in touch with the technical support. I don't work directly with them.

Measuring ROI is a combination of multiple factors. It could be saving time, saving money, or getting controls into the systems. It's a combination of all this things.

I would recommend Automation Anywhere, as it is a known, leading solution in the market.

There are a lot of advantages which Automation Anywhere has over a lot of other vendors. Why we chose Automation Anywhere is because of the ease of scripting, the good support that they have, and we can deploy these bots for more customers, whose preference is also Automation Anywhere. 

Another thing that I have seen, with finance and accounting, Automation Anywhere is the better fit, as compared to some of the other vendors in the market.

Because of the ease in which we can deploy bots, along with the savings that it generates for our customers, Automation Anywhere definitely has an edge over other vendors.

When we started around two to two and a half years back, ease of use was a problem at the time. Right now, with the scripts and exposure that we have, I don't see a big challenge going forward.

My team has been trained through the Automation Anywhere University, so we do have a lot of people who have been trained on this tool. The training materials are good. The feedback that I have received on the University has been good, as I have not been personally trained through the University.

We have four core business areas: Energy, financial services, healthcare, and our internal corporate. We're spread pretty evenly across the four areas.

We have automated a lot of processes serving human resources, legal, life sciences, financial services, healthcare (on the payer and provider sides), and IT. We're all over the place.

We're still in the rapid expansion phase. The last six months have really been an explosion, so we're trying to keep everything under wraps and control it.

We are getting massive efficiencies across our back office, internally.

Th Enterprise platform: Automation on a platform, as opposed to scattered automation.

The ease of use is improving for development. We've had a lot of issues with the installation and performance on a variety of computers, onshore and offshore. Our network bounds multiple domains, and we've had issues there, as well. So, we are looking forward to the web-based development versions.

The bot creation process is getting better. The general development process and change management deployment process is moving more towards enterprise-level and catching up with the more mature software industry around it.

So far, the cognitive document processing is not available at the enterprise level. However, this is being worked on by Automation Anywhere.

I would like them to start building continuity between employees and customer contacts.

There are a lot of new features coming with the release of version 11.

The stability is improving.

The technical support is inconsistent. It seems like every time we call, there's someone who has only been with Automation Anywhere for a couple of months. Oftentimes, if you call two different people, you'll get two different answers, back-to-back. What we tend to do is, if we don't get a fix or resolution right away, we'll call back immediately or submit a second ticket immediately, and try to find someone else.

Our business teams pushed for an RPA solution.

We worked with Automation Anywhere on the deployment.

We have saved time and money using this solution. It varies pretty heavily by use case. We have some bots which are saving a week or month of multiple employees' times. We have some bots saving an hour a half during a day of a team of 30 people's times. So, there is some significant savings that we've uncovered.

Our annual license is somewhere in the neighborhood of $115,000.

Automation Anywhere, Blue Prism, UiPath, and Kryon were on our shortlist. 

At that time, Automation Anywhere was the most responsive to working with us. That actually tipped the scales.

The more you preplan, defining processes and governance upfront, the more successful you will be down the road.

The solution integrates well with others. When it doesn't, it is usually the fault of the other solution.

The courses on Automation University were generally good.

We have not done anything with Citrix automation yet.

We mainly use it for development of finance operations, and it's been performing fairly well for the most part. We have 40 automations going right now and they run daily on the Bot Runner.

We've automated journal entries, bank reconciliations, different claims-accounting - a lot of finance processes. For example, we created a system where accountants can drop in journal entries and the journal entries will be read and posted to our system.

One of the processes we automated was that people who work in treasury would go into their email and download PDFs from their emails over and over. Sometimes there would be 200 or 300 emails that they would have to go through, and they would spend a whole day doing that. Now we have an automation that does it, and it only takes one or two hours, and it frees up their time too.

We have saved time or money using this solution, but I don't know how much. That information is tracked by my manager.

The most valuable feature of the product is the flexibility. There are so many features that you can use to develop; it can hit a lot of use cases.

In terms of the usability, the drag-and-drop, instead of being able to type, makes it hard for somebody with a programming background to get used to it. The drag-and-drop slows down development; I can't just keep my hands on my keyboard, I have to use my mouse as well.

The bot creation process is tedious. The solution has a lot of features, but since you have to drag down a lot of the commands, it can get tedious to use it. You end up having to use the mouse a lot more. You can't do it as fast as if, say, you just typed it out on a keyboard.

Since I do a lot of bot development, I'd like a different way to develop them, other than dragging the commands down. If there were a way to type out the commands, to make it a little bit easier or a little bit faster to create the automation, that would be good.

Integrating this solution with other applications is hit or miss, depending on the application. For some applications it's very easy and then sometimes, for others, it's very difficult. There are occasions when, the first time, the application doesn't work at all, so we have to use commands that are not as consistent.

The stability of the solution is hit or miss. It depends on what you're using it for. Sometimes it's very stable and you'll never have issues, but for some processes it may have issues, and you have to be able to fix them and develop it properly.

What we're trying to figure out right now is how to scale this. That's where the hardware comes in. For the most part, scaling with the application is more a matter of building the infrastructure around it.

To scale from pilot to the point where we are now, where we're developing three or four bots every two weeks, it took us six months. A lot of that was trial and error, creating our standards, and hiring developers to whom we could pass the projects.

Sometimes technical support has been very helpful and they've solved a problem very quickly, while sometimes it takes a month or a few weeks to get a problem solved.

The setup was complex because we didn't want to just start making bots immediately. We needed to build the infrastructure around it so that, in the future, it would be a lot easier for us. Once we had a process for how to build bots, it was a lot easier for us, and we had proper standards.

We used Neuralify. They helped a lot in getting us set up and it's been a good experience working with them.

I'm not 100 percent sure how we measure the ROI of a process we automate because a lot of that is handled by my manager. From what I know, we measure it based on time returned to the employee. Instead of calculating how much time it takes for the automation, we calculate how much time the employee was spending on this task beforehand, and now that we've moved it to an automated process, how much we have saved them.

Overall, I think we have seen ROI, but I don't have specifics.

On the shortlist we had UiPath, Blue Prism, and Automation Anywhere. They ended up using Automation Anywhere because it was the most flexible and the easiest to use.

Instead of trying to build a bot immediately, first build the infrastructure for how you want to build the bots. That way, when you scale in the future, it's a lot easier than trying to figure that out after you've already made multiple bots.

I have taken courses at the Automation Anywhere University, but for the most part the courses have been very basic. I had prior training, but when taking it again in the University, a lot of it was just going over the basics of Automation Anywhere.