UiPath Reviews

We use all three of the UiPath components which include: Studio, Roboyo, and Orchestrator. There are a bunch of use cases that we explored for the POC (Proof of Concept) to be sure the product fits with our expectations for automation. For example, one use case is reconciliation processes for insurance group retirement and LOB (Law on Occupational Benefits) plans. We built it, tested it, and now that is one of the primary things we use the product for.

This solution has improved the way our organization functions in several ways. It has helped to eliminate human errors. It already saves 20 hours per month for reconciliation and LOB. It helped clients schedule their transactions before the end of the month. All of that automates tasks and makes financial processing faster in the insurance industry. That works out great for us.

The most valuable features provide solutions for when I am using OCR (Optical Character Recognition) technology. It easily integrates with Google OCR, Microsoft OCR, and ABBYY OCR. We are using that integration feature to incorporate OCR mostly for reading scans. To interact with Google OCR, Microsoft OCR, or ABBYY OCR, you don't need to implement a separate component but you can just — in a blink of an eye — integrate those peripheral solutions into the UiPath Studio and use them in your automated processes.

If we can integrate other features that are not part of UiPath, it makes it far more useful in automation. In this case, UiPath is not building out an actual OCR component but they are just giving you an option to incorporate the other OCRs. That is very valuable.

In the next release of the solution, I would like to see the ability to grant permission to users at the job level. Some jobs or processes may need to belong to only one person. Right now, I believe we don't have that feature in UiPath and we can't assign a job to a user. We can give permissions on a tenant level, or we can give permissions on the environment level, but not at the job or process level. 

I would like to see the ability in UiPath to be able to assign each job or each process to a particular user and give that user some specific access and privilege. For example, maybe they should only be able to run or stop a particular job or a particular process, but they can not do anything else. That makes a lot of sense because all users may not need to see all the processes in Orchestrator in one instance or have access to administrative features. The same goes for a tenant or even in an environment. If UiPath can make that happen at the user-level or process-level for a robot, that helps a lot to enable customized bots.

On a scale from one to five where five is the best and one the worst, I would rate the stability of the UiPath platform at a four-out-of-five. The stability is a four instead of a five because the stability is not completely dependent on only UiPath. Underlying obligations play a part too. Sometimes when I am writing applications, I'm not up on how to handle every exception. That is not possible because a developer does not know all the scenarios an application can become involved with. In that scenario, the product can lag. But, otherwise, it is really a very good solution that is dependable and stable.

Approximately five people in our organization are involved in our automation program working in the CoE (Center of Excellence). There are four developers and there are 200 users including business users. So, you can say there are around 250 people currently involved in this. I don't think scalability is an issue.

We did have the opportunity to use UiPath Academy RPA training. On a scale from one to five where five is the most beneficial, I would rate the training as a four-out-of-five. It is good for basic understanding. We have usually had UiPath foundation training for all of our developers. Really, I think you can say that we have not put fully utilized it.

Other parts of technical support we have only used very minimally. For example, we have not used premium support or licensed support levels. Sometimes we called customer support on tickets to integrate with mainframe obligations the first time or some more involved issues. But that type of situation was unusual. We have barely used the customer support because most of the information is available in Academy, in the portals, or the user forums. A few times when we left a ticket, it was not even necessary for us to get back to technical support because we resolved the issue on our own.

We knew that we had an opportunity to invest in a new solution when we heard about RPA three years back. UiPath and WorkFusion came to us at the same time and saying, "We have a solution to improve your work processes."

We spent some time evaluating which tool was right for us by doing a study inside our organization to determine how much manual work could be automated. With some analysis, we found out that there is a huge opportunity for implementing this type of RPA solution in AXA (global insurance, not an acronym) as it is a large organization with a lot of repeated processes.

Because there was a lot of manual work, people in our organization had to work for more hours at times to properly complete a job. Sometimes they had to stay overnight and work additional hours on weekends to complete processing on time. To avoid that we requested that operations consider our proposal for automation.

We showed operations where we could automate repeatable and mundane tasks. The response was very positive and they realized we need to implement these solutions to help us to buy some time for employees to properly do their work and reduce labor intensity.

Our previous solution was either no solution at all except for manual labor or some experience we had with one tool called OpenSpan. OpenSpan did not have a proper management console and was difficult to use so it mostly remained unimplemented. When we introduced the potential solution for seriously pursuing RPA to reducing the workload, that is when we started looking at UiPath.

The set up for the product is straightforward. It is seamless. In fact, you just need to know the server where it will reside. There is material available in UiPath guides and the UiPath forum where you can just follow along step-by-step and install your Orchestrator. So it is very straightforward. 

