UiPath Reviews

Most of the automations that we work with are internal to our systems. We are also trying to use it with BPM.

We are reducing people's activities in our organization. For example, there are monthly reports that we have to upload and read, and it was taking a day to do this activity. Then, using UiPath, we can reduce that time to two hours. 

It has helped a lot to minimize our on-prem footprint. This is really important because it minimizes tasks that people work on, including myself.

If you automate with UiPath, you don't have to worry about firing someone who is doing the same process. Instead, you are giving that person more time for analysis for the information that UiPath brings in.

The OCR is something that is really cool. You can work with a lot of systems and use the HTML feature to interact with websites. I really like that it interacts with websites. 

UiPath Portal works great for accessing features.

UiPath provides single sign-on, which is very important, because we don't have to manage a lot of passwords.

It is fast. With UiPath Studio, you can get the passwords and work in it quickly. 

The UiPath Academy is great for learning the solution. It helped us a lot.

We would like to know how to implement the artificial intelligence (AI) feature because we are working on some activities in this area.

The bank knows about UiPath, but not all people consider UiPath something they really trust, which is why there are just two of us working on it full-time. We do teach people about UiPath, but they are not 100 percent involved with it.

The stability is usually really great. However, at this point, we are uploading a new version because the stability is not right. They told us that our version, 18.4.5, is not 100 percent compatible with Orchestrator. Therefore, we don't have the stability that we had before.

The scalability works great for us. It is really fast when we ask for something.

It is really fast at scaling automations. At the beginning, it was slow because we couldn't work the way that we wanted. Now, it scales automation quickly.

We haven't had contact with technical support because UiPath has been working great for us.

This is our first RPA solution.

Before Orchestrator, we worked on an application to manage UiPath because we didn't have Orchestrator two years ago. So, we create our own application to manage UiPath.

It was very easy to set up UiPath the first time. We implemented UiPath with virtual machines, and that didn't affect our costs in a significant way.

The timeframe for setting up a new bot for implementation depends on whether it will be big or small. It might take a day, if it is really easy, or a week.

Getting the idea to have a new bot for the first time is kind of complicated. Once you can explain how it will work or be a solution, then you can just go for it.

I have to be involved in the beginning when implementing a new bot. 

Two people from our bank were involved in the deployment. One person develops the solution and another does the QA.

We worked with a third-party (BDG) to set up UiPath. They were really good.

It has helped a little to reduce our work. Before, we had people working at 6:00 AM because they had to inspect, analyze, or look into the systems for prevention. For example, they had to prevent the systems from going down. Now, with UiPath, that person doesn't have to come early because we get everything in reports from UiPath. So, that person doesn't have to come early anymore. That person now just has to look at the report and see, for example, that UiPath did a fix in the morning. 

The solution really works for its price.

The license cost is the only cost to start a new bot. However, if we want UiPath to do an activity and go through another machine, like Remote Desktop, or application, like Bloomberg, then we have a special license that is an extra cost.

We also evaluated Automation Anywhere, but decided on UiPath, which is friendlier. We also considered that UiPath has its Academy and more documentation.

We are glad UiPath has security because not all the RPA solutions have security.

We are getting into AI now, because we haven't worked with that yet.

Right now, we are 100 percent familiar with Orchestrator.

We didn't have to install a lot of features with this infrastructure. We just download some activities to work with everything, and it works fine. We don't have a lot of infrastructure for using data.

Our first step is getting Orchestrator because we really want to have the entire bank involved in UiPath. The solution is great. It can reduce costs, especially with all that stuff that people do. We have big plans for UiPath going forward.

I would rate this solution as 10 (out of 10).

We use Studio, the Orchestrator, and we have attended and unattended robots.

Our primary use case is automating back-office processes from the corporate side. One example is the automation for ticket closure for some of the customer complaints. We also use it to fill information gaps between systems. Instead of having information run through standard APIs, we have it copied over from one system to another.

We run automations in a virtual environment, and the implementation was pretty easy and quick.

