Understanding SalesExec Sales Workflow: Key Terms and Definitions

Sales workflows are a core component of SalesExec Lead Management Software. They define how leads progress through your sales process, which actions sales representatives can take, and how the system responds to different activities.

Understanding workflow terminology is important when configuring lead management processes, automating follow-up, establishing distribution rules, and troubleshooting unexpected behavior.

This guide explains the key concepts used throughout SalesExec so administrators and sales managers can build more consistent, efficient, and predictable workflows.

SalesExec uses several connected components to manage the lifecycle of a lead.

At a high level:

Understanding how these components interact is essential to configuring SalesExec effectively.

A Workflow is a collection of related lead statuses that represent a broader stage or process within your sales operation.

Workflows help organize leads according to their current position in the sales lifecycle.

Example:

An Attempting Contact workflow might contain several statuses representing different stages of outreach:

Grouping related statuses into workflows helps managers organize lead activity and provides representatives with a structured process for working opportunities.

A Status represents a specific milestone or condition within a workflow.

Statuses indicate where a lead currently stands and help determine which activities should occur next.

Examples:

A lead's status can change as representatives complete actions or as configured automation updates the record.

Why it matters: Statuses help sales managers understand pipeline progress, identify leads requiring attention, and organize reporting.

A System Status is a system-level classification assigned to a lead status.

While administrators can create statuses that reflect their organization's terminology, System Statuses provide standardized classifications that SalesExec can use for certain built-in functionality.

These classifications can be important when configuring lead distribution strategies.

Example:

An organization may have several custom statuses associated with contacting prospects. System Status classifications enable SalesExec to identify milestones for relevant system processes.

Why it matters: Incorrect System Status configuration can affect how leads qualify for certain distribution strategies and other system functionality.

Pipeline % to Sale represents the estimated probability that a lead in a particular status will result in a sale.

Administrators can assign a percentage to a status to reflect its position in the sales process.

Example:

These percentages are illustrative. Organizations should define values that reflect their own sales process.

Pipeline percentages are used with SalesExec's product and pipeline functionality to help represent the estimated likelihood of closing an opportunity.

Why it matters: Pipeline percentages provide a consistent way to express sales progression and potential outcomes.

Max Allowed Assignment Time determines how long a lead can remain assigned to a representative in a particular status before it becomes eligible to be pulled by another representative.

This setting applies when Enable Pull From Other Agents is enabled in System Settings.

Example:

A lead remains assigned to a salesperson in a follow-up status. If the configured maximum assignment time expires, the lead may become eligible for another authorized representative to retrieve through Pull distribution.

Why it matters: This setting helps organizations prevent leads from being tied to a single representative indefinitely, so they are available for additional outreach.

Learn more about SalesExec Pull-Based Lead Management.

An Action Category organizes related actions that sales representatives can select while working a lead.

Categories make the available actions easier to navigate and help standardize how representatives record their activities.

Example:

An action category named Contact Attempt might contain:

Another category named Sales Outcome might contain:

Why it matters: Well-organized action categories help representatives select the appropriate dispositions and maintain more consistent activity records.

An Action is a disposition or activity that records what happened while working a lead and can control what happens next.

Actions are central to SalesExec workflow automation.

Depending on configuration, an action can:

Example:

A representative calls a prospect and selects No Answer.

The configured action may update the lead's status or schedule a future callback.

Alternatively, selecting Appointment Set may move the lead to an appointment-related status.

Why it matters: Actions help connect salesperson activity to the next step in the sales process.

For more information, see Sales Workflow: Configuring Actions.

An Automated Event is a configured automation that performs actions when its trigger and criteria requirements are satisfied.

Automated events reduce the need for representatives or administrators to perform repetitive tasks manually.

Two common types include:

New Lead Events

Evaluated when a new lead is created.

Example: A newly created lead meets configured conditions, causing the system to perform an automated action.

Action-Based Events

Evaluated when a specified action occurs on a lead.

Example: A representative selects a particular disposition, causing an automated event to evaluate whether additional actions should run.

Why it matters: Automated events help organizations apply consistent processes without relying on manual intervention for every step.

A Trigger defines when SalesExec evaluates an automated event.

Triggers are events that initiate the automation process.

Examples:

A trigger does not necessarily mean that every associated automated action will execute. The lead may also need to satisfy configured criteria.

Why it matters: Understanding triggers helps administrators identify when automation should run and troubleshoot events that are not executing as expected.

Criteria are the conditions a lead must satisfy for a configured automation or routing rule to apply.

Criteria allow administrators to target specific leads rather than applying the same behavior to every record.

Depending on the configuration, criteria may evaluate:

Example:

An automated event is configured to evaluate new leads.

Its criteria require the lead to be met, those actions that are not executed originate from a particular marketing source.

When a new lead is created, SalesExec evaluates the event. If the lead meets the configured criteria, the associated actions can execute.

If the criteria are not satisfied, those actions do not execute.

Why it matters: Criteria help administrators create targeted automation and avoid applying actions to leads that do not qualify.

Consider a home services company that wants to manage new inbound sales inquiries.

A possible configuration might look like this:

In this example, the workflow and status identify where the lead belongs in the sales process.

The action category and action determine how the representative records a contact attempt.

The automated event uses its trigger and criteria to determine whether additional configured activities should execute.

These components work together to establish a repeatable lead management process.

Create workflows that represent meaningful stages of your sales process.

Avoid creating unnecessary workflows or statuses that make navigation and reporting difficult.

Choose clear names for workflows, statuses, categories, and actions.

For example, use consistent terminology throughout your configuration, such as Attempting Contact, Appointment Set, and Sold.

Review System Status assignments when creating or modifying statuses, particularly when those classifications affect lead distribution.

Representatives should be able to identify the correct action without guessing.

Organize actions into logical categories and use names that describe the actual outcome.

When configuring automation, confirm both when an event should be evaluated and which leads should qualify.

Multiple automated events with similar triggers and criteria may produce unexpected results.

Review related configurations before enabling new automation.

Maintain internal documentation describing important workflows, statuses, actions, and automated events.

This makes future troubleshooting and administrator onboarding easier.

When troubleshooting, identify the specific lead, its current workflow and status, the action performed, and any automation expected to run.

Providing this information to ClickPoint Support can help isolate configuration issues more efficiently.

A Workflow groups related stages of the sales process. A Status identifies a specific milestone or condition within that workflow.

A Status is a configurable sales milestone. A System Status provides a standardized classification used by certain SalesExec features, including lead distribution.

An Action records an activity or disposition and may perform configured workflow behavior. An Automated Event evaluates a trigger and criteria to determine whether automated actions should execute.

An automated event is evaluated when its configured trigger occurs. Its actions execute when the applicable criteria are satisfied.

Common causes include incorrect triggers, criteria that do not match the lead, or conflicting workflow configurations.

When the applicable Pull setting is enabled, Max Allowed Assignment Time determines how long a lead can remain assigned in a status before becoming eligible to be pulled by another representative.

Yes. Configured actions can move leads between workflows and statuses as part of the organization's sales process.