From the time we purchased the UiPath license until we had our first robot in production is not exactly clear. We had developed a POC, which was ready to be put into production and then we bought a license. After we bought the license, we just put it into production and it had already been built.

We did the entire implementation ourselves with some contact with UiPath.

We are not yet really realizing a return on investment as our deployment continues to be in progress. How much money we have saved is what we are hoping to eventually count in the ROI. In terms of the calculations that we started last year, we asked that the KPI (Key Performance Indicator) points look at time-saving and not really the dollar saving. The time saving you can say approximately 20 hours per month, which we have achieved consistently up until now. We have achieved something but we are expecting that to grow a lot.

The solution has also helped to eliminate human errors. I cannot say exactly what that percentage is —  say even 20% or something like that. There are a couple of instances before we automated the reconciliation process last month — before we actually put the bot into production — where people were getting the wrong details by mistake. I would say we have reduced the human error because those situations are being handled by the bot and they will not be repeated now. 

We license the product on a yearly basis and it costs us around $80,000. We are a very large organization. We have unattended bots and there is a pricing structure surrounding that but I'm not involved in the licensing terms.

What made us choose UiPath to automate our processes was evaluating the capabilities of competition and deciding on the best solution for us. We compared UiPath, WorkFusion and other products — and even other types of tools — in terms of infrastructure, setup, how easily it could be scaled, etcetera. UiPath stood out a little as it had the capability to invoke virtual machines automatically without any human intervention. A lot of other tools didn't have that capability at that point. But the time we had to come down to a decision, UiPath had features that were not available in any of the other tools. With other research into the company and product, we saw that UiPath listened to the customers' needs and was often upgrading. Now all the competition has seen them as the leader and they have tried to incorporate features UiPath had already deployed.

That initial difference we saw between UiPath and the other tools we compared was the reason we took this direction. We believed UiPath and we decided that this was our theater for RPA. Now, if we see some enhancements that need to be made in the product, we just communicate to UiPath and we know they will look at the idea and maybe implement it. UiPath has the capability of adding features immediately. They are releasing around 10 or more versions in a year with important new features. 

We do use a virtual environment such as Citrix when it is appropriate and that works out pretty well. The obvious advantage is there is no dependency on a physical machine being available and they are available 24/7 from anywhere. I am actually comfortable developing anything and everything in Citrix via virtual machines.

On a scale from one to five where one is very difficult and five is very easy, I would rate the ease-of-use of the platform as a five. Ease of use is one other thing that I like a lot about UiPath.

Going a step further, on a scale from one to ten, I would rate this product overall as a ten compared to other RPA solutions. In comparison to its nearest competitor — Blue Prism — UiPath is way ahead in terms of providing features, giving customer support, ease of use, ease of access to our personal history, and surely in the development of robots.

Everybody can understand easily what exactly the product is doing and can become familiar with it quickly. With other competitors, there is a huge infrastructure to set up. Some of the products make it so each bot needs a control room. Those products are not centralized, which makes them more confusing to use.

People have to manage on their own how they are going to build all their RPA management solutions. When you are using UiPath, you just get Orchestrator instead of multiple robots and control panels, then you just scale whenever you want.

I definitely recommend UiPath for simplicity and ease-of-use. If somebody was getting an RPA solution, the advice I would give them is to definitely go for it. Setting up RPAs eliminates human error in tasks and lightens workloads for menial jobs. This lets people focus on more innovative work and it can lead to further integration. What I would think is the natural path for UiPath is that it can integrate the AI in the future. Right now, people think that this is already cognitive or AI integrated, but there is a very long way to go in the future for it to become truly like artificial intelligence.

So, what I am saying is I would take it as a first step towards the AI. I would definitely recommend people use it so that in future when AI comes in, you can just grab an AI solution from UiPath and improve your implementations further.

We are an EdTech company. We are working on a solution that allows us to customize our offering by reviewing the intelligence that we have about a person. For example, based on how a person learns, we can customize our offering. If a person is more tactile, we can give more quizzes and other things so that the person uses his or her hands to interact. It is a work in progress. We are still implementing it. It is a lot of work.

It is very easy to build automations with UiPath. It is completely visual. You can easily drag and drop and create a process. It is fairly easy. People who are not technical are also able to work very well. In education, we have to work with educators apart from techies. In EdTech, we have people who understand learning, so we are able to deploy them for this, and we are able to build a better solution. Techies will not be able to build it because they are not educators. We have educators with over 20 years of experience. If we train them to be techies, they will take 10 years, but if we ask techies to become educators, they might take 100 years. With UiPath, we are able to use the skills of our education specialists along with IT and other departments that are needed.

UiPath enables us to implement end-to-end automation. We can use AWS, Azure, or any other product. It is easy for us to integrate UiPath with our current offering. It is very easy to implement and go live.