We used the Community Edition before purchasing our license. From the point that we purchased our UiPath license until we had our first robot was approximately one week. We found it to be very easy and very fast. We, as a Contact Center, usually face a lot of problems when we suggest any requirements. When we started with RPA, it took approximately one month for a very complex process to be automated.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a five. It is very easy. You can use the UI, or you can use APIs for the connection. In the end, you can do it.

On a scale of one to five, judging how beneficial it is, I would rate the training a five, for sure. In two or three weeks, an RPA developer can do everything.

In the Contact Center, the key issue is the handling time. RPA has helped us to decrease our time, and eventually, it will help to decrease the headcount.

For one of our processes, it reduced the time it takes from five minutes to somewhere between forty and fifty seconds. That saves a lot of time.

In terms of eliminating human errors, there has not been much difference because we have very strict processes and strict steps for them, so human error was minimal, to begin with. Our success is in the reduction of time to complete them.

The unattended, back-office robots are the most beneficial feature.

The Form Builder for back-end robots needs to be a web portal instead of a full desktop application. 

With respect to the stability, on a scale from one to five, I would rate this solution between three and four. For exception handling, it means that a senior RPA developer has to understand the reasons behind the process. If they have not been exposed to it then it is easier to perform some simple fixes and continue the process.

We have implemented eighteen processes so far, they are they used in several departments. In total, we have approximately four thousand people who are using this solution.

From a scalability point of view, we're not that confident that we can have the robots running twenty-four hours a day with a huge transaction. Being a telecom operator, we have a lot of transactions and the stability of the unattended robots needs some enhancement.

I think that both customer support and technical support are very good. When we have any questions or any issues, we are connected immediately. 

We did not use another RPA solution prior to this one.

We learned about RPA because one of the contractors was working on an RPA PoC at our company, and we were convinced that it could help us a lot. The IT people were invited to see the technology and from there, they decided to implement it with our in-house IT group.

The initial setup of this solution is straightforward. We used the Community Edition and it is very easy to use. 

We performed the implementation on our own.

We realized ROI in approximately six months. Our cost savings come from savings in agents.

From a cost perspective, unattended robots are better. They run twenty-four hours a day and do not require running on a client machine. The attended robots are not as cost-effective.

We did evaluate one other RPA solution before choosing this one. Our main reasons for choosing UiPath were the price and the ease of development. The Community Edition is very useful, and we are easily able to find RPA developers working in UiPath. This is different than with some of the competing products.

My advice for anybody researching this solution is that it is easy to download and it has a big community. A PoC can be done easily, and you can decide from there whether this solution is suitable.

This is a good solution, but the stability of the unattended robots needs to be improved.

I would rate this solution an eight out of ten.

We are using attended and unattended bots. The attended ones are very low profile. We are also using Orchestrator.

Our primary use case for this solution is to automate underwriting processes.

We do not run our automations in a virtual environment, yet.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate it a four. I think that we still struggle sometimes with what kind of a bot we need to use for what kind of work. It may be a lack of understanding on our side. We need to have more clarity on this.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. This is what I have heard from my team members. I did enroll in the training but I didn't make much progress. That said, I have heard good things about it.

From the point that we purchased our UiPath license until we had our first robot was approximately a six-month transition.

In terms of eliminating human errors, I would say that this solution has done so to a certain extent. The stuff that we are automating was quite simple to begin with. As such, there was not a lot of room for error because we have multiple verification steps. I cannot estimate a percentage for the reduction of human error.

I would say that we have a time-savings of approximately fifty percent.

The most valuable feature of this solution is the unattended robots because I can schedule my jobs and it can run on its own. I don't need to pay much attention, except in the case of an exception. That is the only time that I need to deal with it.

We sometimes struggle trying to figure out what kind of a bot we need to use for what kind of work, and it would be nice to have more clarity on this.

With respect to the stability, on a scale from one to five, I would rate this solution a five. It is quite stable.

We have a team of ten developers who work with this solution.

We did not use another RPA solution prior to this one.

We got involved in automation because it makes us more efficient and we save money. These are a few of the important things that we are always looking for.

The implementation of this solution was done in-house.

