Skip to content
Motive Integration

Turn Driver And Fleet Data Into Transportation Visibility

Motive, formerly KeepTruckin, provides ELD, driver activity, HOS, and fleet visibility data. FTM connects that information to dispatch workflows, customer communication, reporting, and transportation operations inside Salesforce. Driver, fleet, customer, shipment, and financial data stay in one platform.

Motive
Fleet and driver data
ELD, HOS, location, activity
Driver
Vehicle
HOS
Geofence
FTM
FTM on Salesforce
One transportation record
Dispatch
Portal
Reporting
Billing
Salesforce
Native platform
46+
Integrations
14 days
Typical go-live
24
Countries
Common use cases
Asset-Based Carriers
Dedicated Fleets
Private Fleets
Brokers With Carrier Visibility
Mixed Operations
From visibility to operations

Fleet Data Needs Transportation Context

Knowing where a truck is does not explain which load is affected, which customer is impacted, which dispatcher needs to know, which shipment milestone changed, or which workflow should trigger next.

Motive
Load Record
Dispatch Console
Customer Portal
Reporting

Motive provides ELD data, driver activity, HOS status, and fleet visibility. FTM connects that data to the load it belongs to, the customer waiting for it, and the dispatcher who needs to act on it.

Fleet data tells you what is happening. Operational context tells you what to do about it. FTM provides the connection between the two.

Motive provides visibility. FTM provides operational context.

From ELD Data To Transportation Visibility

Transportation teams can use Motive driver and fleet information inside transportation workflows rather than viewing it separately from shipment records and customer context.

Motive Provides
Vehicle location
Driver activity & status
Hours of service (HOS)
Safety events & alerts
Geofence events
FTM Connects It To
Dispatch visibility and workflows
Customer updates and portal
HOS visibility for load planning
Load records and carrier context
Operational reporting
Why transportation teams connect Motive to FTM

Why Transportation Teams Connect Motive To FTM

Fleet visibility and driver data become operationally valuable when connected to the records, workflows, and reporting that transportation teams already run their business from.

Reduce Dispatcher Follow-Up
Live vehicle location and driver status from Motive in FTM means dispatch teams stop making check calls to get updates they can already see.
Improve Customer Visibility
Customers see real shipment progress on the Customer Portal instead of calling dispatch. Visibility data from Motive powers the customer-facing experience.
Centralize Driver Activity
Driver status, HOS, safety events, and location from Motive connect to the same platform dispatch, finance, and leadership already use for transportation operations.
Track Operational Performance
Fleet activity, driver performance, and HOS compliance from Motive appear in the same Salesforce dashboards used for operational and financial reporting.
Connect Fleet Activity To Revenue
Delivery events from Motive can trigger document collection and AutoFill, turning the end of a trip into a billing action without manual data entry.
Reduce Compliance Exposure
HOS data visible in FTM means loads are assigned to drivers with available hours, reducing late pickups, compliance violations, and last-minute coverage problems.
Driver availability

Hours Of Service Connected To Dispatch Operations

Driver availability impacts dispatch planning, shipment execution, customer expectations, and transportation performance. HOS data from Motive gives dispatch teams the information they need to make better decisions before problems occur.

Motive HOS
Real-time hours of service data
Driver Availability
Who has hours for the next load
Dispatch Planning
Load assignments based on actual availability
Shipment Execution
On-time pickups with compliant drivers
Customer Visibility
Accurate ETAs from real driver status

When a dispatcher assigns a load without knowing a driver’s HOS status, the risk of a late pickup, a missed delivery window, or a compliance violation increases. HOS data from Motive, connected to FTM, removes that blind spot.

Dispatch teams can see which drivers have hours available before making assignments. Load planning reflects actual driver capacity, not estimates. Customer ETAs are based on real driver availability, not optimistic scheduling.

For brokers and shippers who do not own the drivers they dispatch, HOS visibility is especially valuable. Knowing a carrier driver’s available hours before tendering a load reduces late pickups, last-minute coverage issues, and compliance risk.

HOS visibility supports better dispatch decisions before problems occur
Operational automation

Geofencing And Operational Automation

Use location and geofence events from Motive to automate transportation workflows. Location visibility becomes more valuable when it creates action.

Motive Event
FTM Action
Arrive At Pickup
Shipment status updated, operations notified
Depart Pickup
Transit workflow begins, customer visibility opens
Arrive At Delivery
Delivery milestone created, customer notified
Depart Delivery
Billing workflow triggered, document collection begins

Location visibility becomes more valuable when it creates operational action. FTM helps transportation teams use vehicle location and geofence events from Motive to automate workflows, customer communication, and transportation operations.

Driver data in context

Driver Activity Connected To Transportation Workflows

Motive provides driver activity and operational visibility. FTM connects those events to shipment records, dispatch workflows, customer updates, and reporting inside Salesforce.

Driver Activity On The Load Record
Driver status, HOS, and activity from Motive connect directly to the carrier and load records they belong to inside FTM.
HOS In Dispatch Planning
Hours of service data from Motive informs load assignments before dispatch. Drivers with insufficient hours are visible before a compliance issue occurs.
Dispatch Informed By Live Status
Dispatch teams see actual driver and vehicle status from Motive without switching platforms or making check calls for updates.
Customer Visibility From Driver Location
Shipment status on the Customer Portal can reflect actual driver position from Motive rather than requiring manual status updates from dispatch.
Safety Events In Operational Context
Safety alerts and driver events from Motive appear alongside the shipment and carrier records they affect, not in a disconnected fleet system.
Fleet Performance In Reporting
Driver performance, HOS compliance, and fleet activity from Motive appear in the same Salesforce dashboards used for operational and financial reporting.

