Logistics Exception Center
Overview
Builds one worklist of every active delivery exception from the carrier, then dedupes it against the systems that may already be handling it - the mailbox that was notified, and the help desk where a ticket may already exist. Joining the three on the tracking number tells the robot which exceptions were mailed, which already have a ticket, and which nobody has picked up yet. Writes a consolidated exception CSV. The story is consolidation: three systems each hold part of the picture, and the robot joins them so a stuck shipment is neither missed nor double-worked.
Logistics Exception Center
A stuck shipment shows up in more than one place. The carrier flags it as an exception, the customer gets an automated e-mail, and sooner or later someone opens a help-desk ticket. Handle them system-by-system and you either miss one or work the same one twice. The valuable robot pulls all three together into a single worklist and marks, for every exception, what has already happened to it — so the team works the gap, not the duplicates.
This flow builds that command center. It reads the carrier's active exceptions, then dedupes them against the mailbox and the help desk on the tracking number.
It spans three fictional training systems — SlugExpress (the carrier), Lookout Mail and Grumpdesk (the help desk) — whose data is entirely synthetic.
What it produces
logistics-exceptions.csv in your home folder: every active exception with its consignee,
destination and status, and — joined on the tracking number — whether it was mailed and whether a
ticket already exists, with an action of has ticket or NEEDS TICKET. On the seeded data that is
30 active exceptions, 6 already mailed, 2 already ticketed, and 28 that still need a ticket.
How it works
1. The carrier's exception worklist
Sign in to the carrier portal and open the exception worklist — every shipment on customs hold, failed delivery or delay. Read the tracking number, consignee, destination and status for each. This is the master list everything else is checked against.
2. Who already knows
Two more systems hold part of the story. The mailbox received delivery-exception notifications — the robot reads which tracking numbers were mailed. The help desk may already have a ticket — it filters to the escalated (customs-hold) tickets and reads the tracking number each is linked to. Each is an independent source, joined back on the tracking number.
3. Dedupe & report
For every exception the robot marks whether it was mailed and whether a ticket already exists. The
ones with no ticket are the real work — flagged NEEDS TICKET — while the ones already in the help
desk are left alone. All of it lands in one CSV.
Running it
Ready to run as-is. It signs in with the published training credentials
(svc.rpa@slugexpress.example, hiroshi.tanaka@globex.example, svc.rpa@grumpdesk.example), which
are not secret. Real system credentials belong in the Robomotion Vault, never in a flow.
More web automation templates
See all 16 →- Bank ReconciliationTakes the payments and receipts the ERP could not reconcile and confirms each one against the real bank statement. It pulls the ERP's flagged paid-bill exceptions and open invoices awaiting cash, then signs in to the bank, searches the operating account by reference and reads what actually settled - quantifying the four ways money and ledger drift apart: a missing payment, a transposed amount, a double payment and unapplied cash. Writes a reconciliation CSV. The story is evidence: the ledger raises the question, the bank statement answers it, and every discrepancy comes out with a number attached.
- Monday Morning BriefingOne robot, every system, the whole week's work on a single page. It signs in to the CRM, the mailbox, the ERP, the carrier and the help desk in turn, reads the one number that matters from each - duplicate contacts, invoices to post, ledger exceptions, stuck shipments and refund requests - and writes a consolidated briefing with a total across all five. The story is reach: the back-office queues a team would open one browser tab at a time, gathered into one report before anyone has had coffee.
- CRM Duplicate CleanupCleans up a CRM by merging duplicate contacts - the same person entered twice under name variants like Bob and Robert. Signs in, switches the contact list to its duplicates view, and merges the first remaining pair until none are left, keeping the primary record and folding each variant into it. Writes a before-and-after report. The "your CRM cleaned itself while you slept" demo.
- E-Invoice Portal HarvestDownloads every e-invoice for a tax period from a government portal and builds an index spreadsheet of what was collected. Signs in with a one-time code, walks the paged register until the portal says there are no more pages, then opens each document to read its government reference number and pull down both the XML and the PDF. Every download is gated behind a confirmation dialog and an "I am not a robot" checkbox.
- Friday Payment RunPrepares a weekly vendor payment run in the ERP. Signs in, proposes every bill due within seven days and confirms the run, then separately opens the bills list, filters to the blocked bills the run left out, and reports each one with the reason it is on hold - a pending goods receipt, a quantity or price mismatch against the purchase order, or a missing PO reference. Writes a CSV of what will be paid and what will not.
- Invoice Inbox to LedgerReads vendor-invoice e-mails out of the mailbox and posts each one as a bill in the ERP. It reads the vendor, reference, gross and purchase-order number from each message, derives the net, and keys a new bill - handling the two controls that fire mid-batch: a duplicate reference (cancelled rather than paid twice) and a failed 3-way match against the purchase order (posted but blocked). Writes a posting report. The story is straight-through processing with judgment: the clean invoices post themselves, and the two that should not go through are caught and reported.