Automation Anywhere Reviews

The use cases depend on the group functions that are in our business units. They are related to finance, procurement, and marketing spaces. This is where we are heavily utilizing it for productivity gains in terms of FTE realization.

It is an enterprise-grade tool for us. At the COE level, we are using it for automations related to the group functions. We have a comprehensive team of around 30 to 40 people supporting it. It is not used for one or two use cases. It is a proper enterprise-grade automation mechanism for us for different areas. On average, we do a couple of million dollars of automation engagements annually with it.

It meets the productivity targets that we have set for ourselves. The customer service that they provide is also quite efficient. They try to keep a close eye on our key problem areas and how they can be a partner in solving it. It has always been a very positive collaboration with them.

The integration of automation into our workflows, APIs, business applications, and documents with Automation Anywhere is quite good. It is quite seamless and scalable. They are certified. We can only adopt it if it is a certified integration.

Automation Anywhere has helped save time and cost. The savings are tangible and recorded with us.

The core RPA service that it provides and the stability that it has in maintaining that as a cloud service solution is a key enabler for us. Its stability is good, and the low-code/no-code setup that it has is very user-efficient.

The AI centricity is a bit behind compared to the way we see Microsoft and AWS doing it. This is the feedback that I have also given to them. They need to expand themselves to provide more services than just RPA. Only RPA may not be enough for us, and it would not be our preferred choice for an automation tool.

I have been using Automation Anywhere for around three years.

It is quite stable. I would rate it an eight out of ten for stability.

Its scalability is quite good. It is much better and improved now. I would rate it a seven out of ten for scalability.

It is being used by multiple departments at one location. It is being used purely at the group functions level such as finance, supply, and marketing, but not for the asset-centric operations with mining and other things.

They are quite good. I would rate them an eight out of ten.

Positive

We are using both Automation Anywhere and Power Automate Desktop for different purposes. Automation Anywhere is our COE tool, whereas Power Automate Desktop is our citizen developer tool. We have good experience with both of them, but we are trying to make a switch from Automation Anywhere to Power Automate Desktop as a part of our cost-efficiency drive. We are doing a competitive analysis to see whether we are ready for it or not.

Overall, Automation Anywhere has been stable, especially the latest versions, but its usage is expensive for us. Power Automate Desktop is our preferred tool.

Our business users who are not technical are more comfortable with Power Automate Desktop than Automation Anywhere. Automation Anywhere is a COE-grade tool. It is not for citizen developers. Automation Anywhere is easy for professional developers or someone who has experience with automation technology. It would take a non-technical person a month of hands-on experience to learn it.

The deployment was good, but the migration to the cloud was a bit tedious. It was an extensive engagement.

The upgrades are quite seamless now because it is now in the cloud, so the effort is quite less. We have a team set up for maintenance.

A team of around 20 people was needed because it was a big-scale implementation. In migration, 25 to 30 people were involved. We have a DevOps team for operational support with almost the same number of people.

We have seen ROI for our original automations. They were mostly low-hanging fruits with savings of a few FTEs, but the moment any automation has an ROI of only one FTE, it is not an economical solution for us to use. Power Automate Desktop is cheaper for us to use.

Its usage is expensive for us because my user base is mostly in Manila and KL. The unit cost of labor is cheaper there than in the U.S. or Australia, which puts a bit more stress on how to get a positive ROI while continuing to use it.

I would rate it a six out of ten for pricing.

I would absolutely recommend Automation Anywhere. It has great potential. The people who provide services are quite professional. They want us to succeed in our journey. They are not only interested in profits. They want us to do well. 

When it comes to automation and AI, there is a huge appetite at the group functions level but not much on the asset side of it. We are more focused on health and safety, and from the functional or transactional aspect, we have a keen interest in the overall automation and AI.

Overall, I would rate Automation Anywhere a seven out of ten.

We have implemented Automation Anywhere for 2 finance use cases: recurring collections and payment forms processing. To achieve this, we leveraged the platform's invoice-tracking capability and built our bots around it.

We implemented Automation Anywhere to explore more automation possibilities.

We are happy with Automation Anywhere and the good experience it has provided. Automation Anywhere has successfully allowed us to implement our use cases.

We have identified several areas where we could potentially optimize the AI within our automation processes. However, the ultimate decision depends on the cost-effectiveness of automation. While we have a couple of significant use cases that seem well-suited for automation, others involve lower volumes that may not justify the investment. Currently, we're considering Microsoft's automation solutions due to their existing integration with our other Microsoft products. However, we might also explore Automation Anywhere for specific, complementary automation needs.

Someone with little automation experience can still create a bot using Automation Anywhere.

The learning curve of Automation Anywhere is adequate.

The time it takes to train someone to create a bot with Automation Anywhere depends on their existing technical background. For individuals with no prior technical experience, the learning process can take two to three months. However, if someone simply needs to become a casual user of a pre-built bot, a few weeks of training might be enough to get them comfortable navigating its features.

