Significantly expanded booking-agent configuration: administrators can control human escalation and notifications (including choosing one clear escalation delivery mode instead of two confusing switches, and turning off automatic escalation once a human has replied), follow-up cadence and nudge limits, how high the agent may negotiate (including a configurable ceiling at both the policy and rule level, with named negotiation modes), what load details are shared before a carrier is identified, commodity disclosure tiers, which offer sources the agent engages with (including consolidating carrier offers from multiple sources with proper attribution, and a "collect offers only" mode that logs offers without countering), a connected Gmail mailbox for booking conversations, and automatic hand-off to a human rep once one joins the conversation.

Extended the booking agent to engage carriers automatically from more sources: it now reaches out when a carrier posts an available truck on Highway, recognizes more Highway offer and booking-confirmation messages, and can pick up inbound calls handled by an overflow carrier-sales line.

Added the ability for a workspace to configure its booking agent's persona and personality guidelines.

Added the ability to assign and remove booking reps (not just yourself) on a load post, including via automation rules that auto-assign a rep with a given role.

Added a redesigned booking board for carrier sales reps that surfaces load-triage signals directly on the board, for enterprise workspaces in the new experience.

Added the ability to resolve or clear "Needs attention" and "Escalated" states on booking-board conversations.

Booking conversations now appear directly on load posts alongside offers, so reps can see and act on carrier conversations without leaving the post.

Added a custom HTML email signature, with support for uploaded signature images, that brokers can set per connected mailbox on booking-agent emails, along with a per-mailbox address tag; booking-agent conversations now also correctly reflect messages a rep sends from their own connected Gmail or Outlook inbox.

Added an opt-in setting for enterprise workspaces so the booking agent can recall carrier relationship notes written by any of the enterprise's workspaces, not just the one currently talking to that carrier.

Added support for connecting more TMS and ELD providers for automatic load tracking and syncing, including Quantum ELD, Tai, McLeod (DFM, API Module, and carrier webhook), 3PL Systems, FiveELD, and PandaELD.

Added support for four more ELD providers: Apex Ultima, QuantumELD, Next Fleet, and Orient ELD.

Added support for tracking loads through TrendyELD and Konexial (My20).

Added support for two more public external tracking-link providers: Monarch Tracking and, later, NewELDWorld and Loadbase.

Added support for McLeod DFM as an inbound TMS integration source.

Added the ability to pause and resume automatic inbound data sync for a TMS integration directly from each integration's settings.

Added a raw TMS status field alongside Chain's normalized shipment status, now available across McLeod and ten other default TMS providers, and as a condition when building Autopilot automation rules.

Added DAT load board posting for partial loads, with the live posting automatically kept in sync when the load's details change.

Added the ability to publish tracking-agent checkpoint outreach back to your connected TMS as an outbound event, and to filter TMS event integrations by which checkpoint triggered them.

On-demand load sync is now available for McLeod API Module integrations, matching the existing daily sync for McLeod DFM.

Added one-click bulk sync to pull all supported shipments from a connected TMS on demand, instead of relying on automatic sync alone.

Added automatic posting of loads to Load Board 1 driven by your TMS's own "post to load board" flag, with the posting automatically removed when a load is covered, cancelled, or deleted.

Added automatic extraction of container and line-item details from POD and BOL documents, with grouped handling-unit totals and source evidence shown in the product.

Chain now automatically sends an ELD connection request to a carrier as soon as they're assigned to a shipment, if they aren't already set up for ELD tracking.

Added a way to stop tracking a shipment from one specific ELD source (a truck or trailer number) without deleting the truck/trailer number and losing that data.

Added a client-credentials authentication option for Revenova integrations, letting customers connect using a lower-cost Salesforce API-only login instead of requiring a full interactive-login license, and a one-click button to deploy Chain's Salesforce components.

3PL Systems Portal integration can now enable location polling directly from its setup screen.

Added Manitoulin as a new supported carrier integration.

Added a shipment compliance panel that lets brokers configure driver verification requirements based on load classification (including by warehouse or facility) and see per-driver compliance status on each shipment.

