Skip to content
English
  • There are no suggestions because the search field is empty.

Track and Trace AI Agent

Automated driver check calls so your team doesn't have to make them.

 

⭐  Early Access Program

The Track and Trace AI Agent is available to all Tai customers. Right now, activation is done through an Early Access Program a guided onboarding process where the Tai team works directly with you to get the Agent live. Full self-service availability is coming soon.

What Is the Track and Trace AI Agent?

The Track and Trace AI Agent is an autonomous AI voice agent built into Tai TMS and powered by CloneOps. It proactively calls drivers, captures real-time location and ETA updates, and logs everything directly into the shipment record — with no manual steps required. The Agent operates 24/7, including nights and weekends, and communicates with drivers in multiple languages, reflecting the real diversity of your carrier network.

Once configured, the Agent will:

  • Call drivers automatically on active shipments on a schedule you define — 24/7, including after hours
  • Capture location, ETA, delivery outcome, and any issues reported during the call — then log them directly into the load record
  • Automatically advance shipment status — from Dispatched to In Transit, and from In Transit to Delivered — and adjust appointment times as conditions change
  • Resolve the check call alert and repeat the process the following day

The result is continuous, automated visibility into your freight — without the phone tag. When your team needs to act on a specific shipment right away, calls can also be triggered manually at any time from within Tai.

How It Works Behind the Scenes
This integration uses a dedicated connection between Tai TMS and CloneOps. Tai is responsible for scheduling the calls and storing the results. CloneOps is the AI platform that actually places the calls and gathers the driver responses.

Before You Get Started

Before the Track and Trace AI Agent can be activated for your account, a few things need to be in place. Your Tai support team will handle the technical setup — this section gives you a clear picture of what they will do, what you need to provide, and what you will configure yourself.

What Tai Will Set Up

The Tai support team takes care of all the technical configuration. Here is what they will set up on your behalf:

  • The AI Agent in CloneOps, configured with your outbound phone number (either your own number or a provisioned one)
  • The Integration Source in Tai that links the Agent back to your account in the TMS
  • All credentials and secure variables needed for the Agent to communicate back and forth with Tai
  • Guidance on setting up your Workflow Automation schedules — the scheduling step is yours to configure in Tai (more on this below)

What You Are Responsible For

There are two things you own in this process:

  • Providing the phone number and any information Tai needs to complete the setup (see below)
  • Setting up the Workflow Automation schedules in Tai that control when the Agent places calls each day (see the How the Automated Check Call Cycle Works section for guidance)

Information You Will Need to Provide

To complete the setup, have the following ready:

What You Need

Details

Phone number for outbound calls

The number drivers will see when the Agent calls. This can be your existing business number or a new number provisioned by Tai. If you use your own existing number, it will go through a short validation process before it can be activated.

Phone number validation

If you are using your own existing phone number, Tai will walk you through a brief validation step — either a phone call or SMS confirmation — to verify the number before it goes live.

How the Automated Check Call Cycle Works

Once everything is set up, the process runs automatically every day. Here is what happens from start to finish:

Step

What Happens

Details

1

Shipment Triggers the Call

At your scheduled time, Tai automatically identifies active shipments that need a check call and sends the shipment details to the AI Agent.

2

AI Agent Calls the Driver

The AI Agent places an automated phone call to the driver's number on file. It gathers location updates, any delays, and relevant status information.

3

Results Come Back to Tai

Once the call is complete, the AI Agent pushes all captured updates directly back into the shipment record in your TMS — notes, location, status changes.

4

Alert is Resolved

The AI Agent Call alert on the shipment is automatically resolved, signaling that the check call cycle for that day is complete.

5

The Cycle Repeats the Next Day

The following day, the automation detects the resolved alert and triggers a fresh check call — keeping your tracking up to date without any manual effort.

No Duplicate Calls
The two automated schedules are designed so that no shipment ever gets called twice in the same day. Schedule 1 handles shipments that have never had a call. Schedule 2 handles shipments where the previous day's call was already completed and resolved. They work together without overlap.

Setting Up Your Workflow Automations

Once Tai has completed the integration setup, you will configure two Workflow Automation schedules in Tai. These schedules are what actually drive when the Agent places calls each day. You need two — not one — because they handle two different situations: a shipment that has never had a call, and a shipment that was called on a previous day and is ready for a follow-up.

To get started, navigate to Settings > Workflow Automations in Tai and create the two schedules below.

Schedule 1 — First Call (Shipments With No Prior Agent Call)

