Intent Score Threshold Configuration — v1.0.56 Release

Published: 2025

NurtureHub v1.0.56 gives org owners full control over how intent scores are calculated and when hot lead alerts fire. This post walks through what's changed and how to make use of the new Scoring settings page.

Why this matters

Not every agency operates at the same pace or with the same definition of a "hot" lead. A high-volume lettings desk may want a lower threshold so agents are alerted earlier in the engagement cycle. A boutique estate agency handling premium instructions may prefer a tighter definition of intent before an alert interrupts their workflow.

Previously, NurtureHub applied fixed thresholds to everyone. As of v1.0.56, those defaults are yours to adjust.

What you can configure

Head to Dashboard → Settings → Scoring (/dashboard/settings/scoring). The page is available to org owners only.

Alert thresholds

Warm threshold (default: 70) — When a contact's intent score reaches this value, they are classified as warm and a warm alert is dispatched.
Hot threshold (default: 85) — When a contact's intent score reaches this value, they are classified as hot and a hot lead alert is dispatched to the relevant agent.

Raise these values if you're receiving too many alerts; lower them if you want earlier visibility on engaged contacts.

Alert cooldown

Minimum time between alerts for the same contact (default: 24 hours) — Prevents the same contact from triggering repeated alerts in a short window. Useful for contacts who open and click multiple emails in a single session.

Trigger events and weights

You can choose which engagement events contribute to a contact's intent score and assign a numeric weight to each. Common events include email opens, link clicks, reply activity, and re-engagement after a period of inactivity. Higher weights mean a single occurrence of that event moves the needle more significantly.

Score decay rate

Intent scores are not permanent. The decay rate controls how quickly a score decreases over time when a contact stops engaging. A steeper decay rate keeps scores fresh and reflective of recent behaviour; a shallower rate gives contacts more credit for older engagement.

Score Simulator

Before committing to a new configuration, use the Score Simulator on the same settings page to sense-check your changes.

Enter a hypothetical sequence of engagement events — for example, two email opens, one link click, and a reply — and the simulator will calculate the resulting intent score under your current settings. No live contact data is touched; this is a read-only preview tool.

This is particularly useful when:

You're tightening or loosening thresholds and want to understand the downstream impact.
You're onboarding a new team member and want to demonstrate how scoring works.
You're auditing why a particular contact did or did not trigger an alert.

Important: changes are not retroactive

All threshold, weight, and decay changes apply to future score calculations only. Scores that have already been recorded will not be recalculated. If you need to reassess a contact's current standing, you can use the Score Simulator as a manual reference point.

Getting started

Navigate to Dashboard → Settings → Scoring.
Review the default thresholds — warm: 70, hot: 85, alert cooldown: 24 hours.
Adjust event weights to reflect the engagement signals most meaningful to your agency.
Set a decay rate that matches your typical follow-up cadence.
Use the Score Simulator to validate the configuration with a sample engagement sequence.
Save. Changes take effect on the next scoring cycle.