We are working on using their AI functionality. We are trying to use the user data that we have to understand about a person and deliver a solution accordingly. For example, right now, in education, one size fits all, so there is one program that is directed at a hundred people. If you see Coursera, they have a completion ratio of around 3%. What we have observed is that when we use a solution like UiPath, for the test cases, the completion ratio is very good. It is close to 80%, which is very good. It is going in the right direction.

As far as our business is concerned, if a person does not complete the program, we do not get paid. There is a revenue leakage. By using UiPath, we are seeing a higher completion ratio. For example, if a person enrolls in a university and completes the program, he will pay up for four years. If he drops out in two months and finds that we are not useful, then obviously, we would lose the revenue for three years and ten months. It is helping us reduce wastage. It is helping us increase our revenues with minimal cost addition. The pricing of UiPath is negligible compared to the benefits. We can recover its monthly cost from the revenue that we get from just one student. We have close to 5,000 students. It is very good for us.

In terms of reduction in human error, when you are developing a program, initially, you will discover many errors that you have been missing out on, so human error will be reduced to minimal if your protocol is right. If you make a basic flaw in your design, then it is different, but otherwise, human error is more or less eliminated. There is close to 30% reduction in human error. Once we scale up, that percentage will go up and efficiency will go up.

We plan to automate all manual processes. Some of them are already automated using UiPath, some of them are in progress, and some of them will be automated in the future, but we will save a lot of human time. Human resources are very costly these days. It takes years and years of training for them to add to our business. UiPath has been good for a lot of things that we thought were not possible. We are able to do them after using UiPath. They are able to help us in finance. They are able to help us in HR. They are able to help us with contact centers. It is very good.

One thing that we love about UiPath is that the pricing is very good. While we are developing, they have a free option. The Pro option is for just $420. Once we go live, we do not mind paying, so the price point is very good.

The platform is robust. Particularly in process mining and task mining areas, it is very good. We are working on integrating it with our solution, and the API is fairly easy for us to work with. 

UiPath is very good. They have OpenAI integration. It is a free integration. They have something for extracting data. They have something for copying text from an image. These are all free and ready to be used in automation.

They have a UiPath community. They have a lot of activities to engage people, and the community is growing. It is not as wide as some of the older products such as PHP or Java, but for AI, it is a very good community. They have DevCons that are very popular as well. Their community is all over the world. They have developers in India. They have developers in the Philippines. It is very good.

We would like to see small modules that we can pick and use. Currently, we have to implement a lot of things. The platform is very good, but we would love to have some more templates that we can quickly implement. Other than that, it is very good. We do not require anything else. We are very happy with UiPath. It has been an eye-opener for us. We have discovered things that we thought were not possible earlier.

I have been using UiPath for 3 years.

It is completely stable. I have not had a single downtime in our development journey and usage. It is a very stable solution. I would rate it a ten out of ten in terms of stability.

It is easily scalable because of the way it is implemented. You start with a small license, and as your needs grow, you can keep taking more resources. UiPath also makes money as you grow. They scale it up for us, so we do not have to worry much about the product as such. It is quite scalable.

We have UiPath in multiple departments. We are an EdTech company, and we are using UiPath in the product department and the finance department. We are integrating some elements of HR. Customer support is the most vital component for us because you save a lot of manhours in customer support. Our tech teams are based out of India and the Philippines.

At the implementation stage, we have only 14 developers, but once implemented, it will be used for at least 5,000 customers.

They have been very prompt and helpful. They pay attention to detail. They are available. Their support is a class apart. There are no issues. I would rate them a ten out of ten.

Positive

We tried several products but did not implement any RPA. We tried Automation Anywhere and Microsoft Power Automate. We found UiPath to be the best in terms of features, community, and support. Some of the things that we tried did not work well for us.

UiPath is a class apart. Automation Anywhere is a standard solution. Overall, Automation Anywhere is very easy. It does not have a community. It does not have all the features. You are mostly platform-dependent when you are using Automation Anywhere, whereas UiPath has a community. You do not need UiPath to help you with everything. There is a lot of talent available. UiPath Academy is good. A lot of people get trained in UiPath. Pricing-wise also, UiPath is cheaper. It is also easy to implement. Automation Anywhere helps to get started very quickly, but we needed customization for our business. This is something where UiPath was better.

It is deployed on the cloud. Everything is on the cloud. UiPath has helped to minimize our on-prem footprint. Ever since COVID, everyone has been moving to a phase where they can be completely remote. We have been transitioning from on-premises for the last few years, and this is a step in the right direction. Of course, we need to do more, but it is going in the right direction.

