Warm Lead or Intent Spike? A Field Checklist for Telling Them Apart | NPLUS Global

Every pipeline report has a lead marked "warm" that never picks up the phone, and an account "surging" on a topic that turns out to be a compliance officer skimming a news article. The two get treated as interchangeable because both show up as a green flag in the CRM. They aren't the same thing, and healthcare sales cycles are unforgiving enough that confusing them wastes a quarter of outreach on the wrong people.

A warm lead is a person who did something — replied, booked a call, filled a form, asked a question. An intent spike is a statistical inference — a topic-level surge in research activity, usually resolved to an account or domain, not a named decision-maker. One is first-party and specific. The other is third-party and probabilistic. Treat them with the same urgency and you'll burn rep hours chasing noise generated by a regulatory news cycle, not a buying process.

Here's how to keep the two straight, from vendor evaluation through ongoing hygiene.

Before you trust the signal

• Ask any data provider to define "intent" in one sentence, then push until you know whether the resolution is contact-level or account-level — most is the latter.
• Request the actual topic taxonomy behind the spike; healthcare terms like "value-based care," "interoperability," and "compliance" surge industry-wide every time CMS or ONC publishes a rule, regardless of buyer interest.
• Check whether the spike is tied to a named title. An account-only signal can't tell you if it's a facilities manager researching an unrelated RFP or the VP who actually signs.
• Cross-reference spike dates against the public regulatory calendar — comment periods, HIMSS week, breach headlines. A spike that lines up with an industry event is noise, not demand.
• Pull the last 20 leads your own team marked "warm" and check how many had real reciprocal contact versus just repeated email opens.
• Ask for the raw volume behind a "surge" claim. Three extra page views isn't a spike; find out what threshold the model actually uses.

During onboarding — build the filter, not just the funnel

• Give intent signals and warm leads separate pipeline stages with separate SLAs. Don't let a rep treat a topic surge like a person who just replied.
• Map every surge topic to a persona in the buying committee — clinical ops, compliance, IT security, procurement. A "revenue cycle" spike from a clinical domain is a mismatch worth flagging, not scoring higher.
• Require repeated surges across multiple weeks before triggering outreach, not a single-day blip — healthcare buyers tend to batch-research after news events, then go quiet.
• Build a suppression list for known noise triggers: recent breach coverage, new rule announcements, conference weeks. Otherwise the whole team gets flooded with false positives on the same day.
• Get written sign-off from both sales and marketing on what "actionable" intent looks like before the first delivery lands, so there's no argument later about whose definition of "warm" was wrong.
• If you're piping in a third-party feed alongside first-party engagement data — which is how most teams at NPLUS Global and similar data operations structure incoming signals — make sure the two sources are visibly tagged, not blended into one undifferentiated score.

After the first delivery — audit before you scale

• Pull every lead marked "warm" or "in-market" from the batch and manually check for a real first-party action — reply, meeting request, direct download — not an inferred behavior.
• For intent-flagged accounts, check public evidence of an actual buying process: job postings for relevant roles, published RFPs, leadership changes — before assuming the spike means anything.
• Track time-to-response separately for warm leads versus intent-flagged accounts, then compare eventual conversion. This is the fastest way to see if the "warm" label is inflating urgency without inflating results.
• Look for spikes that cluster by geography or account size in ways that mirror a known regulatory rollout — a state Medicaid change, for instance — rather than organic interest.
• Flag any spiking title with no budget authority. A clinical informatics analyst researching a topic is not the same signal as a VP of revenue cycle doing the same search.
• Have a rep manually call five to ten flagged accounts that show intent but no other engagement, just to establish what the sales floor actually encounters when it dials in.

Ongoing — keep the definitions honest

• Re-run the audit quarterly, not once. Intent providers change their models and topic taxonomies without much notice, and last quarter's threshold may not hold.
• Track a "false spike" rate — the percentage of intent-flagged accounts with zero response after three touches — and hold the data source to a baseline over time.
• Retire topics from your trigger list once they've become industry-wide noise words. This happens fast in healthcare; every regulatory cycle mints a new "hot" topic that everyone searches for a week and then abandons.
• Anchor your warm-lead scoring to actions your own systems actually recorded — an identified site visit, a reply, a booked meeting — and treat third-party intent as a layer that adjusts sequencing and timing, not a layer that changes lead status on its own.
• Revisit your suppression list every time there's major healthcare news; yesterday's noise trigger becomes today's baseline, and the list needs to move with it.

None of this eliminates intent data's usefulness — a well-modeled spike is still a decent reason to move an account up the call list. But it's a reason to look sooner, not a reason to treat someone as ready to buy. The distinction matters most in healthcare specifically, where buying committees are long, procurement is bureaucratic, and a single news cycle can make half the industry look "in-market" on the same Tuesday for reasons that have nothing to do with your product.