Skip to content

Client A PO from instructions

← All scenarios

Literal assignment load JSON; the PO is parsed from the instructions and answered.

Client A dry van Model call eval passes
Load 481207: Riverbend Foods, 2 stops, 3 contacts

Stops

  1. Riverbend plant (pickup)
    Oct 13, 6:00 AM PDT to Oct 13, 2:00 PM PDT
  2. Valley DC (delivery)
    Oct 14, 9:30 AM PDT

Contacts

  • driver drv_20931 sms
  • dispatcher dsp_4410 email
  • broker brk_0087 email, slack
  1. 7:01 AM Step 1 of 2

    Ping turns delay risk high: SMS the driver for the ETA

    matches the eval

    In

    Location ping: delay risk high for stop 1

    Decide

    SOP client_a/delay_risk_high@v1

    followed client_a/delay_risk_high@v1

    No model call 2 delivery outcomes recorded

    Out

    SMS to driver
    Load 481207: what is your ETA to Riverbend plant? Please reply with the time.
    step 1 of ask:eta_request:ping_0700481207/ask:eta_request:ping_0700/1/send_sms
    Timer set for 7:31 AM PDT481207/ask:eta_request:ping_0700/1/set_timer
    Asks after this step 1 open
    • ETA requestOpen
      Target
      driver
      Stop
      Riverbend plant
      Attempts
      1 of 2
      Next timer
      7:31 AM
      SOP
      client_a/delay_risk_high@v1
      ask:eta_request:ping_0700
  2. 7:13 AM Step 2 of 2

    Driver asks for the PO: answered with 55821 parsed from the instructions

    matches the eval

    In

    SMS from driver

    What's the PO number?

    Decide

    Triage

    answered po_number from load data

    1 model call: triage 1 delivery outcome recorded

    Out

    SMS to driver
    Load 481207: the PO number is 55821.
    481207/evt:sms_0712/send_sms
    Asks after this step 1 open
    • ETA requestOpen
      Target
      driver
      Stop
      Riverbend plant
      Attempts
      1 of 2
      Next timer
      7:31 AM
      SOP
      client_a/delay_risk_high@v1
      ask:eta_request:ping_0700
Prepared for Freight Hero by Marcus Caum Source on GitHub