BotFarm Reviews

I use it in my client project to extract data and communicate it for business purposes. I summarize the data, and when a customer talks about their details, I extract the data from that point in the conversation to create a summary and report, then send the data to the client.

I am using Automation Anywhere with SQL Server for the data. I utilize the data extraction feature, including Document Automation and IQ Bot. I also use the Bot Dashboard, which has an analytics feature that provides all information regarding the service.

More detailed error handling would be beneficial, especially since the AI feature was recently added.

I have been using Automation Anywhere for approximately five years.

I use error handling and delays to ensure the network is proper and the service is running properly.

I rate the technical support by Automation Anywhere 10 out of 10.

Positive

Licensing and other pricing matters are handled by my manager, so I am not able to fully describe the price and licensing. Automation Anywhere provides partner licenses free for six months and also offers a community edition to check the details and get hands-on experience.

I work as a developer, and my manager is responsible for the research and analytics for the project with the client and business users. I am satisfied with BotFarm. I would rate my experience with BotFarm an eight out of ten. I do not see any room for improvement for BotFarm. I am using AI tools such as Amazon, Microsoft Azure, and ChatGPT. I am not using AI-powered bots in BotFarm. I am a partner with Automation Anywhere.

Our company uses the solution to collect insurance data and transport it to a specific destination. BotFarm is also used in our organization for mobile solution development. I help the development team solve problems, assist in solution design and delivery, and ensure the business requirements are followed in BotFarm implementation.  

The solution can improve the accuracy of hand-written data reading. In some situations, the data needs to be hand-written by the agents, and at our organization, we face some rare challenges with such data in BotFarm. 

I have used BotFarm in our company.  

It's a scalable product. In our organization, we sometimes write a script once and reuse it several times, which improves workflow efficiency. Our team inputs the datasets one by one or in a batch mode into BotFarm and schedules them or calls individually as needed. For instance, if one individual has 15 or 20 forms that need to be scanned and logged immediately, it's possible to implement with BotFarm and its scheduling operations.

The solution is ideal for small and medium-sized enterprises and can fit in for large enterprises as well, depending upon the use case. For instance, if 100 agents are working across different locations through a mobile app, all the data from the agents can be stored in a common repository and scheduled. BotFarm can be configured based on the architecture and business operations. 

Some of our organization's professionals have found UiPath to have more libraries and be easier to use than BotFarm. Our company's developers and leads also found UiPath to have better integration capabilities than BotFarm. In our small organization, we haven't personally faced any difficulties integrating BotFarm. 

The product is slightly expensive. In comparison to competitor tools like UiPath, BotFarm's cost is greater. Our organization also works with UiPath and Microsoft products. Our company doesn't want to burden customers with heavy costs, so we also propose or shift customers to solutions like UiPath. 

Some of our company's customers have shifted to UiPath due to its ease of use, quick EOC, and component development. We also have a license for Microsoft's competitor product for a customer in the logistics industry. Our organization also uses Automation Anywhere and IBM products. 

BotFarm can streamline repetitive and high-volume tasks in our organization. The solution reduces manual data errors and improves data accuracy. The data accuracy in our organization was previously around 75%, but with BotFarm, it has enhanced to 80 or 90%.

Presently, the only manual task our company team has to implement is providing the data in a format that helps the solution check data accuracy. Once BotFarm was implemented, the need to input data one by one was eradicated, along with accuracy errors. The solution has also saved time through the automatic features in our company. 

BotFarm has been mostly used by our organization's banking sector customers, who had a bigger budget than others. Overall, I would rate BotFarm an eight out of ten. It's a low-code and easy-to-onboard product for developers. At our organization, we could easily train a few professionals on BotFarm from the RPA team who were more familiar with products like Selenium and Java; therefore, it's easy to comprehend. 

The solution is used for RPA. We use it for report generation, complaint resolution, and system administration. The solution resolves the complaints with routine tasks and steps based on the configured rules. We use it for IT support for some repetitive tasks on systems.

Using the solution, we aim to optimize report generation, customer complaint resolution, ticket closure, and administrative tasks.

The product has increased efficiency and reduced the time spent on tasks. It is easy to integrate the solution with other tools.