The number of people required depends on what you are using it for. We are using it for our own custom solution. We have 14 resources working on UiPath for our solution, but a small enterprise does not need that many people. A smaller team is good enough to implement because it has everything. For example, if you want to integrate Salesforce, you can easily integrate Salesforce. You can go and click on the marketplace and just use Salesforce.

It does not require any maintenance from our side. Everything is automatically maintained. The platform is continuously upgraded in the backend. We do not need much maintenance. It is a cloud solution, and everything is maintained at the backend. You do not need any intervention.

It is super cheap for the value you get. Their free version is good enough to implement. When you are building a solution, it takes months of effort, and sometimes, it takes years. Its free version is good enough for you to test out everything, so when you are developing, you do not need to pay. After that, there is a Pro version at $420. It is reasonable for the value it is offering. Their basic support is also very good, which comes with the Pro version. 

The Enterprise license is suitable when you need a hundred automation licenses. It is also reasonable. They give good pricing when you negotiate.

I would highly recommend UiPath. You can definitely go for it. I would suggest being a little bit patient while implementing this solution initially because it can be overwhelming. There are so many options.

UiPath as a company is also good. They respond quickly. It has been a pleasure so far. Our product is not yet live. We are still working on it. It is a very big solution for us, and it will be a game changer for our business.

Overall, I would rate UiPath a ten out of ten.

We use the tool for mostly attended and unattended automation. 

UiPath's most valuable features are the UI library and object repository, which speed up the development. 

The tool needs to have more documentation and change logs. Minor upgrades break a few things. 

I have been using the product for four years. 

UiPath is stable. 

The solution is very scalable. 

We get good support with the help of an account manager who escalates issues. We had to escalate issues only a few times. 

Positive

We used Pega RPA and Microsoft Power Automate. We have high-volume workloads that are not feasible with Power Automate. We also have a lot of legacy applications that don't work well with product license applications. Pega RPA was not very user-friendly. 

The tool's deployment is easy. We use Jenkins in the pipeline. We are still on-prem and most of our processes are deployed through the Orchestrator to the dev instance. 

Our partner helped us with the deployment. We were also knowledgeable on the technical side. 

We have saved 10 million dollars so far. 

The solution's pricing is fair. 

We use UiPath to save costs and man hours. 

The tool has helped us improve accuracy on compliance and regulatory policies. The bots make it more consistent. We can document everything, which makes auditing easier. 

Some of our processes were manual. Now, five robots do it. We have not hired anybody despite the workload being increased. 

We used Task Capture for some documentation. 

I rate it a ten out of ten. 

We utilize UiPath to automate manual and repetitive tasks that range from simple Excel manipulations to web scraping. We have several use cases related to refinancing, such as handling accounts payable for invoice processing, remittances, and accounts receivable, among others. In addition to that, UiPath enables us to develop public-facing applications that are integrated with automation. This automation is triggered automatically whenever there are user interactions or events, resulting in numerous use cases. For instance, if the requested data is not already available in the document, we can obtain input from customers using UiPath. 

Furthermore, we employ UiPath products for automatic invoice processing. When we receive invoices in PDF format, we digitize them using our own OCR engine. Subsequently, this information can be utilized to save data into systems like SAP. We extensively automate ERP systems, including SAP, Oracle, and NetSuite.

We also use UiPath for application testing. We have built several test cases for suppression, user acceptance, and so on, which can be scheduled to run or run on demand.

UiPath has a small learning curve because we leverage Microsoft technologies, benefiting greatly from UiPath's integration with the Windows Workflow Foundation. Moreover, there is also a version tailored for business users. Personally, I have a tech background, but we have received feedback from other users who find it very easy to create simple automation. However, for more complex automation, some experience or training might be necessary. Fortunately, UiPath offers completely free on-demand training through their Academy. Once someone completes the training, they will be able to proficiently build automation.

We employ our bots to collect data on emissions, consumption, and byproducts. We do not have any byproducts. Recently, we published a report detailing where and how we have achieved our sustainability goal.   

With UiPath, we have been able to achieve a 100 percent scale-up in the finance department without increasing the headcount. Therefore, it has played a crucial role in generating significant capacity and managing all the challenging tasks efficiently.

Being able to implement end-to-end automation using UiPath is crucial. We have use cases where human involvement is necessary. For instance, if there are invoices exceeding ten thousand dollars, we require approval. Therefore, UiPath allows us to pause automation until we receive those approvals from various stakeholders. Once the human input is provided, the bot proceeds with the remaining steps. It is highly reliable and adaptable to changes in the sales flow. We have utilized UiPath for automation without the need for additional staff.

