UiPath Platform Reviews

We use it for the automation of internal HR processes in our company.

It helps with the ease of implementing new logic from business requirements, which very rapidly change.

UiPath has also helped because fewer people are engaged in the processes we automate, and they can do more important things. It saves our staff time, on the order of 80 percent. In terms of employee satisfaction, I don't really know how they feel, because they are not in my department, but I believe that when you don't have to do such routine, repetitive work, you can have a coffee and come up with ideas on how to improve the automations. That is, by far, better than clicking and typing thousands of forms.

Also, there is less chance of a person making a mistake. If a given operation would take one person, for example, two days to do, the automation can do it in one hour, or even 30 minutes. It is very useful. We saw benefits with the first automation that was implemented, because it started to work and free people from routine work, within the first second of the automation working.

We have a lot of automations that involve filling forms on the internet and creating events in a calendar. There are a lot of fields to fill out. When creating these meetings, you have to add a description and pick the actual time. All this stuff should be done precisely, because if there is a mistake, somebody will not come to this meeting, or the information will not be applicable. Now the number of errors is zero because robots don't make mistakes.

We also don't need to involve the IT department, and we now have 15 automations. The group of people who implement it do the maintenance as well. We don't need IT and, actually, everything works fine without any maintenance. The problems come when there are updates, but the time needed for maintenance is very small.

Because we don't need to create virtual machines to install the solution on-premises, the cost is as little as it can be. Of course, we have to create several virtual machines for actual clicking, because the robot works the way a human does. But it has definitely helped with our on-prem footprint because we don't have to install the core of the system on-premises. I know, from my experience, that those kinds of core components take a lot of hardware resources. They would not require just one virtual machine; it would be a bunch of virtual machines. It is definitely very efficient to use the cloud solution from UiPath.

UiPath reduces costs because it reduces the time it takes to create automations. You don't have to write the actual code. You just build automations with higher levels of abstraction and you don't have to worry about what is done behind the curtains.

The best part is the way UiPath provides the ability to automate everything, including the architecture and Orchestrator. The interfaces are very user-friendly and intuitive. It's very easy to build automations. Someone who is not very technical can understand quite a lot and start to automate.

All automations are built starting with process analysis, then robot building, and monitoring. One person can gather the requirements, build the automation, and monitor it. This end-to-end coverage is very important. I can't even imagine how it would work if not in this way. This is the essential part of the automation: the idea, the implementation, and the maintenance.

UiPath's approach allows adding new workers, new agents, or robots to perform quicker and in parallel. For example, if you create two extra virtual machines with two extra robots, a whole bunch of operations will be performed three times faster. This kind of implementation is very convenient. And, we can change the way automations are deployed in Orchestrator and make it more efficient as well. We can do all these kinds of things really easily and quickly, like in minutes or less than an hour. That helps to scale things. You can change something in an automation in several minutes and deploy it or publish it in Orchestrator, and it already works. The challenge of implementing innovation can be addressed very quickly and very efficiently. The challenge is that we have to change our automations because other applications change with time. They have new user interfaces. But we don't need to upgrade anything to automate.

Several of our team members are studying the UiPath Academy courses at this moment. It has definitely helped because they get to know about new features that make automations more mature. One of my colleagues said, "As I read and study more in this course, I begin thinking more creatively and in more interesting ways." That means their understanding is growing and that it is changing their perceptions of what they can do with UiPath.

The information in the Academy is structured, starting with simpler concepts and moving to more advanced levels of knowledge, gradually. Also, you really learn about things you haven't used before. Thirdly, it leads you to the certification exam and getting the certificate on passing this exam. That makes you a good candidate for better jobs.

UiPath also has a very nice community of developers. When I face problems that I can't resolve by myself after several hours, I Google it in the UiPath Community and almost every problem can be solved by searching their resources. I work with different vendors and not all of them have such a big and open community. This is a real advantage. I'm not very familiar with other communities in RPA, but I can say that this community is, by far, more useful and more open than any other vendor's community I have seen.

I faced a problem when a new version of UiPath Studio didn't work with an older version of the packages that were part of our project. The problem is that when I have to change something just a bit, I actually have to rebuild the automation with new versions of these libraries. There is no backward compatibility. 

This question was addressed to an engineer from UiPath in the Community but I haven't gotten an answer. This is quite a hard question. So, I just create new automations with new approaches, which takes some time.

