Currently, we are using mostly RPA, which is fixed automation, outcome-based. We know what the input and output are. This will do that regular task, so that is what is current. Earlier I was preferring RPA, however after seeing agentic's potential, I wanted to explore more on agentic AI and how that entire business workflow can be automated.

Currently, we are in food manufacturing, and we have many business functions such as order-to-pay or procurement-to-order. We are doing all these things by having third-party software such as an ERP suite, Snowflake, and other tools.

I want to explore how we can use Maestro to bring up that entire business automation workflow. We are trying to achieve the same business flow that is happening. I wanted to try it with Maestro.

We went with UiPath Platform for a specific use case. We were already doing it, however, there was significant manual involvement. So, for us to implement UiPath Platform was to find software or a tool that can automate all these things.

For our use cases, we were previously using different tools and a tech stack. It made a difference, though not drastic, with about a 2 to 3% change over in the three or four use cases we are doing. It was previously a manual process combined with specific tools. With UiPath Platform, we are using RPA bots and have removed all other tools.

As a business-based person who handles engineering and IT from the business side, I can say that improvements would be beneficial in the automation of the entire software development life cycle through more agents, similar to the testing automation currently being done.

The activities we have implemented are pretty straightforward. The testing time and process were somewhat challenging. While deployment was straightforward and easy, the testing part, particularly testing the functional use case, was difficult.

Writing test cases and dealing with failures was challenging. We had apprehensions about whether it would work well with the current setup, even with some latency.

I have been using UiPath Platform for the past eight months.

We maintain metrics and KPIs for these bots, monitoring their functionality and performance. We compare metrics between previous and current states, which shows significant improvement. We have not experienced any stability issues so far.

While we are not using the full set of functions or functionality of UiPath Platform, only utilizing a limited part of RPA bots, we have experienced good scalability with what we are using.

I have been using the community support, which I would rate between seven to eight out of ten.

The response is good as they have a large community. When questions are posted, someone always tries to help. The notification system is effective, alerting users when someone from UiPath Platform has posted a potential solution to their thread.

In terms of technical support, we haven't reached out so far so I can't say how they are.

It made a tremendous change in the way that we are doing the deployments. Right now, are doing on-prem deployments. It's connected, yet we eventually wanted to move to UiPath Cloud or maybe AWS.

It's pretty straightforward for whatever the activities that we have made, and we didn't have much. Testing was pretty straightforward and easy yet testing the functional use case made it a little difficult.

The change came from business requirements when customers indicated that the current process was not optimal. We then started exploring alternative solutions, which led us to implement UiPath Platform.

We wanted to remove that manual intervention or bring up some human touch there. First, we did a prototype to see how the end-to-end workflow was happening for one use case. Then we tried to derive metrics, such as how much time we are saving in terms of resources and for the entire flow. It made a significant difference for us at that point in time. Usually, it used to take many minutes and had to interact with numerous tools and technologies. When we implemented UiPath Platform and RPA, it showed substantial improvements from a metrics perspective regarding time savings and overall efficiency.

I cannot provide specific advice about certain aspects as we have not extensively explored all features. We have not had to raise any support requests so far.

Every business and company has its own requirements. The best suggestion is to understand the full functionality of UiPath Platform and carefully consider the areas where it should be implemented rather than utilizing it everywhere without proper evaluation.

Based on the overall functionality and features being used, the reviewer rated UiPath Platform an eight out of ten, indicating satisfaction with the solution.

My primary use cases for UiPath Platform are around investment type data, where we normally work with business units needing to pull in data where an API is not readily available.

We have not started testing use cases as we are governed heavily by compliance, and we have what's called an RAIC council, so anything involving AI or LLMs has to go through them. We submit an intake form and wait for approval before we can start working on it.

That being said, we have two potential use cases that we've already submitted the request to start testing out agents and AI within some workflows. I can share some details about those use cases, which are really centered around extracting data from very unstructured documents, as the structures frequently change quarter over quarter, making it quite complicated.

