Example bot · Process Watchdog
Rex, your process watchdog
Rex is a process watchdog that watches for things breaking around your ERP, like failed syncs, stuck orders, past-due jobs, and exports that did not run, and tells the right person what broke, where, and what it affects. It is an example bot Compass AI builds around the ERP you already run, and it only alerts: a person approves any fix, rerun, or change to a record.
Never sleeps, never panics.
The work today
The problem it takes off your plate
Most breakages get found late, when a customer calls about an order that never moved or someone notices last night’s export never ran.
- A sync between the ERP and another system fails quietly
- Orders sit in a status nobody is watching
- Reports built on an export that did not run
Step by step
How Rex works
One job, step by step. The last step is always yours.
On a schedule or after a job
Checks the usual suspects
Looks at the sync logs, order statuses, due dates, and exports you have told it to watch.
When something looks wrong
Spots the problem
Notices a failed sync, an order stuck longer than your rule allows, or an export that did not run.
Before it alerts anyone
Works out what it touches
Looks up the orders, jobs, or customers affected, so the alert is useful instead of noise.
As soon as it knows
Hands it to you
The owner of that process gets a plain-English alert by email or team chat, and any fix or rerun is their call.
Same rules for every bot: one job, inside your systems, nothing changes without a person, and a plain-English note on what it did.
Your systems
What it works with
Around the ERP you already run.
ERP
Order and job statuses, due dates
Integration and sync logs
Between the ERP and the systems around it
Scheduled exports and reports
Checks that they ran
Email or your team chat
Alerts to the process owner
People stay in charge
What it never does without you
Rex only watches and alerts. A person approves any fix, rerun, or change to a record.
Always waits for a person
- Rerunning a sync or an export
- Changing an order or job status
- Any fix to a record
A person approves anything that changes a record, spends money, or goes to a customer or vendor.
Questions
Questions about Rex
No. It tells the right person what broke and what is affected. Fixes, reruns, and record changes stay with your team.
You decide. Each kind of problem goes to the person who owns that process, so alerts land with someone who can act.
You set what counts as a problem and how alerts are grouped. Each alert says what is affected, so people can tell what matters.
The things you point it at around your ERP: syncs, order and job statuses, due dates, and scheduled exports or reports.
Let's talk
Want a bot like this in your shop?
Book a 30-minute fit call. Tell us how this work runs today, and we will tell you plainly whether a bot like this fits around your ERP.