Try our new research platform with insights from 80,000+ expert users
Senior Process Automation Analyst at a computer software company with 501-1,000 employees
Real User
Top 5Leaderboard
Helps us save time, save costs, and improve productivity
Pros and Cons
  • "A cloud deployment typically takes no more than one business day."
  • "Automation Anywhere has a persistent click-related issue that can make automation difficult, particularly in unattended environments."

What is our primary use case?

I utilize Automation Anywhere for automation purposes. Recently, I completed a project for a client in the telecom sector. The project involved automating their monthly bill review system for customers. Previously, this system required on-site employees to check millions of invoices each month manually. A dedicated department then verified these invoices, sent them to customers, and verified payment status after payment. This process was time-consuming. We used Automation Anywhere's RPA and OCR capabilities and the AI document processing module to analyze document structures and verify tabs. We then automated various steps like accessing the portal, applying checks, and sending invoices via email. Now, the entire process is automated, triggered by a robot each month.

The main challenge which organizations want to address through any implemented RPA solution is the repetitive nature of their tasks. Instead of having ten employees perform the same monotonous task from nine to five every day, a single RPA robot can handle the workload, freeing those employees to focus on tasks that require human intervention. Automation is ideal for repetitive tasks, such as processing millions of invoices monthly, which can now be managed by a few RPA robots working around the clock. This allows employees to explore new opportunities, which is the primary goal of automation and the main reason for using RPA or any automation technology. Most automation technologies have features that enable this shift. However, automation is not suitable for all tasks; tasks requiring approvals or human judgment cannot be automated.

The deployment model varies depending on the client. In Pakistan, I worked with several clients using ABL who opted for cloud deployment. However, clients dealing with highly confidential and sensitive data, such as banks and telecommunications companies, prefer on-premises solutions. In contrast, clients in sectors like healthcare might be more open to utilizing cloud infrastructure.

How has it helped my organization?

Automation Anywhere has enabled repetitive tasks previously done manually to be automated.

Regarding RPA, ever since generative AI was introduced, we have ChatGPT and Google Gemini. The advent of these generative AI models has shifted the automation landscape. Automation has moved from Robotic Process Automation towards Intelligent Process Automation. The difference between RPA and IPA lies in their ability to handle changes. For example, if a website form changes its layout, a traditional RPA bot might fail because it can't identify the fields or buttons in their new positions. However, with IPA, the bot is intelligent enough to understand the fields' requests and can still process the data regardless of UI changes. Besides this, numerous other IPA use cases leverage Large Language Models and generative AI. For instance, a company could have a trained dataset monitored by an RPA bot, which then uses generative AI to create and send daily reports to top management, analyzing current numbers concerning past performance. This is a fascinating area that I've been exploring and working on lately.

For business users without technical skills, automation is achievable depending on the complexity of the task. Simple processes like sending custom emails from an Excel list can be easily automated with basic tutorials. While time and practice are necessary for mastery, basic automation can be initiated with just a few introductory videos.

We recently started using Automation Anywhere Copilot, so we haven't had the opportunity to integrate it with many of our automations. However, we have integrated it with SAP, where the bot reviews SAP data and provides the user with the required information at runtime. I have utilized this feature, and it's quite interesting. They also offer integrations with many other software, so the integration level is relatively high. Regardless of the type of features the business uses, whether they are using Salesforce, Microsoft Dynamics, SAP, or even AWS, integrations are available. They provide custom APIs that can be used for integration.

Automation Copilot helped increase our productivity by 60 percent.

Copilot has enabled staff to focus on other tasks by automating processes. For instance, the business department aimed to automate 350 processes this year, but by September, they had already surpassed that goal with 370 automations. Similarly, last year's target of 250 automations was exceeded, reaching 300. This increased efficiency has significantly improved workflows.

Our primary application of Generative AI for our telecom client is to detect service outages, such as when an area experiences a loss of service. We've been strategically planning our Generative AI approach for this year and the next, focusing on utilizing RPA to identify potential solutions and valuable insights within our data. For instance, in the context of outages, we aim to pinpoint the areas with the highest outage frequency, understand the reasons behind those outages, and correlate that information with customer complaint data. By analyzing metrics like complaint resolution times and outage resolution times, we can create a benchmark that helps us identify areas where we can enhance our customer service.

The amount of time Automation Anywhere helps save is dependent on the automated task. For example, the bill review task we automated helped save 10,000 hours per month.

We have several custom ERPs used internally but primarily rely on Microsoft Dynamics. We have a BCRM portal built on the Dynamics portal, hosting both our BCRM business-facing and CRM customer-facing systems. We also utilize Excel with VBA macros and other platforms, including Kofax for OCR. Kofax's Arabic language detection capabilities are crucial for processing UAE ID cards containing Arabic text. Kofax is our organization-wide OCR solution, integrated with Automation Anywhere. Overall, we have integrated Automation Anywhere with various software solutions.

Integrating Automation Anywhere into our workflows, APIs, and business automation is simple. RPA functions like a digital employee, and we can instruct them to perform tasks. Any activity currently done by a human employee can be done via RPA. However, the crucial question is whether it should be automated. If a task is performed infrequently, such as once every six months, creating an automation is inefficient. The time spent developing the automation could be better used to complete the task manually. Automation is ideal for repetitive tasks performed frequently. If a task isn't repetitive, automating it might not be beneficial. Regarding the capabilities of automation, nearly any work an employee performs on an organization's system has the potential to be automated.

What needs improvement?

Automation Anywhere has a persistent click-related issue that can make automation difficult, particularly in unattended environments. Even the Automation Anywhere team is aware of this problem, which has existed for several years. When automating tasks on a website, clicks may not work as expected in an unattended environment despite functioning correctly otherwise. The Automation Anywhere team has had numerous meetings to address this issue, but a solution remains elusive.

For how long have I used the solution?

I have been using Automation Anywhere for almost four years.

Buyer's Guide
Automation Anywhere
April 2025
Learn what your peers think about Automation Anywhere. Get advice and tips from experienced pros sharing their opinions. Updated: April 2025.
849,686 professionals have used our research since 2012.

What do I think about the scalability of the solution?

Automation Anywhere's ability to provide automation at scales is dependent on how well it can integrate with every platform. I would rate the scalability seven out of ten.

How are customer service and support?

I compare all other RPA tools to UiPath, which has excellent support—I'd rate it ten out of ten. In contrast, I'd rate Automation Anywhere's support six out of ten.

How would you rate customer service and support?

Neutral

Which solution did I use previously and why did I switch?

In addition to Automation Anywhere, we also use UiPath, and Power Automate.