Automation Anywhere has significantly reduced our error rates, particularly in areas like allocating payment receipts and collections. Before implementing it, human error was a major issue. Automation Anywhere has effectively addressed this problem. Of course, reducing human involvement is a natural consequence of automation. However, a surprising benefit we've observed over the past two and a half years is that data quality has also improved significantly. Allocations have become much more accurate, which is an incredible advantage. Initially, the existing data was riddled with errors. Consequently, the automation rate was far lower than anticipated. However, as we progressively corrected the database, the automation rate steadily climbed, and error rates began to decline. It took roughly six to eight months to see the benefits.

Our organization has a defined AI automation strategy. We recognize its importance and have prioritized its development over the next two to three years. This focus on AI, particularly in customer service, will help us gain a competitive advantage in the marketplace.

Automation Anywhere is integrated with our ERP, human portals, supplier portal, and CRM.

Automation Anywhere has been instrumental in saving us both time and money. It serves as a core strategy in our efforts to streamline operations and reduce our reliance on manual labor. This has allowed us to handle multiple workloads with increased stability. We are committed to continuing on this path of automation to further optimize our processes.

While we initially implemented Automation Anywhere due to its inherent strengths, the software landscape has evolved significantly in the past two and a half years. Several competing products now offer superior functionality compared to Automation Anywhere's current capabilities. Microsoft's automation solutions are particularly compelling. They integrate seamlessly with the wider Microsoft product suite, which is often the core software environment for many businesses. This integration advantage isn't present with Automation Anywhere, which operates independently of Microsoft products.

The price has room for improvement.

I have been using Automation Anywhere for 2.5 years.

Automation Anywhere is a stable product.

Automation Anywhere is known for its scalability. This means that financial institutions can leverage it to automate large processes without worrying about the platform's ability to handle the increased workload. In simpler terms, Automation Anywhere can grow alongside our automation needs.

In the past, we relied on other automation applications. However, these applications lacked the flexibility and adaptability of a bot.

The deployment process was successful thanks to the contributions of the third-party implementation team.

The full deployment took eight months to complete.

For the implementation, we leveraged a third-party vendor with expertise in Automation Anywhere.

The positive return on investment for Automation Anywhere is clear after two years of successfully automating a few business processes.

Automation Anywhere, once a competitively priced option in the RPA market, has seen a shift in its pricing strategy. Currently, it stands as one of the more expensive RPA tools available.

In our evaluation of RPA tools, we've considered Microsoft Power Automate and UiPath. Automation Anywhere, while a strong contender, appears to have a steeper technical learning curve compared to the other two options.

I would rate Automation Anywhere six out of ten.

We rely on an external company to handle the maintenance of our Automation Anywhere software.

Companies considering an Automation Anywhere solution should approach it with a long-term perspective. Ideally, they should be prepared for a ten-year commitment. This allows them to understand how the product will evolve and adapt over time. A ten-year timeframe, or at least eight years, provides a significant advantage compared to a two to three-year outlook. By taking a long view, companies can ensure they are well-positioned to benefit from the ongoing development and reshaping of the Automation Anywhere platform.

Our use cases are around finance processes and one business function that we have a lot of automation. We're an agriculture and supply chain company, so we also have a lot of processes that would deal more with order processing, order management, customer service, and those types of processes.

We also have a use case from a document processing standpoint. We have a use case where farmers in Asia, in the APAC region, would handwrite inventory of that particular product, send a photo of it, and then someone would manually take that information and put it into the system or put it into a spreadsheet. We've been able to automate that. It not only saves time, but the data is 85% to 90% accurate versus it used to be about 60% beforehand.

We're finding time savings as a benefit. One example would be a customer service rep might get a question about an order, usually through email. It can take a good three to seven business days to answer a customer's question about their order. When we automate it, it takes hours, if not minutes.

We also are building out a new model for our metrics. Our biggest challenge is because Cargill is an international traditional company, we work with many different regions that have to abide by certain local rules and regulations.

We don't have just one order management process at Cargill. We have over one hundred and trying to simplify those processes first before we automate it is our biggest challenge. 

We're in conversations with Automation Anywhere now about process discovery. We've just kicked off. We are installing a tool with process discovery that we still haven't figured out what the best practice for utilizing it with Automation Anywhere will be.

We have a federated model. We are a center of excellence. We own the platform, and we build out the governance framework. We also provide training and updated communications to all of the users.

The learning curve is small. It takes only about four hours to learn it, but hands-on experience is different. That's what takes a little bit longer. Some users sit within IT, and some of the users sit within the business. It's fairly easy to teach others to leverage it. They have to have an interest in learning it, but it's fairly easy. 

Overall, Automation Anywhere has helped us save time. But we're also looking at customer satisfaction. We track sustainability numbers, if that comes into place. So we have a lot of different metrics that we look at versus just time.

One of the reasons that we chose Automation Anywhere years ago was because of the security because we need to secure both our customer and our vendor data. 

We have a lot of confidential data that we work with every day. 