I have been using UiPath for about eight months.

The solution is very stable compared to other enterprise tools. Even if there is an error, if you handle it properly, everything works perfectly. From the point of view of UiPath developers, everything is done on a very high level.

It is scalable. However, to see the scalability you have to use the Enterprise Edition, because the Community Edition doesn't allow you to use more than one robot. But the mathematics are very easy: The more robots you have, the faster everything happens.

The number of automations will grow in our company.

I haven't used their technical support.

The initial setup was easy. It took a few hours.

We are using the Community Edition. The cost is only that of the virtual machines.

The pricing of the Enterprise Edition is a bit high. It's several thousand dollars a month. That's too much, because not every enterprise or organization can build such useful robots that will make it worthwhile for them to pay this much. Maybe the cost of the program could depend on the number of automations, or the complexity of the automations.

The solution is cloud-based, but you have to have some components deployed on the local computers. That is the architecture of UiPath, but the base of the infrastructure is in the cloud.

My advice is to just implement and begin automating. You don't have to even learn something before it, because everything is very intuitive.

We have a variety of projects we use it for. We have automated about 72 processes within six verticals, including sales, finance, HR, and purchasing.

It has helped our client save thousands of dollars, for sure. That is really what they have found to be the biggest benefit of using UiPath. The cost of the product is low because they're using it continuously. It saves cost and it helps them gain more returns.

Our main projects are mostly around SAP and Excel. We have used most of the features available, especially the ones that support SAP and Excel activities. Those are the ones that we have found to be most useful.

UiPath is easy to use and there is less coding. That is very helpful for the development team when it comes to building projects. It's very flexible and really makes our team more efficient. The turnaround time of development is good. 

There is some scope for improvement, especially in the area of variables. Some variables are used in specific workflows and some variables are global. It would help if there was a repository that would showcase which variable is global and which is local to a workflow.

UiPath should also help us whenever we are changing versions. Whenever we make those changes, UiPath should help by documenting the versions and sending us comments on the changes made in UiPath. If that were available, that would really help.

I would also like to see something related to auditing. That would really help the development and peer review teams to identify the gaps, instead of going through the sequence one by one. If there were an auditing tool that clearly brings out issues, that would really help.

We have been using UiPath for four years.

UiPath is a stable solution.

They are plugging in a lot of features that are really helping our teams. It is scalable.

For this year, we don't have plans to increase our usage of the solution, but it depends on our client.

The technical support is good and they respond to us all the time. Whenever we require support, they are with us.

They have a standard questionnaire that we have to complete and send in, and they come back with standard responses. At critical times, instead of the standard response, if they could do a direct call that would really help us. Instead of one or two levels of questionnaires, if they could directly get on a call, that would help us. Hence I rate them eight out of 10.

Positive

I was not part of the initial setup, but I am involved in the renewals.

The renewals could be easier. The documentation is lacking. When you are renewing your licenses, you might encounter errors but there are no proper documents available to explain how to handle these errors.

In terms of maintenance, our automation processes require some attention but UiPath, as an application, does not, other than updates.

There is ROI over a period of years. From the second year onward, it would be around 25 to 30 percent.

The pricing and licensing are okay. It's quite affordable.

There are a few things that come with additional cost. They are mostly features. For example, Document Understanding is an additional feature that you have to pay extra for.

I would recommend it to new users who are choosing among automation tools. 

Also, if a company is new to it or the users who are setting up are new to it, they should be aware of the preparations involved in setting up the environment and setting up UiPath. That can be a little challenging if they are not aware of certain things.

I rate UiPath at eight out of 10. There are a few features or approaches they could enhance, such as an option to view all the variables, as I mentioned earlier. Also, since the code can be very big, we might be searching for certain things that are not available. I'm more concerned about the debugging and evaluation parts. 

And in Orchestrator there are a lot of features they can enhance.

We suggested UiPath for one of our company's clients to automate DevOps processes. This is a part the company doesn't want to touch. They tried automating with Ansible Playbook and Terraform. We wanted to eliminate human intervention altogether. We are still transitioning from dev to staging and then production. We have done most of the research. We will move from staging to production if it works with our architecture and can be scaled.