It ultimately depends on the client's preference for an RPA solution. In my opinion, UiPath remains the leading option in the market, unmatched by any competitor. Automation Anywhere currently holds the second position, but I anticipate Power Automate surpassing it in the future. However, UiPath is considerably ahead of the competition, leaving Automation Anywhere as a distant second. While Automation Anywhere is a suitable alternative, UiPath's high pricing can be a factor in the decision-making process. A lot of our clients choose Automation Anywhere because it is cheaper than UiPath to implement. Power Automate is the solution often chosen by businesses that already have other Microsoft solutions integrated into their environment.

The primary distinction among these RPA tools lies in the connectors and capabilities offered by Power Automate. Many businesses already utilize Power BI and Microsoft Dynamics, with most BI-related software relying on Tableau or Power BI. While some smaller-scale operations may still use Excel for dashboards, it's becoming increasingly uncommon. Power Automate's built-in custom connectors for Microsoft products provide a significant advantage. Overall, Power Automate has proven to be a game-changer, exceeding expectations with its features, custom connections, and level of support. While not currently the case, it's conceivable that with further enhancements, Power Automate could eventually surpass Automation Anywhere in the market.

How was the initial setup?

While I wasn't involved in the initial deployment, I contributed to the migration from version A11 to A360. This was a major undertaking, spanning six months and presenting numerous challenges. Despite encountering various issues, we ultimately achieved a successful migration.

Cloud deployment is straightforward, while on-premises setup requiring server configuration can be challenging. A cloud deployment typically takes no more than one business day.

We have two teams: the operations team and the development team. The operations team handles deployment and typically consists of one or two people. The development team's size varies depending on the number of processes requiring automation. For fewer processes, one developer may suffice; however, we may engage five or even six developers for numerous processes.

What was our ROI?

Automation Anywhere provides good cost savings.

What's my experience with pricing, setup cost, and licensing?

Automation Anywhere's price is considerably better than UiPath's.

Which other solutions did I evaluate?

I evaluated Robocorp from a POC point of view.

What other advice do I have?

I rate Automation Anywhere eight out of ten.

Challenges in implementing Automation Anywhere depend on the process being automated. For instance, if your organization adopts Automation Anywhere, infrastructure won't be the primary concern as their cloud setup is straightforward. The real challenges lie in the processes themselves. RPA automates processes, so if, for example, in bill review, some invoices are unclear due to being scanned images, the robot might struggle to process them correctly. This is a process-related challenge, not an RPA implementation issue. To address this, instead of incorrect automation, we set a confidence threshold, say 80 percent, below which invoices are flagged for manual review. Thus, RPA implementation focuses on the process itself. Businesses have numerous processes across operations, products, clients, and consultations. The key is to identify these processes and determine suitable solutions. RPA involves instructing the robot on the required steps, which it follows diligently. However, even if ten employees perform the same task, each might have their own approach. Therefore, understanding the process from the user's perspective is crucial to identifying the optimal workflow. This ideal process is then programmed into the robot, ensuring consistent execution. It's important to remember that RPA, including Automation Anywhere, has limitations and cannot deviate from its instructions or make independent decisions.

Automating more complex processes requires a deeper understanding of coding concepts like loops, regardless of the automation scale. I teach UiPath Studio X, which is designed for business users without a coding background. It is a good starting point. Training in Studio X includes teaching basic coding concepts, emphasizing their connection to familiar Excel functions. This approach helps users understand the logic behind automation and bridge the gap between their existing skills and new concepts.

The learning curve for RPA automation, depending on your desired level of mastery, is manageable. It is key to understand all the features and how they work, including the AI-powered ones. Basic RPA automation can be learned in about four to five months, allowing someone to start working as an RPA developer. However, working on an actual project for a year or a year and a half is recommended to become a true expert. This provides ample time to learn the ins and outs of Automation Anywhere, understand the challenges, and develop solutions.

Upgrading Automation Anywhere to a newer version on the same platform is straightforward, but our migration from the obsolete on-premise A11 to the cloud-based A360 required moving every single business process, which was time-consuming. Apart from that specific migration, version upgrades are generally not complex.

Bots running on a cloud platform require continuous maintenance. While the cloud platform can monitor the bots, human oversight is essential to identify and troubleshoot issues like crashes. Large clients may necessitate a dedicated maintenance team working shifts to provide 24/7 monitoring and support. These teams typically monitor the bots' control room on a separate screen while performing other tasks. In the event of a crash, they investigate the cause and, if unable to resolve it, escalate the issue to the development team for further assistance.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Application Manager / Product Manager at Bosch
Real User
Top 20
Users save time and effort since most integrations come with clear documentation readily available before the standard setup process, ensuring immediate functionality
Pros and Cons
  • "Automation Anywhere offers a complete suite of development tools to empower developers for various enterprise automation needs."
  • "Automation Anywhere risks falling behind by focusing solely on Robotic Process Automation when competitors offer more versatile and adaptable solutions that integrate AI for a more intelligent automation experience."

What is our primary use case?

Automation Anywhere is an RPA tool we use to automate common workflows that interact with various enterprise applications. These workflows can involve tasks like data generation, sending emails, or completing transactions within those enterprise systems.

We implemented Automation Anywhere to automate our workflows and save time.

How has it helped my organization?

In the past, these tasks were handled manually, leading to a lot of repetition. Automation Anywhere has eliminated that burden, making these same tasks much easier and significantly faster to complete.

We implemented AI-based automation that combines documents using intelligent document processing. This involved integrating generative AI to automatically create responses based on the data extracted from the documents. This automation streamlines the process and delivers the desired business output to end users.

Automation Anywhere caters to business users with its user-friendly interface, allowing them to build automation with minimal technical expertise. Our large business user community exemplifies this – after a five-day training program with hands-on exercises, they're empowered to independently develop their own automation within three to four days. This highlights the platform's ease of use from a business user perspective.

To ensure our business users can leverage RPA, we provide training through Automation Anywhere University. This platform offers in-depth coverage of both use cases and technical aspects, along with customized training that helps users directly connect their daily tasks to RPA methods. This blended approach has proven to be very effective.

Non-technical users can overcome the learning curve in four to five days.

While Automation Co-Pilot is a strong solution overall and integrates well with web applications, integrating it with legacy systems may require some effort on our part. However, this effort is typically minimal, taking just a few days to achieve successful integration. We're currently testing Automation Co-Pilot and exploring its potential for AI integration, which reinforces our belief in its overall value.

Based on our POCs, we project that Automation Co-Pilot will add value to our projects.

Automation Co-Pilot helps free up our staff's time on projects.

Automation Anywhere's service and customer support are improving. Their management prioritizes strong relationships with customers, evidenced by frequent collaborative meetings. This focus on customer solutions, along with other efforts, contributes to a clear upward trend in their overall support effectiveness. They've been a valuable asset to our organization.

