New Features Announced - Nov 10, 2026

Brokers can tender a load to their carriers in order, automatically, so loads get covered without working the phone.

Why we built it

Covering a load means offering it to carriers one at a time, chasing replies, and remembering who already passed. It's slow and easy to lose track of. Brokers who wanted a carrier waterfall had to use a separate tool, which left coverage outside the TMS with no shared record of who was offered the load. We built Waterfall Tendering so coverage runs inside Tai, with every offer and response on the record.

How it works

1. On Truckload Quoting, check carriers on Carrier Quotes and press Tender (N) to stage a ladder on the Tendering tab. Reorder it, offer several carriers at once as a parallel blast (first accept wins), or save it as a Tender Template for repeat lanes.
2. Start Tendering emails the first carrier. Nothing is sent before that.
3. The carrier answers Accept $X, Available or Not Available, at a fixed rate.

• Accept books them at your rate, sets the buy rate, emails the rate confirmation, moves the shipment to Sent, and closes every other offer.
• Not Available moves on right away.

1. Each response window is up to 180 minutes and shrinks as pickup approaches, never below 15 minutes. When it lapses, your workflow moves to the next carrier, normally within 15 minutes. Timed-out carriers stay Standing and can still accept until you close standing offers.
2. Track every waterfall:

• The Tendering Cockpit (Shipments → Truckload → Tendering Cockpit) lists loads most urgent first.
• A status chip shows on the loadboard and search screens.
• The Tendering activity category logs every step.

1. Committed Volume Caps (LSP) limit loads per carrier per day; carriers at their cap are skipped.

Example

• Cascade workflow: Has Open Tenders → Dynamic Tender Timeout → Demote Current Tender (tick Expire the current tender instead) → Send Next Tender.
• Out-of-carriers workflow: Waterfall Exhausted Filter → Add Alert, so your coverage desk hears when the ladder runs out.

Who can use it

• Used by: brokers and coverage reps (Broker role).
• Set up by: admins who build the two workflows. Committed Volume Caps needs TMS Site Admin, LSP Add/Edit or IT Support Admin.
• Requires: a default staff member with access to the shipment, and the cascade workflow.

Good to know

• Offers go by email only, and there are no counter-offers.
• Build each ladder from Carrier Quotes or a template; there are no on-screen routing-guide lists or auto-ranking.
• Without the cascade workflow, nothing moves to the next carrier.
• The out-of-carriers alert needs Expire the current tender instead ticked.
• Tendering doesn't stop at pickup. It runs until the load is covered, you stop it, or the ladder runs out.
• The rate confirmation goes to the email on the carrier quote, so keep it filled in.

Get started

Waterfall Tendering: Auto-Tender Carriers in Order

Brokers on MacroPoint can let tracking manage itself, so dispatchers act when a load is late, untrackable or suspicious.

Why we built it

MacroPoint tracking had to be babysat. It kept running after a load delivered. Schedule warnings and "not tracking" signals sat in status text nobody was alerted on, driver comments were thrown away, and a middle drop could mark the whole load Delivered. We rebuilt the integration so tracking ends on its own and your team is alerted to the loads that need a call.

How it works

• Tracking completes when the shipment is Delivered, and only the last drop delivers the load.
• Schedule updates apply to the right stop and raise Behind Schedule, Cannot Make It or Past Appointment Time. An On Time update clears them. These replace Shipment Delayed for MacroPoint loads.
• Load Track Exception is raised when MacroPoint can't track a load.
• Possible Fraud Detected is raised when MacroPoint flags suspicious tracking.
• In / Above / Below Temperature Threshold alerts cover temperature.
• Open Live Map next to Cancel Tracking opens MacroPoint's map. Share it with shippers by turning on Display in Front Office for Third Party Tracking Link Public in Reference Settings.
• Driver comments land in the Activity Log. Stop times record who reported them and never overwrite a recorded time.
• Optional settings on the MacroPoint integration source (Back Office → Integration Sources):

• MaximumTrackDurationInHours (1–168). If not set, tracking runs until 72 hours after scheduled delivery.
• DelayedArrivalInMinutes (1–120). If not set, MacroPoint's default applies.
• MaximumAllowableDrivingHoursPerDay (1–24). If not set, MacroPoint's default applies.

• Geofence overrides take effect on first and last stops, and link references in the customer portal read Open link.

Who can use it