I have realized benefits utilizing UiPath Platform, and specifically, this year alone from January until last week, we have saved about $650,000 for the firm, with close to 5,000 hours saved by diving deeper into pulling investment data.

The features I find most valuable within UiPath Platform are the logging and controls, and the ability to bring value to the firm extremely quickly due to the low-code, no-code functionality.

The biggest benefit I've seen from UiPath Platform Academy courses is the understanding of the REFramework, which is critical for proper coding, exception handling, and routing to support groups. My engineers with engineering experience often fly through the first part, but pause at the REFramework, where I explain the importance of mastering it.

Understanding the REFramework allows the firm to properly implement try-catch systems and route exceptions effectively, which is beneficial for ensuring everyone can jump into code they didn't deploy and understand how it flows together. It sets the framework within the company to support development and maintenance. If implemented correctly, it will not break and will bring stability to the process.

I am part of a UiPath Platform user community. Being part of the community allows me to network with other firms, share challenges, wins and losses, and seek support whenever I'm stuck with something, which is valuable for problem-solving. This exchange of information helps us to not divulge proprietary information while still offering support.

I did not find support helpful.

I have been using UiPath Platform for about five years.

UiPath Platform itself is very stable while the instability lies in the architectures it interacts with, meaning issues can arise from the VMs and networks managed by different teams, yet overall it is very robust and reliable. The underlying infrastructure causes the perception of unreliability, but removing any VM or network issues reveals no significant problems.

UiPath Platform scales very well with our growing needs, particularly with Gen 3 Windows 11 servers, making it much easier to add more instances and resources compared to the previous architecture.

I have used UiPath Platform support before. I did not find them helpful at all. The support team often cannot understand custom automations we've built, which limits their effectiveness; for instance, when I reported a simple issue about elements not being recognized, they responded with "It works on my end," which was not helpful. I would have preferred support to offer a screen share to truly understand my situation rather than leaving me to figure it out alone.

I would rate UiPath Platform support a seven out of ten. The support would be a ten if they were proactive in testing requests on their end and offered follow-up communication, lending customers guidance rather than leaving them isolated.

We considered UiPath Platform alongside Blue Prism and Automation Anywhere, and we chose UiPath Platform because it seemed more user-friendly and easier to adopt.

When I first started in RPA, we did not fully understand what we were getting into. We had heard of the RPA technology and decided to go with UiPath Platform because it is best in class. Once we began developing our first use cases, the value became clearer, especially related to ROI from saving hours and dollars.

The architecture of the robots themselves was not hard for me to deploy, as I did not focus on that aspect.

From January until last week, we have saved about $650,000 for the firm. That's close to 5,000 hours saved by diving deeper into pulling investment data, which elevated the ROI.

I do not control pricing, setup costs, and licensing of UiPath Platform; that is handled by someone else.

We have not used any other tools, however, we do have Power Automate for small use cases. The right tool for the right process is our approach; however, our major processes are all within UiPath Platform because of its robust capability to log, control, and orchestrate.

I do not yet utilize agentic automation capabilities or agentic AI from UiPath Platform to achieve those, as it's strictly all RPA for now. We are in the process of trying to start developing more agentic, less RPA, and more agent-type workflows. We've been looking forward to having the capability that Maestro offers for case management, which will be a huge game-changer for my firm, as we've been searching for a suitable tool for two years.

Our enterprise firm does not require certification for engineers, however, within our investment side, it's a requirement. I had my advanced developer certification years ago, and all of my engineers have their certified engineer certifications. Anyone joining my team has to go through the academy and prove completion of the certification.

My advice for someone considering UiPath Platform is to clearly understand RPA, agentic work, and assess interoperability with other external systems before choosing a platform, as UiPath Platform typically comes out on top. I'm optimistic about future developments. I appreciate UiPath Platform allowing us to use our own LLMs, so thank you for that flexibility.