Whenever there are new features or releases that lack detailed information, we can use UiPath's User Community to discuss the posted topics. For example, we can seek assistance in understanding how to make the most of a specific feature or determine the necessary settings for our properties to leverage those features effectively. Additionally, training resources for these products are available within the community. Webinars are frequently hosted in the UiPath User Community, which we also utilize to gain insights into the functionality of the product and its application in solving various use cases.

There are several areas in which UiPath has benefited our organization. We gain process intelligence and revenue intelligence. Additionally, we are able to perform virtual investment analysis using automation. UiPath enables us to free up a significant amount of capacity for more meaningful work.

UiPath has helped minimize our on-premises footprint. It's all about the SaaS cloud-based offerings. Therefore, several products are currently available quickly, specifically on the cloud. Essentially, we only utilize virtual machines for the robot itself, which execute alongside all the other services. Everything is hosted in the cloud.

The biggest benefit of using UiPath's Academy is that it offers various labs and exercises, which greatly assist us in utilizing and improving our understanding of the tool. Additionally, the Academy provides certifications that can help individuals become certified in the technology. These are some of the benefits offered by the Academy.

For most of the document understanding process, we utilize machine learning models that are hosted in the UiPath AI center. Additionally, AI is integrated into the process mining and task mining products we employ, which help us discover new automation ideas and opportunities by analyzing information flow within data from ERP systems, among others. Moreover, UiPath recently introduced communications mining, which utilizes a large language model. This enables us to examine emails and other modes of communication to gain insights into the processes and occurrences. There are numerous concealed insights pertaining to both the processes themselves and the sentiments of customers, all of which can be obtained through these AI tools.

UiPath AI has simplified the automation of more complex processes because it doesn't require machine learning, knowledge, or technical ability. It is a very simplified, no-code, local platform. This has greatly helped us build solutions that previously required extensive coding, saving us a significant amount of time during implementation.

UiPath helps to accelerate and reduce the cost of our digital transformation.

UiPath has helped reduce human errors. There are several errors that occur when working with financial data, such as missed dates and miscalculations. However, the bots prevent such mistakes from happening.

UiPath has generated sufficient capacity, allowing us to avoid hiring additional personnel for our department. Despite an increase in workload, the bots are capable of handling it.

UiPath has helped our organization save costs.

The AI feature has enabled us to automate more processes overall.

It would be beneficial to have the capability to track defects during the regression testing of applications.  

I have been using UiPath for six and a half years.

I have used Automation Anywhere, Blue Prism, and Power Plus Automation, but UiPath is more user-friendly.

The price is reasonable. UiPath is priced for the market and is even better considering the value it brings.

I rate UiPath a ten out of ten.

We have implemented UiPath across multiple departments, including HR and Finance.

No maintenance is required.

I have worked on a number of use cases, and one of them that I can discuss was used in a contact center environment. This is a project that we had done for an automotive insurance company, and it had to do with incident management. Our contact center received the first notice of loss (FNOL) from incidents, such as an accident.

When an accident occurs, they raise a ticket to our customer service representative. This can either be done using a chatbot, which is integrated with our ServiceNow platform, or they can call the customer service representative. In the latter case, the customer service representative will pick up the call and get the details. This includes adding their insurance ID and a couple of other fields, and that is integrated into our system.

Our system was acting as an intermediate between their existing platform and ServiceNow. Part of the system included a database, where they were checking to see if the insurance amount the claimant is asking for is above the limit. There were other similar business rules, as well, which the bot was responsible for checking. Based on the result of these checks, the claim was automatically approved, and then a corresponding ticket was raised in ServiceNow.

There was also a manual process, where there was a person who would go to the site where the actual accident took place. They do their analysis, and then they create a review report, and that report would automatically be handled by an attended robot. The robot would take the detail from the agent and based on the review, fetch certain details like the approved amount.

The bot is responsible for sending other information to ServiceNow, including, for example, details about damage to the vehicle. If there are scratches on the front or scratches on the back, then these details are all posted to ServiceNow. At that point, ServiceNow has a workflow that is initiated.

The workflow uses the information taken by the representative and moves from the review stage to agent verification, and then to a mainframe. The system running on the mainframe is responsible for generating checks, according to the amount that is approved, and then mailing them to the claimant at the address they have on file.

In our FNOL process for the insurance company, we use unattended robots quite extensively for both chatbots and IVR. We use the AI capabilities for language understanding and based on the user sentiment, it will trigger the unattended bot. If instead, they want to speak with a representative then it will trigger the IVR process.

