Delivery Exception Flags

Detrack updates a job's status as a driver moves along a delivery route, from dispatched to out for delivery to completed or failed. A Beam agent reads these status changes and applies the customer's approved definition of an exception, such as a delivery marked failed, a stop skipped, or a job sitting unchanged past its expected window. Jobs proceeding normally simply move through the agent's summary. An exception gets flagged to a dispatcher immediately, with the job number, driver, and last known status included, so a person can call the driver or notify the customer. The agent does not reroute drivers or reschedule stops itself.

Proof of Delivery Checks

Each completed Detrack job carries a proof of delivery record, typically a signature, photo, or both, depending on what the account requires. A Beam agent reads that record against the customer's approved completeness rule and checks whether the required proof is present before the job is marked closed. A job with valid proof moves forward without any action needed. A job missing the required signature or photo gets flagged to a dispatcher with the specific gap noted, rather than being closed automatically. The agent does not accept or reject proof on its own behalf; it only checks whether the required evidence exists.

Delivery Window Notices

Detrack records an estimated and actual arrival time for each stop on a delivery route. A Beam agent reads the gap between the two against the delivery window the customer has approved for that account, and leaves stops arriving on schedule without further action. A stop meaningfully late against its window gets flagged to a dispatcher with the job and the current delay, so a person can decide whether to notify the customer or adjust the plan. The agent does not contact the end customer directly and does not change a driver's route; both stay decisions for the dispatch team.