UiPath Reviews

We are using Studio and Orchestrator, and we purchased an unattended bot.

Our UiPath is integrated with Kibana, which is a free tool.

Our primary use of this solution is to automate manual processes. We have approximately eighty use cases to automate.

The RPA team includes two developers, a manger, and two BPOs.

We run automations in a virtual environment, but I am not familiar with the details.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a five. We just drag and drop. If you want to write something we use "Type Into". If you want to click, we use the corresponding click application. For me, it's very easy, and we also have tutorials available on the UiPath website. That is something that is very useful for everyone who wants to learn, and even a non-programmer can start learning to become a developer.

The Academy RPA training was very beneficial and I would rate it a five out of five. You cannot skip one step. There are ten sections and you cannot skip any of them. It means that until you pass a certain test, it will not allow you to go to the next lesson. This restricts people from jumping directly into another section. I really like the training and it is very easy. The tutorials are not very lengthy, they are simple, and the way they are explained is relatable. The practice tests that were conducted at the end were really helpful.

We partnered with IVy to create our first two pilot bots, and from the point that we purchased our UiPath license until we had our first robot was approximately six months. It was very easy because they helped us.

This solution obviously helps us when it comes to eliminating human errors. I cannot estimate the percentage, but our company is manual process-intensive. We have a lot of manual processes like invoicing, where we have a process with the business team. They pull out an invoice number and a purchase order number from a PDF, and the source PDF is not structured. When it was being done manually, they had encountered issues entering data into one of their applications. This is one place where human errors have been reduced.

Using this solution has saved us time. For example, we have a huge process and I have heard that it saves us millions of dollars every year. Each human takes forty hours to complete the task, whereas it takes the unattended bot between ten and fifteen minutes.

Any savings in time for humans gives them time to work on something else.

The most valuable feature in Studio is the macros. They are very useful but at the same time, it depends on how we write them.

UiPath is very easy to learn.

When we deploy code into Orchestrator, sometimes there are macro activities that worked in Studio but do not work correctly in production. For example, I have implemented a Text Reading Activity that worked fine in Studio, but after deploying the code into Orchestrator it does not read the text exactly. I was able to create a workaround by using a split function in the code. It was reading the text fine because the data is being read using split functions, but this is something that I would like to see fixed.

I would like to see more AI and natural language processing.

Having chatbots available would be a helpful inclusion in a future release of this solution.

Customer support and technical support are very nice. I would rate them a ten out of ten.

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

We partnered with IVy to assist us with the implementation. They helped us with two pilot bots. One of them was not up to the mark, so our CEO decided to have it reprogrammed. I would rate them a four out of five.

We have our own IT team that looks after connecting the servers with Orchestrator.

I am not updated regularly about how much money this solution saves us, but I have recently heard that we saved $400,000 USD in six months.

After our CEO decided to invest in RPA, we chose UiPath because it is easy to learn.

I have heard of Blue Prism and Automation Anywhere, but I have not learned them or worked with them.

We are looking forward to the new tools, and when they launch, we are definitely going to use them.

My advice to anybody who is implementing this solution is to speak with UiPath. Many people do not know how to start. The basic things they should have are a proper PDD (Process design document) and a recording of the manual process. These two things are essential. It is also very important to hire the right partner if you do not have your own developers because some of them are not up to the mark.

This solution is simple and easy to implement. I know there are lots of new features coming and every year they are providing good solutions with every release. There is always something new that minimized errors in previous versions.

I would rate this solution a nine out of ten.

We have a bunch of uses for the product so it is hard to judge which is the most important. We started working with data structures for websites and then moved into more complex automation like speech detection and making more cognitive decisions based on rules. Our automation using bots is essentially on the verge of using artificial intelligence.

There are a lot of ways this product has improved our organization. Even a simple project can bring us a lot of recognition. One example is retrieving passwords on Amazon. Imagine that you have a user who forgets their password. Amazon lets you reset your password but there are a lot of steps. In the background, Amazon is validating that you are the person that you are saying that you are with a lot of manual steps. We automated that with a bot and other tools and the customer experience skyrocketed. We reduced the processing by five minutes just for that service. Not only did we apply that solution for one country, but we also applied it to seven different countries. It was a success story.

