Creating and Sending a Contract Sales Document
Contract sales documents in BoldSales are used to formally document and enforce agreements made with customers. These documents capture critical business terms such as conditions, durations, approvals, and signing requirements, helping teams manage contractual commitments in a structured and reliable way.
This article guides you through the process of creating, sending, and tracking contract sales documents in BoldSales.
Before creating a contract sales document, ensure the contract template has already been created and published.
For more details, refer to Creating and managing templates for sales documents.
Note for non admin users: If you do not have access to create sales documents or to access a specific pipeline record, contact your BoldSales administrator.
Note for administrators: For managing permissions in the Sales Documents module, refer to Understanding permissions in the Sales Documents module. For managing permissions in the Pipelines module, refer to Understanding permissions in pipelines module.
Accessing the Pipeline Record
To create and send a contract, first access the relevant pipeline record. The record must belong to the pipeline for which the contract template is configured.
To access the pipeline record:
- Go to the Pipelines module from the left sidebar.
- Select the pipeline configured for contract documents.
- From the listing page, open the required record’s details page.
Creating a Contract Document
- Navigate to the
tab from the record’s details page.
- Select Contract and click
.
- Choose a published contract template from the left pane.
- Click
from the contract page.
The contract document is generated based on the selected template and pipeline record data.
Updating contract fields
Reviewing and updating contract fields before sending ensures that all information is are accurate and up to date.
-
Click Edit Fields. This opens the Contract Details drawer.
-
Update document fields such as:
- Document name
- Document owner
- Primary contact
- Expiry date
- Status
-
Go to the Signature Fields tab under Contract Details, assign signers for user and contact signature fields.
-
Customize contract fields by clicking
to add, remove, or modify fields based on business requirements. For more information on customizing fields, refer to Customizing Sales Document fields.
-
Click
.
Sending the Contract
Before sending a contract, review all details for accuracy. Contracts are typically sent for eSignature, as they include approval and signing workflows.
Sending a contract for eSignature
- Click
in the top right corner.
- The Send via BoldSign drawer opens.
- The To field is automatically populated with the recipient’s information.
- Optionally:
- Add recipients in the Cc field
- Add a message in the Message field
- Insert a predefined email template by clicking Insert template
-
Click Attachments to include any supporting documents.
-
Click
to finalize.
For more details on eSignature, refer to Configuring eSignature.
Tracking Contract Status
When the customer approval workflow is enabled, contract statuses are updated automatically based on recipient actions. This allows teams to track progress without manual follow-ups.
Tracking contract status from a pipeline record
- Open the pipeline record’s details page.
- Navigate to the
tab.
- Select Contracts.
- Locate the sent contract and review its progress in the Status column.
- Click the actions menu (three dots) and select Activity timeline to view a detailed history of events such as creation, sending, viewing, signing, and completion.
Tracking contract status from the Sales Documents module
- From the left sidebar, go to Sales Documents.
- Select Contracts from the menu.
- Locate the contract on the listing page.
- Check the current status in the Status column.
- Open the
from the actions menu to view the complete interaction history.
Important Notes
- Contracts cannot be sent if Enable customer approval workflow is disabled in the contract form. For more information on customer approval, refer to Creating Custom Document Types.
- Documents without required signature fields cannot be sent for eSignature.
- Template configuration determines signing order, required fields, and approval flow.