Attended vs.

Un-attended RPA - Basics

ATTENDED AUTOMATION UNATTENDED AUTOMATION

Handles tasks Automates back-office
WHAT
for individual employees processes at scale

Employees trigger and direct Orchestrated based on

a bot to carry out an activity HOW rules-based processes

Employees trigger bots Bots complete business processes

to automate tasks as needed
at any time
Increases productivity and customer
satisfaction at call centers and other service
desk environments
WHEN without human intervention per a
predetermined schedule
Frees employees from mundane tasks,
WHY lowering costs, improving compliance,
and accelerating processes
1
Attended RPA

Attended software bots typically run on local workstations, meaning they manipulate the same front-office programs as
your human employees. This is sometimes referred to as desktop automation because software bots take actions on the
local machine. Since attended RPA bots respond exclusively to user prompts or to human-triggered events, you might also
recognize them by a different name: personal assistant bots or software assistants.

The key benefit of attended RPA is that it lets users quickly coordinate simple but tedious tasks like searching for and
retrieving a specific customer’s data.
For example, attended bots
might retrieve data from
one application and bring it
into a different application
so a call-center agent won’t
have to toggle between
them.

UiPath Robot Launched from the desktop tray

2
Attended RPA – How Human & BOT Works Together
An employee starts a data-intensive task, triggering a bot from the desktop. The bot logs in and collects
data from multiple systems. The employee reviews the results and authorizes the bot to generate a report or
update the data. Error-prone data processing tasks get a speed and quality lift.

On-demand data processing

3
 Attended RPA – Resource Allocation Process (HR)

• Perform Data Validations • Move the file to processed folder.

• Access the folder • For Failure Record - Add comments. • Access HR Portal and Add New
• Check for File presence Employee record.

Attended BOT

• Send email to designated HR team

with spreadsheet attachment

• Move the File to 'Sent email"

folder.

4
Unattended RPA

Unattended RPA is primarily used for back-office functions that have a more enterprise-wide impact on workflows.
Unlike attended bots which run on individual user workstations, unattended bots usually run on an organization’s servers
with little to no human intervention — but they’re not to be confused with artificial intelligence (AI) in that they’re
not “self-learning.”

Once deployed, unattended bots will run on predetermined schedules or in real time, 24/7/365. They automatically
handle the aggregation, sorting, mapping, analysis and distribution of large quantities of organizational data.
These higher-level data streams and processes ultimately improve the workflows of individual departments, and at
an even more granular level, the workflows of individual people within them.

Some examples of the types of processes unattended RPA bots will automate include:

• Claims processing at an insurance company.

• Application processing for customers opening accounts at a bank.
• Generation and distribution of invoices at a wholesale supplier.
• Responses to interactive voice response (IVR) queries.

5
Unattended RPA - Claims Pend Resolution

Challenge: On average 70% of claims process successfully—or ‘auto-adjudicate’—on the

first attempt, costing the insurer about $3 per claim. Failed claims, requiring manual
processing to correct code exceptions or data errors cost the insurer about $28 per claim—
almost ten times as much. Edits resulting because of data mismatch contributes a ratio of
the 30% claims dropped for edits resolution. [Ref1]

Solution: By implementing a BOT with built-in claims processing validation rules, programmed
to pull the claims with the relevant edit/reason codes, examines the claim for the issue and
takes necessary steps to resolve the edits and finally submit for adjudication.

Secured Auto Extract Specific Auto Process Submit for

Login Claims Built-In Rules Adjudication

Cycle Time to Resolve an Process a Claim

60-90 Seconds