Skip to content
Home » My Carrier Portal

My Carrier Portal

MyCarrierPortal TMS Integration for Carrier Onboarding | FTM
MyCarrierPortal / MyCarrierPackets Integration

From Carrier Invitation To FTM Carrier Record Without Re-entering The Packet

The MyCarrierPortal TMS integration connects MCP carrier onboarding packets directly to FTM. Send an Intellivite invitation through MCP, and then, when the carrier completes their packet, FTM creates or updates the carrier record with available insurance, W9, contacts, factoring, equipment, and compliance data automatically. As a result, carrier information flows into Salesforce without a separate data entry step.

Book Executive Demo Explore Carrier Onboarding
From invitation to active carrier record
Intellivite Invitation Sent
Carrier invited through MCP
Carrier Completes MCP Packet
Insurance, W9, contacts, factoring entered
MCP Returns Carrier and Compliance Data
Matched by DOT or MC number
FTM Creates or Updates Carrier Record
In Salesforce, without re-entering data
Carrier Available Across FTM Workflows
Onboarding, dispatch, carrier management
4.9
AppExchange rating
14 days
Typical core go-live
46+
Integrations
110+
AppExchange reviews
Packet data, documents, and compliance

What The MyCarrierPortal TMS Integration Brings Into FTM

When a carrier completes their MCP onboarding packet, FTM pulls the available data from the packet and populates the Salesforce carrier record. However, the specific fields populated depend on what the carrier submitted and how the MCP integration is configured for your account.

Carrier Identity
Legal carrier name
MC and DOT numbers
SCAC code where available
Carrier address
MCP carrier identifier
Insurance
Insurance certificates from packet
Coverage types and limits
Policy expiration dates
MCP compliance and risk status
Contacts
Corporate contact name
Corporate phone and email
Dispatch contact name
Dispatch phone and email
Factoring and Remit-To
Factoring company name
Remit-to address from packet
Payment instructions on file
NOA where submitted
W9 and Tax
Tax ID submitted in packet
W9 document stored with carrier
Entity type from MCP
Equipment and Availability
Equipment types from packet
Operating regions
MCP blocked status
MCP risk status

For more context on MCP carrier onboarding and compliance, see Descartes MyCarrierPortal.

Packet-completion-driven, not scheduled

The Packet Drives The Carrier Record. No Re-entry Required.

Unlike a scheduled background sync, MCP carrier data arrives in FTM when the carrier completes their packet. In addition, teams can refresh the data on demand using the Sync Carrier Data action inside the FTM carrier record. Then, FTM matches the carrier to an existing record by DOT or MC number, or creates a new record if no match is found.

Intellivite Invitation Sent from FTM
Carrier receives MCP onboarding invite
Carrier Completes MCP Onboarding Packet
Insurance, W9, contacts, factoring submitted
FTM Matches Carrier by DOT or MC
Existing record updated, or new one created
Carrier Record Populated in Salesforce
Documents stored, data fields updated
Carrier Available for Dispatch and Management
Ready to use across FTM workflows
Carrier data can also be refreshed on demand using the Sync Carrier Data action inside the FTM carrier record, without waiting for a new packet submission. In addition, overwrite behavior for existing fields is configurable.
Configurable Overwrite Behavior
When a carrier record already exists in FTM, the integration can be configured to control which fields are overwritten with incoming MCP data and which are preserved. As a result, MCP sync does not have to overwrite FTM-specific data your team has added to the carrier record.
Carrier record and documents in Salesforce

The Packet Populates The Record. Documents Stay With The Carrier.

After MCP sync, the FTM carrier record holds available data from the completed packet alongside the compliance documents the carrier submitted. In addition, insurance certificates, W9s, and other packet documents are stored directly with the carrier record in Salesforce.

FTM Carrier Record
Synced from MCP
Carrier identity
Carrier Name
Summit Freight Solutions LLC
MC Number
MC-391047
DOT Number
DOT-1847392
MCP compliance status
MCP Risk Status
Approved
MCP Blocked Status
Not Blocked
Insurance
Liability Coverage
$1,000,000
Cargo Coverage
$100,000
Liability Expiration
Jun 30, 2027
Cargo Expiration
Nov 15, 2026
Factoring and tax
Factoring Company
Apex Freight Finance
W9 Status
On File
MCP Last Synced
Aug 16, 2026 at 2:14 PM
Carrier Documents from MCP Packet
Certificate of Liability Insurance
Current
Cargo Insurance Certificate
Exp. Soon
W9 Form
On File
Carrier Agreement
Signed
Notice of Assignment (NOA)
On File
Documents Stored With the Carrier Record
Insurance certificates, W9s, and other packet documents submitted through MCP are stored directly on the Salesforce carrier record. Therefore, teams can access them without leaving FTM or logging into MCP separately.

Field labels and document types shown are illustrative. Actual data depends on what the carrier submitted in their MCP packet and your configured integration.

Why packet-driven carrier data works

Carriers Who Complete A Packet Enter Their Own Data. Your Team Stops Re-entering It.

Manual carrier setup requires someone on your team to collect, verify, and enter carrier data from emails, PDFs, and phone calls. Instead, the MCP integration moves that work to the carrier: they complete the packet, and FTM takes what they submitted.

