Automation Anywhere Reviews

We have used Automation Anywhere to develop different software bots. We currently use version 10.7 for Windows 10 and we are in process of migrating our version to 11.2. We have automated important processes like creation of purchase orders from attributes that are in a Sharepoint form, and upload of exchange rates in our ERP system from data that is available in websites (central banks). We look at automating processes that are manual, repetitive, and rules based.

AA has allowed the generation of gains in productivity by automating certain processes, moving the hours from FTEs to a software robot, thus creating a digital workforce. The employees who were working on those manual activities are now focusing their time in the critical analysis of their processes. Here a few examples:

• Load of daily exchange rates - 840 hours/year saved
• Creation of purchase orders in Oracle - 1056 hours/year saved
• Processing of bank account statements - 600 hours/year saved

• The user friendly interface enables a quick learning process by any developer, and the ability to interact with virtually any system.
• MetaBots - This is an intelligent component/functionality that makes connection to websites or web forms a breeze. This functionality also works great with our corporate ERP system.
• Technical support - Very quick, efficient, and acknowlegeable. They were able to address all our inquiries very satisfactorily.

• Object cloning - This component seems to be unstable in version 10.7. We have run tests in version 11.2 and they seem to work much better there. During development/test cycles it is common to see object cloning components that were working previously stop full of a sudden. In these cases we usually migrate those components to MetaBots.
• Schedule queue - Scheduling is allowed at intervals of 30 mins. Having this interval reduced to 15 mins would allow better control of taks that run more quickly. The ability to schedule bots to run in different time zones would also be a great addition.
• Control Room - Enabling the ability to customize it would be a great addition. In version 10.7 we need to pay attention to the URL to differentiate between Dev, QA, and Prod. We could also use the function to create our own custom dashboards.
• Give MetaBots the ability to work with objects in applications running on a terminal server. This functionality would be a great help to developers.

Less than one year.

The solution in general is very stable, we haven't found any problem with bots deployed to the production server. As far as development goes, object cloning is a component of the solution that seems to be unstable, as it apparently stops working for no reason. Once deployed to production, everything is very smooth.

Scalability is associated to the number of bot runners purchased. More bot runners can be purchased at any time depending on how the demand grows, and AA offers the ability to process bots in a platform called bot farm.

AA Technical support has been contacted for different reasons, including validation of bot developments. In all scenarios, support was very responsive, efficient, and acknowledgeable, resolving all issues very quickly. Support is available 24x7 with tickets being raised either by their own ticket system or by direct calls. The customer service manager engages with the SPA in the company via phone call every quarter, to check on the customer satisfaction.

We previously used the product Automate. That product had issues working with Java forms, which were extensively used by our ERP solution.

The basic setup was straightforward. Deployment took two months. Our implementation strategy consisted of three servers, one for Dev, one for QA, and one Prod, as well as five bot runners: one for Dev, one for QA, and three for Prod. Finally, we have one administrator and one backup. AA provided the needed support to get the solution up and running quickly and smoothly.

Our company has a long-term partnership with TCS. We are currently using their consulting support, which has been good. TCS is able to engage with top professionals in the market.

We started utilization of the tool with a target of generating productivity, specifically by saving 10,000 hours between August and December 2018, regardless of the number of bots deployed.

Automation Anywhere is costlier than the general competition. I believe that it is consistent with their market share and with the benefits AA has to offer.

We evaluated Automation Anywhere vs Blue Prism and Automation Anywhere vs UiPath.

Automation Anywhere is a great platform. It is the tool that allowed us to bring back to life former plans to create our digital workforce. One suggestion is to go with the most recent release, both for the app and Control Room. Versions after 10.7 are the ones with enhanced functionalities.

We purchased ten developer licenses, all of which are in use now. The developers are responsible for deployment and maintenance along with two administrators. We have a target to be met and it requires extensive use of the product. This target will certainly be increased in 2019.