Generative AI has the potential to revolutionize how we implement automation. Our organization sees a significant opportunity to leverage generative AI within the Automation Anywhere landscape. As a bot-focused organization, we have achieved a 30 percent automation feasibility rate. By combining automation with AI, we can achieve a 70 percent rate. This represents the kind of scalability we envision for our organization.

Our organization is expanding its use of Automation Anywhere. We have two main approaches: governance is handled through a dedicated platform integrated with Automation Anywhere, while bot deployment utilizes a separate web platform built with XTML or Java that interacts with Automation Anywhere for bot execution and deployment.

Integrating automation and APIs with Automation Anywhere streamlines workflows significantly. Users save time and effort since most integrations come with clear documentation readily available before the standard setup process, ensuring immediate functionality. Automation Anywhere's documentation serves as the primary resource for all integrations, and users can find most information there. For any remaining questions, support channels are readily available for further assistance.

Automation Anywhere has significantly reduced our operational costs and freed up employee time. With thousands of automated processes running on our platform, we're saving thousands of hours of work every month.  

What is most valuable?

Automation Anywhere offers a complete suite of development tools to empower developers for various enterprise automation needs. These tools include packages specifically designed for SAP integrations and other commonly used enterprise applications, making them highly efficient for building automation across different use cases within large organizations. Additionally, the web-based nature of the platform adds further value by enabling easy access and collaboration.

What needs improvement?

Automation Anywhere risks falling behind by focusing solely on Robotic Process Automation when competitors offer more versatile and adaptable solutions that integrate AI for a more intelligent automation experience.

For how long have I used the solution?

I have been using Automation Anywhere for three years.

What do I think about the stability of the solution?

Automation Anywhere offers a 99 percent uptime, ensuring a reliable and stable platform for its users.

What do I think about the scalability of the solution?

Automation Anywhere is capable of automation at scale.

How are customer service and support?

The technical support team is knowledgeable and efficient, readily guiding users toward automated solutions. While some complex issues may require additional data validation, they consistently deliver resolutions within established timeframes.

How would you rate customer service and support?

Positive

How was the initial setup?

Getting started is easy - the initial deployment follows standard procedures and can be completed in as little as two days for a simple use case. Complex setups may take up to a month, and the number of personnel required varies from two to ten people depending on the specific needs of each project.

What's my experience with pricing, setup cost, and licensing?

Automation Anywhere falls within a mid-range price point when compared to other RPA tools on the market.

Which other solutions did I evaluate?

After considering UiPath, Microsoft Power Automate, and Automation Anywhere, we chose Automation Anywhere due to its ability to handle growth in our automation needs and its strong data security measures.

What other advice do I have?

I would rate Automation Anywhere nine out of ten.

Upgrading Automation Anywhere can be challenging, especially when migrating from a client-server architecture to Microsoft's. However, within the Microsoft architecture itself, upgrades are significantly smoother and can be completed within a four to five-hour downtime window.

While Automation Anywhere itself doesn't require application-specific maintenance, we still need to perform regular maintenance on the server it's running on. One person is enough for the maintenance.

The time to maintain bots varies depending on their purpose but typically ranges from one to four days on average. 

Automation Anywhere is best suited for enterprise-level deployments due to its robust features. However, for smaller-scale needs, other options might be more efficient. If you're dealing with a large organization, Automation Anywhere is a strong choice. I recommend trying it to experience its microservice architecture, which allows for scalability and agility, as well as its integrated AI capabilities. These features provide a powerful and user-friendly platform for automating tasks.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Automation Anywhere
April 2025
Learn what your peers think about Automation Anywhere. Get advice and tips from experienced pros sharing their opinions. Updated: April 2025.
849,686 professionals have used our research since 2012.
Ganesh Somasundaram - PeerSpot reviewer
Founder at CTD Techs
Video Review
Real User
Top 20
User-friendly, seamlessly integrates, and uses a drag-and-drop GUI
Pros and Cons
  • "Co-Pilot is a valuable feature."
  • "Automation Anywhere needs to have more testing tools to improve the testing portion of the solution."

What is our primary use case?

We have many use cases for Automation Anywhere including HR and finance processes, and for the code in our production.

Before implementing Automation Anywhere we had complex data that was huge. For example, with the insurance, banking, and health sector domains. We were able to solve this problem with Automation Anywhere.

How has it helped my organization?

As a partner and system integrator, we have access to a vast database of applications. However, there is no direct connection between the upstream and downstream systems, resulting in scattered data across these applications. Automation Anywhere is effectively connecting all the applications, providing a seamless end-to-end workflow that has helped us.

Moving forward we see opportunities to operationalize AI within our organization. We support 15-plus industries and almost 182 clients across the globe. We have different use cases. One of which is for a client for criminal verification automation. This process is complex because we need to get the information from various systems to authenticate the staff. Another is in the healthcare sector where HIPAA compliance is present. So we ensure that we are not touching the customer data. We are using Automation Co-Pilot to solve some of the problems.

We are talking about a powerful tool in Automation Anywhere. They have been in the industry for 20 years and have learning systems such as IQ Bot, Document Automation, and CoE Manager. We are using this powerful tool and getting the best out of the generative AI. We have used the generative AI to solve complex problems for our clients. In one instance, a project that would have typically taken over a year to complete was successfully delivered within just three days using Automation Anywhere and generative AI. We can also extract data faster including clinical data and audio-enabled data for our clients. Our clients want everything as a package and immediately. Before Automation Anywhere and generative AI this was not possible. Now we can provide a solution to our clients within four to eight hours.

Automation Anywhere uses a GUI which is drag and drop. This means even a nontechnical person can use it. There is no need for a developer. With a subject matter expert, in a logistics or health care process, Automation Anywhere can perform miracles. Automation Anywhere is user-friendly and that has enabled us as a partner to help more customers with their digital transformation. A nontechnical person can be trained to use Automation Anywhere in just five days as long as they have an aptitude to learn.

We have used Co-Pilot to enable the digital gate for one of our banking clients with over 30,000 users.

We have used CoE Manager for one of our large clients which easily provides them with a ROI and allows them to see how the BOT is performing. The CEOs, CFOs, and CROs are all able to see how it is impacting their business much easier. CFOs and CROs are now recommending automation to their organizations for the ROI and the scalability it can offer.

Integrating Co-Pilot is a no-brainer. If we are talking about the day-to-day operations, the digital workforce, having a competitive advantage, and scalability, then we have to implement Co-Pilot. It is mandatory and not optional.

Automation Co-Pilot has saved our clients a lot of time. For example, one of our use cases involved a client with 20,000 users where they used to spend 20 to 30 minutes addressing each user's query. With Automation Co-Pilot that time is now fractions of a second. Having to put customers on hold to check information in multiple systems or not responding to emails can result in unnecessary escalation. With the implementation of Automation Co-Pilot the people that used to work on those things are now happy and no longer stressed out because they can now focus on more meaningful work. Automation Co-Pilot improves the employee and customer experience as well as the overall company benefits from it.

