LS
Lead Scoring Agent

Scores every signal, routes the hot ones in seconds.

Watches every lead signal: form fills, page views, email opens, replies, meetings booked. Re-scores on every change against your weights. Hot leads escalate to a manager queue, cold leads auto-archive with reason logged.

No credit card Live in 60 seconds Off-switch per agent
Saves
80% of MQL triage
Touches
Lead managementRoutingScoring
01What it actually does

No demo magic. Real actions, real audit trail.

Each action runs through the same engine your humans use: same routing rules, same approval policy, same audit log. The agent's name is on every record it touches.

01
Re-scores on every signal
Form fill, page view, email open, reply, meeting booked, demo attended: each event adjusts the composite Score per your weights. Re-runs routing if the new score crosses a threshold.
02
Routes by best-fit rep
Territory match named-account match round-robin campaign-specific override. Picks the right rep within seconds; you override anytime via Sales Ops.
03
Escalates hot leads
When score crosses your hot-threshold (default 75), the lead escalates to a Sales Manager queue with the named signals that drove it: 'Pricing page × 3, demo booked, decision-maker title'.
04
Auto-archives the cold
Below cold-threshold (default 20) for 14 days with no positive signal auto-archive with reason logged. Reopens automatically if a fresh positive signal lands.
02How it decides

The logic behind every action.

Not a black box. The decision rules are explicit, configurable, and surfaced on every action so the manager (and you) can trace the why.

01
Weighted composite
Score = Σ(signal × weight × decay). Demographic (firm fit) decays slowly; behavioral (intent) decays in days. Configure weights per segment.
02
Match before routing
Before round-robin, check: does this lead's company-domain already exist as an Account? If yes, route to the Account owner regardless of round-robin. Protects named-account boundaries.
03
Throttle the noise
Don't re-route on every signal. Only when the score crosses a threshold (Hot, Warm, Cold) or when the candidate-rep changes. Avoids whiplash for the assigned rep.
03What you control

Off-switch per agent. Always.

Every agent runs on a leash you set. Approval thresholds, dry-run mode, per-rep / per-account disable, audit trail, your call.

01
Per-segment scoring weights
Different weights for inbound demo requests vs outbound prospects vs partner referrals. Configure per Source × Segment in settings.
02
Hot/cold thresholds
Tune the score bands per segment. Strategic accounts often run looser thresholds (route earlier); transactional run tighter (let signal accumulate).
03
Off-switch per source
Disable the agent on a single Source (e.g. Partner-Referrals always go to a named owner) without affecting others.
04
Read-only mode
Dry-run: agent computes scores and proposes routing, posts nothing. Use during evaluation or after weight changes.
04This morning

A real activity log.

Excerpted from a production tenant. Every line is signed, timestamped, and traceable to the action it represents.

Lead Scoring Agent · activity log · today
09:14
Re-scored 247 leads on overnight signals (124 form-fills, 891 page-views, 56 email-opens).
09:14
23 leads crossed Hot threshold. Escalated to manager queues: 12 to Sales-East, 8 to Sales-West, 3 to Strategic.
09:15
47 leads auto-archived (Cold for 14+ days). 3 reopened on fresh positive signal (demo-booked).
09:16
Routing exception: 1 lead matched 2 Accounts (M&A overlap). Surfaced to Sales-Ops for manual assignment.
05Built on

The skills this agent calls.

Every agent is composed from the underlying CRM skills, the same ones your humans use. No private data path, no shadow record.

06FAQ

Common questions.

Asked by the people whose name goes on the renewal forecast.

Can the agent learn our scoring weights from past wins?

Yes. Opt-in: the agent backtests proposed weights against the last 12 months of conversion data and proposes adjustments. You approve before the new weights go live. By default, weights are configured by Marketing Ops, not learned.

What stops the agent from spamming reps with bad routing?

Three guards: (1) score thresholds, not raw scores, trigger re-routing, avoids per-event whiplash; (2) named-account match overrides round-robin; (3) per-rep capacity limits, when a rep is at capacity, new leads queue at the manager level instead of pile-up on one inbox.

How does it handle leads from multiple stakeholders at the same company?

The first lead from a domain creates the Account (or matches if it exists); subsequent leads attach as additional Contacts under the same Account. Score rolls up at the Account level too: when total Account score crosses threshold, all open leads at that Account escalate together.

07The other 7 agents

Run them together.

Agents share the same accounts and the same audit trail. Lead Scoring hands off to Deal Coach; Quote Approval hands off to Renewals.

Run the Lead Scoring Agent on your own data.

Free to sign up. Live in 60 seconds. Walk every screen, work a test pipeline, invite the team. No credit card, no sales call.

Start free