UiPath Reviews

We automate the entire revenue and order to cash and then process it to payables. It is used for processes, from generating customer invoices to ensuring that all our vendors are getting paid timely. We also use it for data reporting, audit requirements, or whatever information gathering that the company may need.

We've automated about 30-ish processes, and that's just the tip of the iceberg of where it's going.

All of the processes are attended to right now. We're still getting the backend set up to move some of them to unattended.

The solution has improved the organization by providing time savings. That's one of the most fundamental things. We recently had a project that would take a human who's actually navigating through the screens and clicking all the buttons roughly a month's worth of work, if that was their primary focus all day long. We were able to get that completed within two days using UiPath. Therefore, the time savings are phenomenal. 

Also, when you're dealing with all that data, there's a lot less likelihood of human error and missteps. With the bot, we know for sure that the line is the line, and that's it. It's error-free for the most part.

The low to no-code is by far the most valuable feature. Developing a bot in under a minute that saves you an hour a day is phenomenal.

The user community is great. Looking at the forums, when a question is posted, the responses are fairly quick, either from UiPath or the community itself. In my past role, I posted to the community before, and I had been able to answer some questions as well. Then, it's nice to know people are having the same problems you're having and finding solutions.

I've taken UiPath Academy courses. I've taken mostly the developer ones, and then I'm looking into more of the admin side, with the Orchestrator and project management side of it. The biggest value is that it walks you through step by step and you're doing it alongside the course. It's hands-on learning. It's one thing to watch a video. It's a different thing actually to play with it and have something start working.

Overall the training and documentation could be better. There's just so much of it, so a streamlined way to get to the information I need would be ideal.

I've used the solution for about two years. 

It's very stable. Performance-wise and stability-wise, it's great. We're able to access it from anywhere. I have the Orchestrator app on my phone, so I can always keep track of the bots that we've developed and see how they're doing and everything.

Scalability is something we're still looking into. We just started, so we're still in the groundwork. However, in terms of being able to scale, the potential's there. We just need more time to play with it.

I've had one instance with them, and it was great. They knew their stuff, they walked me through everything.

Positive

Before UiPath, we used Nintex RPA, and then an SAP RPA tool as well. We used to UiPath to get more usability and scalability. The user-friendliness of the product and just the engine and the innovations that they're making behind it really placed them as a leader in the sector.

I was involved in the implementation since proposing the idea to start developing and starting a road show to be able to expand.

The process was straightforward. I had no qualms about it.

We started small. We essentially had two developer licenses, a couple unattended, and then a couple attended. We had already identified who would the attended bots go to, and did all that legwork in the forefront. Once we got the license enabled, we could activate it, work in the Orchestrator to assign the specific roles, and then have them start running. Within a week, we were able to get bots out the door and have people actually using them.

Everything has been done in-house. We've been building everything ourselves. 

We've definitely seen an ROI. For example, in one project, we were able to take a month's worth of human effort and completed it in two days with UiPath. We've had several others of a similar nature.

The pricing is a bit high compared to other products. That said, it does offer more. From working with other ones, it is definitely a more powerful tool and well worth the pricing.

We did evaluate other options. We had the ones we used before. We also looked at Blue Prism, Automation Anywhere, and a couple of others. 

The difference was a sense of familiarity. I had previous experience with UiPath. Mainly the innovations and the fact that since 2019 on the Magic Quadrant, they've been the leader consistently, and they will continue to be, were the reason we chose UiPath.

We do not use the AI functionality in our automation as of right now. It is something I'm interested in, however.

Our company will be involved in an environmental initiative using UiPath. We have an environmental group. As of right now, we haven't thought about taking it that far. We've only had it for about a month or two. It's something we're considering for the future. 

The most important part is going to be the user interface. The people who are developing it, the people who are using it, they're the ones who are going to have the most to say about it. Your business end-user has the most to say about it; if they don't like it, that's all you'll hear. By focusing on that user interface, which UiPath has done, you really get a solid project that people get excited about rather than leaving a bad taste in their mouths.

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

Our biggest use case right now is around business development. We use UiPath to run reports that we get off of the internet against our internal databases to try and find anyone who is a client because we're a law firm.