In terms of the robots prioritizing and correctly routing a transfer to agents when necessary, it is a work in progress. From a priority perspective, if you talk about chatbots, let's suppose a customer sale is highly urgent, the AI model can use language understanding to determine an urgent message and in turn, create an urgent ticket. It is something that we can do but it is not 100% accurate. I would say it's 80% of the way there, because of the different types of sentiment that people express during interactions. As an example, when a customer says "I need to have this resolved as soon as possible", there are a number of different things that can happen. According to our business rules, when somebody says ASAP, it should be treated as a high priority, but 20% of the time, this does not work. Overall, at this point, the AI models and machine learning models are not very accurate.

The robot-enabled self-service channels have definitely increased the resolution of issues through self-service. Prior to using the robots, 90% of the calls would need to be addressed by a representative. Since implementing the bot strategy, only 10% have to be handled by a human. We have used UiPath Apps for this and also created some web pages, but those are just to help the bots. Definitely, self-service is one use case that has really benefited because of UiPath.

The Studio is where the development takes place and the interface is very user-friendly. You have the ability to drag and drop components, and this is part of why I think that Studio is the best feature in UiPath. The next best feature is Orchestrator.

The Orchestrator is quite good because it is a one-stop shop where you can run robots after creating them using Studio. You can create queues, monitor the bots, and if there are any issues then you can debug them at the Orchestrator level.

UiPath has a low-code feature called Studio X, which is specifically for business users. They can just drag and drop activities like reading emails, retrieving email attachments, reading data from Excel, and posting data from different sources into different platforms. It is a very good platform for business users who don't know much about coding. It is customizable in the sense that business users can have the system follow a set of simple steps, although it won't do complex things.

UiPath Insights is a feature that has everything from a tracking perspective, which tells you how the bots are working at the production level. It provides statistics about the live environment including how many processes are being run, how much time the bots are being used, and the productivity in general. There is more analytics available from data services, tests, and the AI center. All of these features really help when it comes to analyzing the data, not only from a development perspective, like tracking data on how much a robot is at a log level, but also from the end-user level in a production environment. Reporting on productivity in a single day will show how much time the bot was run, for example, 80% in terms of time or 90% utilization, and other such details.

The UiPath App feature is something that we can use to create simple apps, and these can act as integrators. Suppose there is a process that uses 10 different screens, we can create an app that will be integrated with all of them. As a developer, all 10 screens are used in my workflow, and instead of going to each of them, I can create an app that uses all of the fields that are relevant to me on each of the screens. 

The speed at which we were able to create automations for our contact center was very good. One of the reasons that we choose UiPath over other tools, such as Automation Anywhere and Blue Prism, is the ease of development. When it came to setting up the contact center, it was only the connection between different platforms that took time. The bot creation and the workflow creation were quite easy. It took approximately one and a half months to create the whole automation for the contact center, which is quite good.

The AI and machine learning capabilities need to be improved.

The task mining and process capture methods are capabilities that we use, but they sometimes miss part of the task. For example, let's say that for one of my tasks, I need to open my email 400 times a day. This is something that we can automate but for some reason, probably because it is related to email, it is not accurately evaluated. In this regard, the process mining could be improved and lead to better results.

The built-in OCR is only 60% to 70% correct if you're analyzing a PDF that has images in it, so this is an area that can be improved. Different companies use their own OCRs; Google has one, and Microsoft has one. The UiPath one requires that we use a validation step between workflows in order to improve the accuracy.

I had been using UiPath for three years, up until a few months ago when I joined a new organization.

From what I have seen, the biggest factor for availability is the strength of the internet connection. Whether the deployment is on-premises or cloud-based, they both are the same in terms of stability. I have not seen any deviation between deployment types.

Scalability is not an issue. In my previous company, we started with 10 machines and then after one year, we had 85 machines. There were no issues and the implementation was not a headache.

The technical support is very responsive.

Prior to working with UiPath, I was an automation expert with Selenium for web testing. I was not able to fully automate a website because if there was an image that was used as a security check, where the person had to click an image to get through to the next page, I wasn't able to do it.

However, when I switched to UiPath, it was pathbreaking for me. I was able to accomplish what I couldn't do with Selenium and since that time, we have deployed more than 100 production bots.

The installation is pretty straightforward. We usually get issues when we upgrade to a new version but I think that is a different discussion. Strictly from an installation perspective, we have not had many issues. We had no major issues and when we contacted technical support, the team was quite responsive.

The length of time required for deployment is about half an hour per machine. However, if you have 100 machines then you can do them concurrently.

For some of our projects, we used an on-premises deployment, whereas for others, we used Orchestrator and they were cloud-based. Cloud-based deployment gives us the ability to run bots from anywhere, including outside of our network.

Our clients with the contact center did not see a very large ROI in the first year, although that was because of the consultancy costs that we charged to implement the system. From the second year, onwards, they definitely saw a very good ROI.

We had different metrics to calculate RPA implementation ROI. The first is productivity, which increased by more than 60%. If I recall correctly, their investment was between $110,000 and $200,000 after the first year. I don't remember the exact numbers but it was a huge improvement.

