Lead scoring and saved views

Closr scores every active lead from 0 to 100 once a day and surfaces a "hot" flame on contacts who've been hitting your website. Both signals exist so you don't have to triage by gut. Both are deterministic (no LLM bias on the number itself), so the same activity always produces the same score.

What goes into a lead score

The score is a sum of five components, each saturating at its own ceiling. The total budget is 115 points clamped to 100, which means a fully-engaged contact stays at 100 even if you add more activity.

• •**Recency (35 points max).** Fresh activity bumps the score; long silence tanks it. Activity in the last 24 hours scores highest; nothing in 30+ days zeroes this component out.
• •**Stage (30 points max).** Later pipeline stages weight higher. "New" leads score around 5, "Offer Made" around 25, "Firm" 28, "Closed" 30. Keeps a quiet-but-late-stage opportunity from falling below a noisy-but-cold new lead.
• •**Engagement (20 points max).** Count of activities in the last 30 days. Calls, texts, emails, notes, meetings.
• •**Conversation (15 points max).** Binary: does the contact have at least one inbound message on record? A lead who's only ever been outbound stays at zero here. The moment they reply, you get the full 15.
• •**Web activity (15 points max).** Website tracker visits in the last 7 days. +5 per page view (cap 10) plus +5 if any pathname was visited more than once. Mid-range leads (40-90) move the most with web activity; it's the tiebreaker.

The score appears on every pipeline kanban tile and on the contact card. Hover the number on a tile and you'll see a one-line `aiScoreReason` like "stage: offer made · 4 activities in 30d · 6 site visits · repeat".

The hot-lead flame

Separate from the score, contacts who've visited your website 3+ times in the last 7 days get a flame icon on their pipeline tile and on their contact card. The flame is a leading indicator: someone clicking the same listing page four times this week is signaling more than the activity feed shows.

Hover the flame for the count and the most recent page. The web tracker has to be installed on your site for this to fire (see the Web Tracker guide), and the contact has to have clicked at least one tracked link from a Closr-sent email so the cookie can attribute their browsing.

Saved views

A saved view is a filter on the Contacts list (or the Inbox, or the Leads list) that you can come back to without rebuilding. "Cold leads from Facebook in the last 30 days", "Buyers tagged Toronto with no activity in 14 days", "Anyone whose score crossed 80 this week". Closr saves the filter, gives it a name, and pins it to the chip strip on the list page.

To save a view:

1. 1Open the Contacts page (or Inbox, or Leads).
2. 2Apply filters: tags, source, last-activity range, lead score range. Whatever the page exposes.
3. 3Click "Save view". Name it.
4. 4Optional: toggle "Share with team" if you want teammates to see it. Default is private.

Saved views power three things beyond the list page:

• •**The power dialer** picks a saved view as its call list. "Stale Toronto buyers" → click → burn through 40 dials in a row.
• •**Mass email composer** picks a saved view as its audience. Same filter, now an outbound list.
• •**Behaviour triggers** can target a saved view ("when a contact in this view crosses score 80, notify me").

Behaviour triggers off scores

Lead score isn't just a number to look at; it's something automations can react to. In the chat, say "when a contact's score crosses 80, move them to Hot and text me". Closr picks up the score-threshold trigger and writes the rule.

Other behaviour-driven triggers that work today:

• •**`EMAIL_REPLIED`**: fires when an inbound email lands on a contact you've previously emailed
• •**`SMS_RECEIVED`**: fires when an inbound text lands
• •**`CALL_COMPLETED`**: fires when a Twilio voice call ends with the post-call summary
• •**`PAGE_VIEWED`**: fires per web-tracker page view, with the 7-day count + repeat-pathname signal
• •**`LEAD_STAGE_CHANGED`**: fires when a deal moves columns on the kanban
• •**`LEAD_CREATED`**: fires when a new lead lands from any source

The full story on building rules off these triggers is in the Automations guide.

Where to go next

• •`automations`: building rules off score thresholds and the other behaviour triggers
• •`campaigns`: sending a drip to everyone in a saved view
• •`power-dialer`: calling through a saved view top-to-bottom