My main use cases for UiPath Platform are a number of unattended bot processes that do a lot of replacing manual data entry for the underwriting and claims process.

Besides that, we have a few use cases for generating employee certification letters, along with downloading a number of partner year-end statements, income statements, and things like that.

As agentic automation is now coming to the forefront, we're definitely looking to move to that case, going from just using AI and also the agentic piece of it as well. We do have a few use cases in mind, however, we are trying to find the right fit, and part of this conference is helping us figure out.

We are getting ready to use Autopilot as part of Test Manager, Test Suite, since we just moved to the cloud for our Orchestrator, and now we'll be able to utilize Test Manager in the cloud as well, which includes the Autopilot piece we are going to be using. The department processes we will automate with this capability include software testing.

The feature of UiPath Platform that I prefer the most is Studio, as being a developer at heart allows me to see an idea come to fruition and see it working on a daily basis. Some benefits I've realized from using UiPath Platform include the elimination of data entry errors, giving folks time back to remove those mundane tasks, and allowing them to have high value in things they were hired for or find other ways to contribute to a better steward of the dollar within the company.

We have used UiPath Academy courses; they are lengthy to complete, but we have had some people go through the Academy courses to get certified. The biggest value I've gained from using the Academy is that it's just a great resource, not necessarily just taking the classes, but there are also articles and knowledge bases that you can go out to for help getting answers to the things you're looking for.

I am not part of UiPath Community; I am a viewer, not an active contributor. I have definitely realized benefits from the community, as any error I need help on, I put it in there, and somebody else has had it. The beauty of the community is that we're helping build each other up in terms of our skill sets and also running into roadblocks, finding others who can help, even if I don't know that person; the answers are out there.

In my opinion, UiPath Platform could be improved by being more consistent in the presentation of what's coming down the pipeline and when it can be delivered, as well as not changing the names of the products so often. It's confusing when they say, 'Oh, that used to be called this, and now it's that since we've combined it with this.' Ideally, we get more clarity, so that when I talk to a business user, they know what I'm talking about.

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

My assessment of UiPath Platform's stability and reliability, including its robots, is that typically it's not a UiPath Platform issue; it's more about the business process where the bot may not know what to do if it's not given clear instructions, which could be related to needing new healing agents.

Overall, from a stability standpoint, UiPath Platform has not given us any issues.

UiPath Platform scales very well with the growing needs of our organization; adoption is our biggest challenge, however, once we do achieve that, it scales well with different systems. The concept of orchestration is a key success factor for us.

I would give UiPath Platform's support a rating of ten out of ten across the board, as they helped with troubleshooting any issues whenever I called them, and thanks to the paid support level we wanted, it's more than paid for itself.

I have not used a similar solution prior to UiPath Platform; we did not have anything before that.

The deployment is pretty straightforward. Support was with us. We didn't need much of it, however, they were willing to be on the calls with us, especially when we were migrating to the cloud.

They definitely were a partner that went above and beyond what I would have asked from any other partner.

In terms of ROI, I would say there have been some dollars saved, although I'd have to look for exact amounts. Especially in eliminating data entry errors rather than emphasizing the dollar return, which is actually hard to quantify, some processes did save around 35 hours over a month, and it continues to grow.

I wouldn't say we have eliminated errors completely by 100%. We have definitely eliminated about 60 to 75% of the manual data entry errors.

My experience with pricing, setup cost, and licensing of UiPath Platform is that I have mainly brokered meetings with leadership versus managing those aspects. My manager helps coordinate that, while I focus on implementing it within the organization.

I have considered other vendors besides UiPath Platform. With our company having a Microsoft enterprise license, Power Automate is a competitor that is a bit more attractive due to being free for users. I think that justifying costs to business users, especially when they see Power Automate as free, is definitely a challenge we face.

It is indeed a challenge when folks come to us with an RPA process; we don't say that UiPath Platform is the only way to go. We assess the use case and note that if it's everything in the Microsoft ecosystem, it makes sense to stay there, so we won't force them to switch to UiPath Platform. However, each renewal comes with the challenge of justifying the decision.

Comparing the two solutions, I find that with UiPath Platform, there's more of a development angle, while Power Automate is very tied to a specific user. With UiPath Platform, you can create a service account, so if someone leaves, I don't have to worry about their email being tied to the process, which is one of our biggest selling points.

My advice to someone considering UiPath Platform is to make sure you get buy-in from leadership, as a lot of people see a hot new tool and pursue it without sustainability. Having top-down leadership support is crucial for longevity, especially when pricing increases or licensing renewals arise.