Most of my development right now has been on the business development side. We're helping clients with their cases, whether it's a litigation case, a bankruptcy case, or a real estate case. I use UiPath to help identify potential clients or current clients so that we can help them in their legal space.

UiPath has helped to alleviate some of the workload of our paralegals, assistants, and secretaries. They were going through large files of cell rows, and it was taking up many hours of their day. Using UiPath, I was able to automate a lot of it so that they don't have to spend that time. Now, it's more of a review process as opposed to a daily, mundane process of going through Excel files.

On one of the other processes that I developed, a marketing assistant had to take another daily report, and check to see if any of the companies that were filing for litigation on that report were clients or prospects. It took three hours of her day every day, and it's done five days a week. Now with UiPath, I have it unattended and running at 5:00 a.m. so that when she gets in, all she has to do is review the report that I generate for her. That's a consolidation of what comes off the website, what we have in our internal systems, and anything that matches.

I do all my developing in Studio. I develop and publish into the orchestrator cloud, and then I try and run everything unattended. So, Studio is a very valuable feature for me.

Another feature that I've been using a lot is the new integration app with Microsoft that triggers emails.

The UiPath Academy courses are great because when there are things that you don't know right off the bat, it helps you develop, learn, and grow within the platform. I've done a few courses and plan on doing more. It's definitely helpful for me being someone that didn't come from a development background. I taught myself UiPath in the beginning, and now that I know how expansive the Academy is, I'm definitely going to take more classes so that I can learn exactly how much I can do with UiPath.

I would like to see ongoing integrations with different applications. For example, we have UKG, which is an HRIS or HCM system. I'd love to see if there could be some sort of connection there because there are definitely some HR tasks from onboarding and offboarding that we do in the HCM that I'd love to have UiPath help with.

I like that UiPath is a platform for more than just one specific product. So, I'd like to see continued expansion of the platform and have different APIs connected to it. Different integrations sitting on top of it are just going to make it more beneficial because you'll be able to have everything come into one spot instead of having to buy four or five different products.

My firm has had it since 2019, and I've personally used it for about a year and a half. 

We're in the cloud and not on-premises, and I think the cloud runs pretty well. Up until last week, the stability was great. 

Last week, I had an issue with one of my licenses falling off of the unattended robot. I was surprised that it happened. I don't really know why it happened, and I'm working on getting it fixed.

The scalability is great. There's definitely a lot of potential for it to scale, especially in our environment.

They support infrastructure and not development, which at first was a little bit of a bummer for me. Their tech support has been great when it does revolve around infrastructure, and I'd rate them at eight out of ten.

Positive

We found a couple of clients using the UiPath processes with respect to business development.

I think the pricing is reasonable. I don't think it's too much of a stretch, and I think it's where it should be.

If you have a lot of paper processes or routine processes that are weighing down your employees, then UiPath and automation, in general, are the way to go. There's fear that it's going to take over the human role, which it just doesn't. From a 500 foot view it kind of makes sense, but when you're developing and working on the automations, you realize that you really can't get rid of the human aspect of it. This is because there are always going to be some sort of checks and balances as well as things that the robot can't do and decisions it can't make. So, don't have that fear and push away from automation or UiPath. They go well together, and you should definitely consider it.

Overall and considering the usability of UiPath, I'd give it a nine out of ten. I think there's a lot of documentation out there with the forums and with partners that support as well. UiPath does a really great job, and I'm happy that my firm decided to purchase its product.

We can use UiPath for pretty much anything, including document reading, day-to-day processing, or maintenance cases. For pretty much anything that the business comes up with, we can use UiPath. 

It's the only RPA software I've ever used. It's really given us the capability to help automate a ton of slow-moving tasks.

It is helping to automate some finance processes, shared service processes, and items like that to eliminate some tedious tasks that people don't want to deal with.

The Automation Hub helps prioritize things. I'd say using the community edition to get citizen developers on board has been great. Those are probably the two biggest aspects of the solution for me.

The user community is helpful. The forum is really great. I need to build up a bigger community around me; however, for right now, the users are super helpful.

I've used UiPath's Academy courses. It's great for letting people do training at their own pace. It also speeds up training. I don't have to spend hours teaching people how to do stuff. They can do it whenever they want. That's super helpful.

We'd like more onboarding features for new people. I mostly taught myself. It would help if it was more proactive in reaching out and saying, "Here are all of our connectors. Here's the stuff you can do." The program itself is really easy to use, however, to understand the capabilities, it would be nice to have more of a guiding hand.

I've used the solution for probably two years. 

The stability is good. I've never had a feed down and find it to be rather solid. 

The scalability is pretty strong. It seems to be as scalable as you want to make it. It depends on your design. For example, if you make a shady bot, that's not going to work scalability-wise. However, if you build your bot the right way to handle tasks quickly, it'll do it quickly and will scale well.

Technical support is really good. I've only used it twice. However, both times they have been really quick to respond and help.

Positive

We did not previously use any other RPA software.

I am involved in the initial setup process. I started the CoE of my last job, and I'm doing that at this job now.

We used a partner to help with it, so it was pretty straightforward. If I had to do it myself, I'd probably struggle, however, with partners, it's easy.

I have seen an ROI. The first spot I made paid for the license. It's pretty quick to realize a return on investment. 

We've used Automation Hub to track monetary and hourly savings. My last company probably saved to the tune of $300,000 annualized. I just started this job. I will be able to note an ROI pretty soon.

I need to dig into pricing a bit more. It's pretty affordable for what you get. 

We evaluated the whole market before choosing UiPath. However, I wasn't directly a part of the process and, therefore, can't get into specifics. 

I do not yet use UiPath to automate processes that deal with a good cause that our company is involved in. I've only worked at the company for two weeks. I'm a little new.

I have yet to use the AI functionality in our automation program. 

I'd advise others to work with a partner to deploy it at your company. Don't try to do everything at once. Build a list of ideas before you start trying to get into things. Have a funnel of projects to do.

I would rate the solution a nine out of ten. They could improve a couple of things. However, it's really easy to use. You don't really have to learn any code. It is really easy to get people to learn it on their own. It's pretty solid overall.

Our company uses the solution for documentation understanding, email automation, and onboarding. Many of our use cases include AbbVie. 

Our company has saved thousands of hours by automating accounting processes. Staff no longer have to drudge through manual tasks and that is meaningful to them so they do better work. 

The solution provides ease of access for users with limited knowledge. One of our high-level developers can code it for a user who can maintain it with limited coding knowledge. The solution is much easier to use than having an actual coded application. 

For example, a developer can build out a use case that involves emailing invoices and includes labels and documentation. The product can then be handed off to a user who does not have coding knowledge because all needed information is included for maintenance and administration. 

There is a bit of a learning curve to the solution because it is like coding. If you are a coder it will be easy but you cannot dive very deep into the code. The way you go about the architecting process is very different from other tools because you have to lay out the flow in a certain way. 

Reusability is not as great as straight coding where you can recall functions and methods. The solution requires a whole workflow that can become a bit tedious when processes expand too much. 

Features I have wanted such as enhanced process mining and others have been shown in the new preview so are already forthcoming. 

I have been using the solution for four years. 

The stability is pretty good and the solution has not shut down. I have experienced a few crashes, but they are probably caused by my own computer.

The scalability depends on how you develop it. If you develop it to be scalable, then it will be scalable. In terms of Orchestrator, the platform is pretty good at scaling because it allows you to keep deploying it and branching out. 

The Community is great and operates similarly to Stack Overflow's community. Users have their own niche knowledge and you can query them if you ever need anything. This is a good way to expand your own knowledge base. 

I took the Academy's courses when I first started using the solution so haven't learned the new features yet. Over normal coursework, you learn best practices that enable you to pick up the tool faster, such as how to document process flow or how to set up from a high-level perspective. 

I have not needed technical support. 

I have not used other solutions. 

The setup is pretty easy and straightforward. 

We implemented the solution in-house. 

We always hope to see ROI in every process. We have realized a bunch of ROI on deployed items and hopefully will see more. 

For our provisioning process, we save a few hours per person each day. 

Our company did not evaluate other options. 

I advise others to try out the solution. It is really good software and has helped a bunch of people to switch careers. For example, I used to be an actual developer but now I do RPA. The solution is an industry leader so it is a good idea to try it out at least once.

I rate the solution an eight out of ten. 

We generally work on integrating it with our support ticketing system, which is ServiceNow. That way, we can standardize our input and get better results. It has been working really well for those kinds of processes.

A process that we worked on for operations, for example, was the ordering of phones for our new agencies. It accelerates a lot of that process and gets the people onboarded faster, more easily, and with fewer errors.

The most valuable feature is that it can be integrated with almost anything. We use in-house applications and we're able to integrate them through the database using endpoints and APIs. This sharing of information between systems via UiPath means our staff gets results quicker. Normally, we have to put in a request with the database team to go in and input the data. But UiPath already has access and it's really quick. It's really responsive and makes the experience easier for the business.

That is also true for third-party vendors. The vendor that we order our phones from has a UI, a website that we use, and we have been able to use the UI to integrate their application.

We can implement almost any interface that we want, in any way possible. It's really flexible.

And given that healthcare is highly regulated, UiPath works really well for credentialing and that type of security. We see that it has protocols that ensure that our data is not going to be stolen. We use the credential assets to save our passwords and sensitive information such as licensing.

I've been looking into Document Understanding. I've worked with it in previous jobs, things like AI center and OCR for documents. It would be helpful if they made the Document Understanding modules a little more user-friendly. There is a learning curve for using it correctly. It's a little bit hard, but once you get a feel for it it's good and it doesn't delay the automation process.

I've been using UiPath for almost four years.

The stability of UiPath is good. I haven't seen any abrupt occurrences in my time using it. Our production environment is always running. It's well-secured.

In regard to our processes, it's easy to scale. It is not that easy to scale on the business side of things, but the tool itself does provide an easy scaling process.

I haven't had the need to reach out to technical support that often because, with the community, you can find out anything regarding UiPath online. It's the same support team that answers those questions.

I did submit one ticket to support, and it was answered really fast. However, they did take a little long time to get to the root of the problem.

Positive

We did not have a previous RPA solution.

We do calculate ROI in terms of the hours we're saving the business. For example, with the specific processes that we created for phone ordering, we're saving the business a lot of hours. 

Currently, we're just using it for agencies because we want to see how this can impact things. But it's handling the process for more than 40 percent of our employees because most agency employees get phones as soon as they are onboarded.

I have evaluated other automation tools, and I've been asked many times in the different companies where I have worked why I prefer UiPath. It's the best choice because of the community, documentation, and the number of updates they come out with. They're really on top of things.

Other vendors are not on the same level. I have tried Blue Prism but it has poorer documentation and it doesn't have the support that UiPath has.

To get our certificates we had to use the UiPath Academy. The Academy gives you a sense of how UiPath works. It can get really technical, but to get a sense, at least, of how to start the journey of becoming a developer, in my case, it helped a lot.

Overall, it's a great tool to use. It has a lot of benefits documentation-wise and support-wise. It's really stable and it's really easy to use.

My organization is an outsourcing company. We work with various clients. So, we have many use cases. The current use case I'm working on is related to invoice processing.

We don't use attended automation. We use its AI functions a bit. Usually, we work with document understanding.

Currently, I'm using the latest version. It is deployed on the cloud and on-premises. It is the UiPath cloud.

It is easy and fast to build automation using UiPath. All of our automations are created with UiPath. Usually, we do automation for SLA purposes. Most of the time, the clients don't have enough resources or humans to do the job, and they need automation to improve the SLAs.

It enables us to implement end-to-end automation, starting with the process analysis, robot building, and monitoring of automations. It is good for my company. With these benefits, we can implement it and help with the monitoring.

It has reduced a lot of human error. For example, in the project that I'm working on, people were putting the invoice information on a daily basis. There were more than 20 invoices per day, and each invoice had more than 100 line items. Humans would do a lot of mistyping on the number of packages or the number of items in the package. After we applied the document understanding solution there, we can handle around 90% of invoices, and all of them are correct.

