Skip to content
Dispatch Console — One Screen Dispatch on Salesforce | FTM
FTM Dispatch Console
Live operations on Salesforce

One Screen
Dispatch.

Run every load, driver update, customer request, document, exception, and margin signal from one live Salesforce workspace.

Salesforce-native
Live load status
Driver and carrier updates
Exception alerts
Margin visibility
Dispatch Console Live
Active Loads
142
18 dispatchers
Exceptions
5
2 high priority
On-Time
96.8%
last 24h
Avg Margin
21.4%
active board
LoadRoute / CarrierStatusETAMargin
7201
Chicago → Detroit
TRL-22 · J. Reyes
Transit 2h 40m 23.4%
7202
Dallas → Houston
Atlas Carriers
Late +48m 18.1%
7203
LA → Phoenix
TRL-08 · M. Diaz
Pickup 1h 10m 14.2%
7204
Atlanta → Nashville
TRL-14 · R. Banks
POD In Done 25.0%
4.9
AppExchange Rating
10+
Years as Salesforce ISV Partner
46+
Enterprise integrations
24
Countries supported
14d
Target go-live
The dispatch problem

Visibility alone does not fix dispatch chaos.

Most TMS tools show status. Dispatchers still work across email, spreadsheets, phone calls, PDFs, portals, tracking tools, and accounting systems to actually move a load.

Before: Status Without Action
Load board
Email inbox
Tracking portal
Driver texts
Customer calls
PDF documents
Accounting system
After: Status That Acts
One Dispatch Console on Salesforce

The issue is not lack of data. The issue is disconnected action.

A dashboard shows the problem. A dispatch console lets the team act on it immediately, without opening a fifth tab to do it.

The core concept

Every load becomes a live operating record.

In FTM, the load record connects dispatch, tracking, documents, customer communication, carrier and driver activity, and financial data. One record. Everything attached to it.

Route
Origin, destination, stops
Customer
Account, contact, history
Carrier / Driver
Assignment, compliance
Documents
BOL, POD, rate con
Status Updates
Pickup, transit, delivery
Accessorials
Detention, layover, fuel
Margin
Estimated and actual
Invoice Readiness
POD-to-bill status
Exceptions
Late, missing POD, risk
Salesforce Record
The Load
What the console does

Six capabilities. One screen.

Each capability writes back to the same load record. Nothing here lives in a separate tool that someone has to remember to check.

A
Live Load Board

Every active load in one operational view, filtered the way your team actually works.

All active loads visible in one operational view
Filter by terminal, dispatcher, customer, carrier, status, or margin risk
Built on Salesforce list views, not a separate screen
B
Driver and Carrier Updates

Status comes from the road, not from a phone call to ask where the truck is.

Arrival and departure timestamps captured automatically
POD uploads and GPS updates attach directly to the load record
App and portal updates reduce check calls
C
Exception Management

Problems surface before a customer has to ask about them.

Late pickup and late delivery flagged automatically
Missing POD and detention risk surfaced on the load
Rate mismatch and margin risk caught before the load is covered
Exception Queue3 open
LoadIssueAgeRisk
7202Late delivery48mHigh
7188Missing POD2hMedium
7195Margin risk15mMedium
D
Document Control

Documents live where the load lives, and AutoFill reads them for you.

BOL, POD, rate confirmation, and invoices attached to the load record
AutoFill AI reads documents and populates fields automatically
Invoice readiness visible before billing starts
AutoFill Processing98.4% confidence
FieldValueSource
Rate$2,840.00Rate Con
DeliveryJun 19 14:20POD
E
Customer Communication

Customers get answers without your team picking up the phone.

Customer status updates triggered from the same load record
Customer portal visibility without a separate login system
Fewer “where is my load” emails reaching dispatch
F
Margin and Financial Signals

Profitability is visible on the load, not discovered at month end.

Estimated margin shown at booking, actual margin at delivery
Accessorials and invoice readiness captured before billing
Lane profitability visible without exporting to a spreadsheet
Lane Margin Live
LaneEst.Actual
CHI → DET22.0%23.4%
DAL → HOU20.5%18.1%
Built for the whole team

One console. Different value for every team.

The same load record means everyone is looking at the same truth, just filtered for what their role needs.

Dispatchers
Less switching, faster decisions, fewer manual updates to chase down.
Managers
A live view of exceptions, team workload, and performance without asking for a status update.
Executives
Margin, service, and volume visibility across the whole operation, not just one terminal.
Customer Service
Fewer status calls and faster answers because the data is already on the load.
Finance
A cleaner handoff from POD to invoice, with accessorials already captured.
Salesforce Admins
Configurable workflows, fields, automation, and dashboards, owned internally.
Why architecture matters

Why Dispatch Console works better inside Salesforce.

A dispatch screen bolted onto Salesforce behaves differently than one built on it. The difference shows up the first time something needs to be customized.

Capability
Traditional Dispatch Screen
FTM Dispatch Console
Customer data
Lives in a separate CRM
Native Salesforce account and contact records
Updates
Status synced in from outside tools on a delay
Updates land live on the Salesforce load record
Documents
Stored in email threads or external folders
Attached directly to the load record
Automation
Vendor-controlled rules, change requests required
Salesforce Flow and configurable workflows you own
Reporting
Exports or a separate BI tool
Native Salesforce dashboards, always current
AI
Disconnected data pipeline required
AI runs on structured freight data inside Salesforce
How a load moves through the console

