Skip to content
Load Agent

Broker stand down cancels the ETA chain

← All scenarios

Broker stand-down becomes a Hero task; a Hero override then cancels the chain.

Client A dry van EscalationModel callDo nothing 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 6

    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:15 AM Step 2 of 6

    Broker says stand down in Slack: a Hero task and a TMS note, the ask and its timer stay

    matches the eval

    In

    Slack from broker

    I called the driver, stand down.

    Decide

    Escalated

    news no ask waits for, recorded in the TMS; broker news while an ask is open, a Hero decides whether it stands down

    1 model call: triage 2 delivery outcomes recorded

    Out

    TMS note to TMS
    Load 481207: the broker wrote on slack: I called the driver, stand down.
    481207/evt:slack_0715/tms_note
    Hero task to Hero teamabout the broker
    Load 481207: broker message may affect open ask ask:eta_request:ping_0700: Slack message from the broker (brk_0087): "I called the driver, stand down.". The agent did not act on it and its follow-ups continue. Open asks: ask:eta_request:ping_0700 (eta_request, stop 1). If the message means the request is moot, close it with an ask override (the ask id above) so the agent stops texting and escalating.
    481207/evt:slack_0715/create_hero_task
    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
  3. 7:18 AM Step 3 of 6

    A Hero confirms and overrides the ask: cancelled, nobody is contacted

    matches the eval

    In

    Hero overrideoverride_0718

    Decide

    Human override client_a/delay_risk_high@v1

    override by hero hero_ana: Broker called the driver, ETA confirmed by phone, 1 ask(s) closed

    No model call 1 delivery outcome recorded

    Out

    Timer cancelled481207/ask:eta_request:ping_0700/1/cancel_timer

    No message sent: only timer or stage bookkeeping.

    Asks after this step 0 open
    • ETA requestCancelled
      Target
      driver
      Stop
      Riverbend plant
      Attempts
      1 of 2
      Next timer
      none
      Why closed
      override by hero hero_ana: Broker called the driver, ETA confirmed by phone
      SOP
      client_a/delay_risk_high@v1
      ask:eta_request:ping_0700
  4. 7:19 AM Step 4 of 6

    The same override by type matches no open ask: noop

    matches the eval

    In

    Hero overrideoverride_0719

    Decide

    Human override

    the override matches no open ask

    No model call

    Out

    Agent did nothing (correct) No message, no task, no timer.
    Asks after this step 0 open
    • ETA requestCancelled
      Target
      driver
      Stop
      Riverbend plant
      Attempts
      1 of 2
      Next timer
      none
      Why closed
      override by hero hero_ana: Broker called the driver, ETA confirmed by phone
      SOP
      client_a/delay_risk_high@v1
      ask:eta_request:ping_0700
  5. 7:31 AM Step 5 of 6

    The cancelled timer does not fire

    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 0 open
    • ETA requestCancelled
      Target
      driver
      Stop
      Riverbend plant
      Attempts
      1 of 2
      Next timer
      none
      Why closed
      override by hero hero_ana: Broker called the driver, ETA confirmed by phone
      SOP
      client_a/delay_risk_high@v1
      ask:eta_request:ping_0700
  6. 8:01 AM Step 6 of 6

    No escalation: no dispatcher email, no second Hero task

    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 0 open
    • ETA requestCancelled
      Target
      driver
      Stop
      Riverbend plant
      Attempts
      1 of 2
      Next timer
      none
      Why closed
      override by hero hero_ana: Broker called the driver, ETA confirmed by phone
      SOP
      client_a/delay_risk_high@v1
      ask:eta_request:ping_0700
Prepared for Freight Hero by Marcus Caum Source on GitHub