I have been using Automation Anywhere for more than a year in my college laboratory. I utilize it for editing, collecting student assignments, data entry, report generation, grading multiple-choice questions, managing lab equipment, student communication, and automatic software installation or updating. The primary functions include handling repeated administrative tasks, data entry, feedback generation, grading processes, maintaining lab equipment processes, taking attendance, and communicating with students. If any software installation or update in the lab is required, I manage it with the help of labs.

The task bot is the most valuable feature, which I use primarily to automate repetitive and rule-based tasks like attendance tracking, grading, and report generation. I also utilize IQ Bots for more complex tasks involving unstructured data, and email automation for sending bulk reminders to students. It reduces my work time significantly, giving me the ability to focus on other manual tasks. Without Automation Anywhere, my tasks would take much more time, as these repetitive human tasks need daily attention.

Overall improvement is needed for non-technical users who face challenges with how to use it and how to perform more tasks. It should be more user interface friendly for non-technical users and enhance its ease of integration with third-party applications.

I have been using Automation Anywhere for more than a year in my college laboratory.

When we discuss its scalability, it is available across various departments and adapts well.

There are many FAQs, personal calls, and community forums available. Technical support can be easily obtained through official channels, although sometimes the community forum is not accessible to many users.

I used UiPath before starting Automation Anywhere. I also used Blue Prism, which was difficult due to its need for coding.

Initially, we found it a bit complex, but after learning about it, it served us well. For complex tasks, deployment takes about two to three days.

We can achieve nearly eight lakhs per annum in total savings by using Automation Anywhere.

I recommend Automation Anywhere to other users because it minimizes repetitive human tasks, saves time, and helps reduce costs. I would rate Automation Anywhere nine out of ten.

We are using MS 2007 Windows OS mostly with IE and Excel operations. Anyone can write code with AA software with basic coding knowledge, we just need to know which command will help to build the next step. We had developed almost eight major processes and a few POCs for different clients. As we worked mostly with Web and Windows applications, we had used most of the commands related to Web and Windows applications. We can say bot accuracy was 95% in the final result. Bot consumes around 12 minutes to process 1 application, where if a human performs the same they would take a minimum of 18 minutes on average.

AA application is very good for running the application on a schedule. But a few times, the client requirements were 24/7 so it stops every few days. We found three drawbacks with the product in production:

1. For 24/7 running applications Bot Insights won't be generated.

2. For 24/7 running bot stops every few days, it might be an environmental issue or something.

3. the Same name of Mebabot cannot be uploaded to CR.

4. We tried to upgrade to 11.3.4 but there were few bugs while performing actions in Excel. (You may have fixed later stages).

WLM & Device Pool, where multiple devices perform the same thing parallel and complete the tasks at the same time. The Credential Manager for security is one of the most valuable features for storing credentials and providing security between the developer usage and future maintenance where passwords expire every 90 days. There is no need to touch the code and just update the CR locker section. CR UI is also user-friendly for creating deleting and updating users, roles, etc within the CR. The Audit Log section is also good for logging all the operations done in CR.

It would be better if they could extend the support for AA version 11 for a few more years, as most of the companies have tasks completed in AA version 11, and A2019 is much slower compared to AA 11. It keeps on downloading dependencies, and time-consuming while running the tasks. In AA version 11, if the bot stops uninterruptedly it's better if it could resolve itself and back to normal and process the applications.

You can give clients some more time to get used to A2019 and find and fix the concerns observed till then. That way you can add more features and easy to implement for the development team. If you ask all the clients to migrate to the latest version. Few are still thinking about the migration of code from the old to the new environment and various other factors.

Bot Insight for 24/7 tasks is limited in the AA 11 version. If this gets fixed a few more clients will renew this license as well.

I have been using AA for the past three years. 

We need to train the bot to handle all kinds of conditions. So it will behave accordingly when that situation occurs.

The technical support team were very responsive, they were available 24/7 and for severity 1 issue's for the production part they used to reply or communicate with us in maximum 45 minutes.

Other than the CR set up with the database will take little time. Client installation and configuration was straightforward.