Automation Anywhere product catalog has APIs. The API can integrate with any system in the world. It can be SAP, Oracle, Workday, or any complex core banking application. In the cases where Automation Anywhere is deployed on-premises because the organization is regulated, we can go with Automation Co-Pilot which helps connect internal systems without compromising other aspects of data or privacy. The usage of Automation Anywhere is based on each client's needs and the nature of their business.

What is most valuable?

I have been an Automation Anywhere partner since 2018 and they are always surprising me. Automation Anywhere is customer-centric and on top of the market demand. Automation Anywhere's document automation solution has a 90 percent accuracy rate with handwritten documents. This is a challenge that no other solution has been able to effectively address.

Co-Pilot is a valuable feature. We have a large client with over 30,000 users. A project that size would normally take two to three years but with Co-Pilot we can solve it in two weeks. Not only is it unbelievable to us as a system integrator but also to our clients. 

Automation Anywhere is a powerful tool. The generative AI, hyper scaler with Google and Amazon gives us the power to solve complex problems.

We have learned a lot about how to leverage more of Automation Anywhere on the NLM side.

What needs improvement?

Automation Anywhere needs to have more testing tools to improve the testing portion of the solution. That would help us do a lot of testing and move on.

The Process Discovery, CoE Manager, and Data Analytics are only available on the enterprise edition. They should be made available for general use and the community edition as well.

For how long have I used the solution?

I have been using Automation Anywhere for almost ten years.

How are customer service and support?

We have not required the use of technical support for Automation Anywhere yet. When we use new products such as Automation Co-Pilot, CoE Manager, and Process Discovery we use the support. They have a good concept of Orange and Gold support for the enterprise clients. We can get support in two hours with good response times. We can also find a lot of support from the Automation Anywhere Community.

What other advice do I have?

I would rate Automation Anywhere nine out of ten. As a heavy consumer of Automation Anywhere, I highly recommend the solution to many of our clients. The product catalog is simple and the technology upgrades are frequent.

Automation Anywhere is customer-centric and partner-friendly. As a system integrator, we have a hundred-plus resources across the globe to support almost 182 clients. We prefer Automation Anywhere because of what we get from their partner team,  pre-sales team, and customer support manager team. When we are stuck on something and give them a call, they immediately respond to us. This is why we promote Automation Anywhere the most. Automation Anywhere is coming out with new products every six months that are needed in the market. This also challenges us when we meet our clients to tell them we have something new and ask them to test it. Compared to the old version, the performance has phenomenally improved. Automation Anywhere is also helping with year-over-year return on investment. Product wise it is not overwhelming and it has tools such as Automation Co-Pilot, CoE Manager, and Document Automation. Those are the only tools we need and it is easy to understand, utilize, and integrate with any LLMs. With a click of a button, we can integrate with any tool that is available like ChatGPT, Google, or Azure.

Regarding maintenance, for instance, we automated the statutory complaints process for one of the largest organizations in India, which had 65,000 employees in 2020. They have not required any maintenance since then, except for when the government changed their portal and that process only took us three hours to complete. This is because the process we developed is still functioning effectively. The product is stable, so unless enhancements to the existing portal are necessary, there is no need for maintenance.

When upgrading from V11 to A360 we faced some hiccups initially, and after that, we never encountered any problems. We migrated almost 5,000 bots from V11 to A360. We initially estimated six months to complete the migration but we did it in two months. 99 percent of our clients are using A360 which helps us move faster. We initially had pushback from the clients not to migrate because they were happy with what they were doing. After we demonstrated the benefits of cloud-native architecture, including a 15-fold increase in performance, and conducted a successful proof-of-concept, they were happy to migrate to the cloud.

Migrating from other OEMs to Automation Anywhere is seamless. Two of our clients wanted to migrate from their OEMs to Automation Anywhere and we were able to migrate 1,500 bots in two weeks.

Disclosure: My company has a business relationship with this vendor other than being a customer: Reseller
PeerSpot user
Senior Machine Learning Engineer at Flash.co
Real User
AI integration and intuitive design have transformed our automation process
Pros and Cons
  • "Since it is based on the cloud, it is a highly scalable product. It is easy to deploy, has a very good UI, and the bots can be easily deployed with no issues."
  • "Overall, I would rate Automation Anywhere a nine out of ten."
  • "If I were to mention one area for improvement, it would be on advanced AI commands, such as advanced coding. While this is not critically needed since Automation Anywhere is doing great, improving in that area could be beneficial."

What is our primary use case?

My basic use case for Automation Anywhere is to ensure that the automation is taking place, and we are also using it for UI development. Additionally, we are using it for bot deployments, which is the main use case.

How has it helped my organization?

After implementing Automation Anywhere, we have felt a significant improvement in our processes, especially regarding scaling in the cloud environment we are working in. The cloud feature works effectively after implementing it, along with data manipulation automation for bots and intuitive designing.

We can use AI with Automation Anywhere whenever we are deploying a bot or performing a function. We can integrate multiple AI channels such as ChatGPT, GPT-4, and cloud services, which is the main benefit I love the most. It is a competitor to UiPath, which is a big company. Compared to UiPath, Automation Anywhere is working effectively with its AI compatibility.

For non-technical users, which includes business users, Automation Anywhere is easy to use because it does not require heavy coding knowledge or prior experience. The learning curve is easy, and someone with basic technical skills can easily learn and use it without needing to manually deploy codes or engage in complex tasks.

Our organization uses Co-Pilot with AI integration. Co-Pilot helps us give commands to the automation channel, resulting in outputs that make the job easier. It is a very good game changer in this category, and I would definitely give a good rating to Co-Pilot.

We could see the benefits of Automation Anywhere within 2 weeks of deployment.

We have integrated several tools with Automation Anywhere, including Zoom, Google Drive, third-party channels, and data management tools, ensuring we can easily connect everything needed within our cloud-based network.

What is most valuable?

There are several things I would highlight about Automation Anywhere, including the AI integration which is exceptional. It has several Generative AI agents that enhance automation capabilities and process orchestration. Since it is based on the cloud, it is a highly scalable product. It is easy to deploy, has a very good UI, and the bots can be easily deployed with no issues. 

Additionally, the cost is really good. If we compare it to UiPath, Automation Anywhere stands out significantly.

The learning curve for Automation Anywhere is quite good, as it does not require heavy learning or extensive training for technical and non-technical users.

What needs improvement?

If I were to mention one area for improvement, it would be on advanced AI commands, such as advanced coding. While this is not critically needed since Automation Anywhere is doing great, improving in that area could be beneficial.