What I think is the best thing about UiPath is that it is fairly easy to understand and learn how to use it. One of the most valuable things about the product is the improvement they are making with the tools. They are offering around thirteen new products now. With these additions, there is a lot of value-added enhancement that we can provide via the automation to augment what we already have implemented.

The studio's Orchestrator is the tool that we use in order to create the scripts for the bot. It is what enables us to deliver automation. Having these new technologies within the studio is what enables us to be more creative. With the Orchestrator we can monitor the bots, we can "orchestrate" them, and we can deliver that tool to customers so that they can manage their bots. It is really like digital workforce management. If we created a bot for a business, usually it would just do its job and the customer would not see what the bots are really doing. With this tool, the client has that opportunity to see what the bots are doing. 

The bots automate the work that otherwise would have to be done with other interventions and resources, so reallocation of resources and focus is the most valuable thing overall.

There are a lot of things that can be done to the product to make it better. The feature list that I develop between releases is often covered new releases of the product. That is good. But there are still a lot of enhancements that I would like to have within the Orchestrator and the queues. For example, how we manage the queues is an important thing.

I would like to see the ability to have other ways to look for one transaction within the queue. If I am looking for a single transaction, it would be good to have a filter that you can use to specify a detail, like just looking for a reference name that starts with a particular letter — but not the entire reference, but wildcards. Those are the kind of things that can be enhanced and make a big difference. Maybe they are not on the roadmap for the company when it comes to upgrades at this point because those are tiny things within the tools. But even those tiny little things can make a lot of difference in the functionality of the tools.

On a scale of one to five where five is the best and one is the worst, I would rate the stability of this platform a five. The stability of the platform is very good. During the four years that we have been working with UiPath, we have not encountered any issues with stability because of the platform. There are always issues with the environment and that can affect stability and performance, but with the platform itself, there are no issues.

Within the RPA suite, we have around 40 people working with the product. But we also have to consider that we usually engage people from other places to contribute to every single project. There are a lot more users than are working with us within the project and within our immediate company team. The peripheral people are going to be people from security, people from IT, people with specific business backgrounds, etcetera. The number of users and the product itself are scalable.

The technical support is actually pretty good. We worked a lot with our CSM (Customer Service Management). They are always doing a great job to find someone to help us out when we have issues. They get the right person for the right issue. For now, if I had to rate it from one to five where five is the best, it is going to be a five.

At the beginning, we would try to automate tasks using spreadsheets where we had calculations. We had macros and things of that sort to automate small tasks. The next step in moving to a new era was to turn to RPAs. There were a lot of things that we needed to implement through this new technology. So we did have another solution before for some types of automation but it wasn't really a dedicated system for automation and it wasn't capable of this scale.

We have a turn-around time of four to six weeks. In order to go to implementation and production, it depends on the complexity of the project. A normal project that is not that complex will obviously take less time. We have to take into consideration the time that we have in assessment, in the evaluation of the project, and in development, and only after that do we do testing to put it into production.

There are, of course, always challenges, but not all of them come because of the UiPath platform. There's a lot of things that are an issue because of the environment or the target applications that we're using. It is often more because of that than the platform itself.

We have in-house developers, we have a QA team, and we have a training and communication team specifically for the RPA suite. We also have managers for the teams, the support team, and solution architects. We do our own implementations and assist others in doing theirs.

We usually try to calculate return on investment within a year or two depending on the project. But we start to look at the benefits from the first month we put the product into production. Not really the ROI exactly, but the benefits. What I mean by benefit is if the automation is achieving the goals it was intended to achieve. Once we pass through the cost of implementation, license cost and any additional expenditure of resources, then we look into ROI.