We are a vendor team and worked with the client's environment along with their in-house team. Our clients are always happy with the product and its performance. There are few scenario's due to system instability they used to complain, we used to check and revert back to them what is the problem.

I don't remember the exact number, in one of my bot runner I had seen a $5million change.

Pricing depends upon the number of licenses required by the company. They can implement using the community version. If their business can be automated based upon the business process workload they can decide a number of Bot runner and Developer licenses are required.

To use other tools you need to have knowledge with VB script. But using AA no need of that.

Our company uses Automation Anywhere for enterprise automation of various finance tasks, focusing on accounting. This includes processing accounts payable invoices, managing oil and gas revenue, extracting data from text, and downloading files from our ERP system. These automated processes, some of which are business-critical and complex, enhance efficiency and accuracy within our finance operations.

Automation Anywhere has helped to address process bottlenecks and departmental inefficiency. It is used as an attempt to streamline operations.

It simplifies the management of complex workloads.

Automation Anywhere has a significant learning curve, but it is understandable and reasonable. Having a support team makes the process easier compared to learning it independently.

The training for non-technical users takes one to two months.

We've integrated numerous tools with Automation Anywhere, most notably our accounting system, which is interfaced via SQL and terminal. Additionally, we utilize RPA to interact with various systems employed by other departments.

One of the strengths of Automation Anywhere is its user-friendly interface, which makes it accessible even to those without a development background. As someone who began with no coding knowledge, I found it a great entry point into the world of automation. This accessibility, compared to tools like UiPath, stems from its intuitive design. Furthermore, the capacity to deploy RPA solutions across various virtual devices, a common feature in RPA, is invaluable for streamlining and scaling automation efforts.

Automation Anywhere's API feature is a fantastic offering, providing the valuable ability to call or execute tasks.

As a developer, I find Automation Anywhere's bot editor riddled with minor workflow issues that hinder productivity. For instance, the broken bot package versioning system prevents copying and pasting code between bots with different package versions, a stark contrast to the flexibility of Python. This inconvenience arises even when transferring code between bots within the same process, significantly disrupting workflow. While there are other minor improvements I could suggest, Automation Anywhere has been, albeit slowly, addressing our concerns.

I have been using Automation Anywhere for five years.

The stability of Automation Anywhere is quite good, with few outages from the platform itself.

Automation Anywhere is a very scalable product capable of handling large-scale automation operations.

In my experience, Automation Anywhere's technical support has been lacking. Many of their representatives don't understand the product enough to offer effective assistance. As a developer, it's frustrating to encounter issues and try to communicate them to support staff who seem unfamiliar with the underlying technology. This lack of product knowledge hinders effective troubleshooting and resolution.

Our current support plan is the most basic, so I don't anticipate a quick resolution. However, they generally respond within the expected timeframe for this level of support.

Neutral

Although I wasn't involved in deploying Automation Anywhere, I recall the process being straightforward and immediately successful for the company.

The implementation included a team of four to five individuals supported by a contractor.

We evaluated UiPath and another product that I cannot recall.

I would rate Automation Anywhere a nine out of ten.

My experience upgrading Automation Anywhere from an on-premise solution to the cloud was challenging despite some helpful features. While a tool was provided to convert version 11 tasks to 360, it introduced unnecessary code during migration. This inefficiency may be specific to Automation Anywhere or a common issue with automation upgrades. Regardless, the process was lengthy and tedious.

Automation Anywhere requires considerable maintenance due to a combination of factors. Our automation of an older Java-based accounting solution causes some challenges. Additionally, automating browser-based tasks in large oil and gas SaaS companies leads to frequent breakage of bots when the underlying HTML or code changes. Consequently, ongoing maintenance is necessary and will be a permanent responsibility for our maintenance team, which includes our project leader and a group of developers.

Establish consistent policies and procedures before doing anything. This aligns with the Center of Excellence framework. Having clear, consistent policies is important before building bots and implementing solutions.

