Skip to content
Back

Lead scoringPro

New sign-ups sorted by how well they fit, as judged by a model: every line carries a ring with the number, a Hot, Warm or Cold label and a short why; open one for its signals and weighted breakdown, and send it to HubSpot or Airtable.

oxyn add lead-scoring

Inbound leads

6 new · ranked by AI fit score

The code is part of Oxyn Pro

The preview stays free for everyone. Pro opens the code of every Pro component, screen, agent-app template, block and kit, plus the Pro CLI.

Get Pro

Rendered from Rust at build time · goes live when visible

When to use

  • Inbound leads ranked by an AI fit score with a reason, the signals and breakdown behind it, and a push to the CRM.

When not to use

Installation

Lead scoring is part of Oxyn Pro; the preview is free. Pro items install with the oxyn CLI once your licence is signed in; until then Pro members copy the code from this page.

Terminal
oxyn add lead-scoring

Usage

Dioxus · rust
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Examples

Ranked

Ranked list, rings counting up.

Inbound leads

6 new · ranked by AI fit score

Code Pro
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Open

Top lead open with its breakdown (Oxyn extra).

Inbound leads

6 new · ranked by AI fit score

  • Pricing page ×3SSOBudget this quarter
    • Company fit38 / 40
    • Intent32 / 35
    • Engagement22 / 25
Code Pro
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Error

Push fails, with Retry (Oxyn extra).

Inbound leads

6 new · ranked by AI fit score

  • Pricing page ×3SSOBudget this quarter
    • Company fit38 / 40
    • Intent32 / 35
    • Engagement22 / 25
Code Pro
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

API reference

LeadScoring

PropTypeDefaultDescription
nowrequiredClockMs—Host clock.
introbooltrueCount the rings up on first view.
failboolDefault::default()The first push fails (error scenario).
openOption<usize>Default::default()Lead open at start.

Read from the Rust signature and doc comments.

Keyboard interactions

KeyAction
↑or↓orHomeorEndMove between lead rows
EnterorSpaceOpen or close the focused lead
←or→In an open lead, switch the CRM

Accessibility

  • Rows are buttons named with company, person, score, tier and reason; rings are decorative.
  • Rescoring, opening, the destination and pushes are announced, including that pushes are simulated.
From the spec

Rows are buttons named with company, person, score, tier and reason, with aria-expanded and aria-controls; Up and Down move between rows (roving tab stop), Enter or Space opens, Left and Right switch the CRM; rings are decorative. Every action returns the line the polite live region announces. The focus outline shows only for keyboard focus.

Motion & interaction

Rings count up over 900 ms and their stroke follows the score; tiers read Hot, Warm or Cold in words and colour; open rows fade in.

Timing

Everything on screen is derived from the host clock now (no timers in the block), so playback, tests and the GPUI view agree.

TransitionDurationEasing
Ring count-up900 ms (RING_MS)ease-out
Push1,100 ms (PUSH_MS)—

Reduced motion: fades, shimmer and count-ups stop; every state keeps its words and icons.

Responsive behaviour

  • 360 to 640 px; on narrow cards job titles are dropped and the send-to-CRM button spans the card.
Edge cases (spec)

Fits 360 to 640 px. Below 460 px of block width the role, arrival time and Rescore label leave the row, details start at the card edge and the push button fills the row. Names and reasons truncate with an ellipsis; scores keep fixed slots. Layout follows the block's own width (container queries), never the viewport. Checked at 1440, 768 and 390 px in light and dark with no text overlap. Chrome is monochrome grey; colour is semantic only (success, warning, danger, info) plus data series and the official coloured brand and model marks.

Notes for AI

  • Import LeadScoring from oxyn_dioxus and include STATUS_INDICATOR_CSS plus the token stylesheet once.
  • A GPUI version exists: BlocksView in oxyn_gpui.
  • Props to set first: now.
  • It reads a clock (now) for live timers; pass one clock for the whole page rather than one per component.
  • Keep its states and timings as they ship; restyle it through the CSS variables rather than by hand.

Guides

Oxyn · 74 free components · 264 Pro components · 96 screens · 20 blocks · Dioxus and GPUI