Our client is one of the biggest companies out there. There are maybe a million users worldwide. They primarily focus on the Asia-Pacific region, but there are also users in Europe and the Americas. The client has several web applications and a hybrid structure. Some data are on the cloud, while other data is on the on-premise servers. We created solutions for them over the years. We have an SI and DevOps team working in parallel for years. Our goal was to automate everything that could happen without intervention. 

It's a massive project that will take time, and we still haven't moved out of development. We try to make the processes more streamlined. All the associates are researching it and working on their parts. Right now, I can only say how it has benefited me. I've automated some fundamental DevOps tasks. 

It saves a lot of time because you don't have to come in on weekends to provide service or troubleshoot. You can automate these tasks and schedule them to run automatically. You can optimize your work and how you spend your time. For example, some services need to be routinely patched, so we automated patching every third Sunday. However, we still needed to come in on weekends to troubleshoot after the patch was applied. 

We have shadow scripting to automate these processes, but we had to go online to see if it's up and the ports are open. I automated this with UiPath and scheduled it for the weekend, so I no longer need to come in on weekends. It saves around two to four hours per week. That is about 16 hours a month. It wasn't easy in the early stages. It took around two months to understand the tool. I was also working on other projects simultaneously.

There is a recording feature that copies each step of a task. You can automate every process via this recording. It's a cool feature that helps you define the variables. I also like their trial version, which lets you experiment with the solution and learn the capabilities before buying the license.

I still haven't used the drag-and-drop APIs, but I look forward to this feature. We currently use Jenkins for our continuous integration tools. There are some APIs from Jenkins, and we extract the job details from those APIs.

UiPath's interface and user experience could be improved. The name is UiPath, but their UI is not that great. It's outdated. It seems like a 2014 or 2015 software. They should look at other products on the market.

Another thing is that UiPath lacks online training resources. Maybe they can start their own YouTube channel. You have to rely on the documentation to learn. There are some resources, but they aren't available on the official site.

We have been using UiPath for six months.

UiPath is quite stable. I haven't seen any downtime. I can also pause the upgrade itself if I don't want the upgrades to cause instability. The long-term version is available as well.

We are still in the development stage, so we don't know whether it will be scalable. 

I have never had a need to contact UiPath support. I usually try to Google answers or figure the issues out on my own. 

I am from the build release team, so I automate the deployment and build process. I work on CI/CDs and try to automate most things. The deployment was highly complex. I was new to this project, so it was challenging for me. I was learning on the job and trying to understand the process itself because it was already partially built when I joined, and I was responsible for making some of it. 

The application takes about 10 to 20 seconds to install, but it will take around a week to build the infrastructure. We are just replacing the web service, not the whole application.

We tried a blue-green strategy for implementation. We built blue nodes and ports similar to production and shifted the web services to the new one. If it is up and running and everything works fine, then we can close the previous one, and we can redirect traffic to the new one with the help of load balancers.

We have 25 people on our DevOps team who do everything from architecture to automation. They're not just dealing with one web application. There are hundreds of applications. I worked on several applications building the architecture and helping. For example, let's say we build or add some features to a project. To automate those features, we need to understand them and how it works on Kubernetes or other platforms.

It definitely needs maintenance because we deal with a large user base. It requires a lot of maintenance and downtime to make things work during staging and development. Maintenance is always necessary, and we are the ones who maintain it. We have four or five people on call weekly to maintain the solution. They are the responsible people or points of contact for the developers or application owners if something goes down or goes wrong.

UiPath's price is reasonable. It's not so high relative to the capabilities. I don't know about different licenses or more premium versions. Prices are negotiated on the corporate level. 

We considered Automation Anywhere. However, It doesn't allow for an extended trial. We needed to purchase a license after 50 tasks, and we didn't have enough budget to experiment. Blue Prism is also there. We had the same problem. There wasn't a trial version.

I rate UiPath eight out of ten. UiPath has excellent features, but you need to be patient enough to learn.

We use the solution to speed up automation. We were looking to overcome the challenge of handling vast amounts of data, and we use UiPath to create bots to handle that. Tasks can be automated, and human error is reduced.

UiPath improved our organization as it has many benefits; it's straightforward and quick to use, has excellent third-party integration, and simplifies all our task automation.

The software has an excellent UI; it's very user-friendly. The drag-and-drop options are some of my favorite tools, as they speed up the process, and I find that UiPath offers a solution for all kinds of automation.