Automation Anywhere has an audit tracker feature. When you build a bot, it has a trail of how you went about developing that particular bot.

We integrate other tools within Automation Anywhere. Overall, it's fairly easy. We have about 265 bots in production today. We see bigger challenges on the business side if they change a template and then fail to tell us that we need to change the bot.

We leverage IQ BOT. We have another tool that we leverage as well for document processing called Intelligent Document Processing (IDP). 

I want to learn more about CoPilot and then the process discovery tool. 

We are part of the Pathfinder program. It's more of a program versus a tool, but we're working with people to learn how we can scale our whole program using Pathfinder.

We've been using Automation Anywhere for about five to six years and continue to scale about 50 bots per year.

I'm very comfortable with being able to scale, especially now that it's moving into the cloud.

We've had really good support with Automation Anywhere. 

We have weekly tech meetings with Automation Anywhere. I also have strategic meetings every week and quarterly strategy planning meetings. We have a really good support system.

Positive

UiPath was one of the competitors, and we did bring on UiPath specifically for the Chinese language. That program has not scaled as we expected so we really are an Automation Anywhere shop.

We're going through the 360 migration right now. The bots that we have in production are fairly complex. It hasn't been an easy migration. We're getting through it, and we have a lot of support to get through the migration. But it's really more of the complexity of our organization.

We wanted to put together a streamlined platform versus having puzzle pieces and taping them together using different vendors. 

I wanted us to be more streamlined so that we don't have glitches down the road with upgrades and version updates. That's one reason that I wanted to stay with Automation Anywhere. 

Overall, I would rate the solution a seven out of ten. The only reason I wouldn't rate it higher is because a COE Manager still not getting the full benefit from it and because the premium is a little bit expensive. We don't necessarily have the budget to bring on a full new feature. Also, the process discovery tool is taking a little bit longer to implement than I thought it would.  

In the banking, financial services, and manufacturing domains it is used for process automation and OCR.

For example, it is used by banks for large-scale reconciliation. A group of companies often has multiple bank accounts. We have to do the reconciliation with multiple currencies. On a daily basis, there can be more than 10,000 transactions.

We have implemented Automation Co-Pilot in our organization. Suppose a business head needs to check the details about a customer, such as order history, payment clearance time, how many invoices have been sent, and how many of them have cleared on time. They may also need information about how many projects they have executed with that customer, how many of their resources have been used, and how long that customer has been associated with their organization. I get all this information in one portal by using Automation Co-pilot.

It is talking with Monday.com, our CRM, as well as with our in-house project management tool, and SAP, where I get all the account details. It gets all the information needed and more, such as how many times we had discussions with the customer about multiple projects, and which salesperson is assigned to that customer. All the details required for business management are presented on one page, using Co-Pilot.

An example of how Automation Co-Pilot has affected our productivity is that in India the taxation system differs from that in the UK. Everything is on a government portal. If I want to deal with new customers and need data about their previous taxation, I obtain all the details from the government portal using Co-Pilot.

We also use Co-Pilot for customer support. We are the number-one partner in India for Tableau and data analytics and we have many projects where we provide Tableau support. We've configured Co-Pilot to gather all the necessary background information from our support system about a customer who raises a ticket. This information is displayed on one screen from our project management systems, repositories, and accounts. All the details are presented in our ticketing software, Jira. Based on this information, we understand the customer's scenario, and what kind of dashboards and RPA processes they have implemented. Initially, a customer support ticket is opened by a chatbot, not a human. The chatbot communicates with the customer and registers the ticket. A bot then opens the ticket and triggers Co-Pilot to gather all the details. With all the details collected, a bot will then assign that ticket to a specific person. This process, which used to require three people, is now done completely by bots.

Another benefit is around approval processes. You can build one using Automation Anywhere Co-Pilot when multiple levels of approvals are involved. Initially, we didn't have an approval process. Multiple people were in approvals. Now, with all the details in a ticket, when it is resolved, it is approved by the manager. That wasn't integrated into Jira, so we automated that in Co-Pilot. A solution should be verified by a senior person. Now, when tickets are approved, it helps us provide a good customer experience and customers will renew their contracts.

And in banking, where you have thousands of loan applications each day, assessing each application involves getting the applicant's credit score and details from multiple portals and government websites. Making a decision for one applicant used to take half an hour. But by using Co-Pilot, the decision-making time is reduced to just five or 10 minutes. It is genuinely helping people speed up operations and decision-making processes.

It has also helped us increase automation. Every day we are sending the "overdue" report to everyone in sales because they do the recoveries. The salespeople update all the details in the database and a reminder is automatically sent to the customer as well as the salesperson if the payment has not cleared within the payment terms. Initially, there were three people generating the reports and sending them to Salesforce, updating SAP, et cetera. Now, there's only one person who is handling the exceptions, because there are exceptions that are not handled by the bot.

Now, our salespeople are focusing more on business opportunities and not worrying about payments. Most of the time, payments are taken care of by the bot.