Added saved shipment views, so a user's shipments-list filters and search can be saved by name and set to apply automatically on login.

Added a shipment history view showing when a shipment was created, its current and scheduled auto-close status, and its full open/close/reopen history, plus a dedicated Shipment Lifecycle view in the shipment details drawer.

Added an Overview tab to workspace Reports with executive-level tracking quality and attribution metrics, including per-carrier-rep tracking performance.

Added a view of a driver's historical device switches and reinstalls, not just their most recent device.

Drivers can now capture and submit shipment photos with secure capture provenance, so back-office and broker reviewers can trust a photo was taken directly in the app; shipment files also now flag when a driver's declared document type disagrees with Chain's automatic read.

Added a My Offers view in the driver app so drivers can track offers they've submitted, see status and rate, and jump back into the related conversation.

Added a Chat & Inbox setting to delay archiving a load's chat after it's delivered, canceled, or expired, instead of archiving immediately.

Added a setting for rate-confirmation email accounts so they can be used purely as an email transport, while regular shipment notifications keep using their normal recipients and templates, and added support for sending booking and tracking emails through a customer's own rate-confirmation mailbox instead of only Chain's default sender.

Added granular notification controls: team members can opt in to shipment notifications, enterprise admins can see and manage pending workspace access requests, and post-offer emails (accepted, declined, made within range) now have their own dedicated settings.

Reports access can now be granted directly when inviting a team member, and applied in bulk across enterprise workspaces.

Added self-service options for the email sending domain used for outbound notifications — customers can now use a custom DKIM selector or authenticate a root domain instead of only a subdomain.

Added workspace-level message signature suppression, so a configured email signature is stripped out before inbound messages are processed.

Added an Email Delivery monitoring view where you can search and inspect email send activity by load number, with date and time sorting.

Added automatic follow-up scheduling on tracking-agent checkpoints when a reply is incomplete or never received, plus an optional one-time delay before a checkpoint follow-up fires.

Load-post broadcast emails can now be branded per workspace, with a configurable logo, company name, and color theme, plus a preview before sending.

The Chain MCP server can now create a new Autopilot rule from scratch — trigger, conditions, and actions — not just manage existing ones, so AI assistants connected to Chain can build automation directly.

The Chain MCP server's shipment search can now filter by nearly anything the app's own filters support, including pickup state, equipment mode, and specific appointment dates, not just a limited set of preset filters.

The Chain MCP server can now attach or remove a third-party tracking link on a shipment in one step, so AI assistants like Claude, Cursor, and Codex can manage tracking links directly; this also closed a gap where several tracking-link actions were unintentionally callable without authentication.

Added Customer API sender admission controls and sender intelligence, letting broker teams manage which sender categories are allowed and review which purchased Customer API products are active for their workspace.

The Customer API's /loads and /carriers endpoints now return which workspace owns each load and who made the request, making results easier to attribute for enterprise integrations.

Improved booking escalations: assigned reps now get a briefing before an escalation reaches the carrier, and brokers can configure an ordered chain of who gets notified — including a carrier's most recent booker — instead of one fixed recipient list; the escalation email itself was also redesigned to lead with clear load, rate, and carrier details instead of raw internal reasoning.

The booking agent now proactively offers a clearly labeled nearby load when an exact search comes back empty, instead of waiting to be asked a second time, and now shares equipment requirements (like straps or load bars) up front instead of withholding them.

Made the booking agent's replies to carriers consistently include full load details — weight, commodity, and temperature range for reefer loads — across every reply type.

A booking rep who replies to a carrier from the app now joins that email thread and stays copied on later replies from both the agent and the carrier.

Booking Conversations access is no longer limited to workspace admins or a hardcoded list — it now follows each workspace's actual booking agent setup.

Improved the booking board with accurate offer counts and totals, faster server-side filtering and sorting, a flag when the agent goes silent without replying to a carrier, and automatically hiding loads whose pickup window has already passed (with an overflow toggle to see them again).

Enriched the booking-conversation panel with carrier contact details, live ELD status, a working link to the carrier, sender email, last-message time, and a message preview, so reps can triage without opening the conversation.