The solution saves a lot of time via automation; a task that took over an hour now takes around two minutes, and it's all handled by bots.

We use the drag-and-drop options, and they speed up our workflows.

The pricing could be more friendly. 

We have been using the solution for one year. 

The solution is stable, it's a reliable software. 

The product is scalable; it has very good third-party integration and scalability options within the software.

We use the solution in our office, so there are slightly under 100 total users.

The community support and documentation are helpful. I required some training initially, and was able to learn using UiPath websites and YouTube videos. 

Positive

I wasn't directly involved in the initial setup, but it took our team one to two months to get to know the product well.

I'm not directly involved in the financing, but the IT team considers this product costly.

I would rate this solution a nine out of ten. It's an excellent product, but there is always room for improvement. 

I highly recommend UiPath as it's easy to learn and offers significant advantages for all kinds of automation. 

The solution is perfect for our requirements. 

UiPath is deployed on AWS EC2 instances, and we use it for basic automation.  Very few developers are working on UiPath here. Our end-users don't deal with this. We only use our database and the data collected from UiPath, but the automation is not visible to our customers. We only use it in our internal development or design phase or to collect some automated data. 

We haven't used UiPath's machine learning capabilities, but we are working on that. That could be useful in a few use cases for triggering some queues and running processes in the background. We are using asynchronous jobs, but we don't rely on AI yet.

It helps us design the automation capabilities of our products. You can quickly create some AI-driven, easy-to-use, automated tracking products. We can also design the workflow to enhance the optimal automation process. Before using UiPath, we needed to write code to define some UI tasks manually. It required a vast amount of coding and used up much of our developer bandwidth. 

UiPath saves us some time and development costs by helping us quickly design some automated tasks and workflows. We reduced our work time by at least 70 percent because developers no longer need to write a considerable amount of code for a single automated task. UiPath can do all of that.

The drag-and-drop APIs reduce the time it takes to build workflows because we can define an orchestration URL and how we log in to the system. We can easily define entire edge cases and workflows. This helps us a lot. The AI will help us, too, but we are still in the development phase. 

In the early stages, it took a little time to see value from UiPath. Our engineering team needed to learn the product, but we were good to go in two weeks. 

I find the whole product useful, but I like the intuitive design the best. It's a well-designed UI, and it's comfortable for this use case. You can easily automate anything. The drag-and-drop APIs make things easier for us. We can simply drag and drop based on our application requirements, so things go smoother and faster.

UiPath should improve the test case criteria in future versions because the test cases are not well-designed. I feel everything is fine other than that.

I've been using UiPath for about two and a half years.

We have been using this for about one and a half years, and it's highly stable so far. 

Based on our current use case, we believe we can scale toward the AI path of that product, and we are still in the process of evaluating this. Once we implement the AI features, we expect to scale up further.

I rate UiPath support nine out of ten. I'm impressed with them. It has a steep learning curve, but UiPath provides a lot of online documentation, helping us figure out everything ourselves.

The technical support from the updates team is nice. They provide instant support for any issue, but we've barely used them because everything is well-documented, and the UI is intuitive. 

We were working on coding architecture and directly defining and using our code.

A different team handled the installation. We have two people managing the solution, but it doesn't require much maintenance. We install patches about once a year. The updates can affect our data and the process we use, so that's a challenge sometimes. 

We have definitely seen a return because UiPath has cut the engineering cost significantly. It frees up our engineers to do other tasks. It has reduced our workload by around 80 percent. We still required one or two developers to develop all these UI cases.

We find UiPath's total cost of ownership is cheaper because we significantly reduced the resources required for development. We believe it's a reasonable price for the value we get in this application use case.

We tried Automated Anywhere, but that doesn't work for us. UiPath provides much more features, and we can enhance things better. UiPath's drag-and-drop functionality also makes things easier for us. After trying these two products, we found that UiPath is a major gamechanger for our use case.

I rate UiPath an eight out of ten. The test cases could be better, and we're still evaluating the AI-driven part. Otherwise, I would rate this as a nine. I highly recommend this product because of all the advantages it offers, and UiPath has great documentation and videos available on multiple channels. It has considerably reduced the manual work we are doing. 

UiPath offers direct integrations with multiple platforms that we need, like Google Drive, Slack, Visio, etc. For Slack, UiPath automates the process when we upload a new file, document, or a new version of it. It automatically sends an email or any other sources that we automate through it. That is our main use case.

