Enabling MyCarrier Packets in Integration hub

Note: When RMIS is enabled in the Integration hub, MCP requires a support ticket to enable. 

1. Log into your Turvo tenant. 
   
   
2. Navigate to the Admin console via the Profile icon at the top right corner of the screen.
   
   
   
   
3. Click the Integration hub tile.
   
   
   
   
4. Scroll down to the Carrier tools integrations section of the Available Integrations tab and click the My Carrier Packets tile.
   
   
   
   
5. On the Integrate tab, enter the following credentials obtained from MyCarrier Packets as described in the prerequisites section of this article:
   • Username
   • Password
6. After the credentials are entered, the CONNECT button at the bottom corner of the screen changes from blue to grey. Click CONNECT to establish the connection. 
   
   
   

Set up Payment and Terms mapping

Note: If you do not want 'Payment and terms mapping' to sync from MyCarrier packets, skip this step and complete the setup process. Indicate No in Step 2 of the Post Setup Support Ticket step below. 

To map Payment and terms from MyCarrier Packets: 

1. Toggle ON the desired terms.
2. Copy and paste the exact payment text that you received from MyCarrier Packets in the corresponding payment terms field.
3. Click SAVE.

When you complete and save all enablement configurations , click COMPLETE SETUP at the bottom right of the screen to finish establishing the MyCarrier Packets connection. 

Post Setup Support Ticket

Once you have completed MCP setup in Integration hub, open a Turvo Support ticket and include the details listed below:

• Copy and paste this text: We have enabled MyCarrier Packets using Integration hub in the Turvo UI. We need you to complete the necessary steps to sync carrier accounts created via Turvo UI/Public API
• Payment methods and terms mapping sync from MCP to Turvo: Indicate Yes or No

MyCarrier Packets status in Turvo

Important Note: A prerequisite for any information to be ingested into Turvo is the MCP Carrier Agreement. If the Carrier Agreement is not present then Turvo will not update the status or other info.

To view the status of the carrier that got synced from MyCarrier Packets in Turvo, navigate to the carrier Details tab and then click General > Status.

The status will map to Turvo as either Active or Inactive. This Relates to the DOT Status of Active or Inactive in MCP. As long as the Carrier Agreement is available, the status will map as follows. If the Carrier Agreement is not available, the update from MCP is disregarded.

• Active: The entity’s US DOT number is active.
• Inactive:
  • OUT-OF-SERVICE: Carrier is under any type of out-of-service order and is not authorized to operate.
  • Inactive USDOT Number: Inactive per 49 CFR 390.19(b)(4); The biennial update of MCS-150 data has not been completed.
  • NOT AUTHORIZED: The entity’s USDOT number is active. However, the carrier does not have any operating authority and is not authorized to operate as an interstate, for-hire carrier.

How the MyCarrier Packet integration works

Once your tenant is configured with MyCarrier Packets, the workflow works as follows:

1. In MyCarrier Packets, send the intellivite to your carrier so they can register and submit their information.
   
   
2. After the carrier completes the packet, the information provided by the carrier will then be sent to your Turvo tenant. Information syncs from MyCarrier Packets and Turvo every 5 minutes.
   
   Carrier information is mapped from MyCarrier Packets to Turvo based on their DOT. If the carrier already exists in your tenant, Turvo will update the carrier’s profile with any new information provided in the completed packet. 

Important notes:

• Data received from MyCarrier Packets will overwrite any manual changes that have been entered into Turvo.
• For 1099 carriers, Turvo pulls Tax ID (TIN) information from MCP.

MyCarrier Packets carrier fields ingested into Turvo

The following table contains the fields that are mapped from MyCarrier Packets (MCP) into Turvo. Any fields not presented in this table are currently not mapped via the integration and require you to enter them into Turvo manually. 

Note: We attached a PDF version of the MyCarrier Packets carrier fields ingested into Turvo table. You can find this download at the bottom of the article, just below the table.

Important notes:

• Various carrier profiles in MyCarrier Packets may have different fields completed. If you find a field is not mapping in Turvo, it's likely it is not present or completed in MyCarrier Packets.
• Equipment size will always map to Turvo as Other because the field is not available in MyCarrier Packets.
• The following information is not available in MyCarrier Packets and cannot be mapped to Turvo:
  
  • ARB
  • Exceptions contact
  • Offers contact
  • Claims address
  • Mode service type
• Lanes are not mapped from MyCarrier Packets into Turvo.
• There are no documents stored in the Carrier profile such as the insurance cert pdf.
• Dispatcher information is not pulled into Turvo from MyCarrier Packets, even if it is available.
• If the carrier does not have an SCAC, leave the field blank. Entering filler text like "XXXX" or
  "- - - -" results in Turvo identifying the SCAC as a duplicate and the carrier is not ingested.
• There is an available configuration to block the ingestion of payment methods and terms into Turvo from MCP. Contact your Turvo representative to enable this configuration.