Monday Morning Briefing
Overview
One 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.
Monday Morning Briefing
Every Monday, someone opens five browser tabs to find out where the week's work is: the CRM, the mailbox, the ERP, the carrier portal and the help desk. Each holds a queue; none talks to the others. This is the demo that ties the whole set together — one robot that visits all five, reads the single number that matters from each, and hands back one page before anyone has had coffee.
It is the composite of the individual back-office flows — CRM hygiene, invoice posting, bank reconciliation, shipment tracking and refund triage — reduced to their headline counts and gathered into a briefing.
It spans five fictional training systems — Zapspot, Lookout Mail, RAP One, SlugExpress and Grumpdesk — whose data is entirely synthetic.
What it produces
monday-briefing.csv in your home folder: one line per system with its headline count, and a total
across all five. On the seeded data that is:
| Area | Items | System |
|---|---|---|
| Duplicate contacts to merge | 12 | Zapspot CRM |
| Invoices to post | 12 | Lookout Mailbox |
| Ledger exceptions to review | 8 | RAP One ERP |
| Shipment exceptions | 30 | SlugExpress Carrier |
| Refund requests to decide | 8 | Grumpdesk Help desk |
| TOTAL | 70 | five systems |
How it works
The robot signs in to each system in turn and reads one number:
- CRM — duplicates to merge. Opens the duplicates view and counts the duplicate pairs.
- Mailbox — invoices to post. Counts the vendor-invoice e-mails in the inbox.
- ERP — ledger exceptions. Filters the vendor bills to exceptions only and reads the count.
- Carrier — shipment exceptions. Opens the exception worklist and reads the count.
- Help desk — refunds. Filters to refund tickets awaiting a decision and counts them.
Then it writes the briefing: one line per system, a total, and where each queue lives — the starting point for the deeper flows that actually work each queue.
Running it
Ready to run as-is. It signs in to all five systems with their published training credentials, 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.
- Logistics Exception CenterBuilds 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.
- 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.