We upload a lot of content for our website or internal work on Google Drive. When a team member uploads content, we do not get a notification from Google Drive that a document has been uploaded by someone unless they share it. With UiPath, we have automated it so if someone uploads a document in a Google Drive folder, we get an email on a certain email address that a document has been uploaded. Or, when there is a version change, we also get an email. So, we have automated these kinds of processes using UiPath.

It is mainly the automation process for internal tasks. All our direct integrations are for internal work, mainly email triggers that we built using UiPath. These are very useful.

The direct integrations are most valuable. You can directly link your account to multiple platforms, such as Google Drive and Visio, without using an API.

We have used the Orchestrator's trigger creation workflow to create multiple triggers for our automation processes.

It could be improved with tutorials or documentation-wise. Some of the features of the artificial intelligence or Orchestrator have been a little confusing for me. So, I would like an easy YouTube video tutorial or quick demo call. It would be much better for every user if they could introduce that.

Around six to seven months ago, I started using UiPath.

UiPath has always been up so stability is not a problem.

It is really scalable, even for large businesses. We are pretty small, but as you grow, UiPath has great options for scaling up.

We currently have two people using it: the co-founder and me.

I haven't needed to contact their support yet.

We previously used basic process automation platforms.

We switched to UiPath because it offered better features that we needed. For example, its direct integrations are pretty useful. It has every integration that we directly need so we don't need to use APIs or code anything. It is simple and direct. That is the main reason that we use UiPath.

It was straightforward from the process of registering your account to creating an organization, then doing the integrations. The process was really easy and did not take too much time the first time. I think it took us an hour to deploy.

We are on the Community plan, so it has great return on investment.

UiPath has saved our staff time. Using the automation of UiPath, it triggers an email or notification for a process that we have created. This keeps us informed at all times. However, if we don't use it, content may get missed and we would lose a lot of opportunities.

The pricing is good. They offer a Community edition that we currently use, which is free. Their paid pricing is pretty affordable for businesses as well.

I went to review websites and saw that UiPath is great.

In case you are not going to drag and drop APIs, they should definitely go and have a look at direct integration. 

I would rate the solution as nine out of 10.

We are a service-based development company and we implement automation for our clients. UiPath is one of the RPA solutions that we use for this.

A recent use case that we implemented for a client involved a macro in an Excel sheet. The macro contained approximately 1,000 lines, and it was being used in an Excel spreadsheet about 10 pages long. They had dropdowns within the sheet that had to be set, depending on the action. They also had to work with some of the logic themselves.

With UiPath, we implemented a solution where the bot will create a task. It first checks to see if all of the necessary conditions are there. If they are, then the bot will automatically run the macro. If instead, some of the values are missing and user input is required, then the bot will create a new task to request the missing items from the user. It uses the UiPath forms and the client will receive an email to say that a task has been created and that it will be completed once the necessary values are selected.

Finally, once all of the values have been selected, the bot will run, use the input, and complete the execution of the macro.

A second use case for us was done using the Action Center. In this case, our clients send emails, and we have API calls that are done in response. Once an email comes in, a message ID is created and assigned to it, then it is turned into a Queue item. At that point, the user is presented with different actions that are dictated by the content of the email.

Depending on the user's selection, there are three or four paths that it can take. Ultimately, the bot will send an ETA and some request data to the appropriate parties, which is controlled by yet another process.

Using UiPath for automation is a little bit costly but it saves a lot of time, and it also reduces human error. When humans perform tasks, there are a lot of errors that come about. However, when a bot performs the same task, the number of errors is significantly reduced. This is the reason that companies are implementing UiPath and undergoing a digital transformation.

In our experience, bots run with minimal errors, in the one or two percentage point range. Of the thousands of items that they process, very few will result in an error. Humans, by contrast, normally have an error rate of 5% or 6%.

It is very easy to develop automation using UiPath, and I would rate it a four out of five in this regard. This is true whether it is IT automation, UI automation, desktop automation, or otherwise. We have even performed Citrix Automation recently, where we used remote runtime. In that case, we had access to a lot of features and this made our work very easy to do.

This product enables us to implement end-to-end automation. Some of our clients use the process mining feature, which includes task capture. Then, based on that, they generate the process design document (PDD). After they have the PDD, the bot is designed using Studio, and then it is ready for deployment. Deploying a bot includes publishing it using Orchestrator, and once it is running, Orchestrator monitors it. From end to end, UiPath is part of the process.

