ZAFTYS Analytics · Available
KPI dashboards and drill-downs: corridor reliability, Own vs Network score, cost against trip records, exception queues you can see today in Command Center and Shipments.
Open Analytics
Supply Chain AI · Research
From trip data to desk decisions.
Research on AI that explains exceptions, answers corridor questions, and hands work back into ZAFTYS TMS. TranZfort matching AI is live. Broader desk AI stays Research until labeled otherwise.
Research
Why this architecture
AI only matters if it sits on the trip spine
A logistics desk does not need a generic copilot. It needs answers that cite indent, gate, GPS, ePOD, and labeled Own vs Network capacity. This article walks five stages designed around ZAFTYS TMS and the Amravati desk.
- Built for dispatch and control-tower workflows, not a generic AI brand
- Own fleet and labeled network data stay distinct
- Guardrails force answers back to the trip record
- Status is Research: product claims only when labeled Available or Beta
Boundary
Analytics is Available. Desk AI is Research.
Do not confuse the two. They share the same trip spine. They are not the same product.
Supply Chain AI · Research
Natural-language exception narrative, corridor Q&A, and automated handoff into desk tasks. Designed on top of that same TMS truth. Not sold as finished until status moves.
You are on this page
Desk scenario
What Research is aiming to do on a live trip
Illustrative flow. Not a live chat product today. Shows how input, processing, guardrails, and orchestration should connect.
01
Situation
A contracted FTL is late at a plant gate. The shipper asks why. WhatsApp has three conflicting updates.
02
From the trip record
ZAFTYS TMS shows dispatch time, last GPS ping, gate check-in attempt, and an open detention note. Own fleet labeled, not mixed with network overflow.
03
What AI should return
A short narrative: arrived after the plant window, gate queue open, detention clock started, next action for the desk. No invented ETA that the record cannot support.
04
Handoff
Create or update an exception task in TMS, notify the assigned desk owner, keep the shipper portal status aligned. Analytics still holds the corridor KPI view for the weekly review.
Who this is for
People who will use the answer, not the slide
01
Dispatch and control towers
Need exception narrative and next action without rebuilding the trip story from chat threads.
02
Shipper logistics leads
Want corridor answers grounded in contracted trip events, with Own vs Network still labeled.
03
Technology reviewers
Evaluating how desk AI would sit on ZAFTYS TMS, with guardrails and Research status stated upfront.
01
Data input
Trip truth into one intake layer.
Accurate desk answers start with the same sources operations already trust. Intake is designed around trip records, not anonymous public averages.
ZAFTYS TMS trip records carry dispatch, live map, gate events, and ePOD close-out for contracted moves.
Historical corridor data teaches patterns on lanes ZAFTYS actually runs.
Desk prompts and exception notes capture what the control room is asking in the moment.
ERP and plant windows, plus partner and TranZfort feeds, extend context without blending Own vs Network labels.
Multi-source inputs only help when they stay grounded in trips ZAFTYS actually runs.
app.zaftys.com
02
AI processing
From trip events to desk answers.
The engine turns trip events into answers: what blocked the move, what the corridor history says, what truck fits next, and what risk to flag before the plant call.
Timeline synthesis: order dispatch, GPS, gate, and detention into one readable story for the open trip.
Corridor Q&A: history and live status for lanes in your program, not a national average chart.
Capacity and vehicle fit: the same matching logic already used on TranZfort for corridor and body class.
Risk flags: patterns the desk should see early, such as repeated gate misses on a plant window.
Processing is logistics Q&A on the trip spine, not a generic chatbot with a freight skin.
app.zaftys.com
03
Guardrails
Safe answers on commercial trip data.
AI that touches commercial freight data must fail closed when the trip record cannot support the answer. Guardrails are product design, not decoration.
Input validation checks prompts and feeds before they reach the model.
Answers must ground in the trip record. Invented rates, trucks, or statuses are blocked.
Role-based access limits who can see which corridors and commercial fields.
Sensitive fields stay encrypted, and desk queries are auditable for later review.
Guardrails keep Supply Chain AI honest to ZAFTYS TMS truth.
app.zaftys.com
04
Orchestration
Connect. Assign. Act.
Intelligence only helps if suggestions become desk work inside tools you already run.
The orchestration engine covers task planning, exception queues, decision handoff, and desk follow-up.
Connected systems include ZAFTYS TMS, TranZfort, shipper portal, partner APIs, and billing close-out.
app.zaftys.com remains the operational spine: dispatch, shipments, map, and ePOD already exist there.
Broader automation into ERP and full desk assistants stays Research until labeled Beta or Available.
Orchestration turns AI into assignable work, not another unread dashboard.
app.zaftys.com
05
Desk outcomes
What good looks like when Research becomes product.
Success is measured in how the desk works a lane, not in invented global scale counters.
Fewer conflicting status threads: one trip-backed explanation instead of three WhatsApp versions.
Clearer plant and procurement conversations: corridor answers that cite events, not folklore.
Better allotment on TranZfort: vehicle fit that is already live in matching.
Cleaner weekly reviews: AI narrative for the open exception, Analytics KPIs for the corridor trend.
Impact only counts when it attaches to trips you can defend.
app.zaftys.com
What is live today
Matching AI on TranZfort. Trip truth on TMS.
01
TranZfort matching
AI already supports corridor and vehicle fit on the marketplace. That is product, not a research slide.
02
ZAFTYS TMS and Analytics
Dispatch, shipments, map, and operations analytics are Available. They are the spine this research assumes.
03
Desk AI roadmap
Exception narrative, corridor Q&A, and broader orchestration stay Research until we label them Beta or Available.
Talk Research with the team that runs the lanes
Ask about Supply Chain AI for your desk, or start from Analytics and TMS where product is already Available.