It has absolutely saved us time. It has probably saved us more than 20% of the time. People now have more time.

I feel comfortable with UiPath. The thing that I like most is that UiPath has a very large community and a large ecosystem. So, it is easy to connect with other applications or platforms.

UiPath Apps is a great feature, but it still needs time to evolve. They need to add more features. It hasn't increased the number of automations we can create while reducing the time it takes to create them.

I don't like the sequence feature in the UiPath. It is difficult to analyze and read the code.

The variable management is really messy. When I look at the code, I don't know where the variable is and in which scope.

I have been using this solution for around five years.

It is stable.

It is scalable. We have had three enterprises that are really big with more than 1,000 people. The others are small companies.

In our organization, we have 12 people working with it.

I haven't contacted their support. I have been using UiPath's support indirectly. I just put a question on the community forum, and they answer it very fast.

In the previous version of UiPath, it was a nightmare to set it up, but now, it is really comfortable and convenient. Overall, it is fast, but the deployment duration also depends on the solution. If you design a good solution and follow the best practices, it is really fast. It takes a couple of hours at the most.

We always try to split a project into small parts so that we can test each part and apply it easily. I have seen that many people create very big projects, but when you complete them, you cannot test them. It takes a lot of testing from end to end, and we still can't test it completely. That's why we try to split a project into small parts. We can test each part independently, and after the integration, we can deploy with high confidence.

I am not sure how long it takes for our clients to see its benefits after we deploy it for them.

We have a maximum of five people for deployment and maintenance. We sometimes have issues with the infrastructure. In many cases, the infrastructure is handled by the client, and there is no support or cooperation between the RPA department and the IT department. Usually, they will be late, or they did not check our requirements to deploy the bot.

If you use the cloud model of the UiPath, it will reduce a lot of the total cost.

Its AI functionality hasn't enabled us much to automate more processes. Most of the time, when we propose those functions, we don't have an agreement with the client because of the license price. Currently, the license price is the major obstacle.

My advice would be to contact the UiPath sales team directly. I know that they have different license models for different clients and regions.

I would advise following the UiPath Academy and their best practices. That is enough.

They provide very valuable templates for automation purposes. It depends on your purpose, but you can apply the ones that are already there.

I would rate it an eight out of ten.

We are using UiPath for automation processes in an insurance company in the finance department.

The most valuable feature of UiPath is if you set a form and there's an interaction with the user, it's easy and fast to build than the other RPA tools. Additionally, it is simple to use the connectors.

In UiPath they should improve the input and outputs of processes. I found it very complicated.

In a future release of UiPath, they could improve the OCR engine to make it better. All the RPA tools use some OCR engine, while UiPath's is the best but it is hard to configure and set up for your projects.

I have been using UiPath for approximately six months.

The stability of UiPath is highly stable.

We have approximately four people using this solution in my organization.

I have not used the support from UiPath.

We previously used Blue Prism.

UiPath gives a return on investment, it does what it is supposed to do.

UiPath is an expensive solution but it is worth the money. You have a lot of features. 

The licenses need to be improved because when you have to use UiPath on another system, you have to set up the processes manually, and you are not able to change the process the time if you configure a process running at the system. You have to stop it and then run to the other system. It's not too easy to configure it according to the system. If you have a large deployment, for example, 10 to 20 bots, it's hard to configure.

UiPath has a lot of free training and a lot of free processes ready to go. You have to see the best practices in order to receive the best way of development. It is important to see the best practices guide.

I rate UiPath a nine out of ten.

UiPath is great because it's highly stable, it's fast to develop, and easy to configure. However, there are some improvements to be made.

Since we are a healthcare organization with HIPAA rules, we're on-prem. Our use cases boil down to claims testing and membership testing. It'd be institutional professional dental claims and making sure our membership is loaded correctly.

We have to configure our software to pay claims and pay providers. What we're realizing is that, the more claims that we can run through the system, the more accurate we can get, the faster the payment on the claims, and the faster the payment to our providers.

The only features we're actually using are the orchestrator and 32 unattended bots.