The product must provide features related to AIOps. The tool must be able to monitor system performance based on certain activities or events. It must be able to detect certain health stats of the system. The tool must execute remedial actions to resolve problems before they cause significant incidents. It must detect system anomalies and execute remedial actions based on set rules and processes built into it. It must escalate or resolve the issues automatically.

I have been using the solution for more than a year.

The pricing is fair. We don't have any major problems with the pricing.

Overall, I rate the solution an eight out of ten.

BotFarm is like the entry point for customers. It allows customers to evaluate the automation capabilities and how it will work within their environment. It also provides Bot Store with multiple pre-built bots. 

BotFarm can be used as a plugin, where you can start the process within one or two days. The development process for custom bots may take around one and a half months. During the initial stage, the customer can use Bot Store to test and evaluate the product before proceeding with custom development for enterprise implementation.

For enterprise implementation, customers typically opt for custom development rather than relying solely on Bot Store.

Bot Store is the same thing as BotFarm. BotFarm is a term used to describe the customer's own implementation. When customers have multiple projects and a hundred processes, they may have reusable parts or bots. These reusable components are stored in the customer's own "BotForm." On the other hand, the Bot Store is a global platform where any customer can choose any bot for their implementation.

I am satisfied with BotFarm. The reason is that during the initial stage, if I develop one reusable bot or component, I can use it for multiple processes. 

For example, if I have developed a navigation bot for Oracle EBS, I have developed it for one process, and I can reuse it for fifty other processes as well. 

This eliminates the need to develop the same responsibility and integration again. I just need to specify the type of responsibility I want to select, and the bot will handle the selection process accordingly.

BotFarm has room for improvement. One aspect that can be improved is the accessibility of reusable components for developers. It relates to role-based access and accessibility. 

Sometimes, within the same project, multiple partners are working, and one partner may not want to share their work forms with others. In such cases, the administrator has the authority to decide whether to allow the usage of certain components or not. This decision is taken by the company or the administrator. 

Initially, if partner A develops something, they may not share it with partner B. Unfortunately, partner B may end up developing something similar on their own. However, things are changing now, as standardized development practices are being adopted by partners. This allows partners to share and utilize each other's work even in such situations.

From the customer's perspective, it will have the cost, and it will have the project's timeline.

It is not just about being easy to use, but it should also be simplified and easy to integrate. It should be developed in such a way that it is easily integrable. In fact, one of my customers has dedicated a resource solely to the development of reusable components. However, they have already made improvements in that aspect.

I would rate it an eight out of ten. 

Customer service and support are good. The support is provided equally for all Automation Anywhere products. In my experience, the company has been responsive and helpful in assisting with process implementations and providing resources when needed.

The initial setup is straightforward. 

Additionally, overall, in terms of automation anywhere or integration, it depends on the partner and how they implement it. However, they have managed to tackle this scenario by reviewing the bots before they are deployed on the BotFarm. This ensures a better outcome because each bot developed goes through a standardized platform.

Pricing depends on consumption. The starter price is free. Automation Anywhere's license and model are designed in a way that customer support is easily accessible. Customers or partners don't have to provide support every time to each individual customer. 

This makes it easy to use and understand since automation engineers can quickly grasp it. As a result, it is user-friendly and straightforward to use.

From a partner's perspective, I would recommend using the Bot Store. If you are a partner, you can share your bots with multiple customers. However, if you are a customer, I would suggest using BotFarm.

This is because customers generally prefer not to share the bots they have developed with others. On the other hand, partners want to share their bots with multiple customers to generate revenue. So, BotFarm is more suitable for customers, while the Bot Store is beneficial for partners.

Therefore, recommendation depends on who the user is. If it's for Bot Store, then it should be developed by partners for open market usage. However, for BotFarm, customers who do not wish to share their bots with others would find it valuable since they have already invested in the development.

I would rate BotFarm an eight out of ten. To bring it closer to a perfect ten, I would like to see additional functionalities such as multi-level code review and approval processes implemented.

We use BotFarm to mimic human actions because in our organization, there are certain tasks which are time consuming and require a lot of precision with the data. There are repetitive tasks which are automated through BotFarm, so we've set the schedule depending on the requirement, and there are also schedules that are 24/7, based on the requirement and information available. For example, members of the operations team have to pull the data from a website, select the data, input the data, then process the data. All these tasks are now automated through BotFarm.