After we implemented that process, we then implemented vendor invoice processing, customer invoice processing, customer payments, PO processing, and bank reconciliation. We have implemented multiple processes.

The most valuable feature, which was launched last year, is Automation Co-Pilot. Microsoft has a co-pilot, but it's only for Word, Excel, Outlook, and PowerPoint. But Automation Anywhere offers a co-pilot that is suitable for Salesforce, Genesys, Atlassian, and other contact center and standard applications. This is a game-changing feature for Automation Anywhere compared to the market. We are also getting good responses from customers about this product.

Automation Anywhere is easy to use. In my experience with more than 100 customers, coding is not a big deal nor is writing the bot. Understanding the process and providing optimized workflow, and fitting RPA properly for their processes are important.

In terms of the learning curve, Automation Anywhere provides detailed resources through their portal, including instructor-led training, prerecorded sessions, and exams. When training my team, I initially recommend that they go to the Automation Anywhere University. Then, for two days, I provide high-level training, covering the use cases and overall process. We then give simple use cases to the team and they are ready to implement them. Within three months, I have trained a team of over 20.

I hire people who have worked with other technologies but who want to shift to RPA. They already have knowledge of processes and their logic is strong. Others don't know about logic or how to apply algorithms.

I'm impressed with the solution's OCR and document automation because I've worked with multiple OCRs and Automation Anywhere has built in most of the document formats so you can easily get results. You can easily and quickly extract data from a PDF and it's faster than other tools.

I would like to see a low-code/no-code platform, similar to Zoho Creator or Joget, for process building, so that we can build applications within Automation Anywhere itself. Right now, we need some kind of portal that supports these types of activities. We would like to give a 360-degree solution to our customers without needing to get help from other technologies, like Joget to build processes, or Java to build custom portals.

If Automation Anywhere included these features, I would be able to include all these processes. There are features in place in Automation Anywhere right now, in AARI and Co-Pilot, but they have limitations. They do not match the development capabilities of platforms like Joget or other applications like that.

I'd like to see the stabilization of Co-Pilot and integration with multiple products. Right now, it is integrated with Genesys and Salesforce, among others. In the future, I will require integration with SAP Oracle, Atlassian, and Service Now. The contact center vertical is important and ticketing comes into the picture. We can build integration with Atlassian, but I have to do the coding and use extensions on everyone's laptops. Integration of Co-Pilot with Atlassian and other products will help the user.

For instance, if a big bank wants to automate loan application management with Co-Pilot and I need to use their CRM, if the CRM is not supported they won't do the project. And if a bank has over 3,000 loan agents, I have to install the extensions and integrations on each of their laptops. Instead, I could add one line of code inside Atlassian and get all the results automatically on everyone's laptops. This would save a lot of time for both developers and customers.

I have been using Automation Anywhere for more than four years.

Technical support is related to the product only. We receive good support from them because they respond within one hour. They even have chat support.

Customer environments aren't the same. Sometimes they block the reverse proxy or other things. That's when I need help from Automation Anywhere because they are the product experts, while we are implementation experts. If we have an issue with the product, we get help from Automation Anywhere. 

For example, if there is a problem with communication between the server and client and the bot is down, I need to contact Automation Anywhere to resolve the issue. We reach out to Automation Anywhere for these kinds of problems, but we handle process-related or implementation-related issues ourselves.

Positive

I worked with UiPath for about two to three months.

Co-Pilot is not free. It has a user-based cost. If I have 100 users, I need to purchase 100 licenses. But for practice purposes, you can get the Community Edition where you can understand all the details for implementing Co-Pilot.

The pricing is reasonable.

Automation Anywhere is the only RPA tool that is developed using something other than .NET technology. If you go for UiPath, Blue Prism, AutomationEdge, or Pega, they are all built on .NET, and only support Windows. But Automation Anywhere is developed on Java and Python entirely, and is totally web-based. Other tools are desktop-based. That means I can install their server on Linux too. Most banks and many other enterprise organizations require servers on Linux, not Windows. That's an advantage for Automation Anywhere.

We are working with one of the top-three banks in India. They have a policy that all servers have to be Linux servers. Because of that, UiPath and other tools were eliminated in the first stage of the deal.

We did build our own product related to OCR but not RPA, but Automation Anywhere is the biggest product. We also looked at Power Automate, but cost was a factor. Power Automate charges per process, not per bot. For example, it doesn't take more than 10 minutes to close the last month's General Ledger. One of our customers was paying $600 per month for this process with Power Automate. He went with Automation Anywhere, where he only had to pay $3,000 to $4,000 in total for an unattended bot, which was able to help 24/7.

And to get all the components in UiPath that are similar to what you have in Automation Anywhere, a customer would pay more than $37,000, while an Automation Anywhere customer would only pay $25,000. That is a game-changer.