We have seen a lot of benefits in a variety of ways depending on the projects. Most of what we have been seeing is capacity creation. There are a lot of things that can be introduced to automate processes. If there is work that can't be handled by a team and they are not going to meet SLA (Service Level Agreement), creating bots and putting bots into their team to take over redundant tasks is letting the team use resources differently. It creates additional capacity so the team can focus on more important things — like quality or process. That enables the business unit to accomplish their tasks while raising quality. The bot can always be depended on to do a specific task in the same way. If we have the right steps and if we have the right process to execute, the output from the bot is going to be right. That is another incredible benefit. Of course and for example, giving the customer a response in one hour instead of five hours enhances the customer experience. Proper use of automation can do all of these things.

Bots can also be used in eliminating human errors. Being cautious in estimating that, it could be as much as a 60% to 80% reduction. It will be reducing human error, but there is always some level of error in processing.

The percentage of time saved using UiPath bots depends on the projects, but most processes can save teams 85% of the time they would spend on tasks that can be automated. Some other automated tasks we have the efficiency go up to 90 or 95%. That is pretty good and a great way to allow for the reallocation of resources.

The cost depends on how many licenses we have and how we use the bots. We have a rate for attended bots and a rate for unattended bots. The price itself depends on the project and the number of licenses required. The prices, in general, are good — actually they are the best — but they could always be cheaper. Right now there is no one that is cheaper. The cost is in line with what we thought that it should be.

In 2016, we started to evaluate vendors. We went through Automation Anywhere and a lot of the competing products. We decided to go with UiPath not only because of the cost and the model that they have, but also the relationship that they have with customers. They actually care for you. They are always looking to provide you with the newest and best technologies. They try to make you use it in the best ways and they try to make you test out new features and provide feedback. If you need it and you realize that it's really good, then they help you make it happen. That is the best thing. They are being humble even though they are growing a lot. It is what actually made us go through UiPath.

We are using the entire UiPath tool. We are using the studios, we are using the orchestrator, we are using the bots. That is both unattended and attended bots.

We have two different environments. One is on-prem within Costa Rica data center and then we have another in the U.S. that is on an internal cloud and we use VDI (Virtual Desktop Infrastructure) and Citrix.

The virtual environment is actually pretty functional. There are some pros and cons. The pro is that it enables you to add virtual machines if you need them. The con might be that sometimes you need to enable connections that are not enabled. You might have to go through firewalls, go through network issues, etcetera. With that, it is a little bit more complex to build out automation sometimes. You have to go through configuration hurdles when you encounter them.

On a scale of one to five with five being very easy and one being very hard, I would rate the ease of use of the platform as a five. It is a five because when comparing it with the other RPA (Robotic Process Automation) platforms, it is easier to navigate within the studio and it is more comprehensive. There is a saying in usability that if you need to take more than five clicks in order to find what you're looking for, it is not easy. Finding what you want in one or two clicks is what makes a product easy to use.

We use UiPath Academy RPA training all the time. Every new employee or intern that we employ in our company goes through the RPA academy training first. That is kind of the bible for us. On a scale of one to five, five being very beneficial and one being not beneficial at all, I would rate the academy as a five. 

My advice for anyone considering this solution is very simple: It is worth it, go ahead and give it a try. You will like it. Try to experience everything within UiPath and go through every single feature that they have and can provide currently before you commit to it. The company's support will back you up and they will make sure that you find what you are looking for.

On a scale of one to ten, where ten is the best and one is the worst, I would rate the product as an eight. To get a ten, a product should be perfect. Nothing is perfect. It is not a nine because it is just a cautious rating. In technology, we always say that for every question there is an answer that says "depending on...[something]". Depending on what you're looking at, it is going to be an eight or it's going to be a nine. It should never be a ten.

We're starting within our finance group, so a lot of different processes in our finance group are being automated. Our main project was for our tax department, extracting data from PDFs and putting them into Excel.

We have two people involved with RPA in our company.

We just purchased this solution last week so we're still installing everything. We did automate four processes with the community edition. The length of time in development varied by the process. The longer ones required help from UiPath. They came on-site for the PoC, so that helped us out. Some other easy ones we just did ourselves within a couple of days.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would say that it is a four. But with Studio X, I think it will probably be a five. I say four because as you get more complicated with your processes, you need to learn how to code and there's a brunt learning curve. A lot of people will get turned off by that. So, I made some good sessions with Studio X, it's all drag and drop, mostly, so that's perfect for the business users.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. We are actually in the process of taking it right now. It's good that they have something like that available. There are not that many who have aced it.

