Added reply-capable outreach emails for the booking agent. Carriers can reply directly to an outreach email, and Chain starts a conversation and carries the booking process forward from their response.

Added rep email escalation for the AI booking agent. When the agent escalates a negotiation, the assigned rep gets a full-detail email and can simply reply to jump into the conversation and take over — the AI stands down automatically.

Added configurable Booking Agent outreach policies, including exact send times (in pickup-local time or a chosen timezone) and posting loads directly to DAT as part of an outreach strategy.

Added a driver app load board with bidding, so carriers and drivers can search available loads by location, dates, and truck type, and submit a bid directly from their phone.

Added automated, AI-assisted verification of driver documents (Cab Card, Truck VIN, License Plate) on upload, including multi-photo capture and a review queue for brokers when a submission needs a closer look.

Added proof-of-delivery document capture in the driver app, with live camera preview, quality checks, and the ability to review, retake, and submit multiple photos.

Added a guided onboarding checklist for owner-operators connecting their carrier for the first time in the driver app.

Added proof-of-delivery documents and a Files section to public shipment tracking links, so anyone with a shared link can view PODs, bills of lading, and other shipment documents without logging in.

Added an on-demand "Sync from TMS" action that pulls the latest shipment details with one click, now available for Aljex, Turvo, and Sunnybrook.

Added support for the newer Aljex platform (Aljex Live), including choosing your Aljex version and enabling live tracking polling for both legacy and new connections.

Added Rose Rocket TMS shipment webhook syncing, QuoteFactory TMS shipment syncing, and Ryder as a connectable carrier app that automatically sends tracking updates (appointments, GPS, arrivals, departures).

Added support for CarrierView, Navixy, Vektor, and Cyntrx tracking links, and added AMPM as a connectable ELD provider.

Added automatic delivery of proof-of-delivery and bill-of-lading documents directly into connected McLeod and 3PL Systems TMS accounts.

Added Gmail support for rate confirmation emails (alongside Outlook), including inbox parsing and threaded replies, plus a guided sending setup and the ability to customize the rate confirmation email subject line to match your TMS's format.

Added shipment appointment-window conditions for Autopilot and integration rules — teams can trigger automations based on how close a pickup or delivery window is, down to the minute.

Added shipment/TMS order type (e.g. Dedicated, LTL, General Freight) as a visible detail and as a condition for Autopilot, checkpoints, tracking-agent, and booking-agent rules.

Added enterprise-wide notification management: admins can build reusable notification profiles and bulk-assign or bulk-update them across many users at once.

Added the ability to grant individual team members access to Reports without promoting them to Admin or Owner.

Added live movement status and an alert summary to the shipments table and drawer, so you can see at a glance whether a truck is moving and whether a shipment has any active alerts.

Added new Chain MCP tools that let AI assistants (Claude, Cursor, Codex) read and update workspace settings, developer API keys, driver verification settings, Autopilot rules, app-download automation, and enterprise notification settings on your behalf.

Added a new external API for load and carrier lookups (for partner integrations like inbound-call voice bots), a standard carrier-sync endpoint, and a read-only load-matching API key scope.

Improved the AI booking agent's negotiation behavior across the board: recognizing acceptable rates and escalating to your team instead of continuing to haggle, holding a firmer posture on tough lanes, closing faster when an offer is close to target, avoiding repeated questions, and more accurately reflecting carrier offers in the conversation panel. Also improved Autopilot to correctly skip shipment types (like Dedicated freight) that shouldn't be automated.

Improved location-tracking reliability for Aljex- and McLeod-connected shipments, including always using the newest GPS position, fixing timestamps that could appear hours old, and backfilling tracking for shipments created before it was enabled.

Improved ETA accuracy by using real average truck speeds by state/province across the US, Canada, and Mexico instead of one flat nationwide assumption, and made the shipment tracking window configurable per workspace.

Strengthened fraud detection with cross-source GPS checks (mobile app, ELD, TMS) and device security re-checks, and reduced false-positive mock-location alerts so brokers only get emails for real signals with clear next steps.

Improved rate confirmation and shipment notification emails: correct sender names, fewer duplicates, grouped emails instead of separate messages per dispatcher, a refreshed visual design, and clearer plain-language wording on security and escalation emails. Also made delay/early-arrival email alerts opt-in rather than automatic for every team member.

