How it works

The build is a day. The rest is your team deciding what it may send on its own.

1. Day 1

   Wire it in

   Forward your dispatch line to a Loadmouth number, point an inbox rule at us, drop in the keys for what you already use — TMS, tracking, dock scheduling. Nothing installs on your machines. Your data stays in your systems; Loadmouth reads through their APIs.

2. Week 1

   It reads, you approve

   Every inbound gets a draft. Your dispatcher sees the message, the draft, and what Loadmouth looked up to write it. Approve, edit, or redo. Nothing sends by itself.

3. Week 2–3

   Flip the boring ones

   "Which door?" and "where's my load?" get boring fast. One tap sets that message type to Auto. Detention and disputes stay on Approve for as long as you like.

4. Week 4+

   Read the digest

   Every morning: what it handled, what it escalated, detention dollars it caught. Add a second desk when the first one's quiet.

What the dispatcher sees

One page. Inbox on the left, draft on the right, three buttons. Try it with seeded traffic:

What it will never do

• · Quote a rate, accept or dispute a detention invoice, or decide a claim. Those go to a person with a holding reply already sent.
• · Promise a slot it didn’t book or an ETA it didn’t read from your tracking.
• · Send anything on a message type you haven’t set to Auto.
• · Move your data. It reads your TMS, tracking and scheduling where they live.