My main use cases for UiPath Platform in my organization involve automating those manual tasks that people do all the time.

For example, we have processes that monitor email accounts that automatically pull down the documents associated with those emails and stores them where they need to or uploads them into a database. We have processes that go out to websites, grab information, and bring that down for any reporting purposes or to store in a database, etc. Those are pretty much the main kind of processes for the most part.

The use cases for Agent Builder involve an automation that we're currently working on for our owner relations department. They receive a ton of emails asking about various information about their ownership, or maybe needing to pass off their interest to a family member, or they've sold their interest. So this agent will receive those emails, get the context of that email, get the sentiment, and be able to route that email to the correct person or department that needs to handle that request. So it could be a revenue question, it could be a land question, it could be all sorts of different questions.

The features of UiPath Platform that I most appreciate include the great user interface, and I've really enjoyed using it as well as the ability to write your own code in there. You're not just stuck with the drag and drop, you can actually write your own.

We're starting to get into the Agentic processes, so that's been really cool seeing that, getting to know how it works and building out solutions with that.

I have realized huge benefits from using UiPath Platform overall, especially from Agentic Automation. For the email processing mentioned earlier, just this year, we've processed close to 400,000 emails, which equates to about 6,000 hours of employees' time. So that's a huge savings right now, just processing emails.

We've had processes that someone literally would spend two days out of the month submitting stuff online. That's all they did for two days. We've automated that where they don't touch it at all. They just get a confirmation email at the end of the month that it's been done.

UiPath Platform can be improved in the Studio Web deployment process, as it needs some work. Deploying the agents to the various environments seems not real polished yet. We've had some issues there just clearly understanding. If they put some focus on getting that clearly defined and a clearer process in place, that would definitely help.

I have been using UiPath Platform for approximately four years.

I would assess the stability and reliability of UiPath Platform and its bots as pretty good. We really haven't had any issues too much. We've had some connector issues recently. For the most part, the platform is pretty stable. It's never really hindered our business or anything like that.

As for how UiPath Platform scales with the growing needs of my company, it's not really applicable for the fact that we do all of our stuff on-prem. We have the Automation Cloud, but that's not really affecting where and how our bots run.

We're kind of at our own constraints at that point. We're able to scale pretty easily and set those new servers up within UiPath Platform relatively quick and easy.

If I used UiPath Platform support, I would evaluate it as not being great. Every company I've worked with, their support hasn't been great, and it tends to be the same way here.

We do have a technical account manager who's been great. So a lot of the stuff, we discuss with him and he may create a ticket or escalate in a way. When we have done support tickets, I provide all the information they need and then their first question is to provide the same information.

I don't feel they look at what you submit or what you're asking for. It's frustrating. It seems they have a script that they go by and that's all they do.

I'm really not sure what other RPA solutions were evaluated prior to UiPath Platform. I know in-house we have Microsoft Power Automate. Everything we've done in there, we've moved off and moved to UiPath Platform. We really prefer it.

A lot of the stuff in Power Automate requires premium connectors, while you don't have that issue in UiPath Platform. Things are just much more streamlined and easier to use in UiPath Platform. There's just a lot more flexibility with UiPath Platform and it's overall a better product, in my opinion.

My experience setting up UiPath Platform has been smooth.

The time saved extracting data points with Agentic AI is probably reducing at least 50% of the person's time that has to deal with this mailbox. They're no longer having to monitor it all the time. They're no longer having to create tickets in SAP to route things. All they're doing is confirming that it's doing what it's supposed to be doing, and that's it.

UiPath Platform was given to me. The business decided on it and they wanted it as a citizen dev platform. IT ended up having to take over and now we have our own development shop for UiPath Platform and the citizen dev is essentially no longer.

I would advise anyone considering UiPath Platform that it's a great platform. I would recommend it to anyone that's looking into getting into an automation platform.

Unfortunately, I haven't worked with too many other automation platforms. From what I've seen with UiPath Platform and what I've worked with, it's been great. I'm an advocate for it.

I would rate this platform a nine out of ten. It's easy to navigate and use, with many useful connectors and activities.

My main use cases for UiPath Platform include automating repetitive tasks, file transfers, and website interactions.

The features of UiPath Platform that I prefer most is the queue functionality, which really organizes and keeps track of what was successful and not. It's very helpful.

We have a process where we have to enter a website using UiPath Platform in general. Whenever the queue is empty, we actually go to a part of the website where we export all the items that the team would have to do manually, and that gets uploaded into the queue. When there's content in the queue, we start processing the transactions, which is when it starts doing what it has to do. Once that's done, it reads the queue again to see if it's empty. If it's empty, then we look at the website to see if there's more content to download or not.

Typically, whenever there is something to download, that means there's work the team has to do, creating a self-cycle where it checks to see if there's always something to do.

