Skip to content
Load Agent

Unknown situation escalates to hero task

← All scenarios

An unclassifiable broker Slack message becomes a Hero task, nothing else.

Client A dry van EscalationModel 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. 9:00 AM Step 1 of 1

    Broker Slack message no SOP covers: Hero task, no contact is messaged

    matches the eval

    In

    Slack from broker

    Receiver says pallet 4 is crushed and wants to reject the whole load. Handle it.

    Decide

    Escalated

    message could not be classified safely

    1 model call: triage 1 delivery outcome recorded

    Out

    Hero task to Hero teamurgentabout the broker
    Load 481207: unclear broker message: Slack message from the broker (brk_0087): "Receiver says pallet 4 is crushed and wants to reject the whole load. Handle it.". No SOP covers this and it could not be classified with confidence (triage confidence 0.20). The agent sent nothing. Please review and respond if needed.
    481207/evt:slack_0900/create_hero_task
    Asks after this step 0 open

    No asks on this load yet.

    Prepared for Freight Hero by Marcus Caum Source on GitHub