We have seen ROI because a lot of the work is now automated, so the people who used to do these tasks, the monotonous work, are now doing better things. I would say that we saw ROI in five to six months.

The licensing costs for the unattended bots are a little too expensive. If it were lower then I think we could use it more effectively.

We are excited about the upcoming features with artificial intelligence and document understand capabilities. I think that those are features that would come in quite handy for us.

My advice for anybody considering this solution is to take a look from the grand scale to see which use cases are the prominent ones. Do not look at all of the tiny details because sometimes we can make a use case very complex. The end result is less valuable. Look for the high-level stuff that can be quickly automated, then come down to the final stuff later.

I would rate this solution a ten out of ten.

I have completed an aviation project using this tool. It provided a nearly smooth and seamless performance. The environment was Windows, and we had to automate the Windows-based application. We had to extract data from Excel and put it into this tool and run the tool to get the results. Those results will then be sent to Excel again and will be used for providing better aviation data to the pilots.

UiPath has helped us in automating the manual repetitive stuff and helped accelerate our organization's growth rate by eliminating the stagnant and repetitive manual work. It has brought in an atmosphere of a change of thought process and driven the growth of innovative excellence.
I will definitely recommend this product to all those who are planning to chose an RPA tool but are confused on which to choose. I have worked with many RPA tools, but I found this as a proficient and user-friendly tool.

• Its ease of use
• The user interface is friendly.
• It has self-learning tutorials.
• It provides RPA advance training which provides a smooth path and helps in clearing the certification. 
• All Excel and manual work can be done very smoothly. 
• It provides REFramework which takes care of all the exception handling, and Orchestrator to remotely run the bots as per your convenience. 
• It provides us with UiPath Connect which is a one-stop platform for all your additional needs and for resolving issues.
• Its recording feature is great and looking up to its upcoming new feature: computer vision. 
• This tool is very easy and smooth to work with.

It could have been visually great and colourful. There are functionalities which need to be added to make automation work much easier like executing a test method by which we can test how the activity will work on that particular browser or stuff without running the whole workflow.

For some of the complex activities, visual demonstration of how that activity works should be provided. There are some minor bugs like we could not find the voting option for Outlook mail.

My client is a bank, and we create bots for them. They had processes that their employees used to do manually. They gave them to us to mimic the actions that they did. We automated those processes.

UiPath has increased the net worth of our organization. From UiPath, our organization has gained much more than expected.

UiPath improves the workflow. When we automate the processes, they go into the bank environment where they are used by all the employees from all the regions or states.

UiPath enables us to implement end-to-end automation. It is very easy to build automation using UiPath.

UiPath improves efficiency. The last project I worked on had 1,200 people working on the process. We automated that process, and with automation, 1,200 people have been eliminated directly.

I have not used UiPath's AI functionality but my team has. It makes it easy to automate processes that are more complex or involved.

UiPath has not saved us costs. When we use AI Fabric, we have to implement it additionally to the production environment, and it costs more.

UiPath has reduced human error by about 70%.

UiPath has freed up employees' time. The time saved depends on the process. If a person is doing the same process the whole day and we automate that, he has the whole time for other activities.

The Excel activities are valuable. We can do browser automation through other sites or tools, but for Excel, using tools or options like Selenium or JavaScript is quite complicated because we have to import the file from the JSQL or other things, whereas, in UiPath, we get direct activities. We can directly perform the operations by using the activities. We can directly apply logic to it, and that is how UiPath makes Excel automation easy. This is why I like it.

We have been getting positive outcomes from the UiPath Community. Whenever I have any questions, I go directly to the UiPath Community. Most times, we get the answer from there.

Currently, we have to additionally implement UiPath Fabric. It would be easier if it is already integrated with UiPath rather than having to add it. We have to take the dependencies by searching them. We should be able to go for the default ones.

Its stability also needs improvement.

It has been approximately one and a half years.

The stability needs to be improved. The UiPath selector is consistently failing.

It is a scalable product. We have about 150 users using the solution. It is being used in multiple departments.

Technical support is much needed. It has to be there. 

Our team has used UiPath Academy and UiPath Community. Whenever we get stuck while building the solutions, we most often get a solution from there. It is quite efficient.

