Understanding Deals Pipeline

The deals pipeline in BoldSales provides a structured way to manage each stage of a sales opportunity, from initial qualification to final closure. By customizing stages, arranging them in the right order, and configuring key fields, teams can work with greater accuracy and consistency. With clear stages, flexible rules, and mapped processes, the pipeline improves visibility, supports organized workflows, and helps teams track and advance opportunities more efficiently.

Accessing pipelines

1. Go to Setup from the left sidebar menu.
2. Scroll to the Modules and Fields section and select Pipelines.
   
3. Alternatively, go to Pipelines from the left sidebar. Click Manage pipelines in the Business Process Pipelines menu.

Deal configurations

1. Under Manage Pipelines, locate the Configurations tab if it is not opened by default.
2. To edit a deal pipeline’s configurations, click Edit next to the field, update, and save.
   

The fields are as below:

Pipeline name

The main name for the deals pipeline represents its overall purpose. It is commonly used as a reference within the system.

Single record name

This name refers to a single record within this pipeline, such as when creating a new deal record. For instance, it will appear on the record create button (for example, ‘+ Deal’). If a unique singular name is not required, you can use the same name as the pipeline name.

Multiple records name

This name represents multiple records within the pipeline and is used in controls such as menus, dropdowns, and view lists for selecting pipelines. For example, if the name is ‘Deals,’ it will appear as ‘Deals’ in the pipeline selection menu and as ‘All Deals’ in views and headings. If a unique plural name is not needed, you can use the pipeline name instead.

Description

A short summary of the deal. A maximum of 30 characters is allowed.

Pipeline purpose

Defines the main goal of the deal (for example, Deal tracking) and determines which features are available in the pipeline. This value cannot be changed later.

The Products option enables product-related features so users can add products as line items in the Products tab.

The Use this pipeline as contract for next renewal option allows the pipeline to act as the contract for the next renewal. When this option is turned off, renewals can be managed through a separate contracts pipeline. After the pipeline is created, you can map processes such as contracts, renewals, and orders to the deals pipeline from the Process Mapping tab.

Note:

• This section cannot be edited.
• All fields marked with an asterisk must be filled.

Sales documents

Select the sales document types (such as quotes and invoices) that users can generate within this pipeline.

Quote is checked by default and cannot be unchecked, as it is a mandatory sales document type for a Deal tracking pipeline.

Permission sets

Choose who can access and manage the pipeline. Admin is checked by default. Add system or custom permission sets as needed.

Admin cannot be unchecked, and they have access to every module within BoldSales.

Show summary

Select this option to display a summary widget on the listing page, showing metrics such as open and closed records along with their total values. The widget appears only if the Amount field is included in the pipeline.

Customizing stages

Stages define the steps a record passes through in your pipeline. Under Manage Pipelines, go to the Stages tab and click Manage Stages.

Open stages

Open stages list the active steps a record moves through before it reaches a closed state. Each stage appears as an editable text field, and you can modify the stage names directly. You can add more open stages using the Add stage option.

At least one open stage must be present. If you add a new stage and leave it empty, the system will show a validation message indicating that the field is required. You can remove any stage using the delete icon next to it, as long as the minimum requirement of having at least one stage is maintained.

Closed stages

Closed stages represent the final outcomes of a record. You can add closed stages using the Add closed stage option. Each closed stage includes a dropdown where you select whether the stage is marked as Won or Lost. The deal must have at least one closed-won stage. You can rename or remove closed stages as needed, except where minimum requirements apply.

Reordering stages

Both open and closed stages can be reordered using the Reorder option. This allows you to drag and drop stages into the sequence that best matches your workflow.

Once all the customizations are done, click Update to apply the changes to the pipeline.

Process mapping

Overview

The Process Mapping section allows you to connect the deals pipeline with related business processes such as contracts, renewals, and orders. By defining how records across multiple pipelines relate to one another, Process Mapping ensures that all deal-related activities remain connected throughout the customer lifecycle.

Benefits

Process Mapping is optional, but configuring it provides significant benefits:

Improved visibility within the deal record

Enabling process mapping activates contextual widgets inside the deal record. These widgets allow you to:

• Quickly create related records
• Access associated contracts, orders, or renewals
• Manage relationships without navigating away

This reduces manual linking and improves workflow efficiency.

Access to related history

Users can view important histories such as renewal cycles within the same deal record, ensuring continuity and a better understanding of customer progression.

Structured cross-pipeline relationships

Process Mapping defines how records across pipelines connect. This maintains a consistent flow of information between:

• Deals
• Contracts
• Orders
• Renewals

These relationships ensure that each stage of the customer journey remains logically connected as records move through different business processes.

Relationship labels

The Process Mapping section also allows configuration of default relationship labels. These labels describe how records are connected when linked across pipelines.

For more details on relationship labels, refer to Introduction to relationship labels.

Customizing fields

Fields help capture important information for each record in a deal. Some fields (such as Name and Stage) are system-included and cannot be modified.

From the Fields tab, you can perform the following:

• You can reorder fields by clicking more actions (three dots) next to each field.
• In the Form settings column, choose Show in create form to display the field in the create form and further choose Make this field required to make this field mandatory.
• In the Dynamic field behavior column, click Add to add a Controlling field or Conditional logic to a field.

Note: For more details on dynamic field behavior, refer to Understanding controlling fields (Field dependencies) and Understanding conditional logic.

For the fields with Included in create form set, the Add dropdown in the Dynamic field behavior will be disabled.

Click Manage Field Dependencies to add or remove dependencies.

Note: For more details on managing field dependencies, refer to Understanding controlling fields (Field dependencies).

Click Add Field to open the Add Existing Fields drawer to add a new custom field or include existing ones. To create new fields, click + Create field in the Add Existing Fields drawer, then fill in the required fields as provided.

Pipeline rules

The Pipeline Rules section lets you define how records, tasks, and documents behave within your pipeline. These rules control document generation, stage transitions, and how associations are managed. By setting these rules, you ensure consistent actions, clear workflows, and a structured, compliant process as deals move through the pipeline.

For more details on pipeline rules, refer to Introduction to pipeline rules and Creating and Managing pipeline rules.