Skip to content

Client B delay risk sms then slack never dispatcher

← All scenarios

Client B delay risk high; one SMS, then a broker Slack alert, never the dispatcher.

Client B dry van EscalationTimers 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 3

    Delay risk high: one SMS to the driver and a 30 minute follow-up

    matches the eval

    In

    Location ping: delay risk high for stop 1

    Decide

    SOP client_b/delay_risk_high@v1

    followed client_b/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, last attempt sent
      Target
      driver
      Stop
      Riverbend plant
      Attempts
      1 of 1
      Next timer
      7:31 AM
      SOP
      client_b/delay_risk_high@v1
      ask:eta_request:ping_0700
  2. 7:31 AM Step 2 of 3

    Timer: no ETA, alert the broker in Slack, no second SMS, no dispatcher

    matches the eval

    In

    Timer fired: ask:eta_request:ping_0700 attempt 1

    Decide

    SOP client_b/delay_risk_high@v1

    ask:eta_request:ping_0700 unanswered at step 1, continued client_b/delay_risk_high@v1

    No model call 1 delivery outcome recorded

    Out

    Slack to broker channel
    Load 481207: no ETA from the driver after our text and delay risk is high for Riverbend plant.
    step 2 of ask:eta_request:ping_0700481207/ask:eta_request:ping_0700/2/post_slack
    Asks after this step 1 open
    • ETA requestEscalated, waiting for a reply
      Target
      driver
      Stop
      Riverbend plant
      Attempts
      1 of 1, 1 escalation
      Next timer
      none
      SOP
      client_b/delay_risk_high@v1
      ask:eta_request:ping_0700
  3. 8:01 AM Step 3 of 3

    Nothing further: the dispatcher is still not contacted

    matches the eval

    In

    Clock tick: no timer was due

    Out

    Agent did nothing (correct) Nothing reached the agent, so nothing was sent and no model was called.
    Asks after this step 1 open
    • ETA requestEscalated, waiting for a reply
      Target
      driver
      Stop
      Riverbend plant
      Attempts
      1 of 1, 1 escalation
      Next timer
      none
      SOP
      client_b/delay_risk_high@v1
      ask:eta_request:ping_0700
Prepared for Freight Hero by Marcus Caum Source on GitHub