As for using an API integration instead of RPA, API is faster than desktop automation, but it depends on the scenario. If you want to work with standard applications like SAP or Oracle, you can use APIs or desktop automation. I faced an issue with one of my customers who said that to do an API ABAP integration for SAP automation, he would have to pay for automation and ABAP development. I suggested he not pay for ABAP and just do desktop automation. What will be cost-effective depends on the scenario and the automation.

If a customer has to spend $10,000 on ABAP and another $30,000 to $40,000 for Automation Anywhere, they will kick us out. But if we go with Automation Anywhere and there is no need for ABAP, and instead we'll do desktop automation, the customer will be much happier because they are saving costs.

I have replaced existing portals for multiple customers. For one of my customers in Dubai, when we came into the picture, multiple things were not in their portal. They had developed the portal in-house. We started by understanding all the requirements. Before we started with RPA, we redeveloped the portal and then applied RPA OCR and pushed the data where it needed to go.

People develop their portals according to their convenience, but they don't know the standard processes and how to implement them. When they have to provide reports to management, or they have to do an audit, or they have to check details of particular transactions, they don't get the details from their existing portal or process. We standardize their process and then we implement RPA. If their process is not standardized, RPA will be a failure for the customer.

A simple process, from requirement gathering to production, takes about one month. Solutions don't require more than two or three people. For smaller projects, we don't assign a dedicated project manager. Instead, we use a shared project manager. The business analyst is also shared, because the costs of these roles need to be recovered. If the cost isn't recovered, there's no need for us to assign this role. The business analyst will do the final testing of the project because they're involved from the initial phase of the project.

The time spent maintaining bots depends on the bots, the situation, and the customer. A critical process might have 40-plus unattended bots and might take two resources during business hours for project support and monitoring. But I recommend support on an hourly basis.

An enterprise with multiple licenses should have at least one dedicated support person. That resource will provide reports to management. For instance, when discussing future projects, management will require all the information to approve the budget. We can present all the information: the number of transactions over the last month, and how much time or money was saved. Support will also provide training to business users if required. When AARI is part of the picture, we have to train people.

I use Automation 360 as an RPA developer to automate BPS processes. I have developed over 12 to 15 bots that handle back-office tasks. 

My current project is a UK-based water project. Previously, they would take the meter readings and send them to us for quarterly billings. We used to manually enter them in the system, whereas now, we have a bot to help us enter meter readings.

We have also developed a bot to open accounts for new customers. The bot takes all the input from the customer, creates an account, and sends a welcome letter.

Automation Anywhere has significantly helped my organization by automating tasks that were previously done manually by the back-office staff, resulting in increased efficiency.

A technical user can see the benefits of Automation Anywhere within a few days. After developing a bot, there might be some issues that need to be fixed in the bot. After resolving those issues, the benefits are immediate.

In terms of integration, I have integrated Automation Anywhere with some desktop-based applications, web-based applications, CRM applications, and Excel. I have also integrated Outlook where the bot sends an email through Outlook.

The recorder capture tools, specifically the AISense Recorder and Universal Recorder, are valuable. We use these tools in almost every automation. These tools are very effective in capturing data from various applications. We can get data from a web page or an application.

The integration of Generative AI is promising, though I have not yet developed bots using this new capability. It will be helpful for us in the future.

Automation Anywhere is a simple and easy-to-use solution with drag-and-drop activities. Automation Anywhere is easier to learn than any other tool. They also have Automation Anywhere University for learning. They upload all the videos there. They also have a good community.

Automation Anywhere has newly integrated the Generative AI feature. It should be more customizable. Currently, we can change certain parameters, but we would like to have the ability to do modifications within the LLM for better outputs. We would like the ability to fine-tune it. It would be better if Automation Anywhere could add some extra features for us to use the Generative AI feature.

I have been using Automation Anywhere for two years.

We are not facing any issues related to stability, lagging, or downtime.

Automation Anywhere handles scalability well with features like workload management, which helps in distributing tasks across different machines and bots. With workload management features, we can manage and distribute our workloads.

We have been facing an issue with the bots for the last two weeks. We have developed 15 to 20 bots for a client. After making any changes, when we push a bot in production and run it, the bot gives a preprocessing error. We were not able to find the reasons for that error, so we contacted their support and created a ticket. They got back requesting the log files. We need to take those log files from the client and provide those log files to Automation Anywhere support. They have been responsive so far and are working on resolving our issues.

Positive

I have used other tools such as Selenium, UiPath, and Power Automate to automate processes but have not extensively worked with them. I primarily work with Automation Anywhere.

Currently, we are using it for one client, and for that client, it is deployed on-premises. The initial setup was quite straightforward, but I was not responsible for the deployment. My role is focused on bot development and testing, while other team members handle deployment and maintenance.

I have not worked a lot with earlier versions or migrations of Automation Anywhere, but I have experience in migrating a bot, which was easy. I could easily migrate a bot from version 11 to Automation 360.

I recommend learning one RPA tool thoroughly before moving to another. With advancements in AI and ML, it is crucial to look into how to integrate these technologies into your automation.

