Skip to content
Home » HelloSign

HelloSign

HelloSign is now Dropbox Sign

HelloSign Integration for Freight Documents in FTM

The FTM HelloSign integration, now Dropbox Sign, lets teams send e-signature requests from Load, Carrier, and Lane Quote records in Salesforce. Then, when the recipient signs, the completed document returns to the originating FTM record automatically. As a result, teams avoid downloading the signed file and uploading it back to Salesforce.

Book Executive Demo Explore FTM Platform
From an FTM record to a signed document
FTM Record
Load, Carrier, or Lane Quote in Salesforce
Click Use Dropbox Sign
Select template and recipient
Dropbox Sign Sends to Recipient
Document delivered for signature
Recipient Signs
Via email link, no account required
Signed Document Attached to Record
Filed automatically in Salesforce
3 records
Load, Carrier, and Lane Quote
4.9
AppExchange rating
110+
AppExchange reviews
Salesforce
Native platform
E-signatures across FTM records

What does the HelloSign integration do in FTM?

The Dropbox Sign integration is available on three FTM records: Load, Carrier, and Lane Quote. Therefore, dispatchers, account managers, and compliance teams can begin a signature request from the Salesforce record where they already work.

Load Record
Load confirmations and related documents
Carrier Record
Carrier agreements and contracts
Lane Quote Record
Quote documents and confirmations
Signed documents return to the originating record
After the recipient completes signing, Dropbox Sign returns the completed document to FTM. Then, FTM attaches it to the Load, Carrier, or Lane Quote record where the request began, so no manual download and re-upload is required.
Two platforms, one workflow

How do Dropbox Sign and FTM divide the workflow?

FTM stores the load, carrier, and quoting data. Meanwhile, Dropbox Sign manages document delivery and the recipient signing experience. Therefore, the integration can begin from the Salesforce record and return the signed document to that same record.

Dropbox Sign Handles
Document delivery to the recipient by email
E-signature capture from the recipient
Document templates and signing experience
Signing status tracking within Dropbox Sign
Returning the completed document when signed
FTM Does
Presents the Use Dropbox Sign button on the record layout
Passes record context for template and recipient selection
Receives and attaches the signed document to the record
Keeps signed documents filed with load, carrier, and quote data
Supports optional field mapping into document templates
End-to-end signing workflow

How the HelloSign integration works in five steps

The FTM user begins the request from Salesforce. Next, Dropbox Sign delivers the selected document and manages the recipient signing experience. Finally, FTM attaches the completed file to the originating record automatically.

01
Open the FTM record
First, open a Load, Carrier, or Lane Quote in Salesforce.
02
Choose the request
Next, select Use Dropbox Sign, the template, and the recipient.
03
Dropbox Sign sends it
Then, Dropbox Sign emails the document to the recipient.
04
The recipient signs
Afterward, the recipient reviews and signs without creating an account.
05
The signed file returns
Finally, FTM attaches the completed file to the originating record.
Templates are created and managed in your Dropbox Sign account. In addition, Dropbox confirms that recipients can sign without creating an account in its official signer guidance. An appropriate Dropbox Sign account and FTM configuration are required.
Signed documents in Salesforce

Where does the signed document appear in FTM?

Once a recipient completes signing, the completed document returns to the FTM record where the request began. Therefore, operations, account management, and compliance teams can access the signed file beside the related load, carrier, or quote data.

FTM Load Record
Document Signed
Load information
Load Number
FTM-2026-09112
Carrier
Summit Freight Solutions
Origin
Chicago, IL
Destination
Nashville, TN
Document signing
Document
Load Confirmation
Sent To
[email protected]
Status
Signed
Signed Document
Attached to Record
Use Dropbox Sign
Record Attachments
Load_Confirmation_Signed.pdf
Returned by Dropbox Sign
Signed
Carrier_Agreement_Signed.pdf
Returned by Dropbox Sign
Signed
Rate_Confirmation.pdf
Sent for signature
Pending
Signed documents stay with the load data
Completed documents from Dropbox Sign attach to the FTM record automatically. As a result, the signed file remains available beside the load, carrier, and dispatch information without a separate download and upload process.