This is important to us because some of our clients are not very technical. They have ideas of what they want to do, so they walk us through the steps in a process. During that time, we will begin using the task capture capability to record what they do, making it easier for us to gather ideas and requirements. The whole process is an easy way to capture good use cases for the client.

Most of our clients are now opting for cloud-based deployment. This is important to them because they don't have to store everything on their on-premises servers. Essentially, they don't have to waste any space.

One of the features that I like is that the bot will continue to work on other tasks, even if one task is blocked because it is waiting for user input. For example, it's very good because whenever we need to have user input, we don't need to use the attended automation. Just because the user is not available to select the actions, it will not break the bot. Rather, the bot will work on other tasks. Once the person manually completes the required action, the bot will resume the pending task.

It is very easy for us to get selectors by using the UI Launch Explorer. I have used other tools that require we visit the webpage and get the selectors manually. This means that we have to inspect the page and find the elements. However, with UiPath, we have the selectors readily available using UI Launch Explorer.

Another good feature is the UiPath Academy. Whenever a new feature is released, we learn about it from the Academy. I would rate it a four out of five in terms of helpfulness for getting employees up to speed. When we review the new courses that they release, we can quickly get a complete idea of the feature that they are presenting.

The UiPath forum is very helpful. It is the best forum available for any of the tools that we have. I would rate the UiPath forum a five out of five.

One of our clients is using the UiPath Apps feature, and although it is easy to use, they are having some issues with it. For example, when they deploy an update, it is pushed to the cloud and then it will break an hour later. There have been two or three such issues and ultimately, they result in a high priority ticket to fix the problem.

I have been working with UiPath for approximately four years.

With respect to stability, the general system is stable. This includes the robots, Automation Cloud, and the Action Center. However, we have had a lot of downtime with UiPath Apps. It had been one or two days per month when our processes were getting blocked and although many of these issues are resolved, last month we had recurring issues with downtime.

The technical support team is very helpful. For anybody with a license, there is an option to raise a ticket based on priority. The support team tries to fix such problems very quickly.

Overall, the support team is very good and I would rate them an eight out of ten.

Positive

I have explored two or more other RPA solutions. One of them is Automation Anywhere, and another is Microsoft Power Automate.

When I explored Power Automate, it didn't have many features. It is a product that is still growing but when I looked at it, UiPath had more features.

In the case of Automation Anywhere, it's a little bit more difficult to work on. As an example, Automation Anywhere does not have ready-made selectors. There is no equivalent to the Ui Launch Explorer so we have to go to the webpage and find the elements by ourselves.

One advantage to Automation Anywhere is that it's a little bit less costly.

Using the Apps feature for one or two of our clients has sped up the time required to develop bots for them. Also, because it is a drag-and-drop interface that only requires a small amount of coding, making it work is much easier.

Our clients dictate the deployment model, whether it is on-premises or cloud-based. One of our clients uses Amazon but the majority of them work using virtual machines that are running on their in-house servers.

The automation saves time and money for our clients, although the amounts vary and are based on the specific solution. As an example, in an email task that we automated, the bots replaced a team of people. On average, the automation saved 28 hours per day for that task.

In general, several hours can be saved per day for each automation.

Due to the reduced costs and other benefits, our clients are ready to create more bots.

UiPath is a little more costly than competing solutions such as Automation Anywhere. 

The cost for licensing is handled by our customers that use the bots.

I have not personally used the AI functionality when creating automations, although some of our clients use features such as Document Understanding for invoice processing. They also use the ML Trainer. These features help them to automate processes that are more complex. For example, when they have 20 or 30 invoices coming in each day, the bot is trained to look at them and it makes the job very easy to do. Also, when the accuracy drops, the bot can wait for input in an attended fashion. This has helped a lot of our clients.

I would rate this solution a nine out of ten.

I use it for automating activities and processes in my company, and for discovering new automation opportunities. UiPath is my main tool for automating every process in business operations.

One of my main use cases for UiPath is around service desk and support center operations. I use it to take tickets from customers and users and automate answers using UiPath's machine learning. It links the questions to documentation where we already have answers.

I also use it for automating invoices with the pricing and other information and sending them to customers when they buy an item.