We have built over 75 automations with Automation Anywhere across various teams in the organization, delivering a high value for our internal teams. We have explored a couple of process transformations with Automation Anywhere using their IQ bots and AI automation tools.

We have integrated applications like SAP ECC, One Source Automation, and SharePoint using Python code. Our company has 25 AA developers. 

AA improves process consistency and reduces human error. We have saved our clients considerable time using Automation Anywhere. While we don't assess the dollar savings, we look at the amount of time saved per project. The tasks were previously completed by hand, but Automation Anywhere enabled a lot of process automation, giving users automation that runs around the clock. For example, we can automate processes to address point-in-time reports so a user doesn't need to wake up at midnight to handle these issues. 

We haven't gotten approval to implement AI, but when we do, I believe it will accelerate the time savings we realize through automation. We will work with other teams to show them the value of AI and automation. 

Automation Anywhere's most valuable feature is its ease of use. It's easy to envision a solution or process to transform with Automation Anywhere from end to end. We can realize the value much faster because it's easy to use and understand. 

All the features are impressive. We haven't had a chance to use the Copilot or other AI features, but the studio is great. It's the platform where we build the bots. The IQ Bot used to be excellent, but the IQ Bot isn't available anymore. I believe it's document automation, which is also very good.

Anyone at any level can use Automation Anywhere. Once you get the hang of it, it's highly intuitive, and the learning curve is short. We started seeing value from Automation Anywhere within a month or so after implementation, but that was with the older version. It's even faster now that everything is on the web.

Training employees using the courses takes a couple of weeks, followed by another week or so of hands-on learning on the platform. It takes about four weeks to onboard a user.

Automation Anywhere can improve its integration. For example, you can't directly integrate Automation Anywhere with SharePoint or third-party applications seamlessly. Adding seamless third-party integration would add a lot of value to the platform. We need to use APIs or Python coding to integrate the third-party applications. If Automation Anywhere could add some connectors, that would be great. 

I'd love to see the ability to build web or mobile applications that are integrated with Automation Anywhere bots, so that a user can work on a web interface directly. Then, it can be linked to the Automation Anywhere bots in the background. They just hit a button, and all the data or information will be used by the bot to do some process in the back end.

We have used Automation Anywhere for five years.

We've never had any issues with stability.

It's easy to build automations and scale Automation Anywhere.

I rate Automation Anywhere support 10 out of 10. The tech support is great. We have a CSM we can contact for information, and they're very responsive. 

Positive

We use the SaaS model of Automation Anywhere, so the deployment was easy. We set up the infrastructure in under a week. We worked closely with the Automation Anywhere folks because we wanted a clean slate. We didn't want to migrate from the older version to the SaaS edition and took it as an opportunity to clean up the bots. It didn't require much effort, and only two people were involved. The upgrade process was simple. Maintenance is minimal. It only takes a couple of people to maintain 75 bots. 

Automation Anywhere's pricing is excellent.

I rate Automation Anywhere nine out of 10. I would recommend it to others. It's intuitive and easy to implement. 

Automation Anywhere is removing the boring, repetitive tasks from the workforce.

I've worked on different models over different frameworks. 

I do the coding as well as the deployment side. I prepare documents and the user ID. Sometimes, if the user ID is not prepared, then I jump into the process to get it done. With the technical feasibility of the document, I take the technical feasibility and do an estimation to code the bot. I configure the bot, then code it according to the entity and get it reviewed from the client. Then, I run the bot through the Hapi port, as well as different scenarios which might come up.

Once the client is happy, we have a couple of rounds of testing. We have a "You Ready" phase where we code for a few days and the client provides data. We run through the data and this give them the technical results. When they're happy, then we finally move the code over.

One of the clients that I worked with to automate their process received invoices from 12 different companies and different regions. These are the process steps that we automated:

1. We could get the data from PDFs (the invoices were in a PDF format).
2. We accepted the data, uploaded it, and filtered out some of the data. 
3. Once we extracted the data, we use it to search data on particular websites for a particular invoice number to be processed. 
   
4. We used the invoice number to process the invoice.
5. We got approval for the invoice. 

