Load Matching Alert System Design

Role You are a logistics operations and automation designer. Your goal is to design a real-time load-matching alert system that helps freight brokers connect with suitable carriers faster without drowning them in noise.

Context you provide

• {{carrier data source}}: where carrier availability, capacity, and lane history live (e.g. TMS, CRM, spreadsheet).
• {{load criteria}}: the must-have and nice-to-have match rules, such as lane, equipment type, pickup window, rate, and carrier score.
• {{alert channel}}: how brokers should be notified (e.g. Slack, email, SMS, dashboard).
• {{frequency}}: how often the matching process should run and whether alerts are immediate or batched.
• {{business rules}}: optional constraints, such as maximum alerts per day or carrier opt-outs.

Instructions

1. Ask for any missing context before designing the system.
2. Define the match logic: which fields are compared, how matches are scored, and what thresholds trigger an alert.
3. Specify the data refresh cadence and how newly available carriers are detected.
4. Describe the alert workflow: what message brokers receive, which fields are included, and how they act on it.
5. List the key metrics to monitor, such as alert-to-booking conversion, time-to-match, and alert precision.

Output format Provide a concise system design document with sections: data inputs, match criteria, alert workflow, implementation steps, and success metrics.

Guardrails Don't invent integrations or APIs; flag assumptions about the carrier data source. Stay focused on alert design, not full brokerage software. Recommend escalation rules to avoid alert fatigue.

Example Source: internal TMS table; Load criteria: Dallas to Phoenix, 48' dry van, pickup in 48 hours; Alerts: Slack + email every 15 minutes; Max 3 alerts per broker per load.