HOS and Dispatch: Why It Matters For Brokers. Many brokers and shippers dispatch loads through carriers whose drivers they have never met and whose schedules they cannot see. When HOS data from Motive is connected to FTM, that blind spot shrinks. Brokers can see driver availability before tendering a load, reducing late pickups, last-minute coverage problems, and compliance exposure across their carrier network.

Where the data lives

One Transportation Record

Vehicle visibility, driver activity, HOS information, shipment milestones, customer communication, documents, dispatch actions, and reporting remain connected through the same transportation record inside Salesforce.

FTM runs natively on Salesforce. Not integrated with Salesforce. Not synced to Salesforce. Every load record, carrier record, customer record, and fleet data point lives in the same environment your business already uses.

When Motive data enters FTM, it connects to the load it belongs to, the carrier managing the driver, and the customer waiting for delivery. Existing Salesforce licenses are not required. Salesforce can be provisioned as part of the FTM implementation at no additional platform cost.

Driver visibility and transportation visibility become the same visibility.

Salesforce-native, not a separate fleet system
Load Record
Vehicle
Real-time location from Motive
Driver
Activity and status from Motive
Carrier
Linked to driver and vehicle
Load
Dispatch, status, and milestones
Customer
Visible on the Customer Portal
HOS
Driver hours connected to the load
Status Updates
Triggered by location events
Documents
BOL, POD, rate confirmation
Reporting
Fleet, HOS, and operational data
Salesforce-Native Does Not Mean Salesforce Required
Salesforce platform can be included as part of the FTM implementation at no additional platform cost. Existing Salesforce licenses are not required. Organizations can deploy FTM inside an existing Salesforce environment or launch with Salesforce provisioned as part of implementation.
From location to invoice

From Visibility To Billing

Transportation visibility becomes more valuable when connected to billing and financial workflows. A delivery event from Motive can trigger document collection, AutoFill, and invoice generation in the same workflow.

Motive
Delivery Event
Document Collection
AutoFill
Invoice
Reporting

When a vehicle departs a delivery geofence in Motive, that event marks the end of the load. FTM can use that delivery confirmation to trigger document collection: proof of delivery, signed BOL, and rate confirmation.

AutoFill reads those documents, matches the customer and carrier already on the load record, and populates the customer charge and carrier pay item automatically. The visibility event at the end of the trip becomes the billing action that opens the invoice.

This connects transportation visibility directly to revenue generation, without manual steps between delivery and invoice.

Explore AutoFill
When direct access is unavailable

Visibility Beyond Direct Telematics Access

Many brokers and shippers move freight through carriers that own their own ELD and telematics systems. Direct access is not always available. FTM can support driver location requests as an additional visibility option.

When Motive Is Available
Full ELD visibility
Real-time vehicle location, driver activity, HOS data, safety events, and geofence information flow directly from Motive into FTM load records, dispatch workflows, and customer visibility.
When Direct Access Is Unavailable
Driver location requests
When a carrier manages their own ELD system outside your control, FTM can send a location request directly to the driver. The driver shares position through a mobile browser. Location returns to the Dispatch Console without requiring telematics integration.
Motive Data
Driver Location Request
FTM Dispatch Console
Particularly Valuable For Brokers And Shippers
Many brokers and shippers do not own the ELD systems used by their carriers. FTM helps connect available telematics data from Motive and supplemental driver location requests to the same dispatch visibility, customer portal, and transportation workflows regardless of which carrier is on the load.
Motive Integration FAQ

Questions teams ask before connecting Motive.

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

Why integrate Motive with FTM?
+
Motive provides ELD data, driver activity, HOS, and fleet visibility. FTM connects that information to transportation workflows, dispatch decisions, customer visibility, and reporting inside Salesforce, turning driver and fleet data into operational intelligence.
How can Motive data improve dispatch visibility?
+
Vehicle location, driver activity, and HOS status from Motive can connect to load records, carrier records, and the Dispatch Console inside FTM. Dispatch teams see actual driver and vehicle status without switching platforms or making check calls.
Can HOS information support dispatch planning?
+
Yes. HOS data from Motive, connected to FTM, gives dispatch teams visibility into driver availability before load assignments. Loads can be tendered to drivers with sufficient hours, reducing late pickups, last-minute coverage issues, and compliance exposure across the carrier network.
Can geofence events automate transportation workflows?
+
Yes. Location and geofence events from Motive can support shipment status updates, dispatch notifications, customer visibility updates, document collection, and billing workflow triggers inside FTM automatically.
Does FTM replace Motive?
+
No. Motive remains the ELD, HOS, and fleet visibility platform. FTM manages the transportation workflows, shipment records, customer communication, and operational reporting that surround driver and fleet activity.
Do we need Salesforce before implementing FTM?
+
No. Salesforce platform can be included as part of the FTM implementation at no additional platform cost. Existing Salesforce licenses are not required. Organizations can deploy FTM inside an existing Salesforce environment or launch with Salesforce provisioned as part of implementation.
Can FTM support visibility when direct telematics access is unavailable?
+
Yes. When a carrier manages their own ELD system outside your control, FTM can send location requests directly to drivers as an additional visibility option. Location returns to the Dispatch Console without requiring telematics integration. This is especially useful for brokers and shippers who do not control carrier ELD systems.
Get started

Turn Driver And Fleet Visibility Into Transportation Intelligence.

See how Motive data can connect to dispatch operations, customer visibility, workflow automation, reporting, and transportation intelligence inside FTM.

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