Clarified how booking rules relate to the policies they reference, so it's clear when editing a rule will or won't change the underlying policy, and brokers can now see whether an offer was submitted from the web app or the driver app.

Improved truck and trailer tracking reliability: if a tracking source can't be found right away, Chain now automatically keeps retrying instead of requiring a manual remove-and-re-add, and increased how long a source is retried before being marked inactive.

Improved shipment tracking pings to render in the ping's own local time zone instead of the viewer's browser time zone, fixing detention-time discrepancies on the map, and stopped tracking maps from unnecessarily reloading when switching shipments or during background updates.

Workspace tracking reports now show how many tracking stalls or breaks occurred on a shipment, with detailed, timestamped stall records showing exactly when and for how long tracking stalled.

Exposed TMS-provided pickup/delivery reference numbers on shipment stops, previously invisible in the product.

Added the ability to retry outbound integration requests that failed to reach a customer's TMS or platform, so failed syncs can be resent without manual rework.

Carrier fraud (GPS-spoofing) alert emails now reflect the actual tracking status of the recipient's own loads, instead of one generic alarming message regardless of whether their shipments are affected.

Location tracking pings sent to Infios now cover pickup stops, not just deliveries, and FourKites now also sends stop-level appointment updates.

Made Salesforce/Revenova integration setup safer by only provisioning Salesforce components when explicitly requested, and Revenova now writes the assigned driver's phone number back to the load.

Driver verification and compliance lifecycle events (completed, requested, reminders, required, cancelled) are now published to your connected external integrations, and truck and trailer numbers captured by Autopilot are now sent back to your TMS and included in the related email.

Autopilot rule conditions can now match a text field against a list of values ("is any of" / "is none of"), support "is between" and "exact time" on more date-based conditions, evaluate "X minutes ago" comparisons for arrival and departure, add a Carrier TMS ID condition for tracking agent rules, and expose customer and carrier sales rep IDs for building more precise rules.

Broker notification emails now include the customer, lane, carrier MC number, and reason instead of the bare minimum, and shipment lists now show each carrier's live ELD status instead of a value that could go stale.

Redesigned chat mute into an always-visible toggle with clearer feedback, and redesigned the pickup/delivery stop card in the driver app with clearer maps and fixed address rendering.

Removed the loadboard promotional banner from the driver app's shipment details page.

Fixed numerous issues with booking-agent escalation notifications not reaching the right people — assigned reps missing in-app alerts or briefing emails, carriers occasionally seeing internal reply copies, escalations failing to trigger for some workspaces or for offers without a stated price, escalations still notifying reps after they'd turned them off, and settings checkboxes that didn't do what they said.

Fixed several issues in the booking agent's negotiation and rate-ceiling logic, where a per-load or rule-level policy could grant more negotiating room than the workspace allowed, an unset policy could silently pin itself to the wrong default, or the agent could quote an opening offer below the authorized ceiling.

Fixed the booking agent failing to find or correctly match the load a carrier was asking about (due to reference numbers, city abbreviations, or wording differences), quoting a rate for the wrong load, sending corrupted or repeated load and stop details, discarding a carrier's stated price instead of recording it as an offer, and losing track of which load a conversation was about.

Fixed the booking agent resuming messages to a carrier after a human rep had already taken over, sending the same reply multiple times after a period of silence, using unnatural conditional phrasing, re-asking for information (a load, or an MC/DOT number) already provided, sending malformed load summaries on a carrier's first message, and occasionally stopping mid-negotiation.

Fixed carrier-facing booking emails showing incorrect branding, the email parser occasionally destroying the content of an inbound carrier message, a carrier's quoted reply thread being misread as a new message, the agent's own suggested rate being recorded as if it were the carrier's offer, and messages from a connected mailbox not showing up correctly in the conversation.

Fixed issues that let a carrier or dispatcher removed from a shipment continue sending messages into that shipment's chat, and shipment chat messages that included unwanted Outlook auto-signature text pulled in from email replies.

Fixed a bug that could create duplicate shipment chat messages from Gmail-based rate confirmation processing, and a live outage where Gmail-connected mailboxes stopped sending because of missing OAuth configuration.