From booking to invoice-ready, on one screen.

Six steps. No tool switching. Each one updates the same load record the rest of the team is already looking at.

1
Load created or imported
A load enters the console manually, from a quote, or imported from a load board. The Salesforce record is created immediately.
2
Dispatcher assigns carrier or driver
Compliance status and equipment availability are visible at the point of assignment, not discovered afterward.
3
Status updates come in
Pickup, transit, and delivery events post to the load record from telematics, driver app, or manual entry.
4
Exceptions are flagged
Late pickup, late delivery, or margin risk surfaces on the console the moment it happens, not at end of day review.
5
Documents are uploaded or read by AutoFill
BOLs, PODs, and rate confirmations attach to the load. AutoFill extracts the data so no one re-keys it.
6
Load becomes invoice-ready
Accessorials, POD, and final margin are already on the record. Finance picks up where dispatch left off.
What changes operationally

Control the day before the day controls you.

These are the operational shifts teams report after moving dispatch onto one console, not promises about specific numbers your operation will see.

More loads per dispatcher
Less time spent switching tools means more time spent moving freight.
Fewer check calls
Status updates arrive on the load record instead of through a phone call.
Faster exception response
Problems are flagged the moment they happen, not discovered hours later.
Cleaner billing handoff
Finance starts from a load record that already has POD and accessorials attached.
Fewer missed accessorials
Detention and layover are captured at the time they happen, not at invoice review.
Live operational reporting
Leadership sees the same console the dispatch floor is working from, in real time.
Ecosystem integrations

Works with the transportation tools you already use.

Dispatch Console connects to telematics, mapping, load boards, and accounting platforms already in your stack.

Implementation

Go live without a year-long TMS project.

FTM is configurable because it runs on Salesforce. Dispatch Console is set up around how your team already dispatches, not a workflow imposed on top of it.

Core workflows live in as little as 14 days
Salesforce Enterprise included
Configured around your current dispatch process
Supports brokers, carriers, shippers, or mixed operations
Go live in as little as 14 days or your first month is free.
Dispatch Console deploys as a configuration project on existing Salesforce infrastructure. Your dispatch process maps onto the console, not the other way around.
Dispatch Console FAQ

Questions teams ask before switching.

For questions specific to your operation, a transportation specialist can walk through your use case.

Is Dispatch Console only for brokers?
+
No. Dispatch Console supports brokers, asset-based carriers, shippers, and mixed operations. The load record adapts to whichever model your operation runs, including brokered and owned-asset freight on the same board.
Can carriers use Dispatch Console for drivers and equipment?
+
Yes. Carriers use Dispatch Console to assign drivers and equipment, track compliance, and manage terminal-level operations alongside the same load and customer records brokers use.
Does it replace our current tracking tools?
+
Dispatch Console connects to your existing telematics and tracking providers rather than replacing them. Samsara, Geotab, MacroPoint, and others feed location and status data directly into the load record.
Can customers see shipment updates?
+
Yes. Customers can see live shipment status through the FTM customer portal, which pulls directly from the same load record dispatch is working from. No separate sync or delay.
Does it support documents like BOLs and PODs?
+
Yes. BOLs, PODs, rate confirmations, and invoices attach directly to the load record. FTM AutoFill can read these documents and populate fields automatically, reducing manual data entry.
Can we customize fields and workflows in Salesforce?
+
Extensively. Because Dispatch Console runs on Salesforce, your admin can configure fields, layouts, automation, and dashboards using standard Salesforce tools without involving the FTM vendor for every change.
Dispatch Console
Board
Exceptions
Documents
Margin
Active Loads
142
Exceptions
5
On-Time
96.8%
Avg Margin
21.4%
Invoice Ready
38
LoadRouteStatusETAMargin
7201
Chicago → Detroit
TRL-22 · J. Reyes
Transit 2h 40m 23.4%
7202
Dallas → Houston
Atlas Carriers
Late +48m 18.1%
7203
LA → Phoenix
TRL-08 · M. Diaz
Pickup 1h 10m 14.2%
7204
Atlanta → Nashville
TRL-14 · R. Banks
POD In Done 25.0%
7205
Seattle → Portland
TRL-31 · K. Hahn
Transit 3h 05m 22.7%
Open Exceptions
Load 7202 · Late
Detention risk, 48 min past appointment
Recent Documents
POD · Load 7204
AutoFill read · 98.4%
Rate Con · Load 7201
AutoFill read · 99.1%
See it on your loads

This is the board your team would work from.

Loads, exceptions, and documents in one view. Tell us about your operation and we will walk through it with your own lane structure.

Request a console walkthrough
We will tailor the demo to your dispatch process. No generic pitch deck.
No commitment required  ·  Reply within one business day

See how your operation would run from one screen.

Bring your dispatch process, load flow, and exceptions. FTM will show how they can run inside Salesforce.

Salesforce Enterprise included  ·  Go live in as little as 14 days  ·  No long-term contract required
Let's Talk!

Thanks for stopping by! We're here to help, please don't hesitate to reach out.

Watch 3-Min Demo