Feature Requests

I want ETA turned on automatically for every load so I don't have to enable it one by one. Right now some loads have it and some do not, and I have to set it manually inside each load.

I couldn't find where to enable ETA on a load so the miles would show. I had to ask support where that option is inside the load.

Problem When a Broker Update notification appears, the card shows the load context (status, load ID, driver, pickup/delivery) but nothing about which email account the update will be sent from. Clicking "Approve & Send" fires the message blind — the user has no way to confirm the sending identity before the broker receives it. This matters because: Carriers often have multiple connected mailboxes (dispatch@, updates@, personal user accounts, or a shared team inbox). Sending from the wrong one confuses brokers and can break their reply threading. If a mailbox was disconnected or re-authenticated, the user can't tell from the notification whether the send will actually go through or from where. There's no way to catch a misconfiguration until after the broker has already received it — sends are not reversible. Proposed solution Add a "From" line to the Broker Update notification card, above the Approve & Send button, e.g.: From: dispatch@carrierdomain.com Ideally alongside the existing "Also send to Telegram / Connected" row, so all delivery channels for the update are visible in one place. Nice-to-haves (secondary) If multiple mailboxes are connected, make the From field a dropdown so the user can switch sender at approval time rather than in settings. Surface a warning state on the card if the connected mailbox has an auth/token error, instead of failing silently after approval. Acceptance criteria Sender email address is visible on the Broker Update card before the user clicks Approve & Send. The displayed address matches the account actually used for the send. Applies to the Preview view as well.

A setting is needed on the broker side so that all loads related to a specific broker automatically have AI Updater features applied — for example, receiving notifications. Within the same framework of expanding AI Updater features for invoices: after an invoice is created and sent to the factoring company, a copy of such an invoice sometimes needs to be sent to the broker. Therefore there should be a setting for automatically sending a copy of the invoice to the broker.

Integration with Spireon and Thermo King already exists. Temperature needs to be displayed on the load page. Note that in addition to minimum and maximum temperature, acceptable deviations must also be included. If the temperature is outside the acceptable range, a notification must be sent to the dispatcher and such a load must be highlighted in Live Loads.

The Dispatch Board doesn't display ETA or a 'running late' indicator. Surface both inline on the board so dispatchers can spot at-risk trips without drilling in.

The new Live Loads page is missing two important filtering capabilities that were available in the previous version. Restore Truck Filter Previously, the Live Loads page had a dedicated Truck column, allowing users to filter loads by truck. In the current version, the truck information is displayed under the Driver column, which only allows filtering by driver. Customers need the ability to filter loads by truck, as this was an important part of their workflow. Restore On-Time Status Filter The previous Live Loads page also included an On Time column with filtering options for: On Time At Risk Late The new version no longer provides this filter. Many customers rely on Saved Views and use these statuses to prioritize and manage their daily operations. Without this filter, it is much more difficult to quickly identify loads that require attention. Expected Outcome Please restore: The ability to filter Live Loads by Truck. The On Time status filter (On Time / At Risk / Late). These filters were available in the previous Live Loads page and are essential for customers' daily dispatch workflow.

We need the Pick-up Check in Time, Pick-up Check out Time, Delivery Check in Time, and Delivery Check out Time as available columns in the Loads and Trips exports. These timestamps are crucial for our financial reporting, and having them in the export would streamline our process significantly. Is there a timeline for implementing this feature?

I need to share the driver's location with a broker using a link. This feature would allow me to easily communicate the driver's whereabouts to the broker without needing additional tools or applications. It would streamline the process and improve efficiency in our operations.

Problem The Geofence tab in the AI Updater panel is text-only. When geofencing is ON, the user sees the radius as a number ("1 mi radius") and, before any check-in happens, only the placeholder "No geofence activity yet." There's no way to see where the geofence circles actually sit relative to the stops, or where the truck currently is in relation to them. Users have to leave the panel and open the load page or an external map to answer basic questions: is the truck approaching the pickup fence, is the fence sized sensibly for this facility, why hasn't a check-in fired yet. Large yards, truck stops, and shipper campuses make a 1 mi default either too tight or too generous, and there's no visual feedback to judge that. Proposed Solution Render a map inside the Geofence tab (in the area currently occupied by the empty-state message), showing: Origin and destination stop pins, plus any intermediate stops The geofence circle around each stop, drawn at the configured radius The truck's last known position with its timestamp Optional route line between stops Additional behavior worth considering: Radius edits update the circle live so the user can size the fence visually before saving Check-in / check-out events plot on the map as they fire, with the event list remaining below or beside the map Map stays visible in the empty state instead of the text placeholder, since that's precisely when a user most wants to confirm the setup is correct