How Waterfall Lead Distribution Works in LeadExec

Overview

LeadExec is designed to automate the process of qualifying, routing, and delivering leads to Clients based on the distribution rules and requirements configured within the platform.

When a lead enters LeadExec, the system can evaluate which Clients are eligible to receive it, determine how those opportunities should be prioritized, attempt delivery, evaluate the result, and continue processing the lead when an earlier opportunity cannot be completed.

This type of behavior is sometimes described in the lead generation industry as waterfall lead distribution.

In LeadExec, waterfall distribution is not a separate setting or routing mode that users enable. Instead, the term describes how LeadExec's qualification, routing, delivery, and response-handling capabilities can work together to continue evaluating eligible distribution opportunities.

Depending on the account configuration, LeadExec distribution can take into consideration factors including:

Together, these capabilities allow LeadExec to determine which Clients are eligible, which opportunities should be attempted, and what should happen when a particular delivery opportunity cannot be completed.

For a broader look at the platform, see LeadExec Lead Distribution Software Platform Overview.

For additional routing concepts and configuration options, see Advanced Lead Routing in LeadExec.

How the LeadExec Distribution Process Works

Lead distribution begins when a lead enters LeadExec through its configured Lead Source and Campaign.

From there, LeadExec evaluates the lead against the applicable distribution configuration to determine which Client opportunities qualify.

A typical distribution process may look like:

Lead Received → Validate Lead → Identify Eligible Clients → Prioritize Opportunities → Attempt Delivery → Evaluate Response → Continue to Another Eligible Opportunity if Necessary

If the first Client successfully receives and accepts the lead, LeadExec can complete distribution according to the Campaign's configured rules.

If that opportunity cannot be completed, the system can evaluate the result and determine whether another eligible Client should be attempted.

The exact path a lead takes depends on the routing, qualification, delivery, and response settings configured for the account.

Understanding Waterfall Lead Distribution

Waterfall lead distribution generally describes a process in which multiple eligible delivery opportunities are evaluated until a lead is successfully delivered or the available distribution opportunities are exhausted.

This does not mean that LeadExec simply sends every lead to every Client.

Before delivery occurs, LeadExec evaluates Client eligibility based on the account's configured requirements. Only qualifying opportunities participate in the applicable distribution process.

If an attempted Client cannot accept or successfully receive the lead, LeadExec can proceed to another eligible opportunity when the configuration allows distribution.

This helps prevent an unsuccessful first delivery attempt from automatically ending the distribution process when other qualified opportunities remain available.

How LeadExec Determines Eligible Clients

Before deciding where to deliver a lead, LeadExec evaluates which Clients qualify for it.

Client qualification can include criteria such as:

Only Clients that meet the applicable requirements are considered for distribution.

By identifying eligible Clients before delivery, LeadExec can avoid attempting destinations that do not meet the requirements for a particular lead.

For more information about the standard Client distribution configuration, see Client Settings – Distribution.

How LeadExec Prioritizes Distribution Opportunities

When multiple Clients qualify for the same lead, the configured distribution strategy helps determine how those opportunities are evaluated.

LeadExec supports distribution capabilities that can account for factors including:

The distribution strategy used by an organization determines which eligible opportunities are attempted and how the system proceeds through the available Client pool.

As a result, LeadExec distribution should not be thought of as a single fixed sequence. Different Lead Types, Campaigns, and Client configurations can produce different routing behavior.

What Happens When a Client Cannot Accept a Lead?

An unsuccessful Client opportunity does not necessarily mean that distribution must end.

Depending on the Campaign, Client, Delivery Method, and response configuration, LeadExec can evaluate the delivery attempt's result and continue processing the lead for other eligible opportunities.

Conditions that can affect continued distribution include:

This response-driven behavior is an important part of automated lead distribution because Client availability can change from one lead to the next.

A Client who qualifies under the original lead criteria may still be unable to complete the transaction when delivery is attempted.

LeadExec can use the resulting delivery information to determine how the lead should continue through the configured distribution workflow.

Example: How LeadExec Can Continue Distribution

