Unifying the Agent Portal: 90% Less Time Searching for Landstar

Landstar agents jumped between SOPs, shipment systems, and the capacity portal to answer a single customer question. RTS Labs built an AI copilot directly into the Agent Portal — RAG over Landstar's internal documents combined with live tool calls to the Shipment and Capacity APIs, deployed entirely inside Landstar's private Azure VNet. Agents now ask plain-language questions like "What's the current capacity in Lexington, KY?" and get cited answers in seconds.

logistics supply chain header
Case Study at a Glance
Client
Use Case

Agentic AI Copilot: RAG + API Tool Use

Tech Stack

Azure OpenAI (GPT-4o)

Azure AI Search

Promptflow

GPT-Vision

Time to Production
From brief to live deployment
0 weeks

Dealing with a similar challenge?

Our engineers will map your workflow and define a ship date in a 2-week Discovery Sprint.

Share

1. The Challenge

Landstar’s agents thrive on quick, informed decisions. But the data they needed to make those decisions lived in different places — internal SOPs and reference docs in SharePoint, shipment-level detail in the TMS, and live capacity data in a separate portal. Answering a single customer question meant context-switching across two or more systems, every time.

The team didn’t need another dashboard or another search tool. They needed the answer to find them — in one place, in their existing workflow, with the same speed and precision they’d expect from a colleague who knew every system cold. And it had to live entirely inside Landstar’s private Azure environment, with no customer data crossing the perimeter.

Data Scattered Across Systems

Agents navigated two or more systems for every customer question — SOPs in SharePoint, shipment detail in the TMS, capacity in a separate portal. The context-switching tax was real and constant.

Systems juggled per task
0 –7

Time Lost to Manual Hunting

Every delay in finding an answer was a delay in serving an agent’s customer. Time spent hunting through systems was time not spent winning business or building relationships.

Avg per lookup, before AI
0 –15 min

Search Quality Was the Lynchpin

The team learned quickly that LLM accuracy was downstream of search accuracy. Tuning chunk size, embedding strategy, and retrieval reranking became the difference between confident answers and “I don’t know.”

Search precision before tuning
0 %

2. The Engineer Approach

RTS Labs built the copilot entirely inside Landstar’s Azure environment to meet their private-network requirements. The system combines RAG over Landstar’s internal documents with live API tool calls to the Shipment and Capacity systems — agents get one workspace, one conversational interface, and answers grounded in real data instead of stale documents. Every response includes source citations so agents can verify what they’re seeing.

  • Document Ingestion & Index Build

    Internal SOPs, department contact info, technical terms, and PDF instruction sets are ingested via an Azure Function App indexer. PDFs run through GPT-Vision for markdown conversion — more accurate than OCR for tables and structured layouts. Documents land in Azure AI Search (S2 tier, private endpoint) inside Landstar's VNet, with embeddings hosted in Azure OpenAI.

  • Conversational Agent & API Tool Use

    Promptflow orchestrates queries through GPT-4o, deciding when to retrieve from AI Search vs. when to call the internal Shipment or Capacity APIs. Agents ask natural questions like "What's the current capacity in Lexington, KY?" — the agent routes the tool call, queries the API, and returns a structured answer with source citations and markdown formatting.

  • Guardrails & Evaluation Framework

    OpenAI's content-filter framework (violence, self-harm) plus Azure AI Studio's content filtering. A non-streaming response mode makes monitoring and reactive shutdown straightforward. An evaluation Promptflow scores every change against coherence, relevance, and groundedness benchmarks — peak coherence 4.38, peak relevance 4.67, peak groundedness 4.25.

  • Private-Network Production Deployment

    The entire system runs inside Landstar's Azure VNet behind their Firewall and VPN. Container images deploy via Azure Container Registry to Azure App Service for the chat UI. Promptflow's built-in blue/green deployment ships changes safely. Application Insights captures telemetry and chat logs for ongoing tuning.

Landstar agents were drowning in systems. Between the TMS, LandstarOnline, help docs scattered across SharePoint, and a search function that barely worked, a simple question could eat up 15 minutes of billable time. We built an AI copilot that sits right in the portal and actually understands what agents are asking. No more toggling between five different systems—they ask once, get a grounded answer with sources, and move on. We went from 65% search precision to answers agents can actually trust. The math is simple: thousands of agents saving 10+ minutes a day adds up fast. This isn't just a productivity play; it's a competitive advantage when your agent network can operate 90% faster.
Lead engineer

3. Results & Impact

Less Time Searching
0 %
Annual savings
$ 0 M+
Core Systems Unified
0
From brief to live deployment
0 wks

Before RTS Labs

  • Disconnected Tools

    Agents jumped between SOPs, shipment systems, and the capacity portal for every customer question

  • Fragmented Knowledge

    Information was scattered — no single workspace for answers

  • Lagging Response

    Delays in finding answers meant delays in serving customers

  • Complex Onboarding

    Each new agent ramped up across three+ different systems

After RTS Labs

  • Conversational UX

    Agents ask questions in plain language and get answers from one workspace

  • Unified Knowledge & APIs

    RAG over internal documents combined with live tool calls to Shipment and Capacity APIs

  • Verifiable Answers

    Source citations on every answer for verifiability

  • Enterprise-Grade Security

    All running inside Landstar's private Azure VNet — no data leaves the perimeter

More Case Studies:

National Retailer Case Study

AI Candidate Screening: 60% Faster Hiring: Case Study

Overview:
The retailer's recruiters were spending most of their day on resume reviews, qualification cross-checks, and interview scheduling. RTS Labs built an AI system designed around the recruiter — automating screening...
Evergreen Case Study

AI Sales Assistant: Evergreen Case Study

Overview:
Evergreen Enterprises wholesales home, garden, gift, and seasonal décor — 24,000+ SKUs across four seasonal cycles a year — to thousands of retailers nationwide. Their sales teams relied on slow,...
NonProfit Consulting Case Study

Unifying Fragmented Data: Cause Strategy Partners Case Study

Overview:
Cause Strategy Partners — a nonprofit consulting firm helping organizations build stronger boards and drive mission impact — was drowning in fragmented data across HubSpot, BoardLead, BoardLearn, and a tangle...
Have a Similar Challenge?

Every AI Idea Deserves a Ship Date

Stop strategizing. Start building. Let’s map your workflow and get your AI integration into production in 90 days.