A person without any technical knowledge can learn Automation Anywhere within one or two months. When a new employee joins our organization, our internal trainer gives them training for four to five weeks. Every week, there are two to three sessions of two hours duration. After about 15 sessions, our employees are ready to use Automation Anywhere to develop bots.

I would rate Automation Anywhere an eight out of ten.

We mainly use Automation Anywhere to automate or mimic manual business processes. We use Automation Anywhere to develop bots that mimic human interventions in business applications such as SAP and web report applications. We use Automation Anywhere to automate human actions in the applications.

By implementing Automation Anywhere, we mainly wanted to automate business processes.

I am a developer, and I am using Automation Anywhere to develop automated tasks for business users. I am not a business user. Before automation, business users were manually updating the data into the portals or desktop applications. The business required more time and resources.

Automation Anywhere helps save time and resources for the business. For example, an e-commerce website wants to create purchase orders for its client orders. They get the information regarding the clients in an Excel form, and the bot picks up the data one by one and updates it in the desktop or web application. They get hundreds of records daily, so updating the data manually can take more than a week. The business would require at least two to four resources. To save time and resources, we automate such tasks. With a bot, the process is done within minutes.

We are a service provider for business people. So far, our business people are very satisfied with our bots. They are getting huge outputs as per their expectations. It is beneficial for our clients.

There are multiple features. About three to four years ago, they introduced IQ Bot which helps to get data from documents with different structures. We receive bills, invoices, or purchase orders from different vendors in multiple formats. Each vendor uses a different format. IQ Bot automatically scans all the documents, extracts the required data from all unstructured documents or PDF files, and provides it to the business user. It is a very helpful feature of Automation Anywhere. They have recently introduced Automation Co-pilot which is very helpful for developers doing automation or automating the business process. Automation Co-pilot is very useful to create tasks.

Its user interface is very understandable. Even a non-technical person can understand it. Everything in the user interface is self-explanatory. It is quite good.

To use Automation Anywhere, no technical knowledge is required because it is simply a drag-and-drop type of tool. Each and every action is available in the tool, and we can easily automate a task. Business people can also easily run the created bot and monitor a particular task. They can easily monitor the results based on their business criteria. Automation Anywhere is a very good tool. It is easier than UiPath. A non-technical person can learn it very quickly.

I have experienced the issues of UI getting stuck. There seems to be an issue with server stability. This is something that can be better.

At times, the created tasks start failing randomly or intermittently which affects the business. They are failing at the runtime because of the bot launch crash issue. Business people are impacted a lot because of these failures at the run time.

I have been using Automation Anywhere for four years.

We sometimes have issues with server stability. There are also run-time failures of bots. I would rate it an eight out of ten for stability.

For scalability, I would rate it a ten out of ten. Automation Anywhere is moving with the current technologies. It is scaling day by day. 

We are a large organization.

We have used UiPath. It needs technical knowledge. You must know the C programming language to automate with UiPath. As compared to UiPath, Automation Anywhere is better. A non-technical person can easily understand Automation Anywhere.

We are also learning Power Automate. As a service provider, we need to learn the latest technology. We are looking into Power Automate. Our business people are interested in Power Automate because it comes along with Microsoft Office.

Automation Anywhere also keeps on introducing the latest technologies. In the future, there will be good competition between Automation Anywhere and Power Automate.

Previously, it was on-premises, but now, everything is on the cloud.

Its deployment is very easy. Because it is a cloud platform, you just need to install a single file. It does not take more than two minutes to download. Within two minutes, the cloud license will appear. One person is enough for the deployment.

It gets updated automatically because it is a cloud version. There is no need to update it manually. Everything is done automatically. If auto-update is not working, we can update it manually, but that also does not take more than five minutes.

In terms of maintenance, regular maintenance is required because there are issues related to stability and tasks failing at the runtime because of unknown reasons. These things need to be fixed, so regular management is required for Automation Anywhere at the backend.

I am a service provider for business people. Business people will have a better idea about the ROI. From what I understand, there are time savings. 

My understanding is that the license cost of Automation Anywhere is more reasonable than UiPath and Blue Prism.

I would recommend Automation Anywhere for all business people. Automating a business process is easy with Automation Anywhere.

We have not yet used Automation Co-pilot. From what I know, if we are reading from an Excel file, it helps to generate each and every action for a task. What usually developers do is done by Automation Co-pilot automatically based on the information that we give it. Automation Co-pilot will improve productivity for a repetitive task. It will save 40% to 50% work for developers. We are currently not using the AI capabilities of Automation Anywhere.

I would rate Automation Anywhere a ten out of ten.

Automation Anywhere is used to elevate the customer experience for our financial advisors. We aim to improve our interactions with them in terms of their requests for updates to their banking instructions or anything else related to their accounts. 

Automation Anywhere has helped us improve our service. Our financial service professionals gave us some feedback that they are spending a lot of time calling our home office to check on the status of requests and doing other things that I would describe as administrative activities. That takes some time that would be better spent building their businesses and growing their relationships with their clients. It allows us to automate and streamline those administrative tasks for our financial professionals and employees.

