We use UiPath for our accounts receivable and accounts payable. We are a wood company that uses it primarily for customer care and finance.

We use UiPath for social media marketing.

We're an insurance company, so we use UiPath to enter customer and policy data. Four of us work on the data side of bot development, which is our department's priority. We have multiple inflows of different ideas and use cases coming from various departments that ensure the company runs smoothly and efficiently.

One of the simpler UiPath use cases involves running an SQL query, copying the results into a spreadsheet, and then emailing them to the appropriate people. We also have a third-party system for parking at the hospital. Visitors need to fill out a web form, and the automation process kicks in once the web form is filled out. The data is input into a database and then automatically processed in bundles. The form is filled out automatically for them, and it batches every thirty minutes.

We don't have many use cases for UiPath other than lead generation and sales. Additionally, we use UiPath to move data and consolidate data formats efficiently. We are involved in claims management within healthcare, with a claim bot operating across seven regions and handling numerous transactions. We are also exploring DevOps tooling and CICD pipelines, including automatically setting up environments in Google Cloud.

We are a diagnostic laboratory that receives tissue samples from all over the country daily. To manage these, we implement UiPath for Document Understanding to process requisitions from clinical providers. This information is then loaded into our laboratory information system, enabling us to carry out the diagnostic process. We have a dozen bots operating across various functions, assisting in tasks such as screening resumes in HR and data entry on patient information.

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

We're a financial institution, and we started using UiPath for small, simple processes and day-to-day tasks, such as adding and removing users and updating information, but we're also exploring opportunities to automate lending processes.

We currently use UiPath to process birth certificates. One of my tasks was to apply OCR to the birth certificates and use a named entity recognition model to extract details like the names of the individuals, parents, and the place of birth. The project requires us to handle certificates from all 50 states, and every state uses a different format.

We primarily use UiPath's AI features to pull information from chatbot conversations with insurance providers and identify decisions made.

We are using UiPath for traditional RPA automations at the moment.

We're a food ingredient distribution company that receives documents on ingredients' nutrition, allergens, microbial testing, etc. We primarily use UiPath to process these documents. It was our proof of concept for using the system initially, and we'll expand it to process invoices and other related use cases.

We are considering implementing AI as we are in a healthcare staffing company in the education sector. Our use case focuses on processing a large number of emails and resumes. We aim to mine resumes to determine which are best for rapid and successful placements. On the communication side, we wish to perform sentiment analysis to assess how well our salespeople respond to clients.

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

We use UiPath across departments, including HR, IT, procurement, and the supply chain. One use case is hiring and other simple HR-related tasks. We also automate complex processes, like using Document Understanding and machine learning to extract vendor contract information and input it into our procurement system.

I currently work for a data center company serving real estate clients. Our primary use case for UiPath involves large-scale automation using Document Understanding to process invoices.

We use AI mainly around sales processing and document understanding. Our current use cases involve traditional automation, processing different orders, order formats, languages, and language translation, and creating actual orders in any ERP solution.

We use UiPath to replicate what medical coders do by inputting codes from certain medical systems into another. It also automates our billing cycle, allowing us to input the codes directly into the insurance billing system to receive payments faster.

We have been using the RPA functionality in UiPath mostly for cash management. Our biggest use case is submitting wires and payments.

We use UiPath for claims processing, enrollment, and interpreting what's on documents, and then we use the data that's in them for different purposes. I'm sure there are many other use cases. We're still brainstorming and giving our leaders some ideas. Frontline employees also have process improvement ideas.

Our primary use case for UiPath revolves around document imaging, specifically scraping data off documents and digitizing them. We only use it in our accounting department and haven't expanded it to the rest of the company. We've seen some success with the projects on the financial team, but we might be resource-constrained to get other departments involved. It's hard for them to adapt to new technologies.

We started using AI in Document Understanding by leveraging it against our models for different documents from our customers, primarily in the finance space. We have also used AI to train models for land management documents, helping them learn as we receive new document types.

UiPath is used to automate processes, eliminating the need to increase headcount.

We adopted UiPath to leverage its generative AI capabilities for rule-based automation. This technology enhances the resilience of our automated processes, ensuring continued functionality even when underlying systems or data undergo changes that would typically disrupt traditional automation.

The primary UiPath use cases are document processing and using automation solutions to eliminate repetitive tasks in administrative data entry.

Our communications company intends to use UiPath and AI to determine the best fit and time for commercials based on the customer's usage and payment for the spot. We haven't fully deployed AI, yet. It's becoming more critical to leadership, but we're still doing testing and researching

Currently, our automation work with UiPath primarily revolves around financial processes, such as accounts receivable work and tax deduction management. We are exploring generative AI, but have not developed any AI use cases for UiPath yet.

We're a bank, so we primarily use UiPath to automate tasks such as filling out Excel sheets, organizing PDF files into folders, and reconciling rejected checks and chargebacks.

Currently, we use UiPath in multiple types of use cases and build innovations for our clients to improve their system operations.

My current use cases for the UiPath Platform include web development, web automation, desktop automations, and using document understanding, along with PDF automation using document understanding.

My main use cases for UiPath Platform are in Business Hyperautomation. We are implementers and also the customers.

One of the things that our company struggles with is that we've bought a lot of different systems that don't integrate with one another. What I've really tried to do since starting to utilize UiPath Platform is find ways to make these imperfect systems work together, whether it be Mike Albert for fleet data, Azuga for safety-related data, or Snowflake for data warehousing. I aim to take all that data, put it into our Snowflake warehouse, and then visualize it in Power BI and other tools, so the sky's the limit, and I know we even use it for Amazon, Walmart, and various other processes.

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.

We do not use Agentic AI yet.

My main use cases for UiPath Platform are traditional RPA and Document Understanding, primarily focused on invoice processing and similar tasks. We've delved into GenAI since last year. I am from the Automation COE team at OMERS, and we are not restricted to just UiPath Platform; we engage in various automation initiatives.

My use cases for UiPath Platform involve starting with simple robots, as I saw in my company that I need to handle many paychecks. First, we scan the paycheck and the robot does the job in our system and sends emails of notifications that these paychecks are entered correctly in our system. From that, we started complex robots where some interact with two software systems: our system and another program that does the work orders, leading us to develop a robot that helps the technical team in our company by synchronizing the work orders.

Nowadays regarding UiPath Platform, there are both advantages and disadvantages because nowadays you can just go into an AI tool such as GPT, Claude, or whatever and ask it to do whatever you need, and it will be faster.