So far we haven't gone too far, but I expect that people will be a lot happier because they won't be doing the jobs that they don't like doing. They'll have more time to learn and up-skill technologies like this, which can help further their careers rather than just learning, or not learning by copying and pasting.

The most valuable feature is automating processes and tasks, giving users time for more value-added activities. This results in cost savings.

The free community edition allowed us to test out the technology before investing in it.

I would like a better ability to connect and integrate with other software systems. An example would be integration with data and business intelligence tools. I don't think they have a native connector yet. So, just something that a user can connect, and have RPA in the middle, would be helpful.

I would also like to see an easier UI for the user. It may have already been taken care of with Studio X, but I think if they keep improving that, it's going to get a lot of people interested because users are attracted to it.

We were just using community edition for about six months.

With respect to the stability, on a scale from one to five, I would rate this solution a five. I mean we haven't used it too much so we haven't really pushed the boundaries, but for the stuff we've, done I would say it is stable.

Their sales and pre-sales support is very good. They've been very willing to come onsite and help us out and help with our pilot as well.

We got introduced by RPA from PWC. They came and talked at one of our finance summits.

The paid version, I'm still learning how to use, how to connect everything together. There is still a little learning period for that as well. Learning how Orchestrator works, how the licensing works and things like that, were necessary after using the community edition.

UiPath helped us with our PoC and they were great. I mean they came for free and through just a pilot or a proof of concept. We could actually see if the technology works for a use case.

Before we start anything we evaluate the process and we take down how many hours it saves, the costs, and ROI. In our main project, it took someone approximately three hundred hours a year to do all that data extraction, data input, and that also came along with errors because someone could fat-finger the value.

Then, through the PoC, they're able to turn around within two days. A bot can basically do that entire process and do it error-free as well.

It is a savings of three-hundred hours, and the cost savings is a multiplier of hourly pay.

We also use it as an ETL tool sometimes, so instead of paying for an API connection, we can use RPA. Simply just to run a simple report of the system.

I don't have any other software vendors to compare it to, but I would say if you're fully utilizing it then there's definitely an ROI in it. Obviously, if you have only one process running five minutes a day with the bot, it's not worth it. For us, what we did was we built enough use cases before we bought that enterprise license to make the ROI on it. We've got eight or ten and then we realized that we can cover that license cost easily with ROI before we purchased it.

Ultimately, we realized ROI within six months.

We got purchased the basic minimum package and it was around $35,000 USD, annually.

We tested out Kryon RPA, and we looked but did not test Automation Anywhere and Blue Prism. Those two were out of our price range, and at that time, neither of them had a free community edition, so we couldn't test out the technology.

UiPath sort of fit our company well because it was priced reasonably, and they also had a free version so we could test out the technology. Ultimately, we chose UiPath because of the price. It was not as expensive as Blue Prism or Automation Anywhere. It has a free community version where you can test new technology, which was huge. They also have a local office next to us so we can get their help pretty easily.

They have announced features in the next release, and I think that they are all the things that users would want. There are easier ways to document processes and a better and more user-friendly UI. A lot of people just got turned off by having to learn code. So that was a lot easier, and then being able to track all your RPA projects and the ROI on them saves time. Doing them manually is time-consuming. Fortunately, we're a small company because I couldn't imagine if you're trying to implement this for a bigger company.

My advice for anybody who is researching this solution is to, first of all, do their own research on the ratings and independent research. Secondly, I would just say a lot of them now have free community editions, so there's nothing holding you back from testing out the technology and seeing if it works. I think Blue Prism is the only one that doesn't have it now. That's a really high cost and a barrier to seeing if the technology works. Just going and validating the software and doing a simple automation task is important. All of those vendors have free training so you can just go step-by-step and learn something. I think that's the biggest thing someone can do, and then obviously finding enough processes within your company as well.

This is a good solution but there is always room for improvement.

I would rate this solution a nine out of ten.