Other than that, Automation Anywhere is working effectively for me. I currently do not have any complaints and wish them all the luck, as they are excelling in the automation sector.

For how long have I used the solution?

My organization has been using Automation Anywhere for 2.5 years.

What do I think about the stability of the solution?

We have not faced any kind of instability, lagging, or downtime with Automation Anywhere after implementation; it runs smoothly and is based off the cloud with a good UI, so there is no issue to report.

What do I think about the scalability of the solution?

I feel that Automation Anywhere is definitely a scalable product, and it has the potential to be even better in the future, especially given its good pricing compared to UiPath and similar products.

How are customer service and support?

While I have not needed to reach out for support much. I did interact with their technical support during the implementation. They resolved our issue within 2 to 3 hours, which was not a major problem. I would rate their support positively.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

I have used UiPath as an alternative to Automation Anywhere; however, we made a switch because it was not cost-effective for our organization. During our growth phase, we transitioned and found that Automation Anywhere is better and more cost-effective.

How was the initial setup?

The initial deployment of Automation Anywhere was easy. Our team, which included eight to nine people, assisted with the implementation and deployment process. It took about 1.5 weeks to complete everything.

Automation Anywhere does not require any maintenance on my end.

What about the implementation team?

For the deployment of Automation Anywhere, my team consisted of eight to nine people, including myself.

What was our ROI?

The current pricing of Automation Anywhere is fairly priced and has provided us with a good ROI on investment. UiPath and other similar options would typically cost 2X the price, which is why we have chosen Automation Anywhere.

What's my experience with pricing, setup cost, and licensing?

Its cost is good.

What other advice do I have?

Overall, I would rate Automation Anywhere a nine out of ten. It is a good product.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Flag as inappropriate
PeerSpot user
Senior Process Automation Analyst at a computer software company with 501-1,000 employees
Real User
Top 5Leaderboard
It's cost-effective, but the developer environment needs improvement
Pros and Cons
  • "Co-pilot certainly makes the job easier if the client has a subscription. It allows me to analyze desktop flows and activities and create flows using natural language."
  • "Automation Anywhere offers better value and is more effective for organizations seeking cost-effective solutions."
  • "Providing a desktop version rather than focusing on the cloud is essential. Only UiPath offers a studio environment for desktop application development."
  • "Automation Anywhere lacks a desktop version and is solely web-based and cloud-based. Automation Anywhere is not so easy for business users who are not technical."

What is our primary use case?

As a consultant, I have worked with various clients, including banks, insurance companies, healthcare providers, and different tech companies. Each company has distinct use cases. RPA tools are capable of automating any task. We usually automate processes that are repetitive. Automation is always rule-based.

What is most valuable?

Co-pilot certainly makes the job easier if the client has a subscription. It allows me to analyze desktop flows and activities and create flows using natural language. Natural language processing using LLMs has become an integral part of IT. This tool lets me create flows using natural language, repair automation errors, and answer product-related questions. It is there to assist us in creating automation tests, CI pipelines, etc.

What needs improvement?

There are many areas for improvement, especially in the developer environment. Providing a desktop version rather than focusing on the cloud is essential. Only UiPath offers a studio environment for desktop application development. Automation Anywhere lacks a desktop version and is solely web-based and cloud-based.

Automation Anywhere is not so easy for business users who are not technical. It is at the medium level. UiPath also provides UiPath StudioX to enable business users to automate easily.

For how long have I used the solution?

I have used Automation Anywhere for four years. I have also used UiPath for four years.

How are customer service and support?

The support is good. I have faced difficulties with every RPA tool. Automation Anywhere has a good support system but has room for improvement. UiPath has a huge online community for support. They have a lot of active users.

How would you rate customer service and support?

Neutral

Which solution did I use previously and why did I switch?

The solution we use depends on the client and their budget. 

What's my experience with pricing, setup cost, and licensing?

UiPath is exceptionally more expensive than Automation Anywhere. UiPath is far ahead of its competition, but in terms of finances, Automation Anywhere offers better value and is more effective for organizations seeking cost-effective solutions. Small clients tend to go for Power Automate or Automation Anywhere, whereas large clients go for UiPath.

What other advice do I have?

RPA solutions like UiPath, Automation Anywhere, Power Automate, and Blue Prism can be learned through their academies. When I graduated, I did not know what RPA was. I joined as an intern and was told to go to the academies for these solutions and do the courses. They have developer fundamental and RPA fundamental courses. They also have advanced-level courses of 30 hours, which are free of cost. It took me about two months to learn these solutions. I might have had an edge because of my technical background. For a non-technical person who is willing to put in two or three hours every day into learning, three to four months would be good to take themselves to a level where they can start developing automation at a medium scale. Complex automations happen from experience when you are working with different types of clients. Generally, two to four months is a good period for someone to get a grasp of RPA.

The focus is shifting from RPA to IPA or Intelligent Process Automation. For example, I have done automation for a website task. Previously, when the website changed, such as when a button was shifted, the automation would fail. With Intelligent Process Automation, the bot is intelligent enough to realize the changes that have occurred. It understands what my flow is and what I am trying to achieve. It is then able to modify itself in such a manner that it still works. This is something that RPA has been transitioning toward.

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

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate
PeerSpot user
Fernando Miranda - PeerSpot reviewer
RPA Capability Leader at a financial services firm with 1,001-5,000 employees
Real User
Top 20
Automation software reduces manual effort significantly with user-friendly functionality
Pros and Cons
  • "The most valuable feature is the ease of use. It's very user-friendly."
  • "The automated regression testing could be better. I need to build my own testing suite, and I know other tools have built-in testing suites. That is an area that's very weak in this platform."

What is our primary use case?

I use it mainly as automation software. Any kind of processes that are manual, like data entry, for example, I definitely use it for those. Many legacy applications like Mainframe that don't have APIs or can't access the data to write out to that system are addressed mainly for those purposes.

What is most valuable?

The most valuable feature is the ease of use. It's very user-friendly. Someone with even basic technical prowess can jump in and learn it very quickly. The difference is night and day. With processes involving three or four people, having it full-time manually to address that, and once we implement the automation software on these processes, it effectively reduces eighty to ninety percent of the manual effort.

What needs improvement?

The automated regression testing could be better. I need to build my own testing suite, and I know other tools have built-in testing suites. That is an area that's very weak in this platform.

For how long have I used the solution?

I have been using it for about six years.

What do I think about the stability of the solution?

The stability is pretty good. They are responsive. Just like with any software organization, they usually deal with tier one support, and nine times out of ten, I know more than they do. I get some good support when I advance beyond tier one support. When it gets escalated to the next level is when I receive some good responses and better support.

What do I think about the scalability of the solution?

I think it's a little difficult to scale just because they don't have an automated regression testing suite. We currently have a bottleneck at quality control because of that. If I had to give it a number, I would say six.