Field labels and document names shown are illustrative. Actual fields and file names depend on your Dropbox Sign templates and FTM configuration.

Why in-record e-signatures matter for freight

Why connect e-signatures to freight records?

When signature requests leave the TMS, completed documents can end up in email threads, shared drives, or team folders. Therefore, the Dropbox Sign integration returns the signed file to Salesforce and keeps it attached to the FTM record where the request began.

Start from the FTM record
First, dispatchers and account managers begin the request from the Load, Carrier, or Lane Quote record where they already work.
Return signed documents automatically
Next, when signing is complete, the document returns to FTM and attaches to the originating record automatically.
Use one workflow across three records
In addition, the same integration supports signature requests from Load, Carrier, and Lane Quote records.
Keep freight context attached
As a result, signed agreements and confirmations remain beside the related load, carrier, and rate information in Salesforce.
Before and after

Before and after connecting Dropbox Sign to FTM

Without the integration, teams may manage signature requests and completed files separately from the freight record. By contrast, the connected workflow begins in FTM, moves through the Dropbox Sign recipient experience, and returns the completed file to Salesforce.

Without Dropbox Sign connected to FTM
Document sent from outside the TMS via separate e-sign tool
Signed document returned to email or external folder
Manual download and upload needed to attach it to FTM
Signed documents disconnected from load and carrier records
Document status checked in a separate platform
With Dropbox Sign connected to FTM
Signature request started from the FTM record
Signed document returned and attached automatically
No manual filing needed after signing completes
Signed documents accessible from the load or carrier record in FTM
Business outcomes

What changes after Dropbox Sign connects to FTM?

Start requests from supported records
First, the Use Dropbox Sign button lets users begin from a Load, Carrier, or Lane Quote record in FTM.
Return signed files automatically
Next, when signing is complete, the document returns and attaches to the originating FTM record automatically.
Keep documents with freight data
Finally, operations and compliance teams can find signed files beside the related load, carrier, and quoting data in Salesforce.
Related capabilities

Related FTM capabilities

Workflows
AutoFill
Carrier Onboarding
Documents
Dropbox Sign FAQ

Questions about the HelloSign integration in FTM

For setup questions or account configuration, the FTM team can help.

Talk to a Specialist
The HelloSign integration in FTM now uses the Dropbox Sign name. It lets users send documents for e-signature from Load, Carrier, and Lane Quote records in Salesforce. Then, when the recipient signs, the completed document returns to the originating FTM record automatically. The page URL remains /integrations/hellosign/ for continuity.
The Use Dropbox Sign button is available on the Load object, the Carrier object, and the Lane Quote object. It is added to the page layout for each object during setup. Other Salesforce objects in your org are not included in the current FTM integration.
After signing is complete, Dropbox Sign returns the document to FTM and attaches it to the record where the request began. For example, a request sent from a Load record returns to that Load record’s file attachments. Therefore, no manual download and re-upload is required.
No. Dropbox Sign emails the document to the recipient, who can review and sign it without creating an account. Therefore, carriers, customers, partners, and other recipients can complete the request through the Dropbox Sign interface.
Optionally, yes. FTM supports field mapping that can pull data from the Salesforce record into your Dropbox Sign document templates. This can include information such as agent name, carrier payment fields, or insurance details. The templates themselves are created and managed in your Dropbox Sign account. Contact the FTM team for guidance on setting up field mapping for your specific documents.
An appropriate Dropbox Sign account and FTM configuration are required. The FTM team handles the Salesforce configuration and will confirm what is needed based on your setup. Contact the FTM team to begin.
Yes. Dropbox Sign was formerly known as HelloSign. Therefore, the FTM page keeps the /integrations/hellosign/ path for continuity. Existing users can contact the FTM team to confirm the current configuration for their environment.
E-signatures for transportation documents

See the Dropbox Sign workflow on an FTM record

Tell us which transportation documents your team sends for signature today. Then, we will demonstrate how the Dropbox Sign request begins in Salesforce and how the signed file returns to the originating FTM record.

Book Executive Demo Explore FTM Platform
Requires an appropriate Dropbox Sign account and FTM configuration. Contact the FTM team for details.
Let's Talk!

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

Watch 3-Min Demo
↑