Fixed an issue where enabling carrier vetting on a workspace could silently cause the booking agent to stop responding to carriers at all, or appear to enable vetting when it did nothing.

Fixed several more issues in the booking agent's negotiation, rate-counter, and escalation logic that could stall negotiations, miss escalations to reps, or send duplicate or incorrect replies, and email-threading issues including dropped carrier replies to rep-sent messages and broken subject lines on escalation follow-ups.

Fixed duplicate, missing, or misrouted shipment-chat and rate-confirmation email notifications.

Fixed the booking board's conversation view failing to load, showing the wrong "last activity" time or carrier identity, the conversations section disappearing from load posts entirely, a data-pipeline gap that prevented a load's attention status from updating, a Lane column that cut off key details, and no visible feedback while the board re-sorts.

Fixed a data pipeline gap where an update from a TMS could silently wipe out every assigned rep on a load (disabling escalation notifications), rep replies sent from a connected Outlook or Gmail inbox being dropped from booking conversations, and replying from the app not reliably keeping the sender on the thread for all users.

Fixed the booking conversations list not updating automatically when a new conversation started while the page was open, and a pagination bug that could skip real results.

Fixed numerous issues that prevented loads from being reliably posted to and found on the DAT load board — wrong equipment codes, incorrect pickup/delivery dates and windows, postings not appearing for certain truck types or reaching no audience at all, missing or incorrect load reference numbers, and the app not remembering your DAT username.

Fixed a bug where a location update coming from a customer's TMS could be echoed back to that same TMS, causing incorrect or duplicate location data, across 3GTMS, McLeod, Revenova, Tai, 3PL Systems, Sunnybrook, Turvo, and Transport Pro integrations.

Fixed several QuoteFactory sync issues: the Chrome extension's TMS Companion setting not actually stopping sync when turned off, re-syncs not repairing a stop stuck with missing origin information, failed batch syncs, incorrect BOL/ID display, wrong rate field, missing origin, a workspace-link bug, and rate/driver field mapping not matching confirmed TMS data.

Fixed a tracking pipeline issue that caused driver tracking cards to stop appearing after certain shipment updates, and the driver app showing multiple, conflicting tracking status cards for the same driver.

Fixed an issue where an automatically parsed driver message about a different load could incorrectly change the status of an already delivered or canceled shipment, and an issue where drivers could see "User not found" on login even though their account existed.

Fixed retried document uploads to Salesforce/TMS integrations landing as raw data instead of a properly named file, and Salesforce outbound integration writes being reported as successful even when they were rejected.

Fixed several issues that could prevent an external tracking link from working — links wrapped by email security scanners, stale ELD-provider versions, and TMS-specific link generation bugs — and tracking breaking for DSGELOGS and EvoELD after platform changes on their end.

Fixed public tracking links for enterprise workspaces not including shipments from their child workspaces (now available as an opt-in setting), and newly enabled Tive tracking integrations showing up grouped under the wrong integration name.

Fixed shipment compliance workflow rules silently failing to match hazmat, origin, and destination conditions, and driver verification documents getting stuck in progress or showing outdated status.

Fixed carrier MC number lookup failing to find carriers already known to Chain under their DOT number, and duplicate tracking sources being created for some ExpediteAll-tracked shipments.

Fixed enterprise notification settings for non-member users not saving, and older workspace access requests not showing up in the enterprise view.

Fixed a bug where certain TMS load changes could create a duplicate shipment instead of updating the existing one, and a bug that could create a duplicate load posting when a post's status changed.

Fixed Autopilot repeatedly re-asking a driver for a load's ETA or appointment status after they'd already answered, occasionally mis-recording an on-time reply as a past-dated ETA, and a booking-agent Autopilot condition silently saving 0 when a numeric field was cleared instead of leaving it unset, and saving Autopilot rules with single-select conditions failing outright.

Fixed false "high risk to miss the appointment" alerts for trucks that were actually running early, and scheduled location updates continuing to replay a stale position and ETA indefinitely on loads that had already expired.