Right now, the primary use case is document retrieval from our client system. We are a healthcare billing company, so we have to pull things like medical records and different documents from hospital stays. So, we used the robots to pull those versus an FTE.

We have both unintended and attended robotics that we use. We haven't really delved into Studio a lot yet. That's going to be part of our staging and going into the next phase. We built all of our basic bots, so now we're going into the more complex bots.

We are on-premise. We were looking at moving to the cloud, so that will be something in our next steps.

It has a really good turnaround time for our operations department to start working on claims, because all the information has already been pulled upfront with the bots. Instead of having to go into an account and request medical records or a certain type of document, it's normally already been pulled on the front-end as soon as the account loads because we run everything through the bots.

The most valuable feature right now is we have been able to utilize our staff better with the bots. We can put them on more high priority items. That was the one thing that everyone was afraid of: The bots would replace them. What we did is retrain them to do other tasks that we needed, as that was more of a priority for us.

We do deal somewhat with Citrix. It depends on the client and how the bot has to be set up. We have some clients who do run through Citrix, then we have some who use a VPN tunnel to get in. So, we have it on both.

The implementations or integrations through Citrix are really good. The only problem that we are coming across is just maintenance. If the Citrix platform gets updated and we're not notified, it breaks. So, we have to reconfigure our bot to the new updates. Unfortunately, that's just the name of the game, and that would be true if we were pulling them manually versus a bot. We would still run into that with the Citrix platforms.

I would rate stability as a five (out of five). We have not actually had any issues with UiPath. Most of our issues have been with just platforms changing, breaking, and the regular maintenance.

We have about 40 bots right now with 30 ready to be made.

Our team is really small. We have roughly six people who are working with the developers and actually running the bots. We're the only department using the solution. Our department was asked to lead this on, so we've been very fortunate to be able to lead it and be able to help our own department first. Now, we're starting to look at other areas of the company to deploy RPA.

We have not used UiPath technical support.

The initial setup was a little complex, but that was because we really didn't even know what we were getting into. We were told by upper management (our CFO) that automation was the next frontier and we had to go that route. We were sort of the pioneers going through this for our company,

It probably took about six to eight weeks for us to talk with development and for them to get the context of what we wanted. It took them about five weeks to actually build the bot. Then, once they built the bot, it was in production. Of course, we had to go back and do some maintenance because it did not work first time. After we got the hang of it, it's been great.

We got some consulting from UiPath. We do use their developers. Other than that, we do not go through a third-party. We did everything else ourselves.

Our experience with UiPath services was good. There were some bumps along the way. It's just trying to understand the process and RPA from what we've seen.

It took us about six months to really see what the bots could do. We then started tracking financial savings and how it's helping the company. We set out a bit differently. Our CFO came out, and said, "Automation is where we're going," but on top of that, "This is X amount of money that you have to save in the process."

We have spent the last 18 months tracking how much we are spending and how much we're saving. We hit the goal with no problems because we were able to shift staff. We did eliminate some staff, but this solution really brought out the skill level of our employees. Those employees with the higher skills were able to transfer to more important projects.

Within the first year, we saved a little over $600,000. That totaled to almost 19 FTEs which we ended up saving.

We haven't used any other vendors.

We are on spreadsheets and data. I keep saying we're stuck in 1996. It's been nice to have the vision of being able to be in the 21st century and really be able to use the bots the way we want to use them.

We have not taken part in the UiPath training. That's something that we talked about right before this conference. We really need to start utilizing more of the training that's offered. We want to turn some of our soft coders into people who can really code for us, not always relying on developers to do all of our work. That's definitely something that we're implementing soon.

I would rate it at least a four (out of five) for ease of use. We don't deal so much with UiPath, but from what we do deal with outside of developers, we have not had any problems. It has been very user-friendly, for those of us that don't know coding. We are able to look at things, sort of fix things, etc.

I rated them a four for ease of use, not a five, because we want to see what UiPath can do. We have a lot on the table. We have 30 bots ready to go. A lot of it's more screen scraping, which will be more complex. So, we want to see really if UiPath can do what they say the solution can do. We want to test its scalability.

