This article provides an overview of the Tai ↔ Chain integration. It explains how load booking, tracking updates, field mapping, and exception alerts flow between the two systems, and includes setup details maintained by Chain.
Integration Overview: Tai ↔ Chain
This integration connects Tai and Chain through a two‑way sync, allowing updates in either platform to reflect instantly in the other. It supports key capabilities including:
-
Booking flow: Loads in Tai can be made available for carrier booking within Chain; once a carrier is assigned in Tai, Chain updates the load status automatically, and vice versa. help.trychain.com
-
Tracking updates: Chain forwards driver or dispatcher updates—such as actual pickup/drop-off times and ETAs—to Tai. Supported statuses include Arrived Pick, Departed Pick, Arrived Drop, and Departed Drop. help.trychain.com
-
Field mapping & configuration: Chain provides standard mappings from Tai’s fields, and can customize these during implementation—covering elements like driver phone, dispatcher email, truck/trailer number, and sub‑organization workspaces. help.trychain.com
-
Autopilot alerts & tracking maps: Exception alerts generated by Chain’s Autopilot rules become “Load Track Exceptions” in Tai, and Chain populates location history on Tai’s tracking map. help.trychain.com
For more information on how Tai integrates with Chain—including setup, field mapping, and feature specifics—please review Chain’s documentation: How Tai integrates with Chain