Real-time event notifications, located all in one placeReal-time event notifications, located all in one place

The system has two main dashboards: Quotes, for sending and receiving price quotes, and Loads, for communication, documents, and tracking. Each dashboard shows multiple loads, runs private chats, and sends quote requests to carriers. Dispatchers had to keep an eye on messages and updates across both, but the only signal was a small blue icon — meaning they had to flip between dashboard pages to find what changed.

A notification system that surfaces what matters, anywhere in the app. Users can filter the feed to only see the events relevant to their role.

Brokers, shippers, and carriers communicate constantly, especially during price negotiations for lanes (the start and end points of a journey). A shipper might request quotes from 100 carriers and chat with 20 at once. Prices vary by the mile and depend on route difficulty, weather, load type, and fuel surcharges. A missed notification turns into lost money.

• Cut dispatcher stress by making the system trustworthy
• Deliver load updates fast and accurately
• Shorten the time it takes to resolve issues
• Prevent the delays and misunderstandings that come from missed signals
• Put every event in one place dispatchers can see at a glance

I ran unstructured interviews with experts, stakeholders, customers, and dispatchers to figure out what the system actually needed to surface.

I worked through icon choices, colors, what information each event card needed, and how the elements should sit on the card. Early on, users could not tell read events from unread ones — that was the cue I needed to make the read/unread affordance much stronger.

Feedback on the early concepts made it clear: one feed for everyone wasn't going to work. Dispatchers care about exceptions and messages on active loads. Accountants want balances on completed loads. Other users sit on the quoting side and need RFQ activity. Same notification stream, very different priorities.

• Real-time events from across the system, all in one place
• Faster issue resolution that fed straight into the business
• Dispatchers could multitask without losing the thread
• Far fewer dropped messages between parties
• Per-role filtering kept the feed signal-heavy instead of overwhelming