I definitely would say UiPath is the way, especially with everything that they're coming out with now. It helps you understand more about RPA instead of just being thrown into things. It helps you understand all that on a smaller level. It is what everyone else has said here at the conference too, "Start with a small project. Don't go out with a big thing because it's not going to work." Luckily, we did start small, and we've just grown from there. Those would be my suggestions.

I would rate the solution a 10 out of 10.

We use it to automate administrative functions, like finance and HR tasks. We are also automating a lot of things in our SAP systems, e.g. updating prices. 

We use it for a lot of small tasks, like downloading something from an particular internal website (e.g., SharePoint in Office 365) and uploading it back, or for doing modifications, then loading them back.

We use it in a very large way across the company. Last year, we implemented approximately 22 processes and saved close to 80,000 hours total. This year, we have already saved close to 6000 hours. 

You don't need to know coding, as it's pretty straightforward. The graphical user interface is easy to use. It is drag and drop. You do need to understand the basics of what's happening, what you're doing, and how the technical things work. However, after a short bit of training, you can start doing stuff, and the more you learn, the better you become. 

There are so many workarounds. It allows you to do complicated things in such an easy way. UiPath has provided so many APIs that make it easy to interact with other databases or applications without even going into them. If I want to download something from a website, then I don't need to necessarily go into it, I can use the API function, which is very cool.

With Excel applications, it is not able to handle a lot of pop ups. It should be able to do this automatically. We just change the format of the file from XLSX to XLS, but it should be able to handle this automatically. Instead, when something pops up, it gets stuck there. This type of thing are small, but still the process gets stuck. I would like to see better integration of applications to avoid these issues.

We are also making a lot of manual changes in SAP. We are looking for a solution where we don't have to make manual corrections every time, similar to what UiPath did with some SharePoint websites.

Less than one year.

The product is definitely reliable. It gets the job done. The difference is in how you design it. When you start as a developer, you tend to always take the longest route as part of the learning process. Once you get used to the product, you realize something can be done in two steps instead of five.

A lot of people rely on what I design, so if it doesn't work, I immediately get a call that 50 people are waiting for something. This happens, but rarely, as it works perfectly.

Whenever we get stuck on something and are not able to proceed, then we get in touch with UiPath, who will help us out. Their technical support staff is pretty good. These things really help the user out.

Initially, I used the UiPath Academy when I didn't know anything. At that time, I went through the basic training, then I had to leave the academy to focus on automating our company standard products, like SAP.

I have been working with this solution for 11 months. I did not know about this solution before working as an RPA Developer. Now, you can challenge me on anything UiPath related, and I will find a solution. It is so easy to learn new things. It has good usability.

We automate mostly finance processes, which is our largest area. We also automate some HR and logistic IT processes.

We hear from the process owners that they are very happy with the lead time and data quality, which keeps getting better. 

It is very easy to use, and you still have a lot of possibilities to modify what you are trying to do and achieve. 

We would like more API integrations, especially more API connections to SAP. While this is on the roadmap already, activities and packages with more automated API connections to other software or platforms would really help us.

Documentation-wise, UiPath could get a little better.

The support that we are receiving from UiPath is superb.

We are using the UiPath Academy. We also have our own development standards. When we are recruiting new developers, we first have an introduction of our own that we make. It's mostly to Orchestrator and our environment, then we set them free at the UiPath Academy to do training there. Afterwards, we do some additional training to our standards and best practices. So, part of our training is in the UiPath Academy, and we are using it. We have been very happy with it. It's evolving all the time, which is really good

One place that we struggled was when we were uploading the software. UiPath was helpful with getting started, setting up the server, and installing the robots. All that went pretty smoothly. Every time, when we have upgraded, except for the last time, we have struggled. We did not do it right once. We always had to retry, get some support with it, and the documentation was a little lagging. Therefore, we really struggled with upgrading. It's getting a lot better now, but this has been one place where we have struggled.

Annually, the product saves us 25,000 hours. Everyone is satisfied with that.

We have had our contract with UiPath since November 2016. 