Fixed inbound emails being silently and permanently lost when the mail provider temporarily failed to return them (they're now retried and recorded), email subject lines showing garbled text when they contained special characters, and deleting an email configuration with a mixed-case address silently failing.

Fixed BOL/POD attachment links not working when the document arrived through certain message sources, and shared links (load share, tracking share, privacy policy/terms) pointing at an outdated domain.

Fixed notifications continuing to be delivered after a user turned off personal, workspace, or enterprise notification controls, and workspace tracking reports and Tracking Reports both undercounting loads by leaving out expired shipments.

Fixed connected Gmail mailbox notifications silently stopping after seven days by renewing the underlying subscription before it expires, and generated rate-confirmation emails and their attachments appearing where they shouldn't.

Fixed some shipment activity history entries going missing when a driver was unassigned or a team member was removed, and a dispatcher's email address being lost when it was supplied after their account already existed.

Fixed outbound notification emails still showing outdated branding, and the Exception Detected alert email showing duplicate text for automated checkpoint reviews.

Fixed the Network Connections page crashing when sorted by number of loads or trips, and a removed connection incorrectly still showing as active.

Fixed the shipment ingest API returning a generic server error instead of a clear authentication error for an invalid or missing API key, and an error that could break the private load post board.

Fixed the TMS mapper editor to accurately reflect what transforms and filters actually do, instead of silently discarding parameters or mislabeling supported transforms.

Fixed the Ryder carrier integration setup, which failed to enable and asked for unnecessary configuration; it now only requires a TMS customer ID.

Fixed workspace verification failing for brand-new companies signing up through carrier onboarding, on both the web and driver apps, and duplicate device and tracking entries plus OTP verification failures when the driver app is uninstalled and reinstalled on the same phone.

Fixed driver app logins getting permanently stuck after repeated device verification failures on iOS, and the driver app's "Rate our app" popup not reliably appearing when requested.

Clarified the background location permission flow in the driver app so drivers no longer mistake instructional steps for buttons, and get clear feedback if permission still isn't granted.

Fixed "Available Trucks on DAT" truck suggestions, which were broken and only showing on loads already posted to DAT.

Carriers no longer see the internal "Bookmarked" offer status, which is meant for brokers only.

Fixed the dark/light theme toggle in embedded sidebars (Chrome extension, Outlook, Front) not actually changing the page's theme.

A load's live tracking status now correctly degrades from "Moving" to "last seen" after tracking pings stop, instead of showing a stale in-motion status indefinitely, and the shipment Motion indicator no longer incorrectly shows Stationary while a truck is actively moving.

Fixed the ELD asset location preview getting stuck on "Preparing location preview" for existing truck/trailer selections, and the tracking map showing a different ping time than the stop card for the same event.

Fixed an upload error in the chat photo picker that could leave the screen stuck loading, chat surfaces getting stuck on an open-ended spinner during an outage (now showing a clear unavailable state), and the inbox Unread filter opening the wrong conversation after reading one.

Fixed the driver app's stop count sometimes showing "1 Pick, 1 Drop" on multi-stop loads, long commodity labels overflowing their badge, and load locations rendering with a missing or null state (e.g. "Bolingbrook, null") on the carrier hub.

Fixed workspaces that had never configured the booking agent being unable to set one up at all, rewrote confusing booking-agent settings copy that had caused a real misconfiguration, and made long condition lists collapsible.

Fixed booking policy changes failing to save in production, and saving a booking rule silently corrupting the shared behavior it referenced.

Fixed the embedded tracking map showing "No tracking data found" for valid shipments in cross-workspace embed views.

Fixed a shipments page crash for workspaces with a pending, unclaimed invitation and an active team-member filter, a Connections page crash caused by orphaned workspace invitations, and several web dashboard crashes (workspaces, invitations, API keys, email settings, offers) caused by unexpected empty data from the server.

Fixed a tab freeze on shipment pages whose title contains certain whitespace, and the shipment VIN display being clipped instead of showing the full identifier.

Fixed sessions left open for days not refreshing after the access token expired, which could show a Forbidden error.

Fixed email sending-domain setup so the sending subdomain is optional and the generated DNS host name is explained.