• Used by: dispatchers and track-and-trace teams using MacroPoint.
• Set up by: admins with access to Integration Sources and Reference Settings. Requires: a MacroPoint integration.

Good to know

• If automations or reports use Shipment Delayed for late MacroPoint loads, switch them to the new alerts.
• New alerts are hidden from the customer portal by default; turn on Display In FrontOffice per alert to show them.
• Moving a Delivered load back doesn't restart tracking, and the live map is one link per load.
• Driver comments are inbound only.

Get started

MacroPoint - Shipment Load Tracking

Brokers can flag, track, and automate alerts at each stop, so everyone knows exactly which stop needs attention.

Why we built it

On multi-stop freight (drayage, transload, multi-pick and multi-drop truckload), alerts lived only on the whole shipment. A broker couldn't flag a problem at one stop or automate follow-ups stop by stop, so the load was a black box between dispatch and delivery. We built Shipment Stop Alerts so every stop carries its own alerts.

How it works

• In LSP → Shipment Alerts, turn on Is Stop for the alert types you want on stops. None are set up by default.
• Click the bell on a stop to open the Stop Alerts window: add, resolve, reactivate or delete alerts for that stop. The Edit Shipment Stop window has the same section.
• Add the Stop Alerts column in Shipment Search or Company Loadboard. The Alerts filter finds stop alert types too.
• Custom Reports adds active and resolved stop alert columns for each stop.
• Workflow Automation adds:

• Triggers: Shipment Stop Alert Added / Resolved.
• Filters: Stop Type, Stop Alert and Resolved Stop Alert.
• Actions: Advance To Next Stop and Add / Resolve Shipment Stop Alert.

• Customers see stop alerts read-only in the updated customer portal, for alert types with Display In FrontOffice on.
• The Public API can read, add and resolve stop alerts (broker-level access to add or resolve).

Example

Shipment Stop Alert Added → Stop Alert Filter contains Driver Late → Advance To Next Stop → Add Shipment Stop Alert: Driver Late. Flag a late pickup, and the next stop is warned automatically.

Who can use it

• Used by: ops teams on multi-stop shipments; customers view their alerts in the portal.
• Set up by: admins with access to Shipment Alerts and Workflow Automation. No new permissions.

Good to know

• Stop alerts aren't created automatically from carrier tracking, and they don't change shipment status.
• Only Manual alert types can be resolved or deleted in the Stop Alerts window.
• Stop alerts don't appear in the existing Alerts column or fire shipment-level alert triggers.
• Customers see stop alerts on pickup and delivery (Origin and Destination) stops only, and can't add or resolve them.

Get started

Shipment Stop Alerts

Carrier reps can see who last contacted a carrier, when and how, so nobody calls twice.

Why we built it

Reps couldn't see when a carrier was last contacted or by whom. Two reps would call the same carrier in the same week, follow-ups slipped, and notes lived in spreadsheets or outside CRMs. Reps won't keep a CRM current by hand, so we built tracking that fills itself in from work they already do in Tai.

How it works

• A Contact Activity panel on Carrier Details, and in the carrier pop-up, shows Last Contacted, Contact Type and Contacted By.
• Contacts record themselves:

• Email Sent for quote requests and rate confirmations.
• Email Received for carrier replies.
• Quote Received for quotes, including from integrations and load boards.
• Last Contacted is always the newest.

• Log calls in View Activity → Add Activity → Manual Contact. The date and time can be backdated, but not set in the future.
• Contact Notes on each carrier contact keep dispatcher notes your whole account can see.
• The carrier's Carrier Rep gets an email when someone else records a contact.
• Set a Domicile Address on Carrier Edit.
• The carrier custom report adds Last Contacted, Last Contacted By, Last Contact Type and domicile columns.

Example

Build a carrier custom report with Last Contacted and Carrier Rep, sorted oldest first, to find carriers nobody has called.

Who can use it

• Used by: carrier reps, carrier sales and their managers.
• Set up by: no setup. Assign a Carrier Rep to get the emails. Contact Notes requires Add/Edit Carrier permission.

Good to know

• Calls, texts and other emails count only when logged as a Manual Contact.
• Contact Notes can't be edited or deleted.
• The report's Last Contacted counts outgoing contact only, so it can be older than the panel.
• Parent organizations see their sub-organizations' contacts; sub-organizations don't see the parent's.

Get started

LSP Carriers