It was not just productivity, but also other things like a reduced error rate. The quality of the processes improved quite drastically.

We analyzed and compared the costs of RPA from different vendors and we found that UiPath was the most cost-effective in the long term. An unattended robot costs approximately $8,500 annually. 

We evaluated other RPA tools including Automation Anywhere and Blue Prism. One of the reasons that we chose UiPath is its ease of development.

In terms of ROI, we found that UiPath was the best when you consider the long term.

The length of time it takes to develop and deploy bots for a process depends on its size and complexity. We categorize processes as simple, medium, and complex. Based on how they are classified, we estimate the deployment lifecycle from one month to two months.

My advice for anybody who is planning to implement RPA is to begin by doing research on the vendors. You need to speak with each vendor and start planning, but don't think about clients at that moment. Rather, think about yourself. Consider that you want to implement internal automation, and consider the ROI you would garner during the first year or during the second year.

Once you choose a vendor, as we did when we chose UiPath, you need to make sure that at the very start of your project, it begins with low-hanging fruit. Don't start with all of the complex processes; start with some simple processes. That's why we have divided ours into three sets of processes. Then, don't think that you will achieve a hundred percent automation because that will never be the case. My thinking is that if you achieve more than 70% automation, that is a very good target. Keep your expectations clear.

Another thing to make sure of is that you secure your bot at the workflow level. UiPath provides very good security features that you can use, such as assigning permissions for who can access your workflow. Also in terms of security, be sure that you have all of the required certifications.

Once you have implemented some basic processes and you are getting good results, hyper-automation is something I suggest. Start expanding it to different technologies, such as AI. Also, engage all of your employees as much as possible.

Start with the community version of the software. Although this review is based on the licensed version, the community edition is free and you can create your bots for free. I always say that even one hour saved because of automation will yield a good return annually, and your results will be very quick.

If you keep all of these things in mind then RPA will be fruitful for you.

I would rate this solution a nine out of ten.

Currently, our automation work with UiPath primarily revolves around financial processes, such as accounts receivable work and tax deduction management. We are exploring generative AI, but have not developed any AI use cases for UiPath yet. We prioritize our automation use cases based on RoI and process complexity.

With UiPath, we have saved time and cut costs. For example, one process previously took several people six or seven hours, but we've reduced it to a four-minute process. This allows us to shift our teams to more analytical, value-added work instead of repetitive transactional tasks. 

UiPath's learning modules have been a massive help in training our employees. The Orchestrator also helps us schedule, deploy, and monitor jobs.

We've engaged employees through meetings at the enterprise and department levels. Our manager has quarterly meetings with employees in different areas of the business to get them up to speed on what's happening in automation.

UiPath could have more robust, built-in auditing and logging. Currently, you need to build log messages into your automation to capture what's happening. 

I have been using UiPath for three years.

We haven't really had any trouble with stability. It has been very well.

I was able to scale up very easily, as we recently stood up eight more robots. Setting everything up and gaining access took about five days, and we received a lot of support from UiPath for licensing and key management.

I rate UiPath support eight out of 10. We have had a good experience. Our technical account manager is very responsive, and the ticketing system that UiPath uses is quite successful. We received answers to our questions promptly, and overall, it has been a positive experience.

Positive

We previously used a competitor, Automation Anywhere.

We weren't heavily involved with deploying UiPath, but it seemed straightforward.

UiPath professional services managed the deployment and helped us convert about 40 automations. 

We've saved thousands of hours using UiPath and freed employees to focus on more value-added work.

I rate UiPath eight out of 10. 

We're a food ingredient distribution company that receives documents on ingredients' nutrition, allergens, microbial testing, etc.  We primarily use UiPath to process these documents. It was our proof of concept for using the system initially, and we'll expand it to process invoices and other related use cases.

We operate using an enterprise operating system. It's not a technological thing. It's how you determine project priorities. Soon, we'll set up process mining. Then, the IT team and technology group will decide what we do. Right now, the business units effectively vote on the next quarter's priorities. 

We're a high-tenure organization. The average tenure is 15 years, so we want to avoid growing our headcount. We're continuously growing by 10 to 15 percent annually, so we've had to add enough staff to process the documents. Our primary concern was to stop the increase in staff. Even after we added staff, we were falling behind because they were much slower at processing those documents. 

We get documents from our suppliers and, as a distributor, send them to our customers. If the supplier hasn't sent them, we need to hound them. We were falling behind on our backlog of 250,000 documents. UiPath enabled us to avoid adding more employees. Automation was the way to go. We haven't added any more headcount, and the backlog is going down, but it isn't as much as we had hoped.

