Do I have to learn a rules language?

No. Playbook rules are written in plain English, on the Playbook page or by asking Zippy, and you read the drafted rule before saving it. Every rule written that way starts in Shadow.

Will StatVault start assigning on its own the day we sign up?

No. Nothing is assigned automatically until an admin writes a rule and explicitly switches it to live. A rule can run in Shadow first, where it only logs what it would have done.

What is a good first rule?

After hours. Most couriers start with the orders that land when nobody is at the board: a named on-call driver for a lane, or the best-scoring driver for overnight STAT work, each as a rule an admin has explicitly turned on, with anything else escalated to Slack.

Can a rule undo a dispatcher's decision?

No. An arrival rule never runs again once a dispatcher assigns or moves the order, and rules never move an order that has already been picked up.

How do I know what a rule did?

Every assignment is recorded with the rule's name as the actor, in the same record a dispatcher's assignment goes into, and each rule keeps its own history of what it executed, skipped or could not apply.

Can Zippy assign for me during the day?

Yes. Ask in plain English on the web or in Slack and Zippy makes the change after you confirm it, recorded with Zippy as the actor.

Instant dispatch for medical couriers, even after hours

It is two in the morning. A STAT order lands from a hospital lab and nobody is at the board. In most courier offices that order waits for a phone call, an answering service or a dispatcher who wakes up. With StatVault it can have a driver the moment it arrives, auto-assigned by a rule your team wrote in plain English during the day and an admin tested and turned on. After hours is where instant dispatch earns its keep.

Two kinds of rule, both off until you turn them on

A Playbook play names the driver. "When a new order arrives for this lane in the evening, give it to the on-call driver." Once an admin has explicitly saved the play as live, it puts the order on that driver, updates CXT and notifies the driver's phone, exactly as if a dispatcher had done it on the board.
An Automaton rule picks the best driver, once an admin explicitly switches it to live. Its pick is the driver the dispatch scorer ranks first: live position, today's work, lane history by time of day, and who is out. Use it where any qualified driver will do.

Both kinds can run in Shadow first: there they watch live traffic and log what they would have done, without touching an order. Nothing fires until an admin saves the rule as live.

Rules written in plain English

There is no code and no rules language to learn. On the Playbook page, type the rule the way you would explain it to a new dispatcher, such as "if a STAT order for the hospital lab arrives after eight at night, give it to the on-call driver", and StatVault drafts the conditions and actions for you to read over before an admin turns it on. Or ask Zippy in chat or in Slack, in the same words, and Zippy drafts the play for you. Either way, a rule written in plain English is always saved in Shadow first, and it acts only after an admin has explicitly switched it to live, so nobody turns on automation by accident.

What no rule covers still reaches a person

A rule that cannot place an order does not drop it. Pair instant dispatch with an escalation play, such as "a STAT order still unassigned after a set time, overnight, posts to Slack", so the on-call dispatcher hears about it on their phone without having StatVault open. The rule's history says why it could not place the order.

A record for every automatic assignment

Every assignment a rule makes goes into the order's record with the rule's name as the actor, beside the assignments dispatchers make, so the morning shift can see exactly what happened overnight and why. Each rule keeps its own history of what it executed, what it skipped and what it could not apply. Rules never move an order that has already been picked up, and an arrival rule never runs again once a dispatcher has moved the order, so automation never fights your team.

During the day: the scorer and Zippy

When the board is staffed, the dispatch board suggests the best drivers with reasons and a dispatcher picks. Zippy makes the change on request, in plain English on the web or in Slack, after you confirm it. Instant dispatch is for the hours when nobody is there to click.

Questions couriers ask

Do I have to learn a rules language?: No. Playbook rules are written in plain English, on the Playbook page or by asking Zippy, and you read the drafted rule before saving it. Every rule written that way starts in Shadow.
Will StatVault start assigning on its own the day we sign up?: No. Nothing is assigned automatically until an admin writes a rule and explicitly switches it to live. A rule can run in Shadow first, where it only logs what it would have done.
What is a good first rule?: After hours. Most couriers start with the orders that land when nobody is at the board: a named on-call driver for a lane, or the best-scoring driver for overnight STAT work, each as a rule an admin has explicitly turned on, with anything else escalated to Slack.
Can a rule undo a dispatcher's decision?: No. An arrival rule never runs again once a dispatcher assigns or moves the order, and rules never move an order that has already been picked up.
How do I know what a rule did?: Every assignment is recorded with the rule's name as the actor, in the same record a dispatcher's assignment goes into, and each rule keeps its own history of what it executed, skipped or could not apply.
Can Zippy assign for me during the day?: Yes. Ask in plain English on the web or in Slack and Zippy makes the change after you confirm it, recorded with Zippy as the actor.