Lead Quality Scoring

Make lead quality an explainable routing input

Build rule-based quality models on a 1–10 scale, version and publish them, and apply the resulting scores to eligible routing and prioritization workflows.

Inside Lead Router

Manage your scoring models

Manage your scoring modelsSample workspace
Manage your scoring models. The scoring workspace provides the setup entry point for models used by your offers and verticals.
The scoring workspace provides the setup entry point for models used by your offers and verticals. Real product screen with sample data.

How it works

  1. 1

    Define the model

    Choose the lead fields and factors that represent quality for the vertical. Weighted factors contribute to the result, gates enforce model conditions and modifiers adjust the score under their configured rules.

  2. 2

    Publish and attach

    Work in a draft, review the model, then publish a version. Use the vertical default or an offer-specific model override so the relevant traffic is evaluated with the intended model.

  3. 3

    Use and inspect the score

    See the quality score on leads and in supported reports. Contracts can set a minimum score, and supported dialer/Quality Tier workflows can use the score for prioritization.

A model your operators can explain

Keep the factors, version and routing consequence visible instead of treating quality as an unexplained number.

Weighted, gating and modifier factors

Use the factor type that matches the rule: contribute to a weighted score, gate a condition or modify the result. Map model inputs to the actual lead fields. Model quality depends on available, correctly populated inputs.

Drafts and published versions

Separate editing from the published model. Version history lets operators identify the model attached to the workflow and review changes before promotion. Excel (XLSX) export and import support reviewing and maintaining configured models.

Vertical defaults and offer overrides

Set a default for a vertical and override it on an offer when that traffic needs different criteria. A single universal scoring model is not silently applied to every source or industry.

Minimum-score eligibility

A configured contract minimum can exclude a scored lead below its threshold. Unscored leads currently pass that minimum-quality gate. A missing score is not the same as a low score, so configure required inputs separately when the business needs them.

Keep different scores and decisions distinct

Quality scoring, AI analysis and buyer ranking solve different problems.

Choose a report for your next checkSample workspace
Choose a report for your next check. Start in the report library. Open a supported report to compare lead quality with outcomes. The screen shown is the library.
Start in the report library. Open a supported report to compare lead quality with outcomes. The screen shown is the library. Real product screen with sample data.

Quality Score versus AI Score

Quality Score is a rule-based 1–10 model written by operators and used by routing. AI Score is a separate informational 0–100 signal. Do not treat the AI score as the contract’s minimum-quality eligibility value.

Routing and prioritization

After the usual buyer eligibility checks, supported Quality Tier distribution and dialer prioritization can use quality information. A quality score does not bypass a buyer’s filters, schedule, cap or funding requirements.

Compare quality with outcomes

Use supported lead and reporting views to compare sources, models and outcomes. A rule-based score describes the inputs your model evaluated; it is not a guaranteed prediction of conversion or revenue.

Review model changes deliberately

Check field mappings, missing-input behavior and example leads before publishing a revision. Keep the model aligned with the vertical and campaign requirements rather than relying on a score to repair incomplete intake data.

What your account needs

An operator must configure and publish a model and attach it through the supported vertical or offer settings. Model inputs need the corresponding lead data. Routing thresholds and downstream score consumers are configured separately. Unscored leads still pass the minimum-score gate, and the AI score is a separate value.

Frequently asked questions

Is the 1–10 quality score generated by an LLM?

No. It comes from the rule-based quality model you configure. The separate informational AI score uses a different 0–100 scale and is not the contract’s minimum-quality value.

Does a minimum score reject leads with no score?

Not under the current quality-gate behavior. Unscored leads remain eligible for that gate. Configure required intake fields separately if your agreement requires particular data.

Can two offers in one vertical use different models?

Yes. A vertical can supply the default model and an offer can override it with its configured model.

Can I review a model before changing live scoring?

Yes. Use drafts, version review and the publish/promotion workflow. XLSX import/export also supports reviewing the configured factors and mappings.

Explore the platform

Set up your buyer network

Choose how buyers get leads and calls. Keep their setup and routing rules in one place.

Every feature is part of the plan. Usage is billed in credits.