What I like most about BotFarm is that it's one of the leading RPA products in the market. Very few products focus on robotics today, so I like that BotFarm offers a lot in terms of what general customers expect it to do.

An area for improvement in BotFarm is that the communication between the Control Room and the Bot Client Missions isn't utilized well.

There's also the issue with PCI DSS compliance or certain regulations that require a set of configurations that are not fully supported by BotFarm. The product should be certified or designed according to the required regulations in the finance industry to make it better.

I've been working with BotFarm for four years now.

The latest version of BotFarm is quite stable, and it didn't give us many issues. The previous version of BotFarm had issues, particularly with jobs being triggered but not starting at the scheduled time. Sometimes a job starts, but it's not deployed to the Client Mission, so scheduling in the previous version of the tool isn't as reliable, but with the latest BotFarm version, my team had a better experience.

BotFarm is a scalable solution.

We had some day-to-day issues with BotFarm, so we contacted technical support, and they provided solutions. On a scale of one to ten, I'm rating the technical support for BotFarm an eight.

Positive

We didn't use a different RPA solution apart from BotFarm. We stuck to it because of its pricing and the level of commitment and training that we received from Automation Anywhere.

The initial setup for BotFarm is a little complex because of the two components, Control Room and IQ Bot. It's pretty straightforward to set up Control Room, but it's not the same case with IQ Bot. It only takes around one to one and a half hours for setting up Control Room with proper planning, while setting up IQ Bot takes up to two hours.

An in-house team deployed BotFarm.

I don't have information on how much a BotFarm subscription costs.

I currently work with BotFarm. My company also uses IQ Bot, but it's still in the exploration stage.

I'm an end-user or customer of BotFarm.

Right now, five thousand two hundred people use BotFarm within the company.

The solution isn't that difficult to maintain.

My advice to anyone looking into using BotFarm is that it's the same with other products, and it all boils down to whether you can afford the solution or not.

My rating for BotFarm, particularly its latest version, is nine out of ten.

Lots of different use cases, such as front office customer experience, repetitive tasks, multi-login screens, document processing, and screen notification.

We have been solving a lot of our productivity issues in different areas. And of course, in the core business. Productivity increased far more than thirty percent.

I can not think of just one the whole solution is very good. Maybe because it is user-friendly.

The discovery suite that they just acquired could be included. The more I think, maybe it's going to be targeted to be integrated with the process discovery piece, after the acquisition of FortressIQ.

I have been using BotFarm for the past five years.

BotFarm is very stable from our experience.

The has been proven to be effective and we are building bots every day now.

The initial setup it was simple and deployed in less than two months.

We have seen a return on investment in less than six months from the time we started using it.

I would recommend BotFarm an eight out of ten.

We use the solution to automate the use cases for our clients. We have automized the day-to-day work of their order management system.

The main features of the solution are the IQ Bot and web-based automation.

We do have some troubles with the internal software commands, but we have been troubleshooting this bug to fix it.

I have been using the solution within the past 12 months.

I have found the solution to be very stable.

The scalability has been good. We have approximately 300 users using this solution in my organization and we plan to increase the usage.

Overall the support and customer support areas need to be improved.

I have previously used Blue Prism.

The initial setup was complicated. 

We did the implementation and took us three months.

We are on an annual license for the solution and is priced well.

We have evaluated Blue Prism and UiPath before.

I would recommend this solution to others. I would advise any of your new developers to start using it as soon as possible, it will be beneficial for them to get started.

I rate BotFarm ten out of ten.

There are numerous use cases for the solution for various departments, including weight inspection, or trade ops, or compliance. It's often used for document processing. For example, we receive annual reports from lots of companies that are listed on the stock exchange. To check those reports, there has to be some specific tables and keywords that should be in the annual report of a company. For manually processing thousands of documents, it is not feasible. This solution makes it possible and it happens fast. 

We have implemented solutions where we can extract the text using OCR tools and match all the relevant data that we need to find to prepare a report and forward it to that company. This makes the process a lot faster, and it can be deployed on multiple machines. That way, rather than having a lot of people who work on the same tool, I can just divide the operation on multiple machines and it will be done in less time. Therefore, it offers efficient processing.

