What is our primary use case?
My primary use cases involve UI-level automation across both desktop and web applications, with Automation Anywhere serving as our preferred RPA platform.
Some common examples include insurance verification, insurance renewal processes, and automating workflows that interact with legacy mainframe applications. In general, any process that relies heavily on repetitive manual activities is a strong candidate for automation. We can effectively deploy RPA solutions in such scenarios to improve efficiency, accuracy, and turnaround time.
How has it helped my organization?
We have done close to 100 FTE savings
What is most valuable?
One area where Automation Anywhere could improve is cost optimization. I have been working with the platform across multiple versions, starting from v10, then v11, A2019 (A19), and now Automation 360. One positive aspect is the platform's backward compatibility—some bots that were originally developed in v10 are still functioning successfully in Automation 360.
However, I have observed occasional accuracy and stability challenges when older automations are migrated to newer versions. Existing legacy bots generally continue to perform well, and newly developed bots are also highly accurate. The concern arises when a process that was built several years ago is run after a platform upgrade, as it may experience minor impacts due to version changes. While these issues are not severe, greater attention to maintaining consistency across versions would further enhance the platform.
From a business perspective, one of the key challenges I aimed to address was overcoming the limitations of API accessibility. In many real-time operational scenarios, direct API access may not always be available, requiring organizations to rely on UI-level automation to interact with websites and applications. However, there are cases where data needs to be extracted from an application without providing users with direct UI access. In such situations, building an RPA solution can become complex due to access and credential constraints.
APIs provide a more efficient alternative by enabling direct system-to-system communication, which significantly accelerates processing compared to UI-based automation. They can also support secure data access models, where UI access is restricted but authorized API access remains available. For example, in our operations at Cardinal Health, we need to retrieve insurance-related information. While we do not have direct access to the application's user interface, the availability of APIs enables us to obtain the required data efficiently and securely, resulting in faster and more reliable processing.
What needs improvement?
Automation Anywhere could be further improved by addressing its cost structure. Having used the platform across multiple versions—from v10 and v11 through to Automation 360—I appreciate its strong backward compatibility. For example, I still have a bot that was originally developed in v10 and continues to run successfully in Automation 360, which is a significant advantage.
However, I have noticed some minor accuracy and stability challenges when older automations are carried forward into newer versions. Legacy bots generally continue to work, and newly developed bots perform accurately as expected. The issue typically arises when a process that was built several years ago is impacted slightly after a platform upgrade. While these impacts are not significant, greater focus on ensuring seamless performance and consistency for long-standing automations across version upgrades would further strengthen the product.
For how long have I used the solution?
I have been working with Automation Anywhere in my current field for five years.
What do I think about the stability of the solution?
Yes, in my experience, Automation Anywhere is a stable platform, particularly in enterprise environments where automations are running at scale.
One of the reasons I consider it stable is its backward compatibility across versions. For example, I have bots that were originally developed in v10 and are still running successfully in Automation 360. This demonstrates the platform's ability to support long-term automation investments without requiring complete redevelopment.
From an operational perspective, the platform performs reliably for both web-based and desktop automations, as well as integrations with legacy applications. We have used it for business-critical processes such as insurance-related workflows, where consistent execution and uptime are essential.
That said, like any enterprise automation platform, there can be minor challenges during version upgrades. In some cases, older automations may require small adjustments after migrating to a newer release. However, these impacts have generally been limited and manageable, and they have not significantly affected overall business operations.
I have also found the platform to be stable from a deployment and management standpoint. Its integration with tools such as Jenkins and other DevOps solutions helps ensure controlled releases and reduces operational risks.
Overall, I would rate Automation Anywhere highly for stability. The platform has matured significantly over the years, and its reliability, backward compatibility, and enterprise-grade capabilities make it a dependable choice for large-scale automation programs.
What do I think about the scalability of the solution?
In my experience, Automation Anywhere scales very well for enterprise environments. We have been able to expand automation from individual processes to larger business operations without significant challenges.
One of the platform's strengths is its centralized control and management. As automation demand grows, additional bot runners and bot creators can be added efficiently, allowing organizations to scale their automation programs across multiple teams, processes, and geographies.
The move to Automation 360's cloud-native architecture has further improved scalability. Since the platform is web-based, it is easier to deploy, manage, and monitor bots without extensive infrastructure management. This reduces operational overhead while supporting growth.
From a development perspective, scalability is also supported through integrations with tools such as Jenkins and other DevOps pipelines, enabling standardized deployments and easier management of large numbers of automations.
In our environment, we have successfully automated multiple business processes, including insurance-related workflows and integrations with legacy systems. As new automation opportunities emerged, scaling was straightforward because the platform provided the necessary bot management, scheduling, workload distribution, and monitoring capabilities.
Overall, I would rate Automation Anywhere's scalability very highly. It is well-suited for enterprise organizations looking to expand from a few automations to a large-scale digital workforce while maintaining centralized governance and operational efficiency.
How are customer service and support?
My experience with Automation Anywhere's customer service and technical support has been generally positive. Whenever we encountered issues during development, deployment, or upgrades, the support team was responsive and worked with us to resolve problems in a reasonable timeframe.
One of the strengths of Automation Anywhere is its strong community ecosystem. In addition to official support channels, there is a large and active community where developers can find documentation, best practices, discussion forums, and solutions to common issues. In many cases, we were able to resolve challenges quickly through community resources without needing to raise a support ticket.
For critical issues, the technical support team has been knowledgeable and helpful, particularly when dealing with platform-related concerns or version migration questions. Their assistance was valuable during transitions across versions, from v10 and v11 to A2019 and Automation 360.
Another positive aspect is the availability of learning resources, training materials, and documentation, which help developers become productive more quickly and troubleshoot issues independently.
Overall, I would rate Automation Anywhere's customer service and technical support highly. While response times can vary depending on the complexity and priority of the issue, the combination of official support, extensive documentation, and a strong developer community provides a good overall support experience.
Which solution did I use previously and why did I switch?
Before specializing in Automation Anywhere, I explored other RPA platforms, including Blue Prism and UiPath. Over the years, I have worked extensively with Automation Anywhere across multiple versions—from v10 and v11 to A2019 (A19) and Automation 360—giving me hands-on experience with the platform’s evolution.
Having worked with all three tools, I find Automation Anywhere to be particularly developer-friendly compared to its competitors. One of its key differentiators, especially during the time I was evaluating UiPath, was its cloud-native, web-based architecture. This provided a significant advantage, as it eliminated the need for extensive setup and maintenance on individual machines, making deployment and management much more efficient.
From a performance perspective, the platform has continuously improved over time. In addition, Automation Anywhere has demonstrated a strong ability to adopt and integrate AI capabilities, keeping pace with evolving automation requirements and offering capabilities that stand out in the market. Another major strength is its active community ecosystem, which provides valuable learning resources, support, and collaboration opportunities. The combination of developer-friendly features, cloud-based accessibility, AI innovation, and a strong user community has made Automation Anywhere my preferred RPA platform.
How was the initial setup?
The initial setup was relatively straightforward, especially compared to some other enterprise automation platforms I have worked with. Automation Anywhere's user-friendly interface and developer-friendly design made it easier for teams to get started quickly.
With Automation 360, the experience improved further because of its web-based, cloud-native architecture. There is less dependency on extensive local installations and configurations, which reduces setup effort and simplifies administration.
From an enterprise perspective, integration with tools such as Jenkins and other DevOps pipelines was also smooth, allowing us to align automation deployments with our existing development and release processes.
Like any enterprise platform, the complexity increases when setting up governance, security, credential vaults, environments, and production-grade infrastructure. However, these are standard considerations for large-scale implementations rather than platform-specific challenges.
Overall, I would describe the initial setup as straightforward for basic implementation and manageable for enterprise-scale deployments. The platform's ease of use, cloud capabilities, and integration options helped accelerate adoption and reduce onboarding time for developers and business users.
What about the implementation team?
What was our ROI?
Yes, we have seen a positive ROI with Automation Anywhere, particularly in processes that involve high volumes of repetitive manual work.
One example is insurance verification and insurance renewal processes. Before automation, employees had to manually access multiple applications, retrieve information, validate data, and update systems. By automating these steps, we significantly reduced manual effort, improved processing speed, and minimized human errors.
We have also achieved ROI through automation of legacy and mainframe-based applications, where APIs were not always available and manual interaction was required. Automating these processes enabled us to handle higher transaction volumes without increasing staffing requirements.
Another area where ROI was evident was through the use of APIs alongside RPA. In cases where UI access was restricted, API integrations allowed us to retrieve data more efficiently, resulting in faster processing times, improved system performance, and reduced maintenance compared to purely UI-based automation.
Beyond direct cost savings, we have seen value through:
- Reduced manual effort and operational costs
- Faster turnaround times for business processes
- Improved accuracy and compliance
- Increased employee productivity by freeing staff from repetitive tasks
- Scalability without corresponding increases in workforce requirements
While I cannot share exact financial figures due to confidentiality, the automation initiatives have consistently delivered measurable business benefits and justified the investment. For organizations with high-volume, rule-based processes, Automation Anywhere has provided a strong return on investment through efficiency gains, accuracy improvements, and operational scalability.
What's my experience with pricing, setup cost, and licensing?
My experience with Automation Anywhere's pricing, setup, and licensing has been largely positive. While enterprise automation platforms require an investment, I found that the value delivered through scalability, centralized management, and advanced automation capabilities justifies the cost.
From a setup perspective, Automation Anywhere is relatively easy to deploy, especially with Automation 360's cloud-based architecture. The web-based environment reduces infrastructure overhead and simplifies onboarding for developers and business users.
The licensing model is flexible and allows organizations to scale based on their automation needs. As automation adoption grows, additional bot creators and runners can be added efficiently to support business expansion.
Overall, I have had a good experience with the platform. Its ease of use, developer-friendly design, AI-driven innovation, and strong support ecosystem make it a valuable solution for enterprise automation initiatives.
Which other solutions did I evaluate?
I have worked with UiPath in the past, but I find Automation Anywhere to be more developer-friendly and easier to work with. The platform has evolved significantly over the years, particularly in its adoption of AI capabilities, which has helped it stay aligned with changing automation needs. Another key strength of Automation Anywhere is its strong and active community, which provides valuable resources, support, and knowledge sharing, making development and problem-solving more efficient.
What other advice do I have?
My experience with deployment has been very positive. We use Jenkins and other compatible tools within our delivery pipeline, and Automation Anywhere integrates well with them. The compatibility with existing CI/CD processes makes deployment and maintenance efficient and streamlined.
APIs have also played a key role in helping us achieve our automation objectives. In one of our use cases, we were unable to proceed with UI-based automation due to access limitations. In that scenario, API integration enabled us to continue the automation journey successfully. Beyond improving efficiency, APIs also helped reduce security risks associated with UI access and delivered better overall performance compared to traditional UI-driven automation.
Looking at the future of automation and Agentic AI, my biggest observation is that the technology is still in its early stages and has not yet reached its full potential. While proof-of-concept implementations are showing promising results, real-world adoption still faces challenges related to trust, governance, and data security. For example, in insurance-related processes, there are valid concerns around sharing sensitive customer and insurance information with AI systems. Organizations need stronger assurances that data will remain secure, private, and will not be used outside of the intended purpose. Addressing these concerns is critical to broader enterprise adoption. Apart from these security and compliance considerations, the functionality and potential of the technology are very promising.
I have not used AI Agent Studio, Autopilot, or the Center of Excellence (CoE) capabilities, so I am unable to provide detailed feedback on those areas. Similarly, while I recognize the importance of AI governance, I have not worked with it directly and therefore cannot comment extensively on it.
One capability I have used extensively is Document Automation, and my experience has been excellent. The solution’s performance largely depends on the quality of training and the volume and diversity of documents provided. When I worked with earlier versions such as v11, document processing accuracy was more limited, especially when dealing with multiple document formats. However, in Automation 360, the improvement has been significant. The platform now handles a wider variety of document types much more effectively and adapts far better than before. For example, where earlier versions struggled to accurately recognize and process multiple PDF formats, the current version performs much more reliably. Overall, the enhancements in accuracy, adaptability, and performance have been dramatic.
Overall Rating: 9/10. The platform offers strong deployment capabilities, excellent API integration, significant advancements in document automation, and a clear commitment to innovation. The primary area for improvement remains enterprise trust, governance, and security considerations around AI-driven solutions.
.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure