I use UiPath to reduce any data entry, report generation, or anything where UiPath can help avoid human errors.

The solution is very user-friendly and easy to use. It comes with pre-built automation. The tutorials are very helpful.

I have been working with the product for six months.

The tool is stable.

UiPath is scalable.

The tool's support is helpful.

I use UiPath to reduce human errors during report generation or data entry. Simple errors can cause delays down the stream.

The product has helped us save hours, which can range from a few hours to tens of thousands of hours.

UiPath has helped us increase accuracy. It is helpful in data validation.

I rate it a ten out of ten.

My primary use case is mainframe automation from legacy mainframes that previously hadn't been automated with other automation tools. The product worked like a dream with the mainframe automation.

We're trying to get rid of the boring, mundane tasks that people do every day so that they can spend more time doing more important things like figuring out why there are issues happening rather than just putting a Band-Aid on.

In our first year of jumping into it, we set up the infrastructure and everything, so it's been less of a year of development, but we have saved a hundred thousand hours.

The automation efficiency depends on what the job at hand is and how much it saves. But some of the tasks done constantly throughout the day, even if it's only saving five minutes, add up really fast.

We use Task Capture all the time. We have a bank business analyst who uses it and teaches people how to use it. We're constantly getting process definition documents to review and add to our pipeline.

Studio itself has all its great features and is easy to use.

There are bugs here and there. My only complaint is that each time we open a new ticket, we get someone new and have to explain how everything is set up all over again.

It would be nice if they had that somewhere on record for support.

I have been using UiPath for two years.

It is a stable solution; everything seems to be running pretty smoothly altogether. The biggest issues are not on the UiPath end, but on our company's end like, network issues and issues like that keep popping up every now and then.

The support's been pretty decent. We have a TAM, so we have someone we are constantly in contact with.

We meet with them weekly, and they're very helpful. If we do have to open up a support ticket, there's a bigger issue that they can't help with. They usually help get the ball rolling.

Support has been pretty helpful. Like any other support though, they ask all the basic questions in the beginning just to figure out what has or hasn't been done.

My only complaint is that each time we open a new ticket, we get someone new, and we have to explain how everything is set up all over again. So it would be nice if they had that somewhere on record.

The initial setup was straightforward. There's plenty of documentation that is easy to follow.

The hardest part was more on our company's network and infrastructure, trying to navigate all the hoops that we have to go through just to make sure it's secure and the network's secure. Getting access to what we need to get access to.

We're still kind of new to things and working on migrating to the cloud. We're one small team in the organization. By moving to the cloud, we're hoping we can onboard more and more teams to be able to use it and spread it throughout the company.

UiPath helped us along the way.

There are other automation tools that the company uses, but they can't do everything that UiPath can. All of the potential automations just kept being pushed to the side until we started using it.

We used Microsoft Automate for a very short time. We started looking into it for some tasks. The issue is that we're trying to automate it deep inside our corporate network, so, we haven't really been able to use Power Automate.

Overall, I would rate the solution a nine out of ten. The amount we could do in one year is pretty impressive.

We use UiPath across a diverse range of functions and departments, encompassing accounting, human resources, loan servicing, employee progress tracking, and loan origination.

Our primary objective has always been to navigate the cycles effectively, ensuring that we can manage fluctuations without the need for constant hiring and downsizing. It's all about maintaining a consistent workforce over time.

The most valuable component is Studio—it's the cornerstone of our automation efforts. Recently, we've delved deeply into Insights, which has proven to be incredibly beneficial. Our key focus is on eliminating time-consuming tasks and enhancing reliability, especially in repetitive processes, which is where automation has proven to be a significant asset.

Simplification and adaptability for smaller businesses would be a welcome enhancement.

I have been using UiPath for approximately six years.

It is highly reliable, and we didn't have any issues with it.

When it comes to scalability, one aspect to consider is understanding the licensing for on-demand bots and related components. There have been some challenges, mostly on our side, particularly concerning high-density servers.

The ideal scaling strategy involves adding more instances to these servers. We have opted for standalone virtual machines for each partner, and while this approach offers scalability, it does require the manual setup of additional machines, which can be a slower process for a small IT team like ours.

I contacted customer support only once when we encountered an issue related to changing the institution name within an application. Fortunately, the support team was able to resolve the matter successfully. I would rate them ten out of ten.

We were using a software called Winautomation, which wasn't very robust. So, we made the decision to switch it, which has been a beneficial change.

The initial setup was relatively straightforward. The main challenge we encountered was obtaining security approvals when transitioning to on-cloud.

Initially, there was just one automation tool in place. Our first step was to rebuild that process using UiPath and then we engaged with various business teams to explain the concept of RPA and gather input to create an initial backlog. Afterward, we collaborated with management to prioritize the tasks and determine the order in which we should proceed.

I find the licensing structure to be perplexing, and it frequently changes. The inclusion of AI units, raw document units, and Cloudmont licensing, along with various sub-licensing options, can be quite complex and non-intuitive.

We were considering a few alternatives, such as Blue Prism and Automation Anywhere. The primary goal was to find a solution that we could commit to for the long term. Ultimately, it appeared that UiPath, which is an industry standard, was the best choice. I also had previous experience with it at a previous company, which made the transition more comfortable for me.

Overall, I would rate UiPath ten out of ten.

The process is for background checks. There are all kinds of checks such as academic, criminal, and work as well. We receive all the volume through the queues. We are using the citizen developer, StudioX, to get the cases and understand what are the fields and what are the requirements for each one of the cases. The bot will process them accordingly. For example, for each university or academic, there is a different process around the world.

The industry we use it for is HR. What we do with the backgrounds is providing a confirmation to our clients that people have the qualifications that they say they have. It is for data accuracy and consistency within the HR and talent acquisition departments.

Our AI-powered automation initiative has not yet changed what our organization is able to achieve because the project is still a pilot. We are still working a little bit on the environment. We are working through VDI, so it is not straightforward. We cannot just install or put UiPath to work. So far, we have not seen all the results, but we are looking forward to that in the next quarter.

UiPath would definitely free up time or resources for other tasks. We are a team of six people. We are estimating that two of them will be free for new projects. There is about 30% of resource savings.

Our usage is very simple. We have been getting the text, parsing it, and trying to categorize and analyze it. We are not using it fully, but the OCR is very important. This is a package from StudioX. With OCR, we will implement document reviews to make sure that whatever the applicant puts in the form is consistent with the document provided. For example, in academics, it will be your bachelor's or master's certificate.

The value proposition of implementing UiPath is that if we use UiPath and the RPA functionality, instead of passing the process to a BPO, we will start understanding the process and automating it as much as possible. We will have hybrid workflows between humans and robots. We will create capacity. We will have the same number of workers but increased capacity. We will start having conversations with our stakeholders on how to reinvest all of this capacity that has been liberated.

We have had some issues with StudioX. In terms of features, for now, I am pretty happy with UiPath. The requirements of the process to be automated are covered with the basic functionality. It is not exactly UiPath, but for security reasons, we are not able to download packages and use the functionality provided by the community with their developments. It is not on the side of UiPath.

I was certified as a Citizen three years ago. That is the time frame that I have been using it.

Recently, there was a software update of StudioX. We had some bugs. I would rate it a five out of ten in terms of stability.

We are working on moving to the cloud, so scalability will be good.

We have internal support. I do not speak with the vendor. Our internal support system is pretty consistent. They have quick response times.

From my perspective, I do not think we have been using any other solution. We have been with UiPath for about eight years. I cannot confirm the number, but I know that we have been partners for a long time.

We also use AutoHotkey which is something similar but not a replacement. It is a software solution that allows you to reprogram your keyboard and put some functionality in there to automate some of the things, but it is not a replacement.

I was not involved in its deployment. It is on-prem right now. We are migrating the company to the GCP, so there may be some restraints in regard to that. Everything is currently on-prem, but we are working on going to the cloud.

The ROI would be in regard to the capacity. We estimate two FTEs to be free from this project.

We have not yet used UiPath's AI Center and many other features. We are using StudioX, so we are still in the citizen developer mode. We are not using the full functionality with Studio and all that. We have an RPA COE. They have much more complex processes and projects, but we have not used it for that. This UiPath convention has brought a lot of ideas in terms of how to start leveraging it more.

We have also not used UiPath Process Mining and Task Mining. I am working with one of my colleagues who is like a bridge between operations and IT. We are working together to see how we can better use the technology to improve processes. I have to go team by team, understand the process, and go deeper to see where we can start using this technology. We will have a roadmap of where we need to go.

Overall, I would rate UiPath an eight out of ten.

Our primary use case is more of a reactive ad hoc use case to solve business problems on the fly. We can build automations to update thousands of records.

We're putting a little bit more money and resources into it, and we're starting to go down more of the unattended automation path to actually do more end-to-end processes.

The use of AI has freed up time and resources for other tasks in our company. We are a little bit more of an ad hoc approach right now. I just finished up a new cross-set of processes about two weeks ago that allowed us to onboard a client. I wouldn't have been able to without this automation. It would have taken a couple of months of several people's time to get them to get all this work done in the back end.

It is helping. It provides value where we wouldn't be able to do certain things without it.

The broad functionality is the most valuable feature because it can interact with many different factors, and there are several ways to solve a problem.

There's not just one cookie-cutter way to achieve what you need to achieve. You can get there in various different ways. That's a key aspect for me.

From the UiPath product perspective, this might be a problem because we're on-prem, but they add new functionalities pretty rapidly. It feels like there are releases constantly, and I don't want to update it too often.

I feel like I'm behind even though I might not be. Sometimes, we'll go a year without doing any major upgrade to Studio or Orchestrate or anything.

That's more of a personal problem, but that's because there are frequent updates to understand.

We started using UiPath about three years ago. We're a small company, an 80-employee bank, in Denver, Colorado.

We're smaller than a typical RPA client. Our development is probably underutilized compared to larger institutions. Still, we thought it was important to get in the game early and start establishing the foundation of an RPA environment.

The stability is good. We have run into some issues that they believe are more related to their environment than to the application itself.

We're in the process right now of scaling. It is a scalable solution.

The customer service and support have been amazing. It is honestly the best product support.

I have no complaints about the support. I don't even get worried when I have a situation. I might need to open a case. I like partnering with them. It's a good experience.

The initial setup was difficult because I didn't have a lot of past experience setting up a new program. This was a whole new program for us. Not only was it installing things, but it was also wrapping your head around how to set up properly so that we can get out of this.

It was a little challenging, especially with the on-prem solution and working in Citrix, to make sure these different servers were talking to each other properly, but overall, it was not too bad.

We're on-prem right now, so we're not even in the automation cloud. We're looking into that in probably the next year. The UiPath platform has been great for getting to understand those products a little better.

I see a return on investment. Even with underdeveloped automation, we definitely have a good ROI.

If people don't understand the benefits, they might think it's a bit pricey, but for me, it's very cost-effective.

We looked at Automation Anywhere and Blue Prism. It was three years ago.

I work in banking. We are highly regulated in our server infrastructure, so we decided to do a VDI environment that works in Citrix.

At the time, UiPath seemed like the best product to work with Citrix which was a large reason why we chose UiPath.

We wanted to make sure we were getting something that was going to play nicely with our environment. It has proven to be true to this day.

We feel like we chose the right vendor.

Overall, I want to give it a ten out of ten. I have to give it an honest nine just because I haven't used other RPA solutions. But I love UiPath.

If you're going to go in, go all in. We didn't go all in at the beginning, and we should have. We're playing a little bit of catch-up because of that. My advice would be to go all in and be organized with your approach.

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.

My use cases for UiPath include finance, HR, SAP, and technology.

The tool's most valuable feature is RPA.

UiPath should improve its licensing structure.

I have been using the product since 2018.

The selectors and modern UI are not stable yet.

The product is scalable.

The tool's support is good.

The tool's deployment is straightforward. We started with contractors and built some POCs. We had a pilot to select the business criteria.

UiPath's implementation team helped us with the deployment.

The solution's pricing is a challenge. Every time I go to renew my contract, the prices increase. It is getting expensive.

The business objectives we tried to achieve with UiPath include time savings and user satisfaction.

Automation has freed up our employees' time.

I rate the solution a nine out of ten.

We use UiPath for marketing, accounting, and sales.

The solution has helped us save time.

I like the automation capabilities. I particularly like Autopilot and documentation.

We don't currently use AI Center or process mining, but we want to learn more about these features.

The support team could be more responsive and helpful.

I have been using UiPath for one year.

I would give the stability of UiPath a six out of ten. I've experienced some issues with it in the past.

I would rate the scalability a six out of ten.

I have had to contact the support team on a few occasions. It was a good experience. But the solution could be better with its support team.

We switched to UiPath because it's a better fit for enterprise companies like ours.

It might not be a good fit for smaller companies. It's a bit expensive for small companies, but it's worth the money for larger companies.

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

UiPath is an RPA solution that is very easy to use and local. It's a good choice for companies that are new to RPA or have limited resources for training.

We use the solution to pull documents from audit systems, download documents from document management systems, and grab data from financial management systems.

I like UiPath's framework. It offers a modern design experience, which makes it easy to do different activities.

The solution is expensive.

I have been using the product for four years.

The product is stable.

UiPath is scalable.

UiPath's support is great.

UiPath's deployment within our environment is complex. However, we have online resources available.

We have seen ROI with the tool's use.

The tool's pricing depends on its use. It is expensive.

Our business objective was to improve manual processes and increase efficiency.

Task Capture helps to build documentation.

UiPath has freed up our resources' time.

I rate it a ten out of ten.

We use UiPath to automate various processes across different functions within our organization including back-office operations, with a particular emphasis on finance, procurement, HR, and IT, as RPA technologies initially emerged from the finance sector.

Also, we extend our automation services to areas directly associated with production and supply chain operations.

Our primary goal is process automation, which lowers costs, enhances quality and improves operational flexibility. This is crucial due to our multi-time zone operations, requiring continuous processing. We're also dedicated to integrating various applications within the organization and addressing gaps. While engineering and IT departments have substantial automation, we're working on refining and addressing specific gaps in these areas.

The orchestration process itself offers a high level of impact, flexibility, and ease of development. While we have made significant improvements, particularly in terms of integrations and the seamless connection of integrators to applications, the process remains remarkably straightforward and efficient. It has significantly improved the accuracy of our operations, particularly in terms of quality, and has also reduced the time required.

There's room for enhancement, particularly in the support department and in the area of reporting, to provide a more robust product for gathering insights.

I have been working with UiPath for approximately five years.

The solution's stability is quite commendable and even when we encounter incidents, we consistently update to the latest versions. We typically lag about seven months behind the latest releases because it takes around three to four months for the new versions to stabilize after their initial release. I would rate it nine out of ten.

Scalability appears to be quite robust, especially when we have a solid model in place.

The improvement is needed for their support services. I would rate it seven out of ten.

The initial setup was relatively straightforward. Back then, we were using a standalone automation suite. While we now have a cloud-based automation suite, the transition wasn't complex, and we found it quite easy to implement.

We've seen a positive ROI. Our organization, with the assistance of skilled consultants, successfully implemented the system and we established a robust business model and have maintained a centralized approach.

We evaluated several solutions available at the time, all of which were related to end automation. Ultimately, we opted for UiPath and that decision was influenced by the learning opportunities offered through UiPath Academy. At the time, it appeared to have the most compelling value proposition, with a strong ability to market and demonstrate the product effectively compared to other options.

The ease of use depends on whether you're a developer or someone who mainly uses automation. Nowadays, it is much more user-friendly compared to when I first started using it back in the day. The landscape has evolved significantly with a wider range of solutions available today and they've made substantial improvements, especially in terms of document standards.

Overall, I would rate it eight out of ten.