Try an example query
Press Enter or click Ask to query
Conversation
Ask a tracking question to get started
Agent Pipeline
Submit a query to watch the tracking pipeline process it.
Processing query...
Arc Data Track-and-Trace Agent v1.0
Active Shipment Register
18 shipments loaded| PRO # | BOL # | Carrier | Origin → Destination | Current Location | Status | ETA |
|---|---|---|---|---|---|---|
| PRO-12345 | BOL-88001 | FedEx Freight | Chicago, IL → Atlanta, GA | Nashville, TN | In Transit | 2026-03-27 |
| PRO-67890 | BOL-88002 | XPO Logistics | Dallas, TX → Phoenix, AZ | Tucson, AZ Terminal | At Terminal | 2026-03-27 |
| PRO-11111 | BOL-88003 | ABF Freight | Los Angeles, CA → Seattle, WA | Seattle, WA | Out for Delivery | 2026-03-26 |
| PRO-22222 | BOL-88004 | Old Dominion | Houston, TX → Dallas, TX | Dallas, TX | Delivered | 2026-03-25 |
| PRO-33333 | BOL-88005 | Estes Express | Philadelphia, PA → Boston, MA | Boston, MA | Delivered | 2026-03-24 |
| PRO-44444 | BOL-88006 | FedEx Freight | San Francisco, CA → Las Vegas, NV | San Francisco, CA | Picked Up | 2026-03-28 |
| PRO-55555 | BOL-88007 | ABF Freight | Detroit, MI → Chicago, IL | Gary, IN | In Transit | 2026-03-26 |
| PRO-66666 | BOL-88008 | XPO Logistics | Miami, FL → Orlando, FL | Orlando, FL | Delivered | 2026-03-25 |
| PRO-77777 | BOL-88009 | Old Dominion | Kansas City, MO → Denver, CO | Wichita, KS | In Transit | 2026-03-27 |
| PRO-88888 | BOL-88010 | Estes Express | Austin, TX → Houston, TX | Houston, TX Terminal | At Terminal | 2026-03-26 |
| PRO-99999 | BOL-88011 | FedEx Freight | Memphis, TN → St. Louis, MO | St. Louis, MO | Out for Delivery | 2026-03-26 |
| PRO-10101 | BOL-88012 | ABF Freight | Portland, OR → Sacramento, CA | Redding, CA | In Transit | 2026-03-27 |
| PRO-20202 | BOL-88013 | Estes Express | Baltimore, MD → New York, NY | New York, NY | Delivered | 2026-03-24 |
| PRO-30303 | BOL-88014 | XPO Logistics | Phoenix, AZ → Los Angeles, CA | Phoenix, AZ | Picked Up | 2026-03-28 |
| PRO-40404 | BOL-88015 | Old Dominion | Cleveland, OH → Pittsburgh, PA | Pittsburgh, PA Terminal | At Terminal | 2026-03-26 |
| PRO-50505 | BOL-88016 | ABF Freight | Minneapolis, MN → Milwaukee, WI | Eau Claire, WI | In Transit | 2026-03-27 |
| PRO-60606 | BOL-88017 | FedEx Freight | Tucson, AZ → Albuquerque, NM | Albuquerque, NM | Delivered | 2026-03-25 |
| PRO-70707 | BOL-88018 | XPO Logistics | Boston, MA → Philadelphia, PA | Philadelphia, PA | Out for Delivery | 2026-03-26 |
How the NLP Pipeline Works
The agent runs each query through a four-stage pipeline, extracting structured intent from unstructured English text before hitting the TMS. No rigid command syntax required.
Query Parsing
Normalises whitespace and casing, then applies ordered regex passes to detect PRO/BOL reference numbers. Bare numbers paired with context words like 'track' or 'locate' are also resolved to PRO lookups.
Intent Classification
Matches carrier names, status keywords, and destination city names against known vocabulary. Multi-word phrases (e.g. 'out for delivery') are matched before shorter substrings to avoid false positives.
TMS Query Execution
The resolved intent drives a targeted filter over the in-memory shipment register: exact match for PRO/BOL, substring match for destination, status enum match for status queries, and a derived 'delayed' filter comparing ETA to today's date.
Response Generation
A template-driven composer selects the correct narrative pattern per status (in transit, at terminal, delivered, etc.) and fills in the shipment's live details. Multi-match queries return a structured summary list instead of a single narrative.
See how this agent runs in production
The architecture note behind this demo walks through the full Zero-Touch Visibility Loop, including EDI ingestion, LLM-assisted intent parsing, TMS write-back, and the proactive exception-alert layer that eliminated 94% of manual status calls.
Read the Architecture Note