I have rated UiPath Platform ten out of ten.

My main use cases for UiPath Platform involve lots of document extracting, and business processes, claims, and similar tasks.

The features of UiPath Platform that I prefer most are definitely IXP or Document Understanding.

We have a Comms Mining use case that is pretty cool, and I appreciate how it's all-inclusive in one tool to orchestrate everything together.

The features of UiPath Platform benefit my organization by increasing accuracy with data and reducing our ROI. For example, we have one business process in Blue Prism that we migrated, and it runs on four bots, 12 hours a day, processing claims. This has taken the place of employees doing repetitive work and freed them up to do more intelligent tasks.

I feel UiPath Platform can be improved. Sometimes they concentrate too much on the citizen developer and not enough on enterprise developers or enterprises, as we consistently deliver suggestions to their product team that could make improvements.

In the next release of UiPath Platform, I would want to see something that I could feed a Process Design Document into, and it could determine if this is better suited for an RPA process or should fit in my scope.

One thing I would want to see fixed in UiPath Platform is the licensing, which seems excessive. Although they need to stay ahead, they move too fast, and sometimes things aren't as stable as they could be.

I have been using UiPath Platform for three years.

I haven't experienced any downtime, crashes, or performance issues with UiPath Platform, but the only recent issues we've had are running out of AI Units, which disables the automation.

We have expanded usage, starting with a couple of development teams and now we're up to about 20 squads doing automations. The process has been pretty smooth; we just have to purchase more licenses.

I would evaluate customer service and technical support as great. We have a tech lead we work with for UiPath Platform, and he's been awesome.

On a scale from one to ten, I would rate customer service and technical support a seven.

I feel sometimes instead of bringing issues back to the product team, they provide temporary solutions, and they should take our feedback more to the product team and implement it at an enterprise level.

Prior to adopting UiPath Platform, I was using Blue Prism. The factors that led me to consider a change were that Blue Prism was feeling outdated, though we hadn't updated it for five years.

In the beginning, it was a bit rough. There was lots to figure out and lots of security issues going on with just dealing with, like, opening things up and allowing security to allow us to do that. So that was pretty painful. After a year, it's been pretty smooth.

I have seen return on investment with UiPath Platform.

Currently, our group is saving about 1.5 million a year through all of our automations that we've implemented through UiPath Platform.

I didn't have to deal with any pricing, setup cost, or licensing. The licensing is excessive with UiPath Platform. They have an Insights license, Robot license, and a development license. It seems you need a license to do anything different on the platform and that's frustrating.

The decision was made by others at our company. We migrated off Blue Prism since UiPath Platform consistently ranked high in Gartner and Forrester's right quadrant.

What stood out in my evaluation process when comparing the platforms is that UiPath Platform is more developer-driven than Blue Prism. I appreciate that, especially managing packages and not having the client and server have to be on the same version as in Blue Prism, and their push for GenAI now is impressive, which I think will help us and our customers.

My advice to other organizations considering UiPath Platform is that it depends on the use case, but if they are looking to use it for end-to-end business processes, I would definitely encourage it, just because of the orchestration piece and being able to connect everything together in one platform.

On a scale from one to ten, I would rate UiPath Platform overall a nine.

My main use case for UiPath Platform is mostly in the finance space, specifically our accounting realm, although I come from manufacturing.

The features of UiPath Platform that I prefer most are Studio and Document Understanding. Studio is just a great development environment, easy to learn, easy to get through, and Document Understanding is a best-in-breed data extraction.

My teams have used the vendor's UiPath Academy courses. The biggest benefits that I have seen from UiPath Academy are demonstrated through our citizen developer program which uses it exclusively to help train our citizen developers, and I myself learned the entire platform through Academy.

My opinion on how UiPath Platform can be improved is that I dislike cloud or web apps in general, so getting all of the cool cloud features for Studio Cloud into Studio Desktop would be my biggest priority, however, that's a personal vendetta against web applications.

