AI for logistics companies, built on your dispatch, phones and telematics

Logistics runs on phone calls, a dispatch board, driver texts and a few spreadsheets. The dispatcher takes the call, types it into the system, works out which truck is free, texts the driver, then takes the next call from a customer asking where their load is.

We build AI for logistics companies, trucking fleets, towing companies and field service operators that takes the call, opens the job, recommends the truck or technician with the reasons shown, flags what's running late and keeps customers updated. It sits on top of the systems you run today. Dispatchers make the final call.

Quick answer

Trilix AI builds custom AI for carriers, towing companies and field service operators: call agents that open the job, dispatch recommendations that show their reasons, late-load and hours-of-service alerts, driver apps and customer ETA texts, on top of your TMS or dispatch system. It's quoted as a one-time setup fee plus a monthly fee.

Dispatch board with a fleet map, the recommended truck for a new job with ETA, distance and fuel cost, the reasons for the pick, and the active jobs board.
Dispatch board with truck recommendation.Sample data. Names are fictional.

Who this is for

Trucking carriers

Truckload, LTL, tanker and mixed fleets where dispatch decisions depend on hours of service, certifications, trailer type, deadhead and backhaul.

Towing and roadside companies

Fleets where the first company to answer gets the job, and a missed call goes straight to a competitor.

Field service and delivery operators

Teams sending technicians or drivers to customer sites, with promised windows to hit and customers who call when nobody shows up.

3PLs and warehouse operators

Operators juggling dock doors, cross-docks and several services pulling on the same trucks and people.

Where dispatch and operations lose time

Re-keying every call

Details from the phone get written down, typed into dispatch, then texted to the driver. Each copy is a chance for an error.

Dispatch decisions in one person's head

The best dispatcher knows which driver is close, has hours left and knows the route. When they're off, the picks get worse and nobody can see why.

Late loads found out too late

A load is at risk, a driver is running out of hours or a reefer is failing, and the office hears about it from the customer.

"Where's my truck?" calls

Customers call for ETAs, delivery documents and invoices, and every one of those calls lands on dispatch.

The day reviewed after it's over

Revenue per truck, empty miles, unbilled detention and open invoices show up in a report days later, when it's too late to move a truck or chase a payment.

What we build for logistics companies

ProblemWhat we buildDemo build
Calls missed or re-keyedAn AI call agent that answers around the clock, asks what a good dispatcher would and opens the ticket as it talksTowing dispatch
Dispatch picks nobody can checkA dispatch copilot that recommends the truck, driver or technician and shows why the others were ruled outTowing dispatch, trucking control tower
Late loads and hours of serviceAlerts for at-risk deliveries and hours-of-service limits, with a drafted re-plan for dispatch to approveTrucking control tower
Status calls from customersA customer text line for live ETAs, delivery documents, invoices and delay alertsTrucking control tower, towing dispatch
Paperwork on the roadA driver app with accept or decline, required photos and voice notes that land on the ticketTowing dispatch
Breakdowns on loaded trailersMaintenance ranked by failure risk across tractors, trailers and reefer units, with bay bookingTrucking control tower
No live view for the ownerA morning command center with jobs, revenue per truck and driver, response times, empty miles and open receivablesBoth demos

Both are demo builds on sample data. We keep the carriers' names private.

How dispatch stays in control

Recommendations, with reasons

Every pick shows why: distance, hours left, truck type, certifications, deadhead. Dispatch can see why the other drivers were ruled out and override any pick.

Approvals before anything goes out

Re-plans, customer delay notices and work orders are drafted for a person to approve, until your team decides which ones can send on their own.

It works next to your systems

The system reads from your TMS or dispatch software, telematics, phones and accounting. It doesn't replace them, and it doesn't change load data without the rules your team sets.

Safety stays with people

Camera and telematics flags go into a review queue. Decisions about drivers stay with your safety team.

How a logistics build goes live

  1. A day with dispatch. We learn how jobs come in, how trucks get picked and what goes wrong most often.
  2. Connect the systems. Phones, TMS or dispatch, telematics and accounting, through their official connections or exports, agreed in the written scope.
  3. A first version in about 10 days, usually the call agent on one line or the morning command center.
  4. Run it next to the current dispatcher for 30 days and compare picks, response times and missed calls.
  5. Out from there, one terminal, line or module at a time.

Deployment can be hosted by us or run in an account your business owns. Your company owns its data. See data and security.

How pricing works

Every build is quoted after the first call, based on the systems involved and how many lines, trucks or terminals go live. There's a one-time setup fee and a monthly fee after launch that covers hosting, monitoring, fixes and the next items on your roadmap. A pilot on one phone line or one workflow has a fixed setup fee. See what custom AI costs.

Frequently asked questions

Something else on your mind? Ask us directly or call 416-262-2723.

Does it replace our TMS or dispatch software?

No. It works on top of the systems you already run, and adds the call agent, recommendations, alerts and reporting across them.

Can the AI call agent dispatch a truck on its own?

It can open the ticket and recommend a truck. Whether it assigns on its own or waits for a dispatcher is your call, and most fleets start with a dispatcher approving every job.

What does a good pilot look like?

One phone line and a few trucks, running next to the current dispatcher for 30 days. You judge it on missed calls, time to dispatch and customer callbacks.

Can customers get ETAs without calling dispatch?

Yes. A text line sends the driver's name, ETA, tracking and documents, using templates you approve.

Does it work for field service, not just trucking?

Yes. The same pieces apply to technicians: take the call, open the job, pick who goes, keep the customer updated and show the owner the day.

Do you work with fleets in the US and Canada?

Yes. We're based in Vaughan, Ontario, and work with businesses in the US, Canada, the UK and Europe.

…They can build out anything. It started out just automating some reports. And then I was like, hey, can you do this? He’s like, absolutely.

Auto repair shop owner, United States

You give us one call and access. We do the rest.

No long discovery project and no new software for your team to learn first. We start with what costs you most and ship it.

  1. 1

    One 30-minute call

    You walk us through how the business runs and where the time goes. We show what we’ve built for other operators and sketch your one-year roadmap.

  2. 2

    You give us access

    Logins or read access to the systems involved: phones, POS, accounting, cameras. We handle the setup from there.

  3. 3

    We build, you check

    We build around your own data and show it working before anything goes live. Your part is a short review.

  4. 4

    Live in about 10 days

    Then we keep it running every month and work down the roadmap with you. Bigger builds go live in phases.

More on how it works

Running dispatch off the phone and a whiteboard?

Book a call and we'll show you the towing and trucking demos, then sketch what we'd build first for your operation.