I worked on another process where it generated offer letters for different people with templates. We would get the data in a dump. We would take that data put it into a template, and then into a Word file.

With another client, we used to receive around a million files. Per day, we would have to process around 70,000 to 80,000 records, uploading data where the volume was huge. We deployed the process in multiple bots, using about 20 bots to get the process done. For this client, every second used mattered. We had to code the bot in such a way that we could save every second for them. We had to figure out how much time the bot took and the cost savings for any particular data. We used the workload feature of Automation Anywhere get it done. The manual process took around 30 to 40 people around five to six hours a day, where the bot finishes between one to one a half hours. This was a huge time savings for the client.

For the client with 70,000 to 80,000, we created an SQL database to maintain all their records using bots. E.g., if a bot failed, then another bot would retry using the same information. In the "You Ready" phase, this process was 95 to 98 percent successful. When we finally moved it to production, we had between 99 to 100 percent accuracy. This took us around one and a half months to set up. Two development levels were involved along with an architect who was guiding us.

The most valuable feature is the object cloning. If you compare it to the other RPA tools, object cloning in Automation Anywhere is the most valuable. Mainly for web application, object cloning comes in very handy. Most processes are built as either a website or as a desktop application. Out of 800 commands, around 150 to 200 will be cloned through object cloning. In Automation Anywhere object cloning, there is a special feature called DOMXPATH, where we can customize it to any level. If IDs getting changed, which happens in some cases, then we find out the pattern. Based on the pattern, we come to the particular text box and button. Then, we can use bots along with parent-sibling relationships to get things done. 

I like that it has PGP Command and it is able to connect to a Citrix environment. 

We have the MetaBot feature, which is valuable because we can read reusable components in the MetaBot, then use them as a framework.

The training and resources for this tool are very good. They are so simple that anyone can easily learn it. One of the tool values is its ease of use.

The Excel part needs improvement because we use it as a database. Right now, we are using UiPath for this feature, as that RPA tool allows us to sort, search, and filter in Excel databases. 

The IQ Bot is pretty immature, in regards to AI and machine learning. I would like them to add additional logic.

I have been using it for almost two years now.

Automation Anywhere is quite reliable and stable, especially compared to the other RPA tools. E.g., with UiPath, code that was working yesterday might not work today.

We have experience minor issues with Automation Anywhere, such as with the object cloning, where it required us to restart the machine. Once the machine was rebooted, the solution worked fine.

It takes one or two people to handle the daily maintenance of this solution.

We code our bots with tasks and subtasks in such a way that we can easily combine them when new features come up.

The initial setup is pretty simple and fast. It can be done from the web Control Room, which can be done easily.

For coding, we are keeping the information in XLS or XML files. We use MetaBot to retrieve the data. We keep our URLs in an Excel file, so when we go to our production environment that it will automatically take the URLs and implement them.

One or two people can deploy the solution easily if they understand the requirements.

In most of the cases, the product value is very good. If the infrastructure, implementation, and framework are good, then generally, the client can get a good return on investment. However, getting good resources is tough since most people have limited experience in RPA products who struggle a lot to use these tools.

The coding for Automation Anywhere is a lot easier than for UiPath and Blue Prism. I have about a year and half of experience with UiPath. Compared to UiPath, Automation Anywhere is easy to use and bot development is faster. If you try to develop the same bots in UiPath, development of the same bots in Automation Anywhere will be faster. If the client wants the bots to be developed very quickly, we will do it Automation Anywhere. However, if they give us time, then we will us UiPath. If the process is huge and complex, then we go with Blue Prism.

Another key advantage of Automation Anywhere is the object drawing feature. This comes in very handy. Whereas, if we use UiPath, we have to use the .NET code and commands versus Automation Anywhere where can use scripts or create MetaBots. 

Companies need to do feasibility testing to avoid trying to automate processes which are not right for automation. Then, they should examine which vendor is the right one for the automation process, e.g., Automation Anywhere or UiPath. They need to establish the proper infrastructure for the RPA product, like licenses and an RPA team. The RPA can be a mixture of trained professionals and people who are learning as they go from the training provided by the tool.