The automation has allowed us to provide customers with better-quality documents faster. It has also given employees more time to locate the documents we don't have, freeing them from mundane tasks. It's freed them from the work of typing data on a form into an ERP system. 

We are talking about using it for our environmental and social governance initiatives. We're considering bringing together some of those pieces through automation to track our energy usage or what we've spent on some of the other bits and pieces and have a better ESG profile.

I find the intelligent document processing features extremely interesting. They're fun and represent an actual practical use of AI. There are so many impractical ways to use AI, but this offers a tangible ROI, and you can see its benefits directly. 

There are small issues, such as the Action Center not auto-refreshing. The user has to keep clicking "refresh." It's minor, but if you're waiting for something in your queue, you don't want to sit there and keep clicking. Logging could be improved, and there are a few connectors where I would like to see enhancements, but nothing major.

We started using UiPath in January of this year, so we've used it for less than a year.

The solution is solid, and I've had no issues with stability. The one issue encountered was due to a version change, where the changes in that version were unexpected.

The solution is great for scalability, and we can always add more bots as needed. We haven’t found it limiting at all.

Our experience with UiPath support has been mixed. The responses take a little long, which isn't bad when we only need a question answered. However, our system went down twice, and it took four to eight hours to get our first response from support. If I submit a ticket at 2 pm, I might not get a response until 10 pm. That's still relatively soon, but I might not be paying attention that late at night or be available to respond. 

Positive

We did not use a different solution for document processing before this.

The initial setup was pretty easy and straightforward. It didn’t take much time to get UiPath running.

We implemented the solution in-house ourselves. We do have a partner, Empower dot AI, which we plan to work with on future projects.

We are probably just starting to see a positive dollar ROI versus what we spent implementing UiPath. We only started this in January, and it was fully implemented by late June or early July. Hence, we are still in the infancy phase of experiencing ROI.

UiPath's pricing is reasonable. The model of charging per AI unit makes sense, and the licensing for Action Center and other parts is good. The cost does not seem excessive.

We are considering implementing AI as we are a healthcare staffing company in the education sector. Our use case focuses on processing a large number of emails and resumes. We aim to mine resumes to determine which are best for rapid and successful placements. On the communication side, we wish to perform sentiment analysis to assess how well our salespeople respond to clients.

We want to mine, structure, and analyze data using data science methods. We also hope to use generative AI and large language models to perform some of the data analysis, saving us lots of time. My company tripled in size in the last three years, so we have a lot more people, but the backend operations haven't grown at the same pace as the number of salespeople. 

Automation helps us with operational and analytical work because we lack enough talent for that. By using AI, we can do the same amount of work without hiring more people, so we save money and improve productivity. Generative AI is part of our discussion. We had to decide whether to develop our own model or use existing software like UiPath to get things done faster and easier.

We have about 15,000 consultants working for us during the school year, and to fill those positions, we may need to interview five times that many. A lot of them might drop out by the time school starts. Using UiPath and AI, we can speed up processing and onboarding because that might be why people quit. They might leave for another job if we don't onboard them fast enough. We can save more candidates and prevent revenue loss from a potential placement by making the processing time faster.

After implementing UiPath, we automated many manual tasks. We save a lot of time, and those people who used to do manual work are doing more knowledge work. A lot of them now see what bots can do, so they're more open to the idea of developing bots. That set the stage for them to trust AI-powered bots in the future. 

The most valuable featire is the whole automation suite that helps develop automation processes. In the future, we might further explore Communications Mining and Process Mining. 

There's a push for cloud-based operations, but I prefer to develop things on the desktop. I'd appreciate the ability to develop things on the desktop and roll them out concurrently on the cloud. 

My company has used UiPath for about two years, but I've used it for about a year.

UiPath is very stable.

UiPath has kept up with our growth. However, there's a limitation with licensing.

I previously used Blue Prism in a different company. However, for the current company, they had no prior automation solution.

Our IT support company, Coretelligence's parent company, helped with the initial implementation. There were renewal delays prompting a desire to work directly with UiPath.

From a cost-saving perspective, we are seeing a lot of returns, including internal staffing cost savings and HR bot efficiencies.

UiPath's licensing could be cheaper and more dynamic. The licensing can sometimes feel high, especially for smaller companies, but generally, the pricing is reasonable when considering the time saved and corresponding costs.

I wasn't the decision maker, but my CFO considered industry leaders and attended the Forward Conference. He was impressed and chose UiPath. One thing that he liked was that it was easy to learn and use. 

I rate UiPath eight out of 10. I enjoy working with it, and it seems to have everything we need. They're adding new features at a reasonable rate while not deprecating old stuff too fast. It's a smooth transition from classic to modern activities.