In addition, when somebody subscribes to a newsletter I have set up a process to send an email in reply.

Using the solution we can do task mining and process mining. The automations make everything easier for my business and for the other businesses where I implement them.

For example, one of my use cases is for a doctor's office to help manage the patients by handling their inquiries and automating the invoices. I have also set up processes to help with research and prescriptions. All these processes are automated and run without any human involvement.

And it has helped my business operations a lot. It's helping us detect all the performance issues and data threats. UiPath Insights helps us to prevent these issues from happening again. It's powering up our operation. We can analyze all our departments in one place and get the best usage from them using Insights.

We fully depend on UiPath for the three departments: sales, marketing, and service. Many of our sales operations are done by UiPath, such as generating invoices, research, and engaging with clients through the help tickets they submit, as well as through the email communication we do. 

And one of the most important benefits is the ability to identify new opportunities in my employees' workflows. It is able to record and discover what my employees do and we are able to create automations as a result. 

Digital transformation is another main focus. Through the UiPath Marketplace, I can get expert virtual employees who do very expert jobs and tasks without having to hire somebody or bring them into the office as an employee. It's all automated by the software. I can discover, build, manage, and engage with the robots. My employees can easily manage all the robots and the processes, increasing the collaboration among us.

All of this makes it easier to store and move data from Google Sheets to my own sheets or my CMS on WordPress.

It saves a lot of time. It has really transformed my operation from a situation where we were always pressed for time and had slow response times to customers. With UiPath, we have increased our customer satisfaction scores and get tasks done faster than ever. My employees are now using the time they used to spend on certain tasks for things that require more thought. It has transformed business operations 180 degrees, making everything easier, helping the business to grow faster, and improving performance. We have control of the front-end work as well as the back-end processes.

For me, the most valuable feature is the solution's ability to discover automation opportunities.

The Document Understanding feature for extracting information from documents or images helps reduce manual work, saving people from having to scrub data from PDF files or images. UiPath extracts all the information and stores it.

In addition, its AI and machine learning make everything easy, as do the Data Service tools, because they don't require coding to create automations. I can do everything without coding knowledge.

And the UiPath user community is the best. The people there are very friendly and helpful, and engage with each other. UiPath has done a good job building a good forum and a good blog, and making the community members interact with each other. The community is one of the reasons UiPath is my choice. It is a strong community.

I like most of the UiPath tools, but the UiPath Academy, in particular, wasn't my favorite part. It didn't have enough onboarding guidance when I started. The learning curve for the courses in the Academy was very difficult in the beginning. I had to turn to Google and YouTube to learn from other people, experts, and the community. The community was friendly, but the academy wasn't that helpful for me. I think it needs to improve on the information it provides to make it easier for beginners to learn, to help decrease the learning curve.

Also, the user interface needs to be more customizable, and the debugging tool doesn't work well enough. It needs some improvements.

I have been using UiPath for one year and eight months. I have several websites and three startups, and I also implement UiPath and automations for other companies.

It's stable. It has 99 percent uptime. 

Sometimes, when we are dealing with a large set of data, it becomes slower. I don't know if it is something to do with UiPath or something else, like the operating system or the connections. It is almost always stable, but when dealing with large data, it becomes a little buggy and slower. Sometimes it freezes and I have to turn everything off and restart it.

Their support staff has good knowledge about whatever I raise, but they are late in responding, at times. I have had to turn to the community more. When I can't find an answer, I turn to them and only after them to support. It should be the other way around. I should be turning to the support group and then, if needed, to the community. 

One good thing that I have found is that UiPath responds to the community and the recommendations of users. When we recommend something, they put it on their roadmap and they make plans for it in their app. They are engaging and friendly with users and the community, but they are late in responding.

Positive

I started by using Blue Prism but only for three or four months and then I left it and turned to UiPath. I couldn't find answers to my questions when I was using Blue Prism. I couldn't find a professional community to engage with or to get help from. This was the reason I started turning to UiPath, after reading a few reviews from several websites and some of the community posts. The UiPath community was providing good information about every capability of the solution. In my experience with Blue Prism, I couldn't find any valuable communities out there. With UiPath I found the opposite. 

Even now, I find it good to engage with the UiPath community. Whenever I need an answer to something or an explanation about a use case, I always turn to them.

They have to reduce the price a little bit for basic users, startups, and small companies.