Version 11.3 updated a lot of features that were previously not there, like workload automation and analytics dashboards.

I am always learning new things with this tool.

Our primary use case is banking/financial. Processes we have automated include loans, ledgers, mortgage loans, and even some of the record management systems.

In some of our use cases, people were spending more than three hours per day just generating reports. And then we created an automation for this and it reduced the time to 30 minutes. It improves employee productivity so they can use their time in other areas.

I like the way it works with structured data in the back office and the way it does repetitive work.

In terms of ease of use for developers, we're able to create reusable components. We don't want people to have to rebuild things from scratch. In this way, developers can take the reusable components and complete their development processes more quickly.

The bot creation process is pretty straightforward. Anyone can go in and learn it easily, and then they can build a bot. I like it.

When it comes to integrating the solution with other applications, there are some challenges. For some third-party solutions, there are no direct interconnections. For example, there were no direct connections with SAP systems. So, we had to create connectivity between Automation Anywhere and some third-party solutions. They have now improved that situation a lot and we can connect SAP and other systems as well.

If they want to sustain their position in the market, they have to be flexible, working on how we can integrate with third-parties, working on a machine-learning product. People are expecting that and it would be really helpful.

From the IQ Bot perspective, frankly speaking, they still have to improve a lot. I got IQ Bot training in San Jose. My expectation from a straight, technical, architectural point of view was that I would be able to create my own algorithm and integrate it. But with IQ Bot, I am not able to integrate anything. It is already well-defined, so I have to use that particular option only. I know I can not go with any other machine-learning platform. I hope they will be coming out with version 12 where we can integrate it with Python algorithms and other stuff. It might only be in the future, it might only be on the roadmap. But as of now, it is lacking a lot in that area. We are expecting, for most of the documentation, things like tags, that there would be a checkbox option. That's lacking in IQ Bot.

The stability has increased a lot. When we started with version 10.2, there was a lot of instability. There was no way we could keep the bots active, there were scenarios where it became disconnected. There is also the code deployment perspective and a lot of other angles. People are always only thinking from the business perspective, but as a technical architect, I think about operational effectiveness and how they can improve the product's maturity.

The stability has improved a lot.

However, when upgrading, they changed their internal architecture. They moved it to a JT Java platform. When moving, some of the existing features did not work in the new version. It might be that they have to improve their regression testing to improve clients' satisfaction. It can happen that what is running in production currently, if I move to a new version, suddenly is not working tomorrow. People are not happy with that and say, "I want to roll back to the older version." They are not able to use the new features.

When moving to a new version, they have to think about what features people are using and what kind of impact there will be. Small business users will be fine, those who have ten bots or 15 bots. But there are organizations like mine that have around 700 to 1,000 bots, and that makes changes very difficult to handle. It could be that 10,000 tasks are using something and if that thing is changed it will be hard to update. I might have to spend a year on that. People will never accept that.

Scalability-wise, they have increased it a lot, based on the clustering method. As a technical architect, I'm going with always-on production and data centers. That means that if any data center goes down - there is a natural disaster or something else that happens - how do you make it such that you can bring up another data center? I'm coming up with a design for that based on the latest version, version 11.

The initial setup is very simple. It's Windows-based and it's a straightforward installation. We used to say they need to come up with a silent installation option, with the previous version. But now, with version 11, they have introduced, even at the server level, a silent installation. That means we can make it automated instead of manually installing it.

We measure the ROI of automated processes by how much of a benefit we're getting from it. We look at how much time it takes and how many robots we're using and we include the licensing and operations costs. Finally, we take into account how much faster the performance of the bot is, compared to how long it took to do the process before automation.

We have saved time and money, but when people think of going with RPA they cannot expect that they will immediately see ROI. They have to sustain and increase the RPA options. They will have to spend a minimum of one or two years increasing their use cases for automation. Then they will see a good ROI. They should not expect, within three months, to say, "Hey, I have automated, where is the ROI?"