This schedule picks up any active shipment that has never received an AI Agent Call and triggers the first call. Configure it as follows:

Setting

Value

Trigger Type

Shipment Scheduler

Frequency

Daily — set to your preferred time (e.g., 9:00 AM)

Filter

Alert

Filter Type

Does Not Contain: AI Agent Call

Filter Resolved Alert
Filter Type Does Not Contain: AI Agent Call

Action Type

Call AI Agent Action — select your CloneOps Integration Source from the dropdown

Tip: You can add additional filters before the Action Type — for example, to limit calls to Truckload shipments only, or to specific statuses such as Dispatched or In Transit.

Schedule 2 — Follow-Up Calls (Shipments With a Prior Resolved Call)

This schedule picks up shipments that were called on a previous day and triggers a fresh follow-up call. The date filter ensures the same shipment is never called twice on the same day. Configure it as follows:

Setting

Value

Trigger Type

Shipment Scheduler

Frequency

Daily — set to the same time as Schedule 1

Filter

Resolved Alert

Alert

AI Agent Call

Filter Type

Less than or equal to: Yesterday

Action Type

Call AI Agent Action — select your CloneOps Integration Source from the dropdown

Tip: The Resolved Date filter set to "Less than or equal to Yesterday" is critical. Do not set it to "Today" — that would cause shipments to be called twice on the same day.

Triggering a Check Call Manually

In addition to the automated daily schedule, your team can trigger a check call on demand at any time. This is useful for urgent shipments, exceptions, or any situation where you do not want to wait for the next scheduled run.

There are three ways to trigger a manual call:

Option 1 — From a Shipment Record

  1. Open the shipment in Tai TMS.
  2. Open the Check Call panel.
  3. Click Call AI Agent at the bottom of the modal.
  4. The Agent call is dispatched immediately and the AI Agent Call alert is added to the shipment.

Option 2 — From Shipment Search (Multiple Shipments)

  1. Go to Shipment Search and select one or more shipments.
  2. Open Bulk Operations.
  3. Select Call AI Agent and confirm.
  4. The call is queued and dispatched for all selected shipments.

Option 3 — From the Company Loadboard (Multiple Shipments)

  1. Navigate to the Company Loadboard.
  2. Select one or more shipments using Bulk Operations.
  3. Choose Check Call > Call AI Agent.
  4. The calls are dispatched for all selected shipments.

Not Seeing the Option?
Manual calls are only available on shipments whose organization is linked to a configured CloneOps Integration Source. If you do not see the Call AI Agent option, contact your Tai administrator to verify the integration is active for your organization.

What to Expect After a Call

After the AI Agent completes a check call, here is what you will see in Tai:

  • An AI Agent Call alert will appear on the shipment. This alert is managed automatically — you do not need to create or resolve it manually.
  • Call notes from the interaction will be added to the shipment activity log.
  • If the driver provides a pickup or delivery time during the call, those times will be logged to the shipment details automatically.
  • If the driver provides details that indicate a status change — for example, confirming pickup or delivery — the shipment status will transition accordingly (e.g., Dispatched to In Transit, or In Transit to Delivered).
  • The alert will remain open (unresolved) until CloneOps has finished processing the results and pushed them back into Tai, at which point it resolves automatically.
  • The next scheduled run will detect the resolved alert and trigger a follow-up call the following day.

Required Shipment Fields

For the AI Agent to successfully complete a check call, the following fields must be populated on the shipment before a call is triggered:

Field

Requirement

Driver Cell Phone Number

Mandatory — the Agent cannot place a call without this. Enter it in the Driver Cell Phone Number field under Shipment References.

Pickup Appointment Date

Mandatory — used to determine timing context for the call.

Delivery Appointment Date

Mandatory — used to determine timing context for the call.

Driver Name

Recommended — helps the Agent address the driver by name during the call. Enter it in the Driver Name field under Shipment References.

Troubleshooting

If something does not appear to be working as expected, use the table below as a starting point before reaching out to support.

Issues in Tai

Symptom

Likely Cause

What to Do

"Call AI Agent" option is not visible

The shipment's organization is not linked to a CloneOps Integration Source

Contact your Tai administrator to verify that the Integration Source is configured and linked to your organization.

Alert is added but never resolves

CloneOps does not have the correct Tai API key

Confirm that the API key provided during setup is active and associated with the correct organization.

Shipments are being called more than once per day

Schedule B filter is misconfigured

The Resolved Alert filter on Schedule B should be set to 'Less than or equal to Yesterday.' Contact your Tai administrator to review.