The value of that is the power to be able to run our thousands and thousands of claims and membership to make sure that everything looks correct.

The solution has saved costs for our organization. I know it's over a million, however, I haven't done the exact numbers.

UiPath has reduced human error. We’re finding out that what we've built for configuration in the past, we're finding mistakes that we did a year ago. Now, the bots are proving that and we've been able to correct those past mistakes. This way, we don't have inaccurate payments or recaptures.

The product has freed up employee time - and it's not just the employee time. We do have some triggers that run. Some jobs are run that people use to manually do at night and weekends. We also don't have to hire additional people just to learn 80 different types of things in a claim and identify correctness manually. The robots will go through and then they can identify if there are specific things that are wrong. That part will go to our experts and they'll review those exact issues.

This use of bots allows for employees to do higher-value work. We also have been able to up-skill some of those people to sometimes a leadership role or a different role they would normally never get due to the fact that they were always manually looking at the claims and membership. This has definitely affected their level of satisfaction at work.

I don't know if we have an accurate estimate of how much time we are saving. I just know we do volume and we do thousands and thousands of claims a day, and therefore, it really helps.

We use UiPath’s Academy. That's how we learned the system. We actually learned it in six weeks and then started the development after that. It's very powerful and I continue to use it today.

It’s helped employees get up to speed with the product. This is especially useful when we get newer versions or we onboard other people. That's part of our syllabus. The first thing a new user has to do is go to the Academy and take some of the classes that we recommend. Then we identify, “okay, did you like it? Is this for you? Is it not for you?” et cetera. It’s a quick win where we don't have to take our time as we've got other work that we have to get completed. It acts as a filtering system for us. Both us and the employee can see if it’s a good fit very quickly. We can find out at an early stage instead of a year later.

The biggest value of the Academy is just knowing that we can do so much more volume and get in some more accurately without human error, or having people working nights and weekends. That has always been a really big push and we've been able to slowly work away from that.

Obviously, we’re not in a perfect world yet, however, getting rid of the manual aspect has been great. People just get burnt out. You can only look at things manually for so many hours. If you've been doing this for 10 years, it's got to be frustrating for those people who are always afraid they’ll get their job taken away. At the same time, for them, it’s so much easier as they don’t have to look at 80 things. They can look at five things that failed and then enjoy time with family and have a work-life balance. That’s big.

We've coded up to like 80% of what's possible. We really cut our pain points and said "this gives us our value, our bang for our buck." What we're doing now is saying, "okay, well, how do we improve it?" We've got another area or we've got another part of the software that we use our application that UiPath interacts with. Right now, our main concern is what else we can do to make it even more accurate or get more information or test more information to make it a solid pro program.

I'm a developer and I'll move things around and they'll change order, or I'll try to save something and it won't save the first time. I'll have to open something twice, open something three times. I've got a list. I'm working out quirks with UiPath. There are just UX things where if I copy this and put it here, it should look the same as it was, and I don't know why it doesn't. It could be my machine. It could be my local machine and it might just be that conversation with the premium plus to say, "why is this doing this?" Or maybe there could just be a setting, where we didn't check that box when we set it up. 

I've used the solution for two years. 

We actually had to spend about four months of maintenance to make sure that we got the solution to how we wanted it. We brought in a contracting firm and they didn't know the company and they just kind of said, "here's what bots can do." 

What we did is we did an assessment program for two months. During those two months, we looked at what they built, which was great. This got us up and running and showed us what's possible. 

Then, we took those two months to identify, for example, if the database maybe should have been set up a little better to interact with our other databases. Or if the coding should have had different paths of risk that they didn't know about. If you don't know the business, you don't know the risks, and therefore, you don't know how to set it up. That's why we did all of that assessment and then we spent four months fixing it to adjust to what we thought was a better path or a more stable path in order to support the robots.

The scalability potential is astronomical. We've got so many areas in the company, including finance and pharmacy, and there are all kinds of different areas and authorizations that you can actually go down and say, okay, now we have time. Let's put it on our calendar. 