I have been using UiPath Platform for about three years.

I assess the stability and reliability of UiPath Platform as consistently strong. I have experienced some outages, but minimally unplanned, and anything else that happened has been internal updates causing issues.

My assessment of how UiPath Platform scales to the growth needs of my organization has been positive with no complaints. We have expanded usage. The process of expansion was quite smooth: buying new licenses, paying money, and moving forward.

I would evaluate my customer service and technical support as great.

On a scale from one being the worst to ten being the best, I would rate my customer service and technical support an eight out of ten. There's always room for improvement.

Initially, our technical account manager was not the best, and some things happened that still have a sour taste in my mouth from three years ago. Our current account management has been wonderful, with no complaints. They are super responsive and very knowledgeable.

The deployment was slow. That's more due to company restrictions than UiPath restrictions.

We have received an ROI.

The UiPath user community provides significant value through its large community, being one of the bigger vendors in the space. Being part of that community, the forums, and the people offers a wealth of experience to draw from. My advice to another organization considering using UiPath Platform is to scale quickly, get funding, and buy-in from leadership.

Overall, I would rate UiPath Platform seven out of ten, as there's always room for improvement.

My main case use for UiPath Platform would be to automate user experience and make it faster.

The feature I appreciate the most on UiPath Platform is the web interface. I work primarily on the supporting end in the backend, so that's my go-to place to troubleshoot. These features have benefited my organization by helping eliminate waste.

My teams have used the vendor's UiPath Academy courses. The biggest benefit from UiPath Academy is understanding the process better, as it provided a good introduction when we didn't know what was happening beforehand.

My experience with the UiPath user community shows that talking to people in similar situations is valuable for troubleshooting.

I would love to see UiPath Platform improved by having a better mobile application. Currently, while the web portion is available, the mobile app needs significant improvement.

I have been using UiPath Platform for the last 18 months.

I have not experienced any performance issues with UiPath Platform that I am aware of, and I would have known.

UiPath Platform scales effectively with our growing organizational needs. We are utilizing what we have, and if we need more, it's fairly easy to add more afterward. Though there is a cost associated with scaling, the platform remains scalable.

I have expanded my usage of UiPath Platform.

I would evaluate customer service and technical support for UiPath Platform as great. We have had no issues with support.

Prior to adopting UiPath Platform, we were considering the Microsoft solution to address similar needs, but we never implemented it.

My experience with deploying UiPath Platform was easy. We had assistance.

The process was smooth. We had help setting up the new virtual services.

I cannot share specific data points, however, I have seen a return on investment with UiPath Platform in terms of hours saved. I am not familiar with the financial aspects.

Regarding pricing, setup costs, and licensing for UiPath Platform, I don't see any of that information. From what I've heard, it's expensive and could be more affordable.

I was not part of the evaluation process for other solutions before selecting UiPath Platform.

We are not currently using the generative AI.

My advice to organizations considering UiPath Platform is to find a good partner to work with. Having someone with prior knowledge to help is essential, especially in the beginning, as you might feel lost otherwise.

I rate UiPath Platform a ten out of ten.

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.

Our main use cases for UiPath Platform are mainly back office revenue cycle tasks, including claim statusing, prior authorization, notice of admission, and denials, which is a big one that we're working on now.

Another process we're looking into is credentialing. We have a few use cases in the pipeline that we're looking to tackle next year, which include Agentic AI or Agentic Automation capabilities such as Agent, Builder, Orchestration, testing, or Autopilot.

The biggest part for us in implementing Agentic Automation is the denial space, especially for the appeal letter process. One specific use case that we're wanting to automate with Agentic revolves around our utilization review, where our nurses work through appeals from different payers for DRG downgrades, as all the denials come in from different payers through faxes; we're hoping to have the agent determine what type of document it is so it understands what RPA process to kick off with it. We have started testing this use case, however, it's probably not something that we'll finish this current year; we've started building the RPA processes and we're still working on the agentic piece to solve that.

