The whole shift.
One connected operation.
Track the freight, handle the exceptions, and put your follow-up rules to work. Explore the workspace your brokerage uses from dispatch through delivery.
The loads that need you, first.
Current exceptions and appointment exposure lead the board. Each load carries its next commitment, tracking freshness, next action and owner. Filter the view, search a load, and open its record when you need the detail. Appointments stay in the stop's local time.
One page per load, and no second system to open.
Commodity, equipment, weight, the driver and tractor assigned, both appointment windows, and a customer tracking link you can copy and send. Stops, map, timeline, exceptions, messages and documents each get a tab on the same page.
The tracking link customers get
A read-only page with the stops, the status and the live position when there is one. No account, no login, nothing of yours behind it. It answers the “where's my load” call before it's made.
An ETA that says what it is
Route estimates are labelled as estimates on the page itself, and the system ETA only appears once the load has a recent GPS position. A number nobody can defend is worse than no number.
Every stop, with what the driver sees
Addresses, appointment windows and the instructions that went out with the dispatch, so a question about a stop gets answered from the same record the driver is reading.
From trip evidence to the invoice
The trip record keeps GPS-observed stops and tracking gaps. Add detention from time beyond the customer's free-time allowance, then prepare an invoice packet with the trip record, load summary and delivery documents. Each detention line is added by a person.
Documents that become usable information
Uploaded BOLs and PODs are read for signatures, damage notes, quantities and seal numbers. The original document stays on the load for review.
Four ways a load reports its position.
Work with the tracking your carriers can provide. ELD connections, the driver app, a browser link and supported carrier share links all feed the same load record.
With the link and the app, sharing starts only after the driver agrees to it and stops when the load delivers. Nobody is tracked between loads.
Load NSF-28491, Chicago → Nashville. Tap to share your location with dispatch for this load:
loadsignal.app/t/8Kq2rD
The link, the option that installs nothing. What the driver reads before their phone asks for anything.
Stop retyping what's already on the rate con.
Upload the rate confirmation and review a prefilled load. Pickup, delivery, appointments and carrier details are ready to check before you create it.
For connected load intake, use Rose Rocket Classic sync or the public API.
- Upload the rate confirmationThe PDF you already get from the customer or broker. No template, no reformatting.
- LoadSignal reads itPickup, delivery, appointments and carrier details are extracted into a load review screen.
- You check it before anything existsReview the extracted values and source document. Correct a field before you create the load.
- Create the loadConfirm, and the load exists: stops, appointment windows, commodity and reference numbers already filled in.
You decide what counts as a problem, and who hears about it.
Configure eleven detectors with the controls relevant to each: thresholds, acknowledgment windows, escalation timing and recipients. Turn route deviation off for a lane where drivers always take the same shortcut, or adjust how long a truck can sit before stationary detection flags it.
Two addresses, two levels
Normal alerts go to your operations email. Anything still open past the escalation window goes to a second address, so it lands somewhere else before a customer finds it.
Schedule the tracking link instead of remembering it
Pick a date, time and timezone and LoadSignal texts the driver their link then. If no location comes back inside the response timeout, that becomes its own signal.
Customer drafts need approval
Escalation reaches your team. Customer drafts from AI and the Operator wait for a person to review and send. Scheduled status emails are separate and run only after your team enables them.
Tell it what to do, and how much rope it gets.
Watching and escalating happen on their own. The Operator is the layer above that: rules you write, matched only against exceptions that are already open. It can't act on something your dispatcher can't see on screen.
It ships switched off. You turn it on one rule at a time, and every rule says how far it's allowed to go.
- Suggest onlyWrites down what it would have done, down to the message text. Sends nothing, queues nothing.
- Approve firstDriver and customer messages wait for approval. Internal notifications reach your team.
- AutomaticDriver messages go out on their own. Customer messages still wait for you.
Set a retry limit, then hand it to a person
By default, a rule fires, waits thirty minutes, and tries once more. If the exception stays open, it stops and alerts the load's watchers. Cooldowns and attempt limits belong to the rule, so your team can decide when a person should take over.
A draft dies when the problem does
A customer update queued because tracking went quiet becomes a lie the moment tracking comes back. Anything waiting on approval expires when the exception behind it resolves, so nobody sends yesterday's delay.
Ask, instead of digging.
Pilot AI reads your loads, exceptions and fleet status and answers in plain language. It will draft the customer email too. It will not send it.
Review before sending
Customer updates Pilot AI prepares wait for a dispatcher to check the facts, review the wording and approve the send. Your automatic driver follow-up rules have their own controls.
Answers from your data
It looks up the actual load and fleet records to answer. It isn't reciting a status from a general knowledge of how freight usually goes.
Driver replies can move the operation forward
Alongside Pilot AI, the driver reply loop reads incoming texts and checks their claims against GPS and the load's state. Read and propose is the default. With Automatic enabled, supported updates can be applied when the evidence agrees; uncertain replies get a follow-up question or human review. A delivery is never marked from a text.
Connect the systems behind the load.
Bring positions, load records and incoming messages into your operation. Your team can keep working with its existing tools while LoadSignal monitors the load and prepares the next action.
ELD connections are in beta and set up with our team during early access. These are independent integrations, without vendor partnership or endorsement.
ELD connections Beta
Samsara
Connect the fleet's account for GPS position and hours-of-service data.
Motive
Connect the fleet's account for GPS position and hours-of-service data.
Rose Rocket Classic
Bring each carrier manifest into LoadSignal as a load, including the carrier and stops. Review sync activity and retry failed imports.
Public API & webhooks
Create and update loads through your own integration. Receive load, stop, position and document events.
Chrome Companion
Keep a load's tracking, ETA, alerts and actions beside the TMS page your team is already using.
Carrier share links
Use supported Samsara, Motive and EVA ELD-family links, pasted into a load or received at its email address.
Built for freight data that isn't meant to be public.
Loads, rates and driver contact details are sensitive to a brokerage. Here's what that means in practice, stated plainly rather than left to a badge.
Your data stays in your organization
Every query is scoped to your organization on the server. It's never determined by anything the browser sends.
Role- and permission-based access
Ops admins, dispatchers, managers, drivers, and customer viewers see what their role allows, down to whether they can see a driver's contact details.
Encrypted credentials
API tokens for connected ELD accounts are encrypted at rest, never stored or shown in plain text after you save them.
Private document storage
Uploaded PDFs and delivery paperwork are stored privately and served only through an authorized request, never a public link.
LoadSignal is early-stage and has not completed a third-party security certification such as SOC 2. If that's a requirement for your organization, tell us during early access and we'll talk through where things stand. Full detail on data handling lives in our security page and privacy policy.
Put your operation on LoadSignal.
- Bring a CSV or rate confirmation. We help get your loads and tracking connected.
- Set thresholds, escalation contacts and automation behavior with us on a setup call.
- Get direct product support and a say in what gets built next.
Paid, and priced before anyone is asked to pay. Founding customers shape what gets built next and get their integrations first.