SOPs
Every team has rules that live in one person's head. Write each one once in Settings → SOPs, for a customer, a lane or everyone. The assistant reads the one that fits before it drafts anything, and an SOP can run as its own agent. On Growth and above.
A short procedure your team writes, and an admin publishes.
In the command bar or by voice, the way you already work: quote this, book that, write to the customer.
Before it acts, the assistant looks for a published SOP that matches, starting with the ones tied to the customer or lane in front of you.
You confirm the draft as you would any other. The exact version it read is logged, and Settings → SOPs counts the reads.
Switch on Run as an SOP agent and it starts from a trigger, reads the record, and drafts what the SOP says to do. It never changes a record or sends anything itself.
Three SOPs as a desk would write them, and what happens next.
Your SOP
Quotes for Acme Exports show the fuel surcharge as its own line.
What happens
Every quote the assistant drafts for Acme carries the fuel surcharge on a separate line.
Your SOP
A quote request with no dimensions gets a reply asking for them before anyone prices it.
What happens
Run as an agent on emails read as quote requests, it drafts that reply to the sender for you to send.
Your SOP
Every morning, flag any booked shipment that still has no pickup date.
What happens
Run as a daily agent across open shipments, it puts each one it finds on Needs attention for someone to pick up.
Start free, or talk to us about the procedures you'd write first.