Inside the decision
Context first. Workflow second.
The model keeps the quality question close to the acquisition moment, while leaving downstream sales systems and team policy in place.
01 · Signal collectionStart with the context available.
ThreatIP can consider available visitor behavior, sessions, sources, campaigns, lead attributes, engagement, account or company context where available, intent, and supporting technical or network signals. It does not imply that every signal is available for every visitor.
Review visitor context ->02 · Quality evaluationEvaluate the acquisition journey, not only the form fill.
Quality can be considered across visitor, account context where available, lead, and campaign. A signup or conversion is an input to review—not by itself proof that a record is ready for sales.
Review lead quality ->03 · Verdict and reasonsMake the decision understandable.
Product states such as Trusted, Needs Review, Low Intent, and Low Quality give teams a shared language. Inspect the reasons and context available for the decision instead of treating a single number as the whole story.
See an acquisition review ->04 · Recommended actionConnect the verdict to the next step.
ThreatIP can recommend Send, Review, Nurture, or Hold. The recommendation supports your workflow; your organization owns the final policy, routing, and customer treatment.
Review CRM readiness ->