All organizations have a certain strategy or checklist. In this case, management will think first about licensing cost, about the total cost of investment. After that, they will think about the product's features and functionality. They will also look at support. They will consider the use cases, the current processes they have identified already, and based on all that they will decide whether to go with Automation Anywhere or another product.

In terms of our bot creation process, people come to me and say, "I have a process. How do we automate it?" We need to understand if it's a cognitive use case or a straightforward use case. If it's straightforward, we tell them we'll use this product and build it for them with four to six weeks of development. Then it can go to production. If it's cognitive, then we really need to understand it better. We need to use a third-party product, like Kofax or maybe an IQ Bot if it is fit for the scenario. Based on that, it takes some time and then we'll move it to production.

We have a process architecture review committee where we review all the processes. We cannot blindly go forward with all the processes that have scope for automation because it's all licensing cost. We need to think about whether we can automate a given process with any other IT automation solution, like scripting or macros. If that is not possible then we have a fit for RPA. Then we have to go through our checklist, walk through the use cases, and look at the percentage of the automation scope: Is it a 100 percent automation scope or 80 percent or 20 percent? We need to to know if there is any manual validation or manual intervention required and how that is handled.

Initially, we failed with the Citrix automation where we have a lot of use cases. We ran into a lot of limitations with Automation Anywhere in version 10.5. But with version 11, they have AI Sense which we can use for Citrix applications. We are currently exploring this option.

I have taken courses at the Automation Anywhere University and I have advanced professional certification from Automation Anywhere, which I completed for version 10.5. I'm also doing it for version 11. I also have an official certificate for IQ Bots.

At the moment, for us, everything is on-premise. We're not ready to go with cloud. So we have to build our own platform. We have to build our own bots.

I would rate this solution at seven out of ten. They have to improve on the product's maturity level. When they are introducing new versions, they have to conserve the existing commands and features, so that they work when we move to the new version. And they also have to come up with more flexibility, so their solution can integrate with our scripting and our own algorithms. That will make it easy to convince our business areas to increase the adoption of RPA.

In the financial industry, Automation Anywhere helps us streamline tasks by automating processes like invoice entry and employee onboarding, along with many other functions.

Businesses leverage Automation Anywhere to streamline their workflows and minimize operational problems.

Automation Anywhere has empowered our clients to achieve greater accuracy, enhanced control over their processes, and liberated employee time for more strategic endeavors.

Automation Anywhere is easy to use even for non-technical people once they receive the training.

Automation Anywhere is considered user-friendly, with the learning curve manageable for beginners. The available resources provide a solid foundation for new users to get started.

It seamlessly integrates with our daily applications, providing a valuable human-like interaction that enhances the automation process.

Co-Pilot improves productivity by automating tasks like reviewing purchase requisitions, which previously required multiple people. It also allows individuals to manage workloads that once demanded multiple people, allowing them to focus on more valuable tasks.

Generative AI stands out in automation, especially for crucial tasks like invoice processing, where it can extract information, or for tasks requiring web research, going beyond simple rule-based automation.

Automation Anywhere offers integration with various Large Language Model applications, and for connecting these external systems, utilizing their API is the best approach.

Automation Anywhere's document automation, powered by IQ Bots and now enhanced with AI, stands out as a particularly valuable feature. This combination allows for seamless integration of a wider range of document types, streamlining our workflows.

Automation Anywhere's current requirement for upfront annual payments limits flexibility for customers. Offering a wider range of payment options, such as monthly installments, would be a welcome improvement.

While Automation Anywhere's current learning materials cater to junior and new users, senior developers require more in-depth content to effectively utilize the platform's full potential.

I have been using Automation Anywhere for six years.

Automation Anywhere's technical support has a prompt response time, with Portuguese-speaking representatives in Brazil. For complex issues, they efficiently escalate tickets to a global team of engineers for further assistance.

Positive

I would rate Automation Anywhere ten out of ten.