I have a few ideas on how UiPath Platform can be improved, however, they have fleeted from my mind.

I have been using UiPath Platform for three years.

I assess the stability and reliability of UiPath Platform as very strong. I have not experienced crashes or downtime. It's very reliable overall, although there's an ongoing issue with a selector that doesn't want to be read for one particular website, which we're addressing by submitting a ticket.

UiPath Platform scales beautifully with the growing needs of the organization.

We have expanded our usage of UiPath Platform, and the smoothness of that process is primarily found in developing processes and collaborating with stakeholders, ensuring everyone understands the growing transaction volumes that ultimately lift the team. However, the volume does increase significantly.

I love everyone in the customer service and technical support teams; they're great. I would rate the customer service and technical support I receive a ten out of ten.

Although we don't submit tickets too often, we work closely with the account technical help, and if I were to rate him and his team, they are always there to provide answers. If they don't have an answer right away, they come back with one after a few days.

Prior to using UiPath Platform, I was using another solution.

The deployment in general is really straightforward. The one thing that was an obstacle, from everyone I've talked to, is more of a compliance issue, an information security issue, and just getting them on board. Once you get the green light from that side and they green-light certain projects, deploying bots is very seamless.

As long as you know the basics and what you're trying to tackle, it's very straightforward to publish and run things in production.

I have seen a return on investment with UiPath Platform. For instance, one process I mentioned would take the team 50 tasks per day, which has ramped up to a substantial number of 500 to 600 tasks.

Even with 50 tasks per day, it would take them a whole day to complete it. There's no way they could have handled 500 tasks, however, the bot does it in less than half a day, and we have approximately 10 to 12 bots tackling that process.

I don't really handle the pricing.

My advice to another organization considering UiPath Platform is to be patient in getting your information security team on board; I had to be patient for about a year. But after that, being able to use the product was worth the wait. So step one is patience, and in the meantime, increase your team's knowledge on how to use the tool, which aligns with my earlier point on UiPath Academy being perfect and really good.

I would rate UiPath Platform as a nine out of ten.

My main use cases for UiPath Platform involve working within departments within our organization, discovering pain points, trying to automate those, and free their time up. That's what we were focused on for a while. Now we're trying to scale up, and hence why I'm here, to see what all the Agentic stuff is about.

From a developer standpoint, the features of UiPath Platform that I appreciate the most include the ease of building. They've made it a pretty simple tool. The features of UiPath Platform benefit our organization since we can go to production quickly. When we talk to a department, we identify a good use case for it, and it's rolling within a week or two.

I and my teams have used the vendor's UiPath Academy courses. The biggest benefits that I have seen from UiPath Academy are purely knowledge. We hit the ground running fast when we got into UiPath, so it's been a good resource.

In terms of the value that I gain by being part of UiPath Platform's user community, it's shared experiences. Being here, talking to other people in other financial services, has been helpful. If there's one thing my team talks about a lot regarding UiPath Platform, it is staying on top of updates.

In a perfect world regarding UiPath Platform, in Orchestrator, I could select a process and hit the "update all" button. There are some things coming down the line regarding licensing for UiPath Platform where our current license structure is being sunsetted. There's just a lot of confusion over that.

A little more clarification around licensing and how we can best take advantage of it for our organization's purposes would be helpful.

I have been using UiPath Platform for two and a half years.

I assess the stability and reliability of UiPath Platform as very stable. I have not experienced any downtime, crashes, or performance issues with UiPath Platform, not at the fault of UiPath.

UiPath Platform scales very well with the growing needs of my organization. I have expanded usage of UiPath Platform.

The process of expanding was fairly smooth. There are some hurdles that we had to overcome just with different business units and getting adoption going.

I evaluate customer service and technical support for UiPath Platform as pretty good since we have their premier support package.

On a scale from one to ten, I would rate customer service and technical support for UiPath Platform a ten. I have no complaints. They're just very expedient. They respond quickly. They're there when we need them.

When evaluating UiPath Platform, the aspects that stood out to me were that we were on Foxtrot prior, and it was changing hands, and we didn't want to be a part of that. We'd have to redo everything anyway. UiPath was also a leader in the market, so we wanted to be a part of that.

Before adopting UiPath Platform, I was using Foxtrot to address similar needs. The factors that led me to consider a change for UiPath Platform included that they were changing their platform and pricing. So we figured if we were going to have to do all this change anyway, we might as well assess what's out there.

The act of deployment was pretty seamless from my perspective. We have an engineering team that takes care of deploying, so I just turn it on.

I have definitely seen a return on investment with UiPath Platform. We have about 150 processes in production with UiPath Platform. The one department that has the majority of those processes has not had to hire anybody else for those two years. Their people are happy, and we've saved them money and the need for more people.

