Robotic process automation (RPA) is software that clicks, types, and moves data on screen the way a person would, following fixed rules. It does not redesign the process. It does not interpret a Laredo crossing exception. It runs a script at the interface layer.
- clicks and data, not a redesign
- UI layer
- RPA market 2024 (Gartner MQ 2025)
- USD 3.8B
- scale ceiling Forrester measured
- ~10 bots
Cluster: what is process automation · what is an AI worker · RPA vs agents.
What RPA is
An RPA bot opens the app, finds a field, pastes a value, hits save, and moves to the next record. It lives in the interface: it does not need the system to gift it an API (application programming interface). That is why it sold so hard in banks, hospitals, and back office.
In logistics that matters because the Mexico–U.S. stack is not one clean ERP: it is a TMS (transportation management system), WhatsApp, a GPS portal, SAT XML, and Finance’s inbox. The short glossary RPA in logistics covers the limit; this article wins the generic definition and the corridor example.
How it works (UI layer)
The classic pattern is record, lock rules, and queue. The bot does not “see” the trip: it sees coordinates, selectors, and strings that match the script.
Recorder / studio
What it does: Captures clicks and fields on a stable UI.
What it does not do: Does not learn a new portal every week without maintenance.
Rules
What it does: If field X = Y, press Z.
What it does not do: Does not solve “the appointment dropped and the driver sent a voice note.”
UI layer
What it does: Operates with no API when the system does not expose one.
What it does not do: Any visual or session change breaks it.
API layer
What it does: Some suites already mix RPA with connectors.
What it does not do: If there is a good API, you often do not need the click bot.
Attended, unattended, and hybrid
Automation Anywhere, SAP, and Microsoft pages lead with this taxonomy. It tells you who sits at the keyboard. It does not tell you whether the freight process is closed.
Attended
Who triggers it: The person in the tower or Finance.
Where it fits in freight: Fill an appointment form or a SAT field with someone checking.
Unattended
Who triggers it: A server, overnight or in a queue.
Where it fits in freight: Pull XML or mirror a status on a portal that does not change.
Hybrid
Who triggers it: The bot starts alone and asks a human for the doubtful stretch.
Where it fits in freight: Close to a ticket: the bot does not guess, it escalates.
Do not copy the “stand up a center of excellence and buy the suite” CTA. If the goal is to close trips, the question is who owns the exception, not how many bots sit in the catalog.
RPA vs AI vs agents vs APA vs BPM
This is the section buyers want when they type “RPA vs AI.” The acronyms overlap. The table splits them by the work, not by the quadrant.
RPA
What it does: Fixed UI clicks.
When to use it: Stable screen, high volume, rigid rule.
When not: 20 different portals or a dirty PDF.
AI
What it does: Perceives or suggests (text, image, classify).
When to use it: Read an invoice or an incomplete POD.
When not: Alone, with nobody to run the next step.
Agent / AI worker
What it does: Goal + tools + memory + human.
When to use it: Close a trip or hold a payment.
When not: If you only want a chat. See what is an AI worker.
APA
What it does: Market name: orchestrate agents and bots.
When to use it: When you already mix layers and need a flow owner.
When not: Not a brand you must buy to “be autonomous.”
BPM
What it does: Design and measure the process.
When to use it: Before automating a badly drawn flow.
When not: A BPMN map does not move the shipment.
BPA
What it does: Automate the process end to end.
When to use it: The umbrella. Guide: process automation.
When not: Not a synonym for RPA.
Chatbot
Stays in one channel
Chat window
Scripted replies
Cannot reach voice, email, or the TMS.
RPA bot
Stays in one application
One screen
Fixed clicks
Breaks when the UI changes or the input does not fit.
AI worker
Crosses channels and systems
Trip goal
Tools + ticket
Executes; if it breaks, it opens a ticket. Humans own exceptions.
Why RPA still matters
Gartner’s June 2025 RPA Magic Quadrant puts the market at about USD 3.8 billion in 2024 (+18% year over year) and notes that AI and orchestration platforms (BOAT) are already alternatives to deterministic RPA. The market did not vanish: it is being eaten at the edges.
On the corridor, RPA is still the arm when the appointment portal or the carrier GPS has no API. Computer use (operating the screen with context) is that arm’s evolution. The brain is the trip goal, not the script.
That is why we do not recommend “turn off RPA and buy chat.” We recommend not letting the arm make Finance decisions.
Limits the brochure does not lead with
Forrester documented that only about 52% of enterprises that launch RPA progress beyond their first 10 bots (scale coverage; not a new 2026 study). The ceiling is not the license: it is maintenance, governance, and processes nobody drew.
- UI brittleness: a portal redesign kills the queue.
- Unstructured data: a WhatsApp voice note, a blurry POD, an invoice with no usable UUID.
- Scale: bot 11 costs more to keep than the first 10 together.
- Exceptions: a Laredo crossing does not fit “if A, press B.”
Do not use KeyBank, Petrobras, Cargill, or KPMG vendor cases as proof. Those are categories (documents, finance, plant), not your Bajío–Laredo rate.
Corridor cases, not a bank
Generic pages illustrate with employee onboarding and office accounts payable. The process that hurts you is the trip.
Booking / Sales
What RPA tries: Copy a tender from email into a TMS.
Where it breaks: WhatsApp and rates that do not fit the script.
What the AI worker does: Takes the goal, writes the trip, escalates if a field is missing.
Planning and build
What RPA tries: Request a yard appointment in a portal.
Where it breaks: The portal changes or the slot drops.
What the AI worker does: Retries or opens a ticket. Human owner on the exception.
Execution
What RPA tries: Paste GPS status into the TMS.
Where it breaks: 40 different mirror accounts.
What the AI worker does: Computer use with shipment context. See computer use.
POD
What RPA tries: Download a PDF from a portal.
Where it breaks: A photo on a phone, no trip ID.
What the AI worker does: Chases usable evidence and ties it to the file.
Finance
What RPA tries: Push invoice amounts into the ERP.
Where it breaks: Does not match Carta Porte or GPS.
What the AI worker does: Audits rate + CFDI + Carta Porte + GPS + POD. Freight accounts payable.
How it fits with AI workers
The healthy setup is not “RPA or agents.” It is: the AI worker decides and writes; the arm (RPA or computer use) presses; if it breaks, there is a ticket; the analyst owns the exception.
Layer on layer
Decide, press, escalate
Goal
Close or hold
Arm
Click or API
File
Same ID
Ticket
Human owner
Voice
Appointments, incidents
Email and WhatsApp
Thread with trip ID
Documents
Read PDF and XML
Web portals
No perfect API
Systems
TMS, GPS, Finance
Continuous workflow
Booking, Planning, Build, Execution, POD, and Finance. Same trip ID. Ticket if it breaks.
Product noun: what is an AI worker. Screen cut: RPA vs agents.
How to start (without buying a suite)
Do not start with a center of excellence or an Automation Anywhere, UiPath, or Power Automate RFP. Start with a process that already costs you hours or leakage on one corridor.
Elige un paso para ver el detalle
Detalle del paso · 01
One process, one corridor
Related reading
Key takeaways5 points
- RPA is a software robot that clicks and moves data in the interface with fixed rules. It does not understand the trip; it replays a script.
- Attended, unattended, and hybrid describe who sits in front. With AI workers, orchestration decides who acts; the bot label matters less.
- RPA is not AI and not an agent. APA is the market name for orchestrating bots + agents. BPM designs. Compare in the table.
- It still matters as an arm when there is no API. The ceiling is brittle UI, unstructured data, and the stall past ~10 bots Forrester documented.
- On Mexico–U.S. freight the hero is not HR onboarding: it is tender, appointment, POD, Carta Porte, and invoice audit. OCL runs the cycle; if it breaks, a ticket.
Does the click bot fall over on every corridor portal?
Frequently asked questions
Software that imitates clicks, typing, and data movement in the interface, the way a person would, following fixed rules. It does not redesign the process: it runs a script at the UI layer. Definition: this article.
No. RPA follows rules. AI perceives or suggests (read a PDF, classify). An AI worker uses tools (sometimes an RPA bot) toward a goal and opens a ticket if it breaks. Table in this article and in RPA vs agents.
Attended: the bot runs next to a person. Unattended: it runs on a server with nobody in front. Hybrid: both. With AI workers the taxonomy matters less: orchestration decides who acts.
Because someone still has to press a portal with no API. RPA (or computer use) is the arm. The AI worker decides, writes the file, and escalates. Gartner (RPA MQ 2025) puts the RPA market at about USD 3.8 billion in 2024 (+18%) and flags AI alternatives to deterministic RPA.
Yes on stable screens (one ERP, a field that never moves). It breaks across 20 carrier portals, WhatsApp, and crossing exceptions. The short logistics cut is in the RPA glossary.
No. OCL puts AI workers on Booking, Planning, Build, Execution, POD, and Finance. They can click where needed; we do not ask you to stand up an RPA center of excellence.
OCL pattern at 100% audit: 5–7% of spend in that universe. Published case: 2,250 invoices, MXN $3.6M, 5.7% (3PL case). Do not treat vendor bank or hospital cases as yours.