Improved dispatch and load comment syncing from your TMS onto the shipment timeline, and made that context available to Chain's AI agents for more accurate automated responses.

Improved the accuracy and reliability of Autopilot and ZeroTouch analytics reporting — reports now distinguish verified results from not-yet-available data instead of showing misleading zeros, previously stuck reports recover automatically, and several display bugs were fixed. Also improved load speed for large reports and for enterprise member management pages with many members.

Restricted shipment compliance configuration changes to workspace admins and owners (viewing remains available to everyone), and added bulk removal of members from enterprise workspaces.

Improved shipment data accuracy for Revenova-connected fleets — correct team-workspace routing, accurate trailer/truck numbers, and carrier sales instructions surfaced as coverage comments. Added an opt-in fallback so scheduled integration updates still reach your TMS if the original real-time trigger is missed.

Improved the Chrome extension sidebar: added the third-party tracking link option, expanded TMS detection to more white-label domains, and fixed several context and tab-switching issues. Improved the public/external tracking view to show the same detail as the full workspace view (ELD status, truck/trailer numbers, references, commodity, equipment, files).

Fixed several issues in AI booking agent conversations: bare MC/DOT numbers misread as load references, scheduled follow-ups silently dropped after a carrier went quiet, the conversation panel not showing carrier verification status, and messages still sending after a user paused the AI. Also fixed the agent addressing the wrong carrier/driver after a shipment was reassigned, and replying to automated no-reply emails as if from a carrier.

Fixed shipments getting stuck showing "In Transit" after delivery when delayed carrier status updates were dropped, and fixed a truck driving past a stop being marked as departed and prematurely closing the shipment at the delivery stop.

Fixed low-accuracy GPS pings triggering coordinate spikes and false fraud flags, and fixed several causes of ocean/intermodal container tracking silently stalling, including rate-limited polling and missing public links for enterprise sub-workspaces.

Fixed inaccurate distance-to-next-stop estimates and stop times displaying in the wrong timezone, and fixed reassigning a driver leaving mobile tracking stuck inactive.

Fixed numerous TMS data-mapping issues across Aljex, McLeod, Revenova, and Rose Rocket that could show incorrect addresses, ETAs, appointment or equipment details, or sales rep/dispatcher/driver assignments, or block tracking and "View in TMS" links from appearing.

Fixed shipments going missing, appearing duplicated, tendering to the wrong carrier, or bypassing carrier/customer exclusion rules after a load's type or status changed upstream, and fixed inbound loads being silently dropped from ingestion entirely.

Fixed Aljex Live syncing so shipments beyond the first 50 were no longer missed, and fixed multi-stop Aljex loads only mapping pickup/consignee stops instead of all stops. Fixed Canadian carriers without a DOT/MC number being dropped from shipment records instead of retained.

Fixed several sign-in issues: duplicate accounts created behind the scenes, new drivers seeing "user not found," losing a previously verified email/phone if a change wasn't completed, drivers getting stuck signing in on iOS after a device-verification failure, and a Gmail sign-in failure.

Fixed a security gap that let a user in one workspace modify driver assignment on another workspace's shipment, and a separate gap that let a signed-in user view another workspace's billing/usage data.

Fixed API key scopes not being enforced correctly, and newly selected scopes sometimes not saving. Fixed excluding a carrier not actually canceling their active loads for certain enterprise accounts.

Fixed document classification accuracy for photos/PDFs in shipment chat (scanned PDFs like POD scans now read correctly), and fixed a photo sent for one stop incorrectly overwriting another stop's recorded arrival time.

Fixed shipment chat showing the wrong dispatcher or misattributing an inbound email to the wrong sender, and shipments with a large number of synced TMS comments no longer accepting new comments.

Fixed reordering or toggling booking policies partially failing and leaving them inconsistent, the integration logs page showing zero results when filtering by name, pickup ETA times showing incorrect estimates for certain shipments, and Autopilot alerts showing wildly incorrect timestamps.

Continued a large internal migration to a next-generation TMS-integration data-mapping engine, closing many data-accuracy gaps and expanding automated monitoring ahead of a full rollout.

Updated backend dependencies and cloud infrastructure to close security vulnerabilities and strengthen hardening, including encryption at rest, network isolation, credential rotation, and enforced encrypted database connections.

Improved backend reliability across shipment tracking, location lookups, and background jobs through fewer redundant reads/writes, tuned job schedules, and cached lookups.