The Excel processing is very useful to us. The tool that I'm using has all be Excel functions, however, in the current version that is Automation 360, there are a lot of options. They have Excel basic packages where you can open and just do crude operations, like create, update, delete, or, in a higher package, there are lots of functions that offer filters, macros, clips, whatever you want to run. The version that I'm using, 11.3, has a limited Excel functionality. It still works, however, the new version that they have deployed, A2019, and the latest one, Automation 360, have a lot of functions.

They have proper logging mechanism and also we can check whatever we are doing and they enable and disable list debugging feature. 

It is very easy, simple. You're working on a notepad, and you don't need to know programming to work on this.

The dashboards are quite good, especially on the latest versions.

The solution can scale.

Technical support is quite helpful.

For the most part, the initial setup is straightforward.

We've found the solution to be stable.

The version that I'm using, the Excel command, is a bit limited. 

The OCR tool, the optical character recognition tool, could be more efficient. It should be monitored thoroughly due to the fact that the OCR tool we have we have to manually check even if there are only a few characters missing, the processing might go wrong. In general we wish that the OCR of that product would be more efficient.

You do have to make sure your system will be compatible with the product.

I've been using this solution since September 2019. I've used it for more than a year at this point.

The solution is reliable. It has been working pretty well for us for the past few years. There are no bugs or glitches. It doesn't crash or freeze.

We have attempted to scale and we've found it is possible. Some of the operations require a certain level of scalability, and it has been pretty reliable for that.

While we are a company of around 10,000 employees, I'd say roughly a thousand people have been using this product. Our users are scattered through multiple departments, and every department needs processes to be automated. Therefore, there are lots of users.

We do plan to increase usage.

With every financial year, there are lots of processes coming in. Every department says that we have less manpower and the processes are quite repetitive. Likely there are lots of processes every year, around 23 processes scattered through departments. As the word spreads that some users are able to automate a lot of the processes effectively, others come to us and say they need their own efficiencies. Therefore, we're constantly expanding.

Technical support has been good so far. They have a separate portal for assistance. We have raised a few tickets, and based on the priority, they respond to us. They also ask us the expected time, by what time we need them to call, and they have follow-ups every now and then. It is pretty good. We are satisfied with their level of support.

The initial setup's relative ease of setup depends on various versions. In the version that I used, 11.3, the setup was pretty easy. You have to download and install two machines. One is the client developer. However, the new version that they have, is for a cloud-based deployment. You don't need to install a developer. You just need to log into the control room on any webpage and you have to work from there. For deployment, they have a specific installation, and it's my understanding that there are lots of user rights issues. They have made it easy for installation, however, it can grow in complexity depending on your needs.

Licensing is something that management handles. I don't have any visibility on the costs or the licensing arrangements.

We have evaluated UiPath and it was really good. However, the approach was very different from Automation Anywhere. In Automation Anywhere, you just had a command-line view where each line you add new commands. In UiPath there was a flow-chart view. That was more creative, however, that was two years ago. Now, Automation Anywhere has those features, and it is also a web-based platform, so you don't have the burden to install the developer on your system and you don't need an office PC to do that. You just need to have the right access and credentials and you can work from anywhere.

We're partners.

I started off with version 11, and currently, I'm working on 11.3.3. There's a new solution, RPA A2019. That's the new version. I have that certification, however, I have no projects for now on that.

I'd recommend the solution. Automation Anywhere is a very good solution if you're looking to expand all your work areas. There are lots of businesses out there that say that they don't require this, however, once the solution is implemented using RPA, businesses themselves have a lot of time and resources to expand their research areas. The growth increases exponentially.

I'd rate the solution at a nine out of ten.

• We use the solution for automating a noise cancellation process.
  
  
• In our business, we have a certain requirement to gather information from multiple applications in our customer services team, before we can troubleshoot an issue the support engineer has to handle 14 different applications to get the required information. This means the engineer spends approximately 25 minutes getting the required information even before they can start troubleshooting the issue. In the customer support space, we use this solution for automating the gathering of information from 15 disparate applications.
  
  
• In the customer service space, we have three bots and in the finance space, we have one bot.
  
  
• We have a few use cases where we use the bots to essentially increasing efficiency and reducing manual work in different areas.

The most valuable features I have found to be the screen scraping and the integration with third-party solutions.

The user experience could be made a little better with this solution. I find it difficult to find qualified people to be able to use the solution. 