Consider a home-services lead with three eligible Clients:

Client A — $75
​Client B — $65
​Client C — $50

Assume that all three Clients meet the initial qualification requirements for the lead and that the configured distribution strategy evaluates the highest-priced opportunity first.

Client A

Price: $75

Client A qualifies for the lead, so LeadExec attempts delivery.

However, Client A's delivery endpoint returns a rejection.

Based on the configured response handling, LeadExec determines that distribution can continue.

Client B

Price: $65

Client B is the next eligible opportunity.

During the applicable delivery process, Client B indicates that it does not cover the consumer's location.

LeadExec can evaluate that response and continue to another qualified opportunity.

Client C

Price: $50

Client C qualifies for the lead, covers the applicable location, and successfully accepts the delivery.

The distribution path in this example becomes:

Client A — Rejected → Client B — No Coverage → Client C — Accepted

Rather than ending distribution after Client A's rejection, LeadExec continues evaluating eligible opportunities according to the configured distribution workflow.

This is one example of the behavior commonly described as waterfall lead distribution.

The actual order and number of Clients attempted depend on the configuration used for the Lead Type, Campaign, Clients, and Delivery Methods involved.

Price-Based Lead Distribution

Pricing can be one factor LeadExec uses when determining how eligible Client opportunities should be evaluated.

For example:

Client A — $80
​Client B — $70
​Client C — $60

If the configured distribution strategy prioritizes Client A and that Client cannot accept the lead, LeadExec can route the lead to Client B when the applicable rules allow it.

If Client B also cannot successfully receive the lead, Client C may remain available as another qualified opportunity.

This allows organizations to combine price-based lead routing with fallback behavior so that an unsuccessful higher-value opportunity does not necessarily eliminate other qualified delivery options.

Price is only one possible factor in Client prioritization. Other routing methods can determine a different order depending on the account configuration.

Geographic and Coverage-Based Lead Distribution

Geography and service coverage can also affect Client qualification and lead routing.

LeadExec can evaluate geographic information such as:

A Client that does not cover the consumer's location may be excluded during the qualification process.

In other workflows, geographic eligibility may also be determined through a Client response during distribution. When that occurs, LeadExec can use the response to determine whether another eligible opportunity should be evaluated.

Geographic lead routing is particularly useful for organizations managing Clients across multiple service territories, regions, branches, franchises, or other location-based distribution models.

For geographic grouping in distribution workflows, see How to Create Delivery Groups.

For routing based on large ZIP Code, postal code, or other lead-field lists, see Client Settings – Distribution Lists.

Ping/Post Lead Distribution

LeadExec can also use these distribution concepts within Ping/Post workflows.

Ping/Post allows the system to evaluate Client interest, eligibility, availability, pricing, coverage, and real-time responses before sending the complete lead.

A Ping/Post workflow may include:

Identify Eligible Clients → Send Ping → Evaluate Responses → Select Opportunity → Post Full Lead → Evaluate Delivery Response

If the selected opportunity cannot ultimately be completed, the configured distribution and response rules can determine whether LeadExec should evaluate another eligible opportunity.

This is particularly useful in lead-selling and marketplace environments where Client demand, pricing, availability, and coverage can change from one lead to the next.

For a detailed explanation of Ping/Post, Ping Trees, Client bidding, revenue requirements, coverage scanning, and lead-delivery validation, see Ping Post Lead Distribution Explained.

For technical configuration, see Setting Up a Ping Post Lead Delivery in LeadExec.

Delivery Responses and Fallback Behavior

Understanding the result of a delivery attempt is an important part of LeadExec's distribution process.

LeadExec Delivery Methods can evaluate configured responses from receiving systems to determine whether a lead was successfully accepted and how the system should handle an unsuccessful attempt.

Depending on the configuration, continued distribution can be influenced by several types of results.

Client Rejection

The receiving Client explicitly rejects the lead according to the response criteria configured for the Delivery Method.

No Coverage

The Client does not serve the applicable geographic area or satisfy the applicable coverage requirements.

No Sale