Positive

I have used Selenium. In Selenium, we write scripts. We use the Java language for automation. We have to write the code, which makes it more complex, whereas, with UiPath, we can use direct activities, which makes it easier to understand and write the code.

We work in the cloud. Its deployment is easier. For the older versions, it was quite difficult, but with the upgraded version, it is quite easy.

It takes five to ten minutes, depending on how many bots you want to implement. If you want to implement one, you can directly do it in ten minutes.

One person is enough for the deployment. For maintaining the bots, we have a team because the developers and users do not have access to the production environment.

We have seen a 100% ROI.

The price of UiPath is comparatively higher than Selenium. Selenium is a free tool, and UiPath is quite expensive. 

Some organizations make automation costlier than it has to be. They use UiPath, and while selling the products, they make it more costly. It depends on the organization.

Freshers can learn UiPath. They will get knowledge about logic building. 

I would recommend UiPath to others. I would rate UiPath an eight out of ten.

I'm a network engineer at a nuclear power plant, and I oversee multiple crews. I use UiPath to automate the voicemail system, send alerts, and run tests. Our company has about 12,000 employees. 

UiPath has helped to reduce labor costs. 

You can set up processes using macros without basic knowledge of coding.

The hardest part is popularizing UiPath among our employees. 

I have used UiPath for around a year. 

I rate UiPath nine out of 10 for stability. 

UiPath is scalable. 

The South Korean team uses Blue Prism. That's a good solution, but it's too hard to use. 

Deploying UiPath is easy, and I'm teaching my crews. 

It's worth what we pay for it.

The cost isn't important because a good solution isn't cheap. 

I rate UiPath nine out of 10. There are still many other RPA solutions we haven't tried, so I can't say it's the best. 

We use UiPath in the telecommunications and banking sectors to automate various processes, including IT, HR, and financial receipt processing.

We began using UiPath to automate repetitive and rule-based tasks, such as extracting data from documents, inserting data into applications, and sending reports to end users using databases.

UiPath helps implement end-to-end automation by extracting information from documents using the OCR engine and automating procedures by integrating with Salesforce, SAP, and other systems.

The UiPath User Community is extremely helpful.

UiPath has helped to minimize our on-premises footprint.

UiPath Academy courses benefit our developers by providing them with certifications and badges that help them improve their UiPath skills.

We are currently testing the AI and machine learning capabilities of UiPath to make it easier to automate more complex processes.

UiPath has helped reduce the cost of our digital transformation and the number of human errors.

UiPath has helped free up staff time to focus on more valuable work by automating repetitive tasks.

UiPath has multiple valuable features, including stability, automation, and integration with different applications. In addition, the OCR in Document Understanding and the integration with the chatbot are also good.

The data extraction has room for improvement.

AI and machine learning always have room for improvement.

I have been using UiPath for five years.

UiPath is stable.

The technical support is good.

Positive

Compared to other automation tools, UiPath is expensive.

I would rate UiPath eight out of ten.

Building automation using UiPath is moderately difficult.

I recommend UiPath.

We use UiPath for developing and implementing technical applications that provide data solutions.

Building automation with UiPath is straightforward. The API tool enables us to automate tasks such as receiving orders, booking travel, and reading emails with ease.

UiPath enables us to implement end-to-end automation, which is important for me as I frequently travel for business. The solution aids in conducting interviews with customers, handling documentation, and facilitating development.

UiPath saves us around 100 hours per week through automation.

I have completed the UiPath Academy introduction courses. In Brazil, it is the sole method available for us to learn about UiPath.

UiPath saves us approximately $200 per week towards the expenses of digital transformation.

UiPath helps to reduce the number of human errors.

UiPath helps our organization save costs by accelerating our tasks through automation.

UiPath's most valuable feature is Orchestrator.

UiPath's price has room for improvement.

I have been using UiPath for five years.

UiPath is expensive. On a scale of one to ten, with ten being the most expensive, I would rate the price an eight out of ten.

I would rate UiPath a seven out of ten, mainly because of its high cost.