We did everything manually before we implemented Automation Anywhere. When a financial advisor initiated a request, someone had to input that information into the appropriate record system and communicate with the advisor to update them on the status. Someone needed to follow up on the request and ensure it was completed. 

Automation Anywhere has challenged us to rethink the art of the possible. We're still considering how to leverage AI. Our attitude toward AI is evolving, but we know that it's something we must address. We believe that a delay in adopting could have an exponential effect on our ability to compete and remain among the industry leaders. We are evaluating a few use cases. In particular, we see content and knowledge management as a huge opportunity. We're exploring ways to leverage document understanding and natural language processing to quickly process the information and take the appropriate action. 

We have the unattended bots running in our environment and recently launched our first document automation use case. We are also excited about the automation copilot. These use cases are crucial in the wealth management industry, which is paper-intensive, so it's essential to leverage automation for document-focused tasks. Co-pilot allows us to streamline that process while improving the accuracy of the information entering the system record and ensuring efficiency. 

The unattended bots are working behind the scenes so that employees don't need to do work that they had done previously. Our tests of the document automation and copilot features have received a positive initial response.  Employees like the UI and how it brings out the information for them to validate.

We've integrated Automation Anywhere with our internal homegrown systems and a couple of third-party applications through APIs and UI interactions. The integration has been smooth, especially from an API perspective. We can quickly pull together API endpoints for our development and leverage APIs from third parties. It's been pretty easy to bring it all together using some basic Python coding. We spend more time ensuring we have the correct information from the API owner, so we get the right connections. 

From the product side, I like the minimum viable product approach, where the first generation of a new product is released and tested in the market, but it would be great if some of those pieces were a little bit more thought out from a user experience perspective. They could take a little more time to get some insights from their customers like in a beta test or something like that. 

We have used Automation Anywhere for the last 15 months. 

Automation Anywhere's ability to automate at scale is very impressive based on what I've seen internally and heard from subject matter experts. We're starting to see what we can do with it. When we developed a rudimentary proof of concept with co-pilot coupled with document automation, it was eye-opening for our leaders and stakeholders to see how versatile and accurate it was. 

I rate Automation Anywhere support seven out of 10. I would also like to see better communication with their customer success teams. It often takes longer than expected when we submit requests for help or come across a problem we want to resolve. While I can appreciate that it sometimes takes a while to get the appropriate answer, it would be nice to be in constant communication about where they are in the process.

Neutral

Deploying Automation Anywhere was relatively easy. We implemented our first bot last year as a proof of concept. We tried various things to give us a bit of a different flavor. Whether we're using an API, UI, or doing a physical task within a third-party application. Our first bot took 10 weeks to deploy, and the rest took between eight to 10 weeks. The development time is about half of that. Most of our use cases were simple, but it took time to coordinate with various teams, like infrastructure, security team, risk management, and other IT departments. 

My role is in the center of excellence. We're on the business side, not the IT side. The company is a little different in how it sets up its CoE programs. We focus on business processes and engineering. I rely on our technology and security partners for those other pieces. There's a little bit of trial and error. We have to think of security first and foremost. We're protecting our data and our client's data.  

We needed to figure out how it fits into our ecosystem because we had never done it before. We needed to set up virtual desktops, servers, and those sorts of things. We needed to create an Active Directory account for our robots to interact, receive email, use Excel, etc. Early on, we had to learn the nuances because we would need to replicate the processes going forward. We created some reusable runbooks and IDs to set access to the system with different privileges for employees and contractors.

There is some maintenance for bots that utilize UIs, but not those that use APIs. We face more challenges when working with third-party applications because they have scheduled updates. If the bot is scheduled to run on Thursday at 2 pm, but suddenly, a pop-up window appears to run the update. We've mitigated a lot of that. If we don't have APIs, those use cases require a little bit more handholding. 

We leveraged a consulting firm to partner with us on that proof of concept. They brought expertise and ensured we were set up for success. They helped us configure our control room and enabled us to perfect the concepts, so we could see the results and realize how successful we could be with Automation Anywhere's product. 

We looked at some other solutions initially, but one of our sister firms was already an Automation Anywhere customer, and they gave the solution glowing reviews. We saw how successful they had been in leveraging Automation Anywhere's platform, so it made the decision easy for us. 

I rate Automation Anywhere nine out of 10. They're passionate about the product and want to see us succeed as customers. They will go to bat and contact the engineers to help us achieve what we want. We have on-site visits with them and business reviews where they will talk about our roadmap and potential use cases.

We've had many sit-down conversations with the Automation Anywhere team when we were testing out the document automation. We gave them feedback about potential enhancements, so when we launched our most recent document automation use case, the capabilities were already there. We didn't need to come up with a workaround or put the project on hold because the things we needed were unavailable. That commitment to customer success stands out because they know that without us, the product won't succeed. 

Our company uses the solution for automations. 

