Operations
Auto pilot
What the system does on its own when something happens, which of those actions are on, and a log of what it did.
Auto pilot is a small set of safe, automatic follow-ups. When a business event happens (a load is delivered, a customer pays, a carrier is created), the system can send a notification, an email or a document by itself. You choose which of these actions are on. Auto pilot never changes a load, a rate or a carrier's status: those decisions stay with people.
- Where
- Operations › Auto pilot (/autopilot)
- Who opens it
- Dispatch · view
- Who switches actions on or off
- Company · edit (owner and managers by default)
- Runs
- In the background, a moment after the event
- Audited
- autopilot.rule (each switch you change)
The events and their actions
| Event | Action | On by default |
|---|---|---|
| A customer is created | Notify the owning sales agent | Yes |
| Email the customer a welcome | No | |
| Tell finance a new account was opened | No | |
| A carrier is created | Remind compliance if still pending after 15 minutes | Always on (R11) |
| Tell dispatch a new carrier is waiting for clearance | No | |
| A load is created | Notify the operations desk | Yes |
| Notify the sales agent | No | |
| A load changes status | Notify the operations desk | No |
| A load is delivered | Generate the POD request | Yes |
| Email the POD request to the carrier's FMCSA address | No | |
| Email the customer that it was delivered | No | |
| Tell finance it is ready to bill | Yes | |
| A customer pays | Notify the sales agent | Yes |
| Notify finance | No | |
| A carrier is paid | Notify the sales agent | No |
| Tell dispatch the carrier was paid | No |
Actions that send documents follow the same rules as a person would. The POD request email goes only to the carrier's FMCSA-registered email (R3). If the customer has no email on file, the delivered email is skipped and the log says so.
What you see
The numbers band
| Number | What it counts |
|---|---|
| Rules on | Events with at least one action switched on. |
| Events fired | How many times events have fired. |
| Not fired yet | Events that have not happened yet. |
Rules
One row per event, with a plain description (for example Prepares the POD request and tells finance it is ready to bill) and its actions. Each action shows On, Off or Always on. If you can edit, each action that is not fixed has a switch instead.
Activity
The latest events, newest first: what happened (for example Load AR-0042 delivered), the record it was about, when, who triggered it, and how many actions ran. With nothing yet you see Nothing fired yet.
Switch an action on or off
Find the event
In Rules.Flip the switch
On the action. It saves at once.
The change applies to events from now on, for your whole company. It is written to the audit log with the before and after settings. Trying to change a fixed rule is refused: "Remind compliance if still pending after 15 minutes" is a fixed rule and always runs.