We have had a few presentations from Kapow. They have dynamic licensing, which is something that we would really like to have, so we could scale up at peak hours or peak times of the month. This is when we really need to throw more robots at some processes. To my knowledge, that is not possible with UiPath at the moment. Though we are not considering switching at the moment.

Our primary use case is IDP. We're in the Fed market, so a lot of it is all IDP driven. AI and automation are priorities. We're not exclusively a UiPath shop, but we're shifting to utilize it more because we know there are opportunities, especially in the realm of document capture.

For us, it requires fewer resources, and the time to get to the production environment is quicker. It hasn't significantly impacted our stakeholders yet, but people know the brand. When we talk with customers, they ask if we know about about UiPath and if we're a partner. 

We're moving away from the current platforms because they're less robust. The RPA tools we've used previously haven't kept up with the pace of change. UiPath is a leader that has continued to progress with RPA development and invest in improvements. 

We're still in the early stages with UiPath, but two things that will help are the Copilot and the Autopilot. We'll be able to generate new processes based on the learning that's taken place. It will have a significant impact on the things we do. Generative AI is not new to us. We've had these discussions for a while, and our CEO is well-versed in generative AI. Software companies are coming to realize the value and implement it. 

UiPath has spent the money on research and generating libraries. The out-of-the-box libraries are extensive. In the past, we used standard capture products, where we had to create all of the extractions in the zones and all those things. UiPath offers faster implementation. 

UiPath's pricing could be improved. The margins for us as a bottom-level tier partner are not great, which can be a hindrance, particularly when we present it to the customer. Other than that, I don't have any areas of improvement at the moment due to our limited experience. Maybe after six months to a year, we might have more feedback.

I have been using UiPath for several years, although I only started with this company a couple of months ago. Previously, I led a team for four years with another organization.

The stability of the solution has been good. I haven't experienced any platform issues. Any issues that arise typically relate to coding or interactions with third-party vendors.

Reflecting on my previous organization, UiPath was able to scale effectively.

I rate UiPath support eight out of 10. My previous experience with UiPath's customer service was really good. The support from the sales and presales levels and the technical specialists was excellent. They were all willing to help and work with us.

Positive

We eventually switched from our previous solution because it did not keep up with the pace of change. The company did not invest in their product and failed to keep up with the latest and greatest technologies.

It's too early to tell if there's been a return on investment with UiPath.

Pricing is a significant area for improvement. We see little margin as a bottom-level tier partner, which makes it challenging when communicating pricing to the customer.

I would rate UiPath an eight out of ten.

We're still in the exploration and discovery phase. We're learning about UiPath's capabilities and how they fit into the overall picture. We haven't separated AI from our normal process at this point. I work in our company's contact center, and we engage them in many different ways. We talk to management about their problems, report large volumes of transactions, and work side-by-side with the agency to find trouble cases and where they frequently perform manual tasks.

UiPath has helped our customer success unit and various technical teams. We were trying to understand the industry's current state and the direction our peers are taking. We're not so focused on eliminating positions as we are on using UiPath to free staff to work on additional tasks. There are always new tasks in the contact centers, and if we don't need to add staff, we can redirect them to other areas.

We were looking at implementing most of the features. I don't look at it with a specific lens but try to understand where all the tools are and how they can best help us in each situation. I don't have a favorite tool but try to understand how to use each one in combination to give the utmost business value.

Being able to escalate quickly is not a strength for UiPath and may be a focus area.

My department has been using UiPath for about two months.

The people from UiPath, from customer success to various technical teams, have been very helpful. When we open tickets, they respond quickly and escalate to the appropriate teams.

Positive

We did have a different solution. Deploying the solution to our agents' desktops was essential, and UiPath's advancement in that space and innovation position was enticing.

The initial deployment was fine. We had an on-premise deployment and weren't using the Automation Suite. It didn't work for us at the time. There wasn't a lot of flexibility there. I understand that it's changed, but we've already deployed on-prem. We've grown, and the complexity is through the roof, so now we think it's worth transitioning to an alternative solution.  That part has not been great, but at least there are places for us to go.

UiPath is expensive compared to competitors. We're examining where the value comes in and their ability to continue being a leader to justify the cost.

I rate UiPath eight out of 10.