For the Agentic capabilities, the biggest feature functions as a human that can delegate work, which has been the best use case for us to keep the human in the loop as much as possible, only bringing them in when there are exceptions that come up. From what I've seen while assessing Agentic Automation's ability to extract data points, it extracts the information really effectively, especially with Document Understanding and IAXP Document Understanding, which has been amazing with the way that we're able to use that and correctly identify the type of document that we're looking at at the time.

I estimate that with this new Agentic Automation, we will save roughly 4,400 documents a month, saving approximately ten minutes for each document. From RPA, the benefits so far are significant; our healthcare system is expanding and we need new people, however, after COVID, people are getting more expensive and we just don't have the budget, so RPA has been huge in allowing our current workforce to stay the right size and we use automation to really handle those tedious processes, saving money from a people perspective and capturing denials a lot faster, enabling us to appeal in a timely manner. For revenue cycle alone, we have saved roughly 800,000 year to date right now.

The main factors that led us to consider transitioning to an RPA solution were driven by the bankruptcy of our vendor for claim status, prompting us to find a solution, and the cost of RPA turned out to be roughly the same as what we paid the vendor, offering claim status plus more for the same expense.

I am utilizing UiPath Platform community.

I don't have any improvements for UiPath Platform, as we are behind; UiPath Platform is consistently coming out with updates and features, but we are just now starting to implement Agents and Agentic.

One of the biggest pain points for us is that while they have solution decks to help build solutions faster, if they developed more of a framework for areas we don't understand, indicating how to generate ROI or compress time to build automation, that would be beneficial.

I have been using UiPath Platform for coming up on two years.

I assess the stability and reliability of UiPath Platform and its robots as great, especially after resolving the hybrid issue with the bots going down; we haven't had any issues since.

I evaluate UiPath Platform support as very knowledgeable; they respond quickly, and while they may not always have immediate answers, they know who to contact to resolve issues, which has been effective for us during the two times we've needed their support.

On a scale of one to ten, I would rate them a nine. The only reason for subtracting a point is the occasional delay in getting the right people available to address the issues; although the initial documentation of the problems is thorough, sometimes it isn't enough.

Prior to adopting UiPath Platform, we used Python code or simple macros through various applications.

Deployment was good. We're a part of the Enterprise Success Program. When we joined UiPath, no one on my team had UiPath experience. So everything that was learned was either through the UiPath learning plans or through our technical account manager. We met with our TAM once a week, sometimes two, three times a week as far as training, helping us build our automations, and also with code reviews and making sure that things are really meeting the standards that we need.

I estimate that with this new Agentic Automation, we will save roughly 4,400 documents a month, saving approximately ten minutes for each document.

We did consider Blue Prism as Power Automate before choosing UiPath Platform.

The main differences I found between these platforms and UiPath Platform pertained to pros and cons; UiPath Platform provided a comprehensive package catering to our needs while Power Automate seemed too focused on Microsoft products, and Blue Prism was good.

UiPath Platform was easier for my team, who had no development background, to learn and build quickly.

My job title is Director, Revenue Cycle Informatics. According to my job function, I have six years of experience. We are just now starting to implement Agents and Agentic. The value I gain from being part of UiPath Platform user community is great; it has helped us in many places where we have been stuck, as other customers have experienced similar issues; for instance, we had connection issues with our hybrid deployment and found a lot of information through the community, which helped get our bots up 99% of the time, compared to roughly 60% before. UiPath Platform is growing with the needs of our organization, and I credit my account exec for helping us find use cases and ensure we utilize all elements we are currently paying for. One specific use case that we're wanting to automate with Agentic revolves around our utilization review, where our nurses work through appeals from different payers for DRG downgrades, as all the denials come in from different payers through faxes; we're hoping to have the agent determine what type of document it is so it understands what RPA process to kick off with it. I rate UiPath Platform a 10 out of 10.