Fixed quote after a free call

A logistics AI chatbot for shipment tracking questions

Tracking calls take a large part of customer service time, mostly for loads that are on time. We build proactive pickup, delivery and delay notifications plus an AI assistant on your website, customer portal or tracking inbox that answers status questions from live TMS and telematics data, only for the caller's own loads, and hands late loads, complaints and anything unusual to a person. Projects typically cost $2,500 to $7,500 and take five to eight weeks.

The problem

Why tracking calls swamp logistics customer service

"Where is my load?" is the most common question a carrier or broker hears, and answering it means checking the TMS, looking at the truck on the telematics map and sometimes phoning the driver. Customer service repeats this all day, and the loads that really are late get the same attention as the rest.

An assistant can answer most of these questions in seconds, but only with guardrails: it must verify who is asking, show only that customer's loads, stick to live data, never promise a delivery time a dispatcher has not confirmed and hand delays and claims to a person.

What we build

What our logistics AI chatbot includes

Proactive milestones

Picked up, in transit, out for delivery and delivered updates by email or text for customers who opted in.

Late-load alerts

Planned arrival is compared with live position; loads at risk are flagged to customer service with a drafted delay message.

AI tracking assistant

Answers status questions on your site, portal or tracking inbox from TMS and telematics data, with the reference it used.

Caller verification

Load lookups require a matching reference and customer account, so nobody sees another shipper's freight.

Hand-off to a person

Delays, damage, claims, rate questions and anything the assistant is unsure about go to customer service.

Clear AI disclosure

The assistant says it is automated and offers a person at any time.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Question or milestone

    A customer asks about a load, or the load reaches a milestone.

  2. 02 Automated

    Live lookup

    The assistant checks the TMS and telematics position for that customer's load.

  3. 03 Automated

    Answer or update

    Routine status is answered with the reference used; at-risk loads are flagged.

  4. 04 Office review

    Customer service

    Staff approve delay messages and take over complaints and exceptions.

  5. 05 Dispatcher or safety manager decides

    Plan changes

    Re-planning, re-delivery and any promise to the customer are decided by the dispatcher.

How it behaves

How shipment tracking updates behave

What each person sees and what runs in the background, including what happens when something goes wrong.

What the customer sees

  • A clear note that they are talking to an automated assistant
  • Load status with the reference and time of the last update
  • Milestone updates if they asked for them
  • A person whenever there is a delay, damage or a question it cannot answer

What customer service sees

  • At-risk loads flagged with a drafted delay message
  • Hand-offs with the conversation so far
  • A weekly list of questions the assistant could not answer

What the automation does

  • Verifies references against the customer account
  • Reads live status from the TMS and telematics
  • Logs every conversation and never promises a time staff have not confirmed

Edge cases and fallbacks

Reference does not match the account
No load details are shown; the customer is offered a person.
Telematics position is stale
The reply states when the last update was and flags the load to staff.
Customer is angry or mentions a claim
Immediate hand-off to customer service with the transcript.
AI provider or telematics outage
The widget falls back to a contact form and milestone updates pause with an alert.
Load re-planned by dispatch
Updates use the new plan only once dispatch saves it in the TMS.

Architecture

A logistics AI chatbot for tracking at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Customer Site, portal, email Assistant service n8n or Laravel Language model Claude, Gemini, GPT Live load data TMS, telematics Status reply With reference Customer service Delays, claims Transcripts Weekly review
  • Input
  • Logic and services
  • AI step
  • Data
  • Output
  • People

How it flows

  1. 1 A customer asks about a load on the website, portal or tracking inbox and is told the assistant is automated.
  2. 2 The assistant verifies the reference and account, then reads live status from the TMS and telematics platform.
  3. 3 Routine questions get a status reply with the reference used; proactive milestones go to opted-in customers.
  4. 4 Late loads, complaints and claims go to customer service, and every conversation is logged.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Shipment tracking updates & logistics AI chatbot project plan

Typical time to launch: about 6 weeks, then support

  1. 01

    Discovery

    About 1 week

    Real tracking questions, data sources, customer verification rules and hand-off triggers.

  2. 02

    Data access

    About 1 week

    TMS and telematics API access, milestone mapping and test loads.

  3. 03

    Build

    About 2 weeks

    Assistant, milestones, late-load alerts, hand-off and transcript log.

  4. 04

    Test

    1 to 2 weeks

    Test set of real and tricky questions, including other customers' references; staff sign off.

  5. 05

    Launch

    2 to 3 days

    Soft launch with a few customers, then widen.

  6. 06

    Support

    Ongoing

    Weekly transcript review at first, then monthly updates.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

Claude, Gemini or OpenAI models n8n AI Agent node or Laravel Samsara, Motive or Geotab APIs project44 tracking API where used Your TMS API Twilio SMS and your email provider

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and answer rules

    Real questions, verification rules and hand-off triggers.

    $500 – $1,200

  • Build

    Assistant, milestones, late-load alerts and admin view.

    $1,200 – $4,000

  • Integrations

    TMS, telematics, messaging and email.

    $300 – $1,000

  • Testing and evaluation set

    Real, tricky and cross-customer tests before launch.

    $300 – $900

  • Launch and training

    Soft launch and customer service walkthrough.

    $200 – $400

  • Total project estimate

    $2,500 – $7,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Proactive milestones alone sit at the lower end. Model usage, messaging and telematics API access are billed to your accounts directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • AI model usage: Billed by the provider per use; short status answers cost little per conversation.
  • Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees (Twilio's published US pricing).
  • Hosting: n8n Cloud from about €20 a month, or your own server.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

EU: tell people they are talking to AI

Article 50 of the EU AI Act requires AI systems that interact with people to inform them they are interacting with an AI system, from 2 August 2026. We add the disclosure wherever you operate.

Source: artificialintelligenceact.eu

Location data is personal data

Truck positions can identify a driver, so customers see load status and estimated arrival, never a live driver map, and data stays with contracted processors.

Source: gdpr-info.eu

US: tracking texts

Milestone texts go only to customers who asked for them, with opt-outs honoured across every workflow.

Source: www.law.cornell.edu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Shipment tracking updates & logistics AI chatbot questions, answered.

Status of a load, last known milestone, estimated arrival from your data, POD availability and routine questions such as office hours or how to send a booking. It does not quote rates, accept loads or decide claims.

When a load reaches a milestone in your TMS or telematics platform, such as pickup or delivery, the workflow sends an approved update to customers who opted in. Late-risk loads go to staff first, so a person decides what the customer is told.

No. Every lookup needs a reference that matches the customer's account, and tests include deliberate attempts with other references before launch.

Not necessarily. The assistant can sit in your tracking inbox or website. If you already have a portal, we add it there.

The assistant answers from TMS status and check calls instead, and says when the last update was made.

Track how many tracking questions are answered without a hand-off, time to first reply, delay messages approved and complaints about late notice. Weekly transcript reviews show what to improve.

Free 20-minute call

Want this for your logistics & haulage?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call