How are customer service and support?

Their customer service is pretty good. They are responsive. Just like with any software organization, they usually deal with tier one support, and nine times out of ten, I know more than they do. I get some good support when I advance beyond tier one support. When it gets escalated to the next level is when I receive some good responses and better support.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

I have used UiPath, Blue Prism, OpenRPA, and NintexRPA. I've dabbled in a couple of others, and I can't even remember what they are because there are so many, but those are the main ones that I've used throughout my career.

How was the initial setup?

It was already in place when I got to my company.

What's my experience with pricing, setup cost, and licensing?

I think the setup cost is comparable to the other solutions. I don't think it's anything out of the ordinary. I've been on platforms that are a lot more expensive, and this one is comparable.

What other advice do I have?

I would give them an eight out of ten. I definitely would make sure that you at least have some basic understanding of development, just basic principles, and then start training in Automation Software Anywhere Academy. Many like to think businesses can come in and build stuff, which they can, but sometimes they don't know basic software design principles. Once the volume increases or if they don't build it correctly, there are constant issues, and then we have to bring in the core team to help out. It's nice to say something, but in action, it's something that's not the same. Let's put it that way. You can build anything, as I said, you can build all kinds of things, but is it built correctly?

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Flag as inappropriate
PeerSpot user
AutoMan9843 - PeerSpot reviewer
Automation Manager - Nordic at a financial services firm with 1,001-5,000 employees
Real User
MetaBot reusable code makes development much quicker and role-based access gives us security control
Pros and Cons
  • "One of the features that we have used the most is an action in the Workbench called Object Cloning. We find that very reliable and very useful for implementing different business processes."
  • "Security is a top priority for us. To be allowed to automate different processes, we need to have a good set of controls around who is allowed to do what, and what credentials people can and can't use. It allows us to manage access make sure that we have full control."
  • "The main things I've found that could be better are small things that can be annoying when you're using them a lot. I would recommend they add a feature where, if you mark the start of an "If" sentence it will highlight the end of the "If" sentence. That would make it easier to get a better overview."
  • "We would like to see more options for merging and un-merging PDFs. More flexibility there would be good. We've figured out ways around this and, using their software, we've been able to do everything we wanted to do. It just took a bit more time to do it. We were on version 10.5 and in their Bot Store they actually had a bot that did exactly what we wanted to do, but it was for Version 11.0."

What is our primary use case?

We use it to automate all kinds of business processes. The primary use case is the RPA platform, even though they have the cognitive platform and the analytics platform. We use it for so many different things it's hard to focus on one, but it's automating business processes in our banking system.

We're interfacing a lot with Excel, our ERP systems, some legacy systems, the databases, file folders, text files, CSVs. It's hard to pin down one.

How has it helped my organization?

Through the software, we have been able to reduce the time that we spend on manual, repetitive tasks, so that we can focus on activities that add value to the business or to our partners and customers. The most important things are saving time, increasing control, and increasing automation.

If you ask our CFO, I think he would say that the most important thing is that we saved some money, with more efficient operations, etc. But I feel the ability to change from doing non-value-added tasks into work with added value is important.

We have saved the equivalent of about $40,000 to $50,000 by using it, during my time here. That's a lot. We recently did a large migration that saved us a lot of time on things that were going to be done manually. We were able to automate it and we saved around $15,000 to $20,000 on just that migration. That's quite substantial.

What is most valuable?

One of the features that we have used the most is an action in the Workbench called Object Cloning. We find that very reliable and very useful for implementing different business processes.

In general, the security and role-based access control - credentials security - are also important. We have a high focus on security in the bank. It's obviously a very highly regulated environment, so security is a top priority for us. To be allowed to automate different processes, we need to have a good set of controls around who is allowed to do what, and what credentials people can and can't use. It allows us to manage access to make sure that we have full control.

Other things that I also find very useful are the Bot Store and the Apeople community. If we run into troubles, we can always ask the forum and get an answer. People know if there is a pre-existing bot in the Bot Store that we can use to solve a problem. It's very useful to take advantage of the community. When they launched the Bot Store, it was a unique thing in the RPA market and it is providing tremendous value to a lot of businesses.

Also, their MetaBot tool is a very useful building block. We call it Lego bricks, here in the Nordic region. So if you build a wheel for your car, you don't have to build three more, you just use the same wheel over again. That's very useful and it makes the development phase even quicker. I hear other people talking about how they're spending three months on one process and that's a bit crazy. We deliver new processes every week and we estimate a process should not take a lot more than two weeks. But on average, we're spending two weeks per process, to get from idea to production.

What needs improvement?

The main things I've found that could be better are small things that can be annoying when you're using them a lot. I would recommend they add a feature where, if you mark the start of an "If" sentence it will highlight the end of the "If" sentence. That would make it easier to get a better overview. The small things are the most important in our day-to-day work with their software. Incremental improvements for a better overview or better user experience would help.

Also, we would like to see more options for merging and un-merging PDFs. More flexibility there would be good. We've figured out ways around this and, using their software, we've been able to do everything we wanted to do. It just took a bit more time to do it. We were on version 10.5 and in their Bot Store they actually had a bot that did exactly what we wanted to do, but it was for Version 11.0.

I find that they are making a lot of improvements that we are able to take advantage of with every release. I can't really think of something large that's missing.

For how long have I used the solution?

One to three years.

What do I think about the stability of the solution?

It's been very stable. I can't really put my finger on things that haven't been stable that are under Automation Anywhere's control.

There have been some troubles for us when it comes to doing monthly Windows updates. That always turns off the Bot Runner machines and we have to do a complete, new log-on once a month on those machines. But we are aware of it and it's on our side, not Automation Anywhere's side.

Other than that, the runtime might differ. Sometimes it goes very fast, sometimes it can go a bit slower but I think that's also due to the speed of internet access as well as the computers we're running it on. Some of them have less computing power. We don't have the perfect virtual environment yet, so we're still working on improving that. But we can't blame Automation Anywhere for our having a legacy infrastructure.

In general, it works very well and we're really happy with the stability.

What do I think about the scalability of the solution?

The scalability is good. I think we haven't really used the Bot Farm product yet, but that looks very exciting. We're planning on moving the infrastructure into the cloud and it's then a very interesting prospect to be able to scale up from 100 bots to 1,000 bots with just the click of a button. To my knowledge, it's probably the most scalable RPA software out there. We haven't really met any major challenges when it comes to scaling up, other than our own computers. But that's an in-house problem, not an Automation Anywhere problem.

I've talked to people using other RPA vendors and they have said they face some major issues once they pass 40 automated processes, but we haven't really faced those kinds of challenges. It has been running smoothly.