As a portfolio manager, the key responsibility is to determine how to use our latest technologies for use cases. We identify use cases in various functions and buy software licenses for them. 

Once we buy licenses, we use the solution for end-to-end discovery of use cases, onboarding in-house technical staff for ongoing management, and collaborations for training or licenses. 

Our licenses are used by our technical team within our Center of Excellence. The team handles the end-to-end work that includes development, testing, quality assurance, and production. We are using the solution to its full capacity. Bots are at an optimum because we want to extract maximum value from our licenses. 

We plan to increase usage once we finish migrating from on-premises to the cloud. 

The solution has helped us embrace more of a digital transformation footprint, bring in efficiencies, and create an internal infrastructure.  

The solution's architecture is very nice. The three components are a bot, a control room, and a bot developer. 

The control room is quite a good feature. It is easy to use and gives you the power to manage your digital workforce. It gives you a sense of understanding in terms of how the audit trail happens. 

The solution should include an analytics dashboard. As the space is maturing, many vendors sell functionalities as separate components so this is not unique to the solution. If I am buying a license, I should at least get a flavor of my analytics with a dashboard related to operational KPIs. Right now, if you want detailed analytics, you need to buy the dashboard separately. This licensing structure adds to the overall cost. 

The solution should include bot insights instead of selling it as a separate license. From the bot and business perspectives, insights are important for operational agility metrics and managing KPIs. For example, I want to how many hours in a day or month a bot runs for human resources when it performs A, B, C, D, and E and gives benefits across D, E, and F. 

I have been using the solution for three years. 

The solution is stable so I rate stability an eight out of ten. 

The solution is somewhat scalable so I rate scalability a six out of ten. 

We get the right support when we ask for it. Sometimes though, service requests are not handled within the timeframe we expect. Issues move in circles until they are placed with the proper technician. 

There is definitely an opportunity to lessen the response time so I rate support a seven out of ten. 

Neutral

I have prior experience with UiPath to a certain extent. 

The setup takes a good amount of time because you have to develop an infrastructure that includes servers and compliance. A lot of time is spent framing those requirements and signing contracts that are quite detailed. 

I rate the setup a five out of ten because it is not that easy.

We worked with technicians from the solution to implement.

There are some difficulties in migrating to a new platform. There are a lot of internal governance forms or approvals that can delay the process. Lots of things need to be reworked as you go through the process. 

For about four to six months, you can take on the fixed paper side to get all the needed approvals. In some cases, the process might even take eight months because everything takes time and other business activities may take priority. Separate contracts need to be created for automations and they are usually handled by another team. Many approvals are needed at all levels of the organization. 

We currently use the solution on-premises but are migrating to the cloud. This process is also not that smooth and requires nudging. We are going back to the drawing board to take another look at things and rework if needed. Most components should be scalable and reusable but we are having a few issues on that front. 

Ongoing maintenance includes our internal team working with two or three of the solution's technicians to resolve issues. The solution's team routes or allocates the right technician to handle our service request. Our internal team supports and helps their technicians to understand our unique scenario. 

The solution is definitely worth the money. It is up to you to add quality use cases and utilize the digital workforce along with the human workforce. The tools are there, but the actual metrics derived are your baby. There are many benefits to automation solutions. 

I won't give 100% credit to the solution. Perhaps UiPath would have given us the same results. The way you use a solution makes all the difference in ROI. 

Similar to how competing products are priced, the solution has separate licenses for features that should be included in a bundle package. For example, the analytics dashboard and bot insights are sold as separate licenses. 

No one wants to buy a product that is too complex because components are sold separately. Give longstanding customers these benefits as icing on the cake. 

The solution is not the least or most expensive. Pricing is good and in the middle so I rate pricing a five out of ten. 

The options were evaluated before I joined the team, but I believe the company also looked at UiPath, Info Sales, and XCL. 

No tool, product, or technology is 100% foolproof. Each has its own set of pros and cons, including the solution. 

The common sales approach across the solution and other vendors is misleading. They make it look like a utopia where you will increase productivity by 200% in six weeks. This is not possible because organizations can't do magic in six weeks. Some of the claims being made by developers or content providers are creating a false impression in terms of senior management. There is no magic wand. There has to be automation. It looks and sounds simple, but implementation is not that easy. Your program, team, and communications management need to move in tandem to give you the inputs or outputs for sensitivities around people, roles, responsibilities, and training. 

It is important to be realistic when launching a new product or partnering with a player in the market. Be open and honest with customers. Don't make things too glamorous because it will be difficult to achieve that expectation. Stop overselling it and just be natural. A lot of consolidation is happening in the space and customers are aware because they read Forrester and Gartner. You can't fool customers so be honest and let them know that the solution needs to be managed by human beings. 

The biggest lesson is to understand the functionalities you need before you buy the solution. Determine if the solution passes the litmus test. Be cautious about overselling it and instead set the right expectations. 

Ask upfront if some additional features can be bundled because that will really help with your automation journey. 

I rate the solution a seven out of ten.