What is your primary use case for Kryon RPA?

We use it for discovery on desktops to understand what operations are actually doing. Using task mining capabilities allows us to record activities and identify efficiencies and potential process improvements.

We're predominantly focused on the contact centre because that's our primary core business, and a lot of RPA use cases are in the back offices. The challenge for contact centres over the years for all RPAs has been that it's hard to establish the business case. The complexity of that environment includes determining and prioritizing which process you want to automate first. We have done quite a number of back office stuff, but our vision is to link the back office to the front office in terms of customer experience. We are a speech analytics company, and we specialize in that area. We have challenges with corporates because every vendor comes in with a return on investment equation, but there's only so much that our customers will do. We saw that combining our capability with what RPA can do would really help with the business case for automation.

We use it to automate some processes that require no human intervention. Currently, we have three projects: dispute resolution, settlement reconciliation, and consolidation.

Kryon RPA is used in different departments such as Human Resources, Programming, Planning, Production, Commercial, etc. I use it when I program tasks for clients, in particular, to program the bots in client environments.

I use Kryon RPA to make bots for the telecommunication and banking industries.

I primarily use this solution to substitute processes where humans perform checks that do not need human judgment. These include onboarding, offboarding, and changing a contract.

We're looking to discover routine processes that our users do and ultimately automate those processes and deploy them to robots. We've really been looking at just about any of processes. We've initially used it for processes that update invoices or update data on our system. We've used it for processes to send emails such as notification emails. We've used it to run scripts and to run data updates, and as a scheduling tool as well.

We only use unattended bots right now. We build processes to help business departments in our company to improve processes through automation of pretty easily "bot-able" ideas.

As a company in the insurance industry, we use it for various functions within finance, such as identifying duplicate invoices, reporting, some operations functions - moving information from one system to another - as well as claims-processing.

We use it for unattended automation and attended automation. We are working on automating a lot of the support processes that we do within our call centers which are very repetitive. In addition, there are rates and pricing in another area where we have introduced automation. We have some automated processes running multiple times a day to evaluate rates, provide reporting, and perform rate updates, as needed, without human intervention. We are also looking at streamlining some areas on our franchise side, where we are building properties out in our systems and updating their property information. Therefore, we are looking at those components, as well as the onboarding of new hotels.

We manage customer accounts: their orders, modifications, account cancellations, and back office stuff. For example, our clients are network marketing teams. Therefore, they will have accounts for multi-level marketing (MLM). They want their orders and accounts modified. For some of them, we want to change their subscriptions or cancel their accounts. These are all submitted as requests through online forms. Then, we will take them and do the modifications. We do this process automatically through Kryon. All our bots are actually licensed for unintended, but we are not able to use them. So, we have currently 15 bots and all of them are attended only.

We use it to automate a lot of data entry or do manipulation in regards to our ERP system. We are still pretty new with the solution. We have maybe a dozen wizards right now. Some of them are different variants of similar wizards. For the most part, it is used all around our ERP system. E.g., if we have a new product that we're going to make, we take the information from marketing and engineering. That gets handed off to the bot, then the bot enters that information into our ERP. This is a pretty intensive manual entry process. Everything that we use is on-premise.

Our primary use case is two back-office processes from a specific area, an area which was very complicated. In the credit card world, there is a process called a chargeback, when the customer says he didn't do a specific transaction, or it's not the right amount. This process has a very long, complicated and regulated process behind the scenes, after the conversation with the customer. We used a robot to automate a lot of the process, to make it shorter, easier, and to save a lot of agents working on the process. Every week or two weeks we are bringing on a new process with the robot. We are still in the middle of the automation move; we have a very big roadmap for what comes next. We are still on this trail.

We use it for rapid process automation, but we also have Process Discovery. We use it for billing and collections, business administration, and insurance.

Our company buys products from vendors and sells services to end-users. Most of the RPA processes done in Kryon are related to order raising, as well as retrieving reports. We have automated processes involve SAP, Pegasus, ITSM tool, Words, and Excel.

We took all kinds of mindless operational processes, things we were doing over and over again and which cost us a lot of work time every day, or week, or month, and scheduled them to be automatic, with no human hand in the process. We have a lot of examples. We make loans, although we are not a bank, for various purposes. Sometimes, people don't pay us back and the loans go to collection. We have to start all kinds of processes via lawyers, and when we transfer a case to a lawyer we have to prepare it. All the preparation for the lawyer is automatic now. All the letters for the lawyer with all the details about the loan, about the collection - everything is automatic. Also, for each customer whose debt we transfer to a lawyer, we have feedback to our core system to update all the data in the system again. So all the data about the customer and the debt comes from the system to the lawyer, and feedback from the lawyer comes into the system. And all of this, of course, is connected to the loan itself, to the customer. Everything is aligned.

We're automating a lot of shared services tasks within our homegrown system: payroll, billing, and things like that.

The primary use case is for back office processes.

We use Kryon in a number of use cases. We have done a lot of work in the insurance industry, especially client-onboarding. We are also working on AML, anti-money laundering. Another use case is data extraction from invoices, using the Kryon platform.

We have two primary use cases. One is the back office. We're a bank and we are automating some work of the bankers - mostly manual jobs like typing Excel data into our legacy systems and the like. The other thing is automating testing. We have really difficult scenarios involving both legacy and web systems. We hadn't found the right tools to take testing all the way from start to finish. But we have found Kryon very effective in that direction.

The primary use case is process automation. We are a financial institute, a bank. We use it to automate routine processes which don't require any cognitive participation.

We have legacy software in our company. Some processes in our company are being done manually. There are very routine jobs, processes where people are sitting in front of a computer and typing data. This software, Kryon, enables us to make these processes more automated. We program the software, we run the use case with the software and now, instead of things being done manually, they're being done automatically. It's helping leave all this old legacy software which doesn't have APIs. We wouldn't be able to do it otherwise.

We mainly use it for creating automated processes from previously manual processes, to make existing processes faster, better quality and more efficient. We currently have three processes implemented in production and the fourth is going live next week. It's not heavily used, so far. The first one is small. It just enters the US dollar currency into our ERP system. It's a daily task each morning. The second one involves an external, third-party systems from which we export a report and import it into one of our systems. It used to be done on a daily basis by an employee and now it's being done automatically. The third one is an automated delivery note. One of our suppliers, provides our tobacco products with paper delivery notes. So now they send us a daily report and the robot enters the delivery notes into the operations system. The fourth one which will go live next week, will upload bank notes of returned payments into our financial system. That was another manual process that will be automated.

Automating a process involving SAP and Excel operations. Such operations require access to SAP TRX, export in Excel file, and running Excel macros.