It's very scalable and it's easy to have control. There is a good audit log in the Control Room. And there is the ability to create your own roles and have strict, role-based access control where you say: This role is able to run this bot on this machine but it's not able to run another bot on the same machine. That's good from a security standpoint.

How are customer service and technical support?

Technical support is really eager to close tickets as fast as possible, which is good. But as with any support, it can sometimes feel like it's slow because they have to do these standard checks to rule things out. Even though I say I've done them, they have to do them anyway. They have to be able to say, "Okay, this is checked off, this is checked off, this is checked off. Alright, now we can move to the actual issue." It can be a bit slow at the start, but they're always able to resolve our issues.

In general, I'm very happy with it and I can understand why they have to do those checks because if it's a stupid error, it's good to identify that early.

How was the initial setup?

The initial setup is pretty straightforward. I've actually done installations of Automation Anywhere and I have no IT background. I've been able to set it up on a server and some virtual machines and get everything working.

The deployment took some time for us, but that was due to a lack of a good environment on our side. To do a clean install would take some three or four hours to get everything up and running, depending on what kind of machines you have. If you have all the accesses you're supposed to have it can take a very short time. But, if you're installing it in an enterprise environment, it can take longer because you might not have all the accesses. At least for me, coming from the business side, I don't have all the administration accesses that I would need, but that's not Automation Anywhere. Overall, it's pretty straightforward and doesn't take a lot of time.

For our implementation strategy, we started out with a pilot, together with a consulting partner. We automated two processes and created a proposal for an operating model, governance, and a framework. After that, we just tried to pump out new automations as fast as possible to prove the value to upper management. After a while, we got some traction and we went from being just me in 2015 to between 12 and 15 people now. Some of them are not working full-time on it but we have at least 12 full-time employees working on RPA across our organization. We started out in Norway, but now we also have operations in Sweden, Denmark, and Finland, with people working full-time on automation in all of those countries.

All the developers are doing some maintenance. We don't have anyone who is assigned to doing only maintenance because we all find that a bit boring. We share the responsibility among all the developers so that everyone has the chance to do new processes and maintenance when needed.

We have a two-pronged approach there. The processes that are important for business continuity, the business-critical processes, are often maintained proactively. We are notified that a change is coming to the system, so we need to test it out and make a new version that will work when the upgrade of the system is live. So we're proactive in those kinds of processes. Non-business-critical processes are maintained reactively. We try to do it in the most sensible way possible, but there's always room for improvement, obviously.

We put a lot of responsibility on the process owners. They're responsible for notifying the RPA team in case of any changes in the graphic user interface or changes to the process, because of new rules and regulations or any other reason. The process owner or someone in his or her team will always know if there is a change in the user interface or the process.

If there is an error in the code, it is the RPA team's responsibility to fix it and we do most of that ad-hoc, when it happens. We always have some resources available to do those kinds of things and that's taken into account when estimating how long we will spend on creating a new process. We know that something might happen during that week or those weeks, so we add some padding.

In addition to the developers, we have a lot more people using the Control Room to schedule the processes.

So we tried to run fast and then we took a step back and re-evaluated. We built an even better framework, redid the infrastructure, put more thought into the security aspect, and we have industrialized our implementation. We still have some issues when it comes to our operating environment, but that's not Automation Anywhere's fault; that's more in our IT department's hands.

What about the implementation team?

We used Accenture, they're our technology partner in Norway. We had good experiences with them, but I think it could have been better planned on both sides. We were not able to mirror their organization as we should. Ideally, we would have been more self-sufficient after those ten weeks, and it was only by chance that I had the time to be present during all ten weeks, every day, in the project. If we didn't have the people learning how to develop, how to do the business analysis side, and working closely with them, we would have been in some trouble going forward.

The project was a success either way, given where we're at right now. But they should have been a bit clearer on how much time people would need to spend and what was expected of us. It's always better to make the customer self-sufficient.

I think they also proposed a bit too-ambitious operating model with a bit too many people from the get-go. That was not that well received by our management. We're a larger organization right now than what they proposed, but I don't think that our management would ever have accepted or have had the guts to do the leap of faith and say, "Okay, we will have six people working full-time with RPA from today," in 2016. They didn't know the potential and didn't really see that we had that many manual processes.

These are small things. In general, we're happy with what they did. It's just that if I were to point my finger at something that could have been done better, those are the things that could have been done better.

Regarding the number of people involved in the deployment, from Accenture's side there were two developers, two business analysts, and one project leader. On our side, we had a project leader and seven or eight other people, but eventually, it was just me and the project leader who spent our full time on the project, while it was going on. Everyone else was also doing their day-to-day jobs. And with all those people, it was still too few.

What was our ROI?

We have triple-digit returns, in percentage. I feel it's worth every dollar we paid for it. We have seen a lot of the returns in operations and back office because we had so many manual tasks there.

A good example is a process that we automated where, on that specific process, the return on investment is above 30,000 percent. The total cost of ownership is around $1,000 and the return is something like $400,000 in direct cost savings. And that's still increasing. It's an ad-hoc cleaning job that we're doing, but for every contract we change, we save about half-a-dollar per month, per letter we're sending. It amounts to a lot.

We spent one day creating that process and four days running it so the cost of ownership is really low. Those kinds of processes are unicorns. You won't find them in every business and you have to have the right people and the best ideas. But we were lucky to find that process and, by itself, it has paid for a lot of the license cost.

What's my experience with pricing, setup cost, and licensing?

We just did a round of price comparison on a global scale and found it's so hard to compare the license prices. But, Automation Anywhere, in general, is on the same price level as the other vendors, a bit lower in some cases. 

If we're thinking about the list prices, the Enterprise platform license fee is quite high. If you have five Bot Runner licenses, five bot creator licenses, a Control Room, and an Enterprise License fee, Automation Anywhere is much more expensive than the others. But if you have a global agreement with them, the Enterprise platform fee is shared between all the entities that are using Automation Anywhere. In that scenario, it would be a lot cheaper. The prices are quite okay.

Which other solutions did I evaluate?

We evaluated Blue Prism at the time.

We did the assessment together with Accenture and I think they actually recommended Blue Prism vs Automation Anywhere. I find that a lot of the consultants in our region are recommending Blue Prism or UiPath because they have generous compensation and incentive packages for the consultants who sell their products. I'm not sure if Accenture would recommend Blue Prism if they didn't have some interest in it. If they were totally agnostic, I'm not sure if they would have done the assessment the same way. But it's hard for me to say.

If I were going to do a new evaluation today, I would evaluate Automation Anywhere vs UiPath, but I would still choose Automation Anywhere. I've seen demos of both Blue Prism and UiPath and I think the basic capabilities are the same - they're all based on the .NET framework and you can kind of do a lot of the same things with them. But when it comes to the scalability, security, etc., I think Automation Anywhere is superior.

Another major factor that played a role in why we chose Automation Anywhere was their prompt replies to any questions or issues.

I'm not sure how this part is with the other main providers, but Automation Anywhere has a really good customer success program. I have a customer success manager that I'm in contact with daily. He helps us elevate our issues to the correct people and makes sure that, if we have any action points that are pending on someone at Automation Anywhere, they are resolved as quickly as possible. The follow-up from Automation Anywhere's side has been fantastic. They give us information about what's in the roadmap and what's to come, and if we need any additional information for our IT teams or our management team - anything to would help us with information - they are available to do calls and presentations.

What other advice do I have?

My advice is to get started and get help. It's very useful to have consultants come in to help you get started. That will kick-start your implementation journey. Also, look at it as a journey. You won't get to an end-state where you will say, "Alright, now I'm done," because you will have to improve your implementation at all times, keep progressing, moving towards AI.

In my opinion, the vendor you choose in the first year is kind of irrelevant. But when you come to a point where you're about to scale up, then it's important to be associated with the best vendors out there. For us, being a customer of Automation Anywhere puts us in a really good place to keep progressing and keep scaling up.

It's important to remember that we are not doing a full integration here, we are doing RPA. It's okay to do 80 percent of a process - the high volumes - and then do all the exceptions manually. You won't necessarily get a good enough return on spending an extra month to do all the exceptions. You want to go live with the volume that represents the 70 or 80 or 90 percent, as soon as possible. Then see if it makes sense to handle all the exceptions, the last ten to 30 percent. It's important for us to be able to deliver fast, as well as securely and controlled, and with the MetaBot and the other tools that we have through Automation Anywhere we are able to do that.

We have automated in excess of 60 processes running on 17 Bot Runners, which are like machines we can operate 24/7. We have 15 bot developers and we are closing in on capacity so we would have to expand the number of licenses soon. 

Our plans for ramping up are about pumping out new processes every other week. We're working Agile with the RPA so we try to do short sprints and deliver something every week. The usage increases every week actually. I'm not sure if we are planning to have even more developers because we don't want to be in a position where people don't have things to do. We would rather have some backlog rather than having to fire five developers.

We are planning to continue on the same pace and ramp up the number of bots, rather than the number of developers. We did a proof of concept last year with Automation Anywhere's IQ Bot which was very successful. We did not, however, have time or resources available to implement that last year. Hopefully, this year we will have time and we will make the purchase of the IQ Bot license and start using their cognitive platform. We're thinking about implementing their analytics platform as well, because that's very useful for keeping track of our progress.

I would rate Automation Anywhere at nine out of ten. There's always room for improvement and, of course, we would want cheaper licenses and would want them to add even more things that we haven't thought about to their product. Still, we're really happy with the software provider that we're using.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
reviewer2644632 - PeerSpot reviewer
Senior Engineer RPA at a tech vendor with 10,001+ employees
Real User
Provides time savings and supports scalability and integrations very well
Pros and Cons
  • "We have multiple bots running. It saves time. If manual invoice processing in SAP takes two to three hours on a daily basis, a bot can do the same job in half an hour. We are saving more than 70% of the time."
  • "Overall, I would rate Automation Anywhere a nine out of ten."
  • "One improvement would be to implement a log mechanism within the workflow, similar to other automation tools. Currently, the log mechanism uses a text file. If we want to monitor a process, we need to check manually."
  • "One improvement would be to implement a log mechanism within the workflow, similar to other automation tools."

What is our primary use case?

We have multiple entities and businesses in our organization, which leads to various use cases. Specifically, there are numerous SAP use cases where we perform automation. Additionally, there are use cases with application automation and document automation.

By implementing Automation Anywhere, we wanted to automate repetitive tasks done on a daily or weekly basis and utilize the time saved for other tasks. We wanted to save time and costs.

How has it helped my organization?

It integrates well. We have SAP CRM and browser automations. We also have document automations. We also have API integration.

We have multiple bots running. It saves time. If manual invoice processing in SAP takes two to three hours on a daily basis, a bot can do the same job in half an hour. We are saving more than 70% of the time.

What is most valuable?

The feature that I currently like is Agentic AI process automation, where we use LLM models to automate our processes. I have heard a lot about it. I am eager to learn more about it and implement it in my organization.

It is very easy to use. You do not require any prior knowledge. Through Automation Anywhere University, you can learn it and implement your use case. A non-technical person can learn it within a month. For a technical person, it is easier to understand the loops, conditions, and workflows. A technical person needs only 10 to 15 days.

What needs improvement?

One improvement would be to implement a log mechanism within the workflow, similar to other automation tools. Currently, the log mechanism uses a text file. If we want to monitor a process, we need to check manually.

Another improvement would be to facilitate copying code blocks between projects, as currently, it is not possible to copy and paste them either locally or on the web.

For how long have I used the solution?

I have more than six years of experience as an RPA developer and have used other tools. I have been using Automation Anywhere for the past two years.

What do I think about the stability of the solution?

It is very stable. I would rate it a ten out of ten for stability.

What do I think about the scalability of the solution?

It is scalable. I would rate it ten out of ten for scalability.

We have about 1,700 automation users. We are a big organization with multiple locations globally. We develop automation for multiple departments and multiple entities.

How are customer service and support?

Their technical support is good. I would rate it an eight out of ten.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

I have used UiPath and Automation Anywhere. Both are very good. Automation Anywhere is cost-effective compared to UiPath.

How was the initial setup?

The deployment is fine. It is very easy. 

It is completely on the web. We have our own licensing management tool. Anyone who has done internal training can request the license. A dedicated license is generated for you for a few hours or if needed, permanently. We have a dedicated portal for deploying our projects.

The upgrades are also easy. It does not require much maintenance.

What other advice do I have?

We have multiple communities for automation. We have citizen developers and we also have expert developers. To identify the use case, we approach the entities and ask them to identify any mundane, repetitive, or complex task. We have a perfect pipeline for automation use cases. When a use case enters the feasibility check, an expert assesses its feasibility based on multiple parameters. If feasible, we proceed with development, prepare documentation, and design all solution documents. Next, we prepare the architecture, and development commences. After development, we conduct several rounds of UAT. Before deployment, we conduct a pre-delivery check with a dedicated department, ensuring best practices and proper exception and error handling. Once approved, we proceed with deployment.

In our organization, we are the first ones to work closely with the Gen AI and AI topics. We have a few opportunities to use the Gen AI capabilities in automation.

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

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Flag as inappropriate
PeerSpot user
Buyer's Guide
Download our free Automation Anywhere Report and get advice and tips from experienced pros sharing their opinions.
Updated: April 2025
Buyer's Guide
Download our free Automation Anywhere Report and get advice and tips from experienced pros sharing their opinions.