Talk to us

Operations as a service for freight brokers and 3PLs

The middle of every load, handled.

Haulvoy runs pickup, check calls, delivery and proof of delivery for your brokerage. Our AI assistant, Clantus, does the work, a human desk takes the exceptions, and every update lands in your own TMS.

Become a design partner See how it works

Now taking design partners for our first pilot. Nothing is written to your TMS until you say so.

LD-1015
Chicago, IL → Columbus, OH · Dry van
In transit
  1. Dispatched
  2. Picked up
  3. In transit
  4. Delivered
  5. POD
  • Clantus
    Status written to your TMS: In transit From the driver's reply: “rolling, near Indianapolis, ETA tomorrow 1pm”
    Driver text
  • Clantus
    ETA checked against the appointment On time · no action needed
    Rules
  • Desk
    Nothing needs a person Exceptions come here first, not to you
    Haulvoy desk

How it works

A load has six steps. We run the four in the middle.

You keep booking and payment, the parts that need your judgment and your relationships. We take the follow-up that fills your team's day.

  1. 1 Booking You
  2. 2 Loading Haulvoy
  3. 3 Transit Haulvoy
  4. 4 Unloading Haulvoy
  5. 5 Documents Haulvoy
  6. 6 Payment You
2

Loading

Picked up

Confirms the driver, then that the truck arrived, loaded and left.

Driver
Confirmed Carrier email
Departed shipper
09:42 Driver text
Your TMS
Picked up Written
3

Transit

Tracking

Check calls on a schedule, ETA watched against the appointment, your TMS kept current.

Last location
Indianapolis, IN Tracking ping
ETA
Thu 13:00 Driver text
Risk
On time Rules
4

Unloading

Running late

Confirms arrival and delivery. A late load is flagged so you decide whether the customer hears.

Appointment
Thu 17:00–21:00 Your TMS
Carrier's ETA
Thu 22:30 Carrier email
Next
Desk decides Haulvoy desk
5

Documents

POD on file

Collects the proof of delivery, checks it matches the load, and attaches it in your TMS.

POD
Received Carrier email
Matches load
BOL and stop Checked
Your TMS
Attached Written

Illustrative screens. If you already track drivers with a platform, we read its updates instead of messaging drivers.

See it

Every load on one page, with every message and decision.

This is our desk's view of a load in a demo with simulated data. A dispatcher texted back, Clantus read it, checked the ETA against the appointment and queued the next check call. The yellow bar is shadow mode: every TMS write is held for review.

The Haulvoy desk's page for load LD-1009, in transit from Chicago to Dallas: delivery appointment, the carrier's ETA, a milestone stepper and a history showing the dispatcher's text and Clantus's reading of it.
Steps 2–5run for you, on every load in scope
Per loadno seats to buy, no volume minimum
Shadow firstnothing written to your TMS until you say so
One clickstops everything for your brokerage

Built around how you already work

Inside your systems, in your name, by your rules.

Your TMS stays the record

Every status, note and document is written into the TMS your team already reads, with who did what. No second dashboard to check.

Your desk's voice

Carriers and customers hear from your brokerage's operations desk, with a line saying an AI assistant is involved. It never pretends to be a person.

Your playbook, approved by you

Each customer's rules — who to copy, receiving hours, what to report — come from your SOPs. Upload the document; you approve every line before it runs.

A human desk behind it

A silent carrier, a late truck, a reply that doesn't add up: our desk handles it and brings you only what needs your decision.

Full truckload and drayage

Container loads too: delivery orders, last free day, demurrage and per diem watched, empty returns followed up.

Numbers you can check

Reports show how much of your freight ran itself, what reached a person and how long it waited — exportable for your own review.

The pilot

Start in shadow. Go live when the numbers say so.

  1. 1

    Shadow · about two weeks

    Clantus works your loads and talks to your carriers, but writes nothing to your TMS and emails none of your customers. You review every update it would have made.

  2. 2

    Live on a slice

    Writes go live for the loads you choose: one customer, a few carriers or one lane.

  3. 3

    Live

    Every load in the agreed scope. Each stage moves on only with your yes in writing, and one click takes you back.

Pricing

Per load, priced with our design partners.

You pay for the loads we manage, not for seats or software. Our first partners help set the price, from their own before-and-after numbers.

Design partner pilot

Priced with you

  • Billed per load we manage. No seats to buy and no volume minimum.
  • Set from your numbers: the hours your team spends on these steps today, and what the pilot shows.
  • Agreed in writing before your first load, along with the scope and the go-live checks.
Talk about pricing

You stay in control

Stop it, scope it, take any load back.

  • One click stops everything for your brokerage: messages, TMS writes and follow-ups.
  • You set the scope: which customers, carriers and load types. Nothing outside it is touched.
  • Any load, any time: your team or our desk can take a load over; while held, Clantus contacts nobody about it.
  • No surprise recipients: messages go only to contacts from your TMS and your approved playbook.

Your data

Yours, kept apart, on the record.

  • Kept apart from every other customer's data at the database level.
  • Everything logged: each message, TMS write and staff action, and who did it.
  • Your rates stay private: customer and carrier rates are never shown in our tools.
  • Exported and deleted on request, with our commitments written into the pilot agreement.

Questions

What brokers ask us first.

Will carriers know they're dealing with software?

Yes. Messages go out in your brokerage's name, as your operations desk, and every one carries a line saying an AI assistant is involved. Clantus never claims to be a person or signs as one of your employees.

Which TMS do you work with?

Haulvoy connects to a TMS through one connector per system, behind the same rules. We build the connector for each design partner's TMS. What we need from it is API access that lets an outside tool read your loads and write a load's status.

What happens when Clantus gets something wrong?

The pilot starts in shadow mode, so you see every update before any is written. After that, anything unclear goes to our desk instead of being guessed, a wrong status can be corrected with a reason on the record, and one click stops everything.

Does my team have to learn a new tool?

No. Your TMS stays where your people look; updates, notes and documents land there. Our desk works in its own cockpit, so you don't have to.

Do you text and call drivers?

Clantus works by email and text, and reads your tracking platform if you have one. The pilot starts on email. There are no phone calls to drivers during the pilot.

What happens to our data if we stop?

We export it to you and delete ours. Our data commitments go into the pilot agreement.

Be our first design partner.

One brokerage, its live loads, shadow mode first. Tell us your TMS and roughly how many loads a week, and we'll show you what Haulvoy would do with them.

hello@haulvoy.ai