In the future, I would like to see machine learning built in to support marketing use cases.

I have been using the solution within the last 12 months.

Based on my experience, the solution is stable.

I have approximately 47 users using the solution in my organization. Currently, have this solution deployed in one country and in two departments. Next year we plan to increase have the solution operation in three countries and across 14 departments.

I have previously used Blue Prism and UiPath.

The installation is straightforward.

The license of this solution is on an annual basis. The price is fair. However, what we did initially was a POC, but now we are looking at moving from a POC to expanding it out further. I would appreciate some kind of discount.

I have evaluated Blue Prism and UiPath recently.

Those wanting to implement this solution make sure you have a team that can support you. Getting individuals with the qualified skillsets required has proven to be difficult.

I rate BotFarm a seven out of ten.

We use the Bot Farm solution for two use cases. One is for procurement and the other is for finance. Both use cases required the liquid license availability of the task bot. Therefore, at month-end or the middle of the month, the processing needs to be on a faster pace as we had SLA activity involved with the processing of the invoices and the financial auditing purpose. 

Basically, we use floating licenses which are automatically applied when there was a high peak on the load, and the floating licenses resulted in the shorter processing cycle of the activity.

The scalability is the solution's most valuable aspect. The reason Bot Farm is used is to have only one license availability whenever you have a spike in the transactions. That is a core feature. That is something which we are using to the maximum. It's working well due to the fact that the solution use case is quite structured. The only ask was to have additional bot licenses be present to incorporate it. That way, we don't have to get stuck with the license cost as it's generally on a yearly basis. Right now, it's just on the basis of the usage that we are paying.

The solution has been very user-friendly.

The initial setup is very straightforward.

The interface is seamless.

The solution is very stable and quite reliable.

For the intelligent bots, it is still not quite structured, as far as I can see. I checked for IQ Bot. These licenses are having certain issues. We stopped around the pricing part. It's not just the price, however. It was also not fitting the capability. Based on the on-prem model, if they can include an intelligent bot there, it will be helpful with all the security and the pricing parts involved.

The dashboard needs improvement. For Bot Farm, the visualization is not that good compared to the main Automation Anywhere dashboard.

We've been using the solution at least over the last 12 or so months. We are continuing to use it.

The solution is quite stable. It's very reliable. When you're adding the additional licenses the basic structure is there. It's just the licensing that gets involved. It's more on the configuration side. Otherwise, it is quite seamless with the interface. The preliminary interface is Automation Anywhere, so there are no issues there.

The solution can scale very well.

We have two teams using the solution currently.

We are using this solution specifically in the India region, with the two departments of finance and procurement. We don't have that much load as everything gets outsourced here in India. We are still looking for opportunities where a load of taking Bot Farm license mechanisms can be used. Therefore, I can't speak to if we will increase usage or not.

Technical support has been very good. Many a time, there was an issue with the configuration part, or the licenses were not automatically deployed for the execution of the tasks. We had to connect with them, and we always found them to be helpful and responsive. I would say we are satisfied so far.

We have three RPA solutions that we are using. We also use UiPath and Blue Prism.

The initial setup is very straightforward. It's not overly complex or difficult. We were pretty comfortable with it already. We are already using Automation Anywhere for the past four years and therefore, it was not a challenge for us.

With approvals, customization, et cetera, the deployment took us about 15 or so days.

We have a team of five that is able to handle the deployment and maintenance. We have a two-year maintenance contract lined up.

We pay based on usage, which is quite good for us. We like this licensing model. From the maintenance perspective, we have a contract signed for two years and it has reduced our pay per basis cost.

Real cost savings come with long-term relationships with the company. For four years we have been there. Therefore, the pricing is substantially lower for us.

We are just a customer.

Bot Farm is a cloud solution. We already have A2019, and Bot Farm is one of the products of Automation Anywhere. It's a cloud version we are using and due to it being on the cloud, it is always continuously updated to the latest version.

Bot Farm is for firms that have reached a certain level of maturity. You don't require Bot Farm if you are having applications that are not consuming your licenses. It becomes very useful when you have a use case that has spiked the variation in the load. Regardless, you need to do the math correctly to get the ROI associated with the licensing costs, the value, and the use case intended. 

I'd rate the solution at an eight out of ten.