I would rate UiPath Platform a nine out of ten, as there are aspects that need improvement, particularly around naming conventions. I don't believe any product can achieve a perfect ten since that implies no room for improvement. I see them moving closer to a nine or ten out of ten.

The main use cases for UiPath Platform are automations within the company across different departments. So far, we have only looked at RPA in UiPath Platform, but Document Understanding is the next one, and Agentic. We are evaluating Agentic right now, but we only have a license for RPA and DI now. We are working on an RPA use case right now, the first use case, while Agentic is under evaluation. We don't have a license for it, but we are trying to see if it's going to fit our use case.

My team and I have used the vendor's UiPath Academy courses. The biggest benefits that I have seen with UiPath Academy are the clear step-by-step instructions on taking you through the different tools available. I think UiPath Platform is the best; based on my research, I think it's one of the best for enterprise-level automation, while we use multiple tools for personal automation, but for enterprise-grade automation, I think it's the best out there.

I am still in the evaluation phase of UiPath Platform, so I don't know how it can be improved or what additional features should be included on the next release right now, maybe next year.

I have been using UiPath Platform for three months.

I will have to wait and see to assess the stability and reliability of UiPath Platform, as nothing is in production yet.

I will have to wait and see how well UiPath Platform scales with the growing needs of the organization.

I would evaluate the customer service and technical support so far as pretty good. On a scale from one being the worst to ten being the best, I would rate my customer service and technical support as nine.

Prior to adopting UiPath Platform, I was using Kofax to address similar needs.

My experience with the pricing, setup costs, and licensing has definitely been more money, and it has caused some confusion in the company compared to the competitors.

I could see a return on investment with UiPath Platform, but nothing is in production yet; I can see it's coming.

Before selecting UiPath Platform, I considered Automation Anywhere and Kofax, and we looked at all those options, as we even have a Kofax environment currently running.

What stood out in my evaluation process regarding UiPath Platform was definitely positive, and that's why we went with it. The factors I considered when making the change were definitely not cost, because that's way cheaper, but it's more for the enterprise-level automation that is the reason for moving to UiPath Platform. Nothing is live yet with these features, so we're just waiting, maybe a couple of weeks. I don't have thoughts about UiPath Platform user community in terms of value that I can gain by being part of it yet, since it's only been three months. I would rate UiPath Platform between eight and nine out of ten.

We're using the solution for test cases.

The biggest benefit of these features for our organization is giving the ability to the whole company, or whoever needs to see the information about our test cases, one place to go and look. We're not scattering across many different applications and reports. It's all in one place.

The features of UiPath Platform we appreciate most include Test Manager and being able to integrate with everything we need.

UiPath's user community helps significantly. There always seems to be someone to ask a question and someone to give an answer or reply. It's easy to find answers to questions that might not be standard.

I'm not sure how UiPath Platform can be improved. The Studio can sometimes look cluttered. If there's some way to streamline that or make it a little easier to read some of the modules, it might be better. I do a lot of test case work, and I would love to see more or better reporting of failures or reasons why something failed.

We are technically in the third year of using this solution, or slightly shorter than that. We are still expanding and trying to grow more with what we're doing.

The stability and reliability of UiPath Platform is wonderful. We have very few problems with it. We have more problems with our infrastructure than we do with UiPath Platform.

UiPath Platform scales very effectively with the growing needs of our organization. Our processes seem to grow and what we do with it and the amount of data we handle with the processes we have now and that we're building is almost seamless.

Customer service and technical support are very responsive and quick. Anytime we have a question, someone is ready to pick up a phone or answer a quick email.

On a scale from one to ten, I would rate customer service and technical support a ten since it's always accessible, always there, and very responsive.

We had legacy-type things, such as C# and Selenium for testing, and we really had nothing for RPA before selecting UiPath Platform. Someone who had previously used UiPath Platform came on board and recommended we look at it. Based on their recommendation, we have used it and love it now.

I haven't handled the deployment process.

I have seen a return on investment with UiPath Platform. While I don't know the exact numbers, some of our processes that would take days now take minutes. Time-wise, we have seen a return on investment.

My experience with pricing, setup cost, and licensing was perfect. I didn't have to handle any of that.

Prior to adopting UiPath Platform, we weren't using another solution to address similar needs. We first started with UiPath Platform for RPA processes to automate processes. Everything was manual and taking forever. On the testing side, we would use Selenium for testing.

We don't yet use agentic.

I recommend putting UiPath Platform on your short list and making sure that it's going to do what you want it to do.

I would rate UiPath Platform nine out of ten, as there are minor things that could be improved.

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.