I personally didn't have to experience pricing and licensing for UiPath Platform, as that was someone in a bigger chair than me.

I did not consider other solutions before selecting UiPath Platform.

We do not use Agentic AI yet.

My advice to other organizations considering UiPath Platform is that it works. Use it. Simple.

I rate UiPath Platform a ten out of ten.

We are exploring a use case for agentic AI right now.

The features of UiPath Platform that I value the most are Orchestration, which is a significant component, and the agentic pieces that are coming into shape. The biggest thing is that we need to figure out how to connect other agentic pieces that we have.

The examples of how these features benefit my organization include implementing traditional RPA with the features and functionalities that UiPath Platform offers today. A lot of them are backend business operations, however, we are also exploring clinical use cases.

It significantly reduces the time that a physician spends on documentation versus taking care of the patient, which is what they came into medicine for.

UiPath Platform can be improved by working on specific use cases and partnering with us to help bring more belief in the system, and solving the pain points for the industry is critical. Do not lose focus on a specific industry.

Additional features that should be included in the next release are probably healthcare-specific connection and partnership with Epic.

With the agentic part, we are facing some challenges in terms of governance, in terms of which agentic platform to use, whether we should use UiPath, whether we use our agentic platform that we have chosen. That's going to be the challenge. Governance and clinical use cases typically go through a lot of scrutiny from security and legal. So that's the challenge, however, that's nothing to do with UiPath.

I have been using UiPath Platform for the last three years.

The stability and reliability of UiPath Platform are so far, so good. I have not experienced any downtime, crashes, or performance issues with UiPath Platform.

UiPath Platform has not been used to its fullest potential yet as it scales with the growing needs of my organization.

I evaluate customer service and technical support as phenomenal. When we have a question, we have answers, which is really cool.

I would rate customer service and technical support a ten out of ten. They are available when we want them. It's not just about technical support; it's also about working with us and partnering with us, which is significantly important. That's one thing I want them to keep.

Prior to adopting UiPath Platform, we were using another solution to address similar needs. We started using a smaller tool and also used Microsoft Power Automate, but we needed to scale, so that's why we chose a partner that will work for us. The factor that led me to consider a change was scalability.

It's better to ask this question to my technical folks, however, there have been zero complaints on that front. They're available when there are questions for us, which is really, really good. It's not like sell and then forget. It's like sell, we will make you grow, and then we'll make you successful, which is really cool.

In the last two years we have been setting our COE, and we are working towards seeing a return on investment with UiPath Platform. We have several use cases that are marching towards the ROI piece. One use case will probably pay for itself, the product.

My experience with pricing, setup costs, and licensing for UiPath Platform is that it is significantly simple and a workable solution that's always offered, which has been a blessing for us in a tight financial market, especially in healthcare. It becomes really challenging; however, they have been willing to work with us, which is really good.

Before selecting UiPath Platform, we did look at the other two vendors in the market and also looked at Microsoft. UiPath Platform stood out because of their focus on the domain-specific areas, and the tool is significantly superior.

The advice I would give to other organizations considering UiPath Platform is to jump into it. ROI is something that you will find very quickly. Howecer, build and partner with UiPath Platform and maybe their partners. Most importantly, fail fast if you need to, and don't try to build a big project that goes on for years; do some small pilots, but pilot to project, scale pretty quickly.

On a scale from one to ten, I would rate UiPath Platform overall an eight, based on the features and functionality we've used so far.

My main use case for UiPath Platform is that we use it for a lot of revenue cycle operations, automating different tedious revenue cycle tasks, besides automation.

The features that I appreciate the most on UiPath Platform are the Orchestrator and the ability to kick it off without having to manually do it. One big benefit of these features on UiPath Platform is that I didn't have to have someone manually kick it off; that's one big benefit that saves time and effort, allowing me to run it 24/7.

It also does a great job providing tracking and history, and we can leave breadcrumbs with it to see where things left off and stopped.

My teams have used the vendor's UiPath Academy course. The biggest benefits I have seen from using the Academy when we first started three years ago with UiPath Platform are that those courses helped a lot with just getting used to it, especially since we had to put our skills in our laps, never having done it before. The Academy was straightforward and helped us get started.

Improving the forms on UiPath Platform so you can easily assess answers could be a big benefit. The different dashboards are not very convenient or handy; you have to do a lot of manipulation with them, and I'd rather have ease of use and them be more user-friendly.

It would also be nice to have better insights into the processes, such as whether they are running smoothly and what the outcome is, because we have to leave a lot of breadcrumbs when we build something and would rather not have to do all that.

I have been using UiPath Platform for three years.

I have not experienced any downtime, crashes, or performance issues with the stability and reliability of UiPath Platform.

