Frequently asked questions

A check call is a dispatcher contacting a driver to ask where the load is. Most brokerages run them on a schedule rather than in response to anything, on every active load, several times a day. The answer is almost always that the load is fine.

That is what makes them expensive: the call costs the same whether it tells you something or not, so a dispatcher spends most of a shift confirming that nothing has happened.

Because every alternative asks something of somebody. A telematics integration needs the carrier to be on a platform and willing to share the feed. A tracking app needs the driver to install it. A phone call needs nothing, so it survives.

So the smallest version of our ask is a text with a link, which means a carrier who will install nothing still leaves you with something. Drivers who will install the app give you more, and a truck already on an ELD gives you the most without asking the driver for anything.

Eleven detectors check active loads on a five-minute schedule and on relevant load events. They flag stale tracking, stationary trucks, route deviation, appointments at risk, missing paperwork and other operational exceptions against your settings.

Your rules can notify the team, send driver follow-ups and prepare customer drafts. The dashboard brings the exceptions, supporting evidence and next actions together for your dispatchers.

No. It takes away the calls that tell you nothing and hands your dispatcher the load that needs a decision. Deciding is still theirs, and AI-drafted customer messages wait for a person to review them. Scheduled status emails are separate and must be enabled by your team.

TMS capabilities vary. LoadSignal connects incoming positions to exception detection, configurable follow-up and a command view of the work needing attention. Compare those capabilities with the tracking and automation your TMS already provides. LoadSignal can work alongside it, including through Rose Rocket Classic load sync or the API.

No. There are four tracking paths: the driver app, a browser link, a direct ELD connection, or a supported carrier share link.

The text link installs nothing. The driver taps it, reads what they are agreeing to, and their phone sends a position at most every twenty-five seconds while that page is open. It covers the one load and the link expires on its own. The limit is the browser: when the driver closes the page or the phone locks, positions stop arriving until they open it again. On a short lane, or with a carrier you may never use twice, that trade is usually worth it.

The driver app is the one that keeps reporting from a pocket. It runs a background location service, with a notification the driver can see the whole time, so tracking survives a locked screen and a switch to another app, and it carries from load to load without another tap. What it costs you is an install, a sign-in, and the driver granting background location, which on Android is a two-stage prompt.

Direct Samsara and Motive ELD connections are in beta. With carrier authorization and a vehicle assigned to the load, position comes from the truck. The team helps configure this during onboarding.

A supported Samsara or Motive share link brings the carrier's existing location feed onto the load without a new driver installation.

Choose per carrier rather than once for everyone. Use the link when the ask has to be small, and the app or an ELD connection when you want tracking that doesn't depend on somebody keeping a page open.

If no position arrives inside your configured response timeout, the load can be flagged for carrier non-response. Your team can follow up from the load record.

LoadSignal cannot make a driver share a location. It makes the missing response visible and lets your enabled rules handle supported follow-up actions.

Yes. Direct Samsara and Motive connections are in beta and set up with the team. Supported carrier share links are another option. For other carriers, use the driver app or browser tracking link.

A read-only page with the stops, the status, and the live position when there is one. No account, no login, and nothing of yours behind it.

ETAs appear only once the load has a recent GPS position, and estimates are labelled as estimates. A number nobody can defend is worse than no number.

AI-drafted customer messages wait for a person to review and send. Scheduled status emails are separate: your team can enable them on a load or opt into starting them at dispatch. They are not enabled by default.

A draft waiting on approval expires when the exception behind it resolves, so nobody sends yesterday's delay.

It escalates on a clock you set. The signal fires, waits out your acknowledgment window, and if nobody has touched it, goes to a second address, so it lands somewhere else before it lands with a customer.

The Track and Trace Operator follows the cooldown and attempt limit on each rule. You choose whether supported actions are suggested, queued for approval or executed automatically. Customer drafts always require approval, and unanswered attempts eventually hand the work back to your team.

Yes. Each detector exposes the settings relevant to it, such as a threshold, acknowledgment window, escalation timing and recipients. Your organization can enable or disable detectors and configure the supported response rules.

Pilot AI answers questions about your loads and fleet by reading your records, and drafts messages that a person then sends. It has no send of its own.

Our AI provider is Anthropic. We send them only what a given request needs, and they do not use it to train their models.

What leaves the system, in the privacy policy

Rose Rocket Classic supports one-way load sync. You can also upload a rate confirmation for AI extraction and review, import a CSV, use the public API, or create a load manually.

Other TMS connections are scoped during onboarding and depend on the provider's access. The integrations list distinguishes available connections from planned ones.

There is no public price yet. LoadSignal is in early access and we are still working out what a fair one looks like for a brokerage your size. It will be published before anyone is asked to pay, and nobody is charged for anything they did not see priced first.

What founding customers get is not a discount but a say. The first brokerages on the board decide what gets built next, get their TMS and ELD integrations done ahead of anyone else, and have their thresholds, escalation contacts and lanes set up with us on a call rather than from a help page. That is the part of early access that does not come back later.

Request early access