The configured workflow determines that the opportunity did not result in a successful sale and that additional distribution opportunities may be considered.

Failed Delivery

The receiving endpoint fails to receive or process the lead.

Timeout

The receiving system does not respond within the configured timeout period.

Capacity Limitation

A Client may no longer qualify because an applicable lead, order, or capacity limitation has been reached.

LeadExec can use these delivery outcomes along with the remaining Client eligibility information to determine whether another opportunity should be evaluated.

For more information about sending leads to Clients, see Delivery Methods Overview.

Retry Logic vs. Continuing Distribution

Retry logic and continued Client distribution address two different situations.

Retry logic attempts delivery again to the same destination when a delivery fails according to the configured retry settings.

Continued distribution evaluates another eligible Client opportunity when the current opportunity cannot be completed and the configured rules allow the system to proceed.

For example:

Attempt Client A → Endpoint Fails → Retry Client A → Retry Fails → Continue Distribution → Attempt Client B

Retry functionality can therefore address a temporary technical issue with a particular endpoint before LeadExec proceeds to another eligible distribution opportunity.

LeadExec Delivery Methods support configurable retry attempts and failure handling.

See Getting Started – Delivery Methods: Creating a New Delivery Method for additional information.

Delivery Timeouts

Delivery timeouts can prevent an unresponsive Client endpoint from indefinitely delaying lead processing.

A timeout determines how long LeadExec waits for the receiving system to respond before the delivery attempt is handled according to the configured response and distribution rules.

This can be particularly important for real-time lead distribution, where processing and delivery speed may affect the lead's value and how quickly the consumer can be contacted.

For Ping/Post deliveries, timeout settings can be configured as part of the applicable Client endpoint configuration.

See the Ping Post URL Endpoint Tab for additional information.

Maximum Delivery Count

Continued Client evaluation works alongside LeadExec's Maximum Delivery Count.

Maximum Delivery Count determines the maximum number of Clients to which a lead can be successfully delivered.

It does not necessarily represent the number of delivery opportunities LeadExec may evaluate.

For example, a Campaign configured for a single successful delivery may evaluate several eligible Client opportunities if earlier attempts are unsuccessful, but distribution can stop once one Client successfully receives the lead.

A shared-lead Campaign can allow multiple successful deliveries according to its configured Maximum Delivery Count.

This allows organizations to control the number of successful Client deliveries while still providing LeadExec with additional qualified opportunities when earlier delivery attempts cannot be completed.

For Campaign configuration details, see Creating a Web Lead Campaign.

Lead Distribution for Lead Sellers and Lead Generation Companies

Client demand can vary significantly from one lead to another.

Factors affecting demand can include:

A lead that cannot be successfully sold or delivered to one Client may still qualify for another.

By combining Client qualification, pricing, geographic routing, Ping/Post, response handling, retries, delivery limits, and other advanced routing capabilities, LeadExec enables lead sellers and lead generation companies to automate distribution across multiple potential Client opportunities.

This allows organizations to continue evaluating qualified distribution opportunities when an earlier opportunity cannot be completed.

Monitoring Lead Distribution

LeadExec records distribution activity so users can review what occurred throughout the delivery process.

The Distribution screen provides visibility into lead distribution results and allows users to investigate individual lead activity.

Depending on the applicable activity, users can review information such as:

This visibility helps users understand how a lead moved through the configured distribution process and investigate unsuccessful deliveries when necessary.

See Distribution – How to Use This Screen for additional information.

Advanced Lead Routing in LeadExec

The behavior sometimes described as waterfall lead distribution is only one part of LeadExec's broader lead routing and distribution capabilities.

LeadExec can combine Client qualification and continued distribution with capabilities including:

These capabilities allow organizations to configure lead distribution workflows that account for both which Clients should be considered for a lead and what should happen when a particular opportunity cannot be completed.

The result is a lead distribution process that can adapt to Client eligibility, pricing, geography, availability, delivery responses, and the organization's specific routing requirements.

For a broader explanation of these capabilities, see Advanced Lead Routing in LeadExec.

Related LeadExec Resources