UiPath Platform scales with our growing needs; we have definitely expanded on it utilizing a lot of the current licensing model we had, so we didn't have to buy many new licenses. However, when license time came around or when AI units came around, we did see significant costs and lower ROI.

I would evaluate customer service and technical support for UiPath Platform as very good.

Prior to adopting UiPath Platform, I did consider using a different solution to address my similar needs, as I think the right tool is for the right job.

My experience with deploying UiPath Platform was really simple, and I appreciated how UiPath actually has people who would help you with it as well.

I have seen a return on investment with UiPath Platform; my first year doing it, we saved about 12 FTEs of hours.

My experience with the pricing, setup costs, and licensing for UiPath Platform is that I think it's very expensive; when comparing it to Power Automate or another company, Power Automate is obviously cheaper. All the other companies are kind of in line with the pricing, but I just think it's a real high cost that seems to keep going up, which reduces my return on investment.

Before selecting UiPath Platform, we compared all the major players and looked at the Gartner scale of who was on top. We did some peer references from people I knew in the industry and the gradual typical approach you would go to. We also got to see a demo of it, and compared to other demos, UiPath definitely looked more user-friendly; that's what stood out the most since the cost was pretty much the same as others.

The advice I would give to another organization considering UiPath Platform is to strongly consider your team and what kind of needs your team has; because with different solutions, there are different levels of computer science background you need, and whether you want low-code or no-code versus having someone who has business acumen with a bit of development skills, or just a high development department—so consider your staff.

I would rate my overall usage of UiPath Platform as definitely an eight out of ten.

At my current job, my main use case for UiPath Platform is general processes for finances, where many of them deal with finances. We do data entry with UI automation, and I would say the majority is UI automation.

Examples of how the features of UiPath Platform have benefited my organization include tracking, metrics, and analytics. It feeds into Insights, and it's really useful when it comes to dealing with fires that arise every day. Being able to diagnose and actually look inside is good, having it all organized.

The features of UiPath Platform that I prefer most, as compared to Power Automate, include Orchestrator, which is good, and I appreciate built-in data extraction.

IXP is a good upgrade over Document Understanding, and Action Center is nice. Overall, Orchestrator as a whole is good.

With IXP, we have a few large processes that leverage extraction from PDFs, which has been pretty helpful. Same thing with Action Center; anything that we do with IXP or extractions we include human in the loop.

To improve UiPath Platform, I would really want to see improvements on Action Center in customization on how it's laid out. They have a layout that makes sense in some cases, but I would want to actually create a custom UI for Action Center because sometimes it does not make sense what they're trying to do, and you want to move things around. If we could edit the CSS, that would be great.

On all of their tools, especially those meant for attended or human in the loop, any interface that we have that is business facing should be customizable. I would prefer to see UiPath hands off on that and just let the user figure out what is best for the end user instead of it being a prepackaged thing. Sometimes it works and makes total sense, but in other cases, it does not. Business users ask, 'Can we change this? Can we do this? Can we do that?' and the answer is often 'We can't because it's prepackaged.'

I have been using UiPath Platform for five or six years.

I have not experienced issues with stability or reliability in UiPath Platform. Orchestrator has been down once in the past year.

UiPath Platform seems to scale appropriately for the growing needs of my organization.

My evaluation of customer service and technical support is overall positive as we have direct communication with the product team, and they are pretty good.

On a scale from one being the worst to ten being the best, I would rate customer service and technical support an eight.

They are mostly good, though sometimes we catch them reading off the wiki, and we do not need that when we can read it ourselves.

When you're doing staple UI automation or data entry, the implementation works well. It's consistent. We've been privileged to use all of their products really early.

We had a lot of issues with IXP. We've been using it since last October, and it was really just trial and error and figuring out what worked, what didn't work. It's all fixable. It's just a matter of timeline. Some things are quick fixes. Some things take months.

While we have a hybrid setup, we are moving to the cloud.

Before selecting UiPath Platform, I considered leveraging everything, including Power Automate and the entire Power App suite.

I have used Blue Prism in the past. I find Power Automate always available. Even when I use UiPath Platform, for any email intake we do, if business wants to do a data entry process with an Excel input file, I pick up that email with Power Automate and create a queue item for UiPath Orchestrator through an API call, which is easier because it's part of Microsoft.

If I need to use O365, mainly SharePoint, Teams, or Excel as part of a process, I opt to do that portion in Power Automate because it's simpler. For complex code that is required, data manipulation, extraction, and UI automation, I still prefer using UiPath Platform since we already have the environment set up for that, but data manipulation in Power Automate is a nightmare.

My advice to another organization considering UiPath Platform is to make sure you understand what makes for good automation. Don't try to do something overly complex; don't shoot for the stars, as you might have a really bad experience and waste a lot of money and time.

I would rate UiPath Platform as a solid eight or nine out of ten.