The next piece we're looking into is the citizen developer angle. We know that has some power potential, however, we have to have regulations and audits. We want to be careful if we do start moving in that direction to really understand if it is right for the company and is helping people versus if we build something wrong what that would mean to manually have to correct that. That's time nobody has.

Technical support has been great. We usually get answers within hours of a request. I thought we were on the premium support plan and now we're going to go to the premium plus, I believe they call it. That starts up here for us in November.

We've had some challenging solutions where it has taken us several weeks to work through it. They tell us "here's what we recommended". That said, we know our system. It's just like any other contracting firm. They don't know your system and your solutions, however, they give you the recommendations. At this point, we've been able to work through everything that we've had technical issues with. We decide to do some of them a different way. Technical support has been supportive of this approach. It's like a partnership, and that really makes a big difference.

We started with Rational Robot in 2005. I actually developed that. I've been with the company for over 20 years. I started with Rational Robot and then we moved to some C Sharp and some coded UI.

We tried Test Architect for a little while. We've used different RPA methodologies and UiPath seemed to fit a little better with where we are and the robustness we wanted.

We switched when we moved over to new healthcare software. The old one was just COBOL and green screens, and it was hard to automate it. We did, however, it was very difficult. When we moved to this new application, we needed to make everything more quality controlled, and the only way to do that was with the robots.

I was not a part of the implementation process. 

The deployment process took about eight or nine months via our vendor. 

We brought on some contractors to do our initial setup, including a proof of concept, and they built part of the system and after that, we took it over. They were what we called a vendor tracking firm.

We have definitely seen an ROI.

The biggest ROI was in the configuration. We're realizing we may be setting some things up wrong and that's not how the customer should have been set up. When we see things fail, we ask why is this failing? And then we go upstream and find out that we didn't even build a specific thing and realize that it was a mistake, a key entry, a mistype, et cetera, and the bots catch that on the backend.

We're able to do that quicker. It's manual labor and it's tedious. Now, manual labor's fine if you want to go in and manually check this, that, and the other thing, however, when that's your day job and you're checking the same 80 fields compared to a spreadsheet over and over, it's just got to be frustrating and employees feel it. You hear it on the call.

With UiPath, we can ask the question "what can we do to support you?" We're not going to replace people; we want to get them to a better place. Our employees understand that. It took them a while, however, they do understand that now and think the solution is really cool and are thankful for the support. It's a tool, not a human being's replacement. 

I don't write the checks. I don't know what the actual cost is. That's always on leadership. My understanding is it's a reasonable price for the value that we're getting out of it.

We did look at the Power Automate desktop. It doesn't have the orchestrator to control things, and it has some other limits. When we do formulas and try to validate what the value should be, they are very difficult or impossible to set up on the Power Automate. At some point in time, I'm sure we'll be able to do that. In today's world, what we need right now is UiPath.

We're just a customer and an end-user.

We do not use the solution’s AI functionality in our automation program. We just do some checks and then just make sure via verification that everything matches in the configuration to the actual claims from the inbound files to the outbound.

There's an automation hub, test, capture, process, mining, all of these other features we haven't been able to purchase yet, due to the fact that we want to make sure that our bread and butter, the claims of membership, is solid. Once we have that in a good place, which we're hoping will be in 2022, we've already talked to our sales rep about the next steps. They've talked about the other features and offered recommendations. We'll go down that path next year and it'll be really exciting to see what else we can do to bring on the other areas of the company.

I'd advise potential new users that they definitely want to do some kind of proof of concept against other systems. I have heard other companies here that have said, okay, we're going up against four other automation tools. That's great. However, do your homework. You need to go and present everything to your leadership and showcase the solutions. 

As we get some of the demos of software, we can kind of compare them to what our system's needs are. A new user can say, well, maybe these are our top two. When you get to your top two, that's your time to bring somebody in, an expert to discuss what you're trying to do.  

If you do choose to go with UiPath, that UiPath academy is so valuable. That's a big asset. If you do the premium plus care, they will support you through and help you get things set up and running or make it better. We've been up and running for two years. Their goal and my goal is to see how to make things better to continuously improve the system and make everyone happy.

I'd rate the solution at a nine out of ten. There are just a few system quirks I'm trying to work through.