Example setups / 01

From a rooftop request to the right installer.

One homeowner. Three installer buyers. Follow the decisions that turn a solar inquiry into a clear, accountable handoff.

Watch the 32-second story

Illustrative setup · Fictional buyers · No claimed customer results

Solar panels on the tiled roof of a sunlit suburban home; an illustrative generated photograph

The starting point

A homeowner is ready to explore solar.

Your job: connect the request to an installer who can serve it.

The business
A regional solar lead network
The product
Exclusive homeowner inquiries
The buyers
Three independent installers

See the whole picture

A solar lead network, in half a minute.

Start with the story. Then explore the rules behind each decision.

32 seconds · On-screen captions · No audio neededIllustrative workflow
Read the video transcript
  1. 0–8 seconds: A homeowner asks about solar. A regional lead seller connects requests to three installer buyers.
  2. 8–16 seconds: Intake captures territory, homeownership, electric bill and consent evidence. The example requires a homeowner and a bill of at least $150.
  3. 16–24 seconds: The routing engine checks contract filters, schedule and caps. One eligible installer accepts the exclusive lead; other installers do not receive it.
  4. 24–32 seconds: The installer follows up. The operator tracks the delivery response, buyer charge and configured conversion outcomes. A lead delivery is not a completed solar installation.

01 / The inquiry

A person asking a question.
A buyer looking for the right fit.

Alex owns a home in the network’s North territory and wants to discuss solar. A campaign captures the request, the qualifying answers and the consent evidence together.

For this example, installers want homeowners with an electric bill of at least $150 per month. Those are sample buyer requirements, not universal solar eligibility rules.

Explore lead intake

Example inquiry

Alex’s solar request

Homeownership
Yes
Monthly electric bill
$220
Service territory
North
Request
Speak with an installer
Consent evidence
Captured with the request

Example data only. Each operator defines its own form, notices, qualification criteria and evidence requirements.

02 / The decision

Same inquiry.
Different rules, different route.

Try the three situations below. See who gets the lead, who does not, and why.

01 / Intake

Homeowner inquiry

North territory
Electric bill: $220/month

02 / Qualify

Check the fit

Passes the example rules
Consent evidence retained

03 / Route

One eligible buyer

Exclusive distribution
Priority + filters + caps

North installer

Receives this lead

Regional installer

Eligible backup

South installer

Outside territory

The right territory. Room for one more.

The homeowner matches the North territory and bill threshold. The first eligible installer accepts delivery; this exclusive lead stops there.

Interactive illustration. These buttons change the example; they do not run the routing engine or submit a lead.

A homeowner and a solar consultant discussing a roof plan at a kitchen table; an illustrative generated photograph
Illustrative imagery. The consultation represents a possible next step, not a reported customer outcome.

03 / The handoff

The installer gets the context.
The homeowner gets a next step.

The selected installer accepts the lead through its configured delivery endpoint. Contact details, qualification answers and consent references arrive in the agreed payload.

The installer handles the conversation, site assessment and proposal. Your delivery report tells you whether the lead was accepted; conversion reporting depends on the outcomes the buyer sends back.

See delivery and outcome integrations

Inside Lead Router

The settings behind the solar example

The settings behind the solar exampleSample workspace
The settings behind the solar example. A real product screen from a fictional solar offer shows where the distribution rules are configured.
A real product screen from a fictional solar offer shows where the distribution rules are configured. Real product screen with sample data.

Put it into practice

Four pieces to set up.
One connected operation.

Keep the example simple: one offer, three buyer contracts and a clear definition of a successful delivery.

  1. 01

    Define what you sell

    Create a solar vertical with the intake fields you need. This example sells exclusive homeowner inquiries through one lead offer.

    Lead intake
  2. 02

    Connect your sources

    Create a campaign for each source. Capture consent evidence and pass territory, homeownership and electric bill consistently.

    Consent evidence
  3. 03

    Give each buyer its rules

    Create an installer buyer and contract. Set its territory, qualification filters, delivery endpoint, schedule, price and daily cap.

    Buyer caps
  4. 04

    Prove the handoff

    Map the payload and define an accepted response. Test delivery, fund or approve the buyer’s billing arrangement, then activate the setup.

    Delivery setup

Keep the operation honest

Watch what happens
after “delivered.”

Lead acceptance, buyer charges and completed installations are different events. Track each using the data your buyers actually return.

  • Source quality

    Compare accepted and rejected leads by campaign. Inspect the rejection reason before changing your traffic.

  • Buyer capacity

    Watch caps, schedules and eligibility so a full or unavailable installer does not receive new traffic.

  • Money and outcomes

    Reconcile buyer charges, publisher payouts and approved returns. Add appointment or sale outcomes when the buyer reports them.

Your network can work differently

Start with the model.
Make the rules your own.

This walkthrough uses exclusive, priority-based routing. Your offers can use other supported distribution methods, with the fields and contracts your operation needs.

About this example: fictional scenario and buyer rules; AI-generated illustrative photographs; original animated walkthrough. No real customer results or installation outcomes are represented. Modules, permissions, delivery integrations and account configuration determine availability.