Types of RPA Bots
RPA bots come in different types depending on how they run, how much human involvement they need, and how intelligent they are. Knowing the differences helps you design the right automation for each business situation.
The Three Main Bot Types
At the broadest level, RPA bots fall into three categories: Attended, Unattended, and Hybrid.
Diagram: Bot Type Overview
┌─────────────────────────────────┐
│ RPA BOT TYPES │
└─────────────────────────────────┘
│ │ │
┌───────────┘ ┌─────┘ ┌────┘
▼ ▼ ▼
┌─────────────┐ ┌─────────────┐ ┌──────────────┐
│ ATTENDED │ │ UNATTENDED │ │ HYBRID │
│ BOT │ │ BOT │ │ BOT │
│ │ │ │ │ │
│ Works WITH │ │ Works alone │ │ Switches │
│ a human │ │ No human │ │ between both │
│ on the same │ │ needed │ │ modes │
│ machine │ │ │ │ │
└─────────────┘ └─────────────┘ └──────────────┘
Type 1: Attended Bots
An attended bot runs on a human's computer and works alongside the employee in real time. The human triggers the bot — either by clicking a button or pressing a keyboard shortcut — and the bot handles the repetitive part of the task while the human stays in control of decisions.
Real-World Example: Call Center
CUSTOMER CALLS IN
│
▼
Agent answers phone ──▶ Agent asks: "Can I have your account number?"
│
▼
Agent types account number into desktop tool
│
▼
ATTENDED BOT TRIGGERS AUTOMATICALLY:
→ Opens CRM system
→ Searches for account
→ Pulls customer history
→ Displays recent orders, complaints, and balance
│
▼
Agent reads the information and talks to the customer
The bot handles the lookup. The agent handles the conversation. Both work together on the same screen.
Best Use Cases for Attended Bots
- Customer service desks where agents need fast data retrieval
- HR queries where employees look up policies and payslips
- Sales teams entering order details into multiple systems
- Any task where human judgment is required mid-process
Type 2: Unattended Bots
An unattended bot runs completely on its own — no human is present or required. It gets triggered by a schedule, an event, or the Orchestrator system. These bots typically run on virtual machines in the background, often at night or during off-hours.
Real-World Example: Nightly Bank Reconciliation
SCHEDULE: Every day at 11:00 PM
│
▼
Orchestrator triggers unattended bot on VM
│
▼
Bot opens banking portal ──▶ Downloads transaction file
│
▼
Bot opens accounting system ──▶ Matches transactions with ledger
│
▼
Bot flags unmatched entries ──▶ Creates exception report
│
▼
Bot sends report by email to finance team
│
▼
Bot shuts down — all done by 11:45 PM
Zero human involvement from start to finish.
Best Use Cases for Unattended Bots
- Batch processing of large volumes overnight
- Invoice processing and payment approvals
- Regulatory report generation
- System-to-system data migration
- Email sorting and automated responses
Type 3: Hybrid Bots
A hybrid bot switches between attended and unattended modes. Part of the process runs automatically without human input, and at a specific decision point, the bot pauses and hands control back to a human. Once the human completes their part, the bot resumes automatically.
Real-World Example: Loan Application Processing
Loan application submitted online
│
▼
UNATTENDED phase: Bot collects applicant data,
checks credit score from external bureau,
verifies identity documents
│
▼
PAUSE: Credit score is borderline (650-700)
Bot flags the case and sends alert to loan officer
│
▼
HUMAN DECISION: Loan officer reviews case,
types "Approve" or "Reject" in the system
│
▼
UNATTENDED resumes: Bot processes the decision,
generates the loan agreement,
sends confirmation email to applicant
Comparison Table: Attended vs Unattended vs Hybrid
| Feature | Attended | Unattended | Hybrid |
|---|---|---|---|
| Runs on | User's machine | Server/VM | Both |
| Triggered by | Human | Schedule/Orchestrator | Both |
| Human involvement | Required | None | At key decision points |
| Works 24/7? | Only during work hours | Yes | Yes (with pauses) |
| Best for | Front-office tasks | Back-office batch tasks | Complex multi-step processes |
Other Bot Subtypes Worth Knowing
Cognitive Bots
These bots combine RPA with AI capabilities like natural language understanding, image recognition, or machine learning. They can handle unstructured data — such as reading an email written in plain language and extracting key details from it.
Discovery Bots
These bots monitor and record how humans perform tasks, then generate reports showing which steps are most repetitive and suitable for automation. They serve as a tool for identifying automation opportunities rather than running production workflows.
Testing Bots
Some RPA tools build bots specifically to test other software applications by simulating user interactions. These overlap with traditional test automation tools and are common in quality assurance departments.
Choosing the Right Bot Type
Does the task need a human to make a decision midway?
│
YES ──▶ Use Attended or Hybrid Bot
│
NO
│
▼
Does the task run on a fixed schedule or in large batches?
│
YES ──▶ Use Unattended Bot
│
NO
│
▼
Does the task mix automated and manual steps?
│
YES ──▶ Use Hybrid Bot
Summary
RPA bots are not one-size-fits-all. Attended bots work alongside humans at a workstation. Unattended bots run independently on servers, often overnight. Hybrid bots combine both — automating what they can and pausing for human input when needed. Matching the right bot type to the right task makes the automation more effective and easier to maintain.
