Dispatch & logistics ops console
Own every mile.
Orchestrate every move.
Your dispatchers should not need seven tabs to cover one load. Echo Move joins live telemetry, routing, load and customs workflows, carrier bidding, and trip settlement into a single real-time console, sitting on top of the TMS and telematics you already run.
One console instead of fragmented tools. Every routing call, award, and settlement shows its work in the audit trail, so your team can trust it and defend it.
Built to sit on top of McLeod, MercuryGate, Trimble, and Oracle OTM. And your Samsara, Geotab, or Motive feed. No rip-and-replace.
Agentic AI · The dispatch agent · Early access
An agent that drafts the dispatch plan. The dispatcher still makes the call.
Echo Move is adding an agentic layer to the console. The dispatch agent reads open loads and RFQs, your available vehicles and drivers (respecting hours-of-service, capacity, and customs constraints), and the carrier bids on the board.
01
Proposes load-to-vehicle assignments
That satisfy the constraints, with the reasoning shown.
02
Matches RFQs to carriers
And surfaces the bid it would award, and why.
03
Hands it to the dispatcher
Consequential moves (assignments and awards) are queued for approval and execute on the existing atomic award transaction once a person signs off.
Agentic, dispatcher in control.
Act-with-approval
On every consequential move. Only low-impact actions (such as a proactive customer notification within your rules) may auto-run.
Explainable
Each proposal shows the constraints it satisfied and the trade-offs it made.
Guardrailed
You decide what the agent may do on its own. It fails closed.
Audited
Every proposal and approval is written to the append-only audit log.
Status: early access
In design-partner validation. Not presented as fully autonomous or generally available.
The problem
Dispatch is not a software problem. It is a seven-tabs problem.
A dispatcher's day: refresh the TMS, alt-tab to the telematics dashboard, scroll the email thread of carrier bids, call the carrier, check the spreadsheet of rates, file the customs doc somewhere, and still take the call from the customer asking where the truck is.
Every system holds one slice of the truth. None of them holds the move.
The tab today
What it cannot tell you
Your TMS
Where the truck actually is, right now
Your telematics dashboard
Which load and which customer this truck is on
Your email inbox
Which carrier bid you should actually award
Your spreadsheet
Which accessorials you forgot to bill at settlement
The work that decides your margin (the award, the exception, the settlement) happens in the gaps between tools, where nothing is recorded and nothing is audited.
How it works
One pane, from dispatch to settled invoice.
01
Connect, do not migrate.
Echo Move plugs into your TMS and your telematics provider through open APIs and webhooks. Your TMS stays the system of record for loads, rates, and invoicing. Echo Move becomes the live ops layer on top. Nothing to rip out.
02
Watch the fleet, joined to the work.
Live vehicle telemetry streams into the console over a WebSocket feed, pushed the instant your provider pings, not on a 30-second poll. Every truck is tied to its load, its customer, and its exception.
03
Cover loads in one click.
Post a load to your carrier panel. Ranked bids come back. Award the right one in a single, atomic transaction: the losing bids auto-reject, the load is minted. No half-awarded states, no "did the load actually get created" phone call.
04
Settle, audited.
When the trip completes, settlement is computed server-side from signed line items, accessorials captured, and moved through a pending → approved → paid lifecycle, every transition written to a tamper-proof audit record.
Key capabilities
The move, in one live pane.
Unified dispatch console
One real-time pane that joins telemetry, routes, loads, carriers, customs, and settlement. The dispatcher works the whole move in one place instead of reconciling status across seven tabs.
Live vehicle telemetry
Real-time fleet positions and status pushed over a WebSocket feed the instant your telematics provider pings. Every truck is tied to its load and its customer. No alt-tab to a separate dashboard to figure out what a moving dot is carrying.
Route planning
Plan and review routes with stops in the console, with traffic and re-route context surfaced on the route. Echo Move does not replace your optimizer, it makes the dispatcher's decision visible and logs it to the audit trail.
Load planning
Build and validate loads against the move before the truck rolls, so what is planned in the console matches what is tendered and settled.
Customs workflow
A guarded customs state machine with document upload, so the customs steps for a cross-border move live on the same record as the dispatch. Not in a separate folder and a separate email thread.
Carrier bidding and atomic award
Post a load to your carrier panel, see ranked bids with match scores, and award in one click. The award is atomic: accept one bid, auto-reject the rest, mint the load. One transaction, no half-awarded states.
Trip settlement with signed line items
Settlement math is computed server-side from signed line items, so the number your carrier sees and the number you approve are the same number. The accessorials you used to forget to bill get captured here, and every transition is written to a tamper-proof audit record.
Fleet maintenance
Track vehicle maintenance alongside dispatch, so a truck's service status is part of the same operational picture you are dispatching against.
Driver hours-of-service companion
A driver-facing companion for hours-of-service, keeping the people side of the move on the same platform as the load side.
RBAC and audit
Role-hierarchy access control and an append-only audit log. Who saw what, who changed what, who awarded what. Recorded, not assumed.
OIDC single sign-on
Enterprise SSO over OIDC, so Echo Move joins your existing identity provider instead of becoming another password to manage.
The differentiator
Most tools own a slice. Echo Move owns the move.
Your TMS records the load. Your telematics platform tracks the truck. A visibility platform tells you where it is. None of them holds the decision: who you should have awarded the load to, and what you left on the table at settlement.
Echo Move is the dispatch console where that decision actually happens, and where it is recorded.
One console instead of fragmented tools
Telemetry, routing, load and customs workflows, carrier bidding, and settlement in a single real-time pane. Not seven tabs stitched together by a human and a spreadsheet.
Explainable, auditable by design
Every routing decision, every award, every settlement transition is logged to a tamper-proof audit trail. The console shows its work, so dispatchers can act on it and finance can defend it.
An ops layer, not a replacement
Echo Move sits on top of the systems of record you already paid for. The TMS keeps the loads and the invoicing. Echo Move runs the live move on top.
"We do not replace your TMS. We make the dispatcher's screen finally tell the truth, in real time."
Freight marketplace · Early access
When your panel cannot cover it, the network can.
Echo Move's embedded freight marketplace is not a load board of strangers. It starts as your own carrier panel, digitized: the carriers you already trust, now bidding through a ranked board instead of a 30-email thread, with scorecards and an audit trail.
The long-term vision: as more freight runs through the platform, carriers proven reliable across the network become available to cover the loads your panel cannot. Scored on on-time and insurance, and settled on the same rails as the rest of your dispatch.
Where it stands today, honestly
The RFQ → bid → award workflow exists and is part of the console. The marketplace take-rate billing, charging on net-new, platform-sourced coverage, is in early access and not yet live. We are onboarding design partners now to prove it on real freight before we put a number on it.
Our commitment when it does go live
A take-rate only ever applies to net-new coverage we sourced for you. Never a tax on freight you already source through your own panel, where your rate stays zero. We never take title to freight and never re-sell your carrier relationships without consent. Trust is the product.
Integrations
On top of your stack. Not instead of it.
Your TMS stays the system of record for loads, rates, and invoicing. Echo Move is the ops-and-exception layer on top. Event-driven and contract-first, built to be audited.
Contract-first
Echo Move exposes an OpenAPI 3.1 contract, so your team can generate a typed client and integrate against a spec, not a slide deck.
Event-driven
HMAC-signed webhooks push state changes so your TMS or iPaaS can react in real time, instead of waiting on a nightly batch.
Identity that fits your stack
OIDC single sign-on and role-hierarchy RBAC.
Area
Status
TMS integration (McLeod, MercuryGate, Trimble, Oracle OTM) via API and webhooks
Telematics ingestion (Samsara, Geotab, Motive)
Carrier bidding (your own panel)
Marketplace network coverage and take-rate billing
Social proof
Proof, coming.
Echo Move is onboarding design partners now. We do not publish customer logos, case studies, or performance metrics we have not earned. So this space is intentionally empty until a named partner validates a real result and consents to share it.
Coming soon
Design-partner case studies, validated outcomes, and customer logos.
Leakage estimator
Estimate what you are leaking. On your own numbers.
Many 3PLs lose margin to unbilled accessorials (detention, lumper, and stop-off charges that never make it onto the invoice) and to unaudited settlements. This estimator computes on your inputs. We do not preload it with savings figures, because we do not have a proven one to claim yet.
Estimated potential recovery
…
Computed as your revenue multiplied by the leakage percentage you entered.
This is an estimate based on the numbers you enter, not a guarantee. We will help you pressure-test it against your actual settlement data on the demo.
One pane. One lane. One bad day.
See your worst dispatch day, handled in one pane.
Bring us one lane and one bad day. We will run a 30-minute demo against your TMS and telematics, and scope a 2-week POC with success criteria in writing before day one.
Need this tailored to your environment?
Every Aelix product can be configured, extended, or built bespoke for your industry, data sources, and compliance constraints. Talk to our engineers about what would change.
Configurable workflows
Adapt rules, thresholds, and approval flows to match your operational policies.
Custom data integrations
Connect to your specific ERP, MES, SCADA, CRM, or proprietary systems.
Bespoke modules
Build product extensions tailored to your industry, region, or compliance needs.