Carrier data entered once by the carrier
The carrier fills out the MCP packet. Then, FTM reads what they submitted. No one re-enters insurance limits, contact details, or tax information from an email or PDF.
Documents stored with the carrier record
Insurance certificates, W9s, and agreements submitted through the packet are stored on the Salesforce carrier record. As a result, documents are accessible inside FTM without a separate file system.
MCP risk and blocked status in FTM
Meanwhile, MCP compliance status, including risk flag and blocked status, flows into the FTM carrier record so dispatch teams can see compliance status without checking MCP separately.
On-demand sync when needed
The Sync Carrier Data action lets teams refresh a carrier’s MCP data on demand from inside the FTM carrier record, without waiting for a new packet submission or system event.
Before and after

What Changes When MCP Carrier Packets Connect To FTM

Without the MCP integration, carrier onboarding requires your team to collect and enter carrier data manually. With it, however, the carrier’s completed packet drives the FTM record.

Without MCP connected to FTM
Carrier sends insurance certificate by email
Team enters carrier data manually into FTM
W9 and factoring details collected separately
Documents stored outside the TMS
MCP compliance status not visible in FTM
With MCP connected to FTM
Carrier completes MCP packet with their own data
FTM creates or updates carrier record from packet
W9 and factoring data included in the record
Documents stored on the Salesforce carrier record
MCP risk and blocked status visible in FTM
Carrier onboarding connection

MCP Packets And FTM Carrier Onboarding Work Together

The MCP integration supplies the carrier data. Meanwhile, FTM Carrier Onboarding manages the qualification workflow around it. When a carrier completes their MCP packet, the data that flows into FTM becomes part of the onboarding record that your team reviews and approves before the carrier is dispatched.

From Intellivite invitation to active carrier
One invitation. One packet. One carrier record ready for review.
First, send the Intellivite invitation from FTM. Then, the carrier completes their MCP packet. Next, their data and documents arrive in the FTM carrier record automatically. Finally, your team reviews and approves the carrier for dispatch.
Explore Carrier Onboarding
Intellivite Invitation Sent
Carrier Completes MCP Packet
Data and Documents Flow to FTM
Team Reviews and Approves in FTM
Carrier Available for Dispatch
Business outcomes

What Changes When MCP Packets Drive FTM Carrier Records

Carrier data entered once, not twice
The carrier fills out their MCP packet. Then, that data flows into FTM. As a result, your team does not re-enter insurance limits, contact details, factoring information, or tax data from the same document.
Documents accessible inside FTM
Insurance certificates, W9s, and agreements from the carrier packet are stored on the Salesforce carrier record. Therefore, teams can access compliance documents without switching to a separate system.
MCP compliance status visible during carrier decisions
MCP risk flag and blocked status are on the FTM carrier record. As a result, dispatch teams see compliance status during carrier selection without logging into MCP separately.
On-demand refresh without new packet submission
The Sync Carrier Data action refreshes available MCP data on demand from inside the FTM carrier record. Therefore, teams do not need to wait for the carrier to resubmit a packet to get updated information.
New carriers ready for dispatch faster
Carriers who complete their MCP packet arrive in FTM with their data already populated. The onboarding review step becomes lighter because the data entry step happened on the carrier’s side.
Factoring and remit-to information from the packet
Factoring company, NOA, and remit-to address submitted through the MCP packet are available on the FTM carrier record, reducing the back-and-forth needed to set up carrier payment details.
Related capabilities

Related FTM Capabilities

SaferWatch
RMIS
Carrier Onboarding
Highway
MCP Integration FAQ

Questions about MyCarrierPortal and FTM carrier onboarding.

For questions specific to your MCP configuration, a specialist can walk through your setup.

Talk to a Specialist
When a carrier completes their MCP onboarding packet, the MyCarrierPortal TMS integration attempts to match the carrier to an existing record using the DOT or MC number. If a match is found, the existing FTM carrier record is updated with available packet data. Otherwise, a new carrier record is created. In addition, available documents from the packet are stored on the Salesforce carrier record.
Intellivite is MCP’s carrier invitation feature. From inside FTM, you can send an Intellivite invitation to a carrier, which prompts them to complete their onboarding packet in MyCarrierPortal. Then, when they finish, the packet data flows back into FTM automatically.
Yes. The Sync Carrier Data action inside the FTM carrier record allows teams to pull the latest available MCP data on demand. As a result, you can refresh carrier information without asking the carrier to resubmit their packet. However, the specific data that updates depends on what MCP has on file and your configured integration.
MCP is a carrier onboarding platform where carriers actively complete a packet with their own information. The integration is driven by packet completion and on-demand sync. SaferWatch is a compliance lookup that returns FMCSA authority, insurance, and safety data for a specific MC or DOT number. RMIS is a carrier management platform that syncs approved carrier master data on a configured schedule. All three can be used alongside each other in FTM.
Overwrite behavior is configurable. Therefore, the integration can be set up to control which fields are updated from MCP data and which fields are preserved when an existing carrier record is matched. A specialist can walk through the overwrite configuration options for your setup.
No. Organizations can deploy FTM inside an existing Salesforce environment or launch with Salesforce provisioned as part of implementation. Existing Salesforce licenses are not required before engaging with FTM.
Core FTM workflows can typically go live in approximately 14 days. MCP integration configuration depends on your existing MCP account setup and your carrier onboarding workflow requirements.
Carrier onboarding and packet synchronization

See A Completed MCP Packet Arrive In FTM Without Re-entry

Tell us how many carriers you onboard each month and how long the current process takes. We will show how an Intellivite invitation and completed MCP packet create an FTM carrier record ready for your team’s review, with documents included.

Book Executive Demo Explore Carrier Onboarding
Core FTM workflows can typically go live in approximately 14 days. MCP integration configuration depends on your existing account setup and carrier onboarding workflow.
Let's Talk!

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

Watch 3-Min Demo
↑