How to Verify a Signal Before Creating a Qualified Lead

Who this checklist is for

This checklist is for people and systems responsible for turning early engagement into a controlled pipeline state. It is specifically designed to keep SellersGPT's product rules visible without presenting them as a universal sales definition for every company.

Contents

1 Separate the lead trigger from qualification 2 Define the exact qualification decision scope 3 Apply the SellersGPT SIGNAL-TO-QL Gate 4 Handle each trigger without changing the gate 5 Create an auditable state transition 6 Illustrative example 7 Common mistakes 8 What this does not mean 9 Common questions 10 Sources and methodology

1. Separate the lead trigger from qualification

SellersGPT recognizes three lead-trigger paths: 1 a visit to a landing page through a cold-email link; 2 a direct reply to the cold email or follow-up thread; 3 a form submission, including a submission from natural website traffic. The trigger answers: Did a policy-recognized event occur? Qualification answers: Does the resulting record satisfy the identity/profile and agreed ICP evidence required now? These outcomes are valid:

• Trigger passes, qualification passes: create the qualified lead.

• Trigger passes, qualification is Unknown: create or update the lead and open evidence-completion work.

• Trigger passes, qualification fails: retain the event and apply the fail or alternate route.

• Trigger fails: quarantine, deduplicate, or classify the event without creating the lead state. A qualified lead is therefore not a synonym for click, reply, form, meeting, opportunity, approval, or revenue. It is a versioned state based on explicit criteria. HTTP semantics bound what a landing-page request establishes. IETF - RFC 9110, HTTP Semantics Email message fields support thread and sender-context evidence but do not prove commercial role. IETF - RFC 5322, Internet Message Format Each trigger needs its own validity checks before the common gate.

2. Define the exact qualification decision scope

Every qualification record should identify:

• tenant and active program;

• active ICP ID and version;

• target account, site, and company relationship;

• person/contact and required identity level;

• application or problem context;

• trigger type and event ID;

• event time and decision time;

• qualification policy version;

• evidence sources, states, and expiry dates;

• reviewer or deterministic rule responsible for transition. Profile completeness is policy-defined. It may require legal or operating company, work contact, role evidence, geography, industry, application, and customer relationship. Do not use “complete” to mean that every conceivable field is filled. It means every field required by the active qualification policy has accepted evidence. Identity also has levels. NIST's Digital Identity Guidelines provide formal concepts for identity proofing and authentication in digital systems. NIST - Digital Identity Guidelines Public GTM interactions generally do not reach those formal assurance levels. Use the source as a bounded reminder that claimed, mailbox-controlled, authenticated, and corroborated identity are different, then define the evidence level the business actually requires.

3. Apply the SellersGPT SIGNAL-TO-QL Gate

The SIGNAL-TO-QL Gate is an original SellersGPT editorial tool and product-specific control. Gate Pass condition Fail handling Unknown handling S - Signal validity Genuine, deduplicated trigger that meets its event-specific rule Quarantine or no lead transition Investigate event integrity I - Identity linkage Person and company meet the policy's required evidence level Reject person-level qualification or reroute Research; retain claimed or attributed state G - Required profile Every required field is complete with accepted evidence Incomplete, no qualification Open named field tasks N - Named ICP version Every agreed hard gate passes against the active version Record failed criterion; no qualification Keep criterion Unknown; do not score A - Age and freshness Volatile evidence is inside its defined validity period Refresh or close stale state Review missing evidence date L - Legal/treatment and relationship No suppression, company stop, existing-customer block, or prohibited treatment Stop, reroute, or block Escalate before action Q - Quality trace Evidence source, policy version, decision, and actor are recorded Repair record before transition Hold transition All required gates must pass. Do not calculate a weighted average. One hard-gate fail is not offset by a strong reply, ten visits, or a complete form. The gate does not require multiple signals. One landing-page visit can become a qualified lead when the visit is valid, linked identity/profile is complete to the required level, all agreed ICP criteria pass, evidence is fresh, treatment permits it, and the trace is complete. That is a SellersGPT rule, not a claim that every B2B organization should qualify one visit.

4. Handle each trigger without changing the gate

Cold-email landing-page visit Verify request integrity, scanner/bot risk, unique-link attribution, person and account linkage, and forwarding uncertainty. The link context can support attribution but does not guarantee the intended recipient acted. Direct reply Verify thread and sender context, separate human response from delivery or auto-response, classify positive, neutral, negative, referral, unsubscribe, or company stop, and preserve exact language. A direct reply triggers a lead even when the commercial classification is negative; treatment and qualification decide what happens next. Form submission Validate the event and input, preserve submitted values, check automation and duplicate risk, verify identity to the required level, and evaluate fit. Natural traffic receives the same gate; lack of a campaign does not disqualify an otherwise valid form. Across all three, evidence type can differ but qualification criteria stay versioned and consistent. Do not make forms “worth 20 points” and replies “worth 15.” Ask whether the required fact is supported.

5. Create an auditable state transition

The W3C PROV overview provides a general model for documenting how entities, activities, and agents relate. W3C - PROV Overview A qualified-lead transition should similarly retain its inputs and responsible rule or reviewer. NIST's Information Quality Standards emphasize utility, objectivity, integrity, and correction for NIST information. NIST - Information Quality Standards They do not govern SellersGPT records, but they support four editorial practices:

• show the source near the conclusion;

• distinguish fact, calculation, assumption, and recommendation;

• preserve known limits and contradictory evidence;

• provide a correction path. When the gate passes, write an immutable ledger entry or equivalent audit record containing prior state, new state, event ID, qualifying policy and ICP versions, evidence snapshot or references, actor, decision time, and any downstream reservation or notification reference. If later evidence shows a mistake, append a correction and reverse the operational consequence according to the governing workflow. Do not rewrite the original transition silently. Commercial communication remains subject to treatment controls. The FTC's CAN-SPAM guide provides U.S. requirements relevant to commercial email and opt-out handling. FTC - CAN-SPAM Act: A Compliance Guide for Business A qualified state does not cancel suppression or authorize unrestricted contact.

6. Illustrative example

Illustrative example. The company, person, events, criteria, and calculations below are fictional. They are not a SellersGPT customer result or forecast. A fictional campaign targets end-user food plants in Ontario with 100-500 employees and a qualifying washdown application. Priya at Northstar Foods receives a unique cold-email landing-page link. At 10:05, a security scanner requests the page. At 14:12, a separate request loads page assets and navigates to the application page. Campaign attribution is supported but not person-verified. The account record has verified legal company, facility, location, industry, size, and application. The active policy requires a supported work-person link, not formal identity proofing, and all required profile fields are complete. Gate State Evidence Signal validity Pass 14:12 event distinct from quarantined scan Identity linkage Pass Unique delivered-link context meets active Supported threshold Required profile Pass 7 / 7 required fields complete Named ICP Pass 4 / 4 agreed hard gates pass Age and freshness Pass Event and volatile company evidence current Legal/treatment Pass No customer or suppression conflict Quality trace Pass Event, sources, versions, and rule recorded The lead trigger and every gate pass, so the single 14:12 visit creates a qualified lead under this fictional policy. The 7 / 7 and 4 / 4 calculations measure completeness and gate passage; they are not a purchase probability. If the identity policy required a person-verified reply or form, Identity would be Unknown and qualification would wait.

7. Common mistakes

Making the trigger the definition A click, reply, or form starts the decision. It does not bypass identity, profile, ICP, freshness, or treatment. Requiring multiple events without reason Repetition can add noise. One event is sufficient when every required gate passes. Adding points across hard gates Activity cannot offset suppression, existing-customer status, failed ICP, or unresolved required identity. Calling Unknown a failure Unknown means evidence is missing. Create a specific evidence task instead of inventing pass or fail. Using the latest ICP without versioning Record which criteria governed the event-time decision and re-evaluate explicitly when policy changes. Forgetting duplicate and reversal controls One underlying event should not create multiple qualified leads. Incorrect transitions require traceable correction.

8. What this does not mean

• It does not universalize SellersGPT's trigger or qualification rules.

• It does not promise that a qualified lead will reply, meet, buy, or produce revenue.

• It does not define qualification as a private-intent prediction.

• It does not allow qualified status to override suppression or existing-customer routing.

• It does not explain billing mechanics or replace the separate commercial policy.

9. Common questions

Can one landing-page visit really be enough? Yes, within SellersGPT, when the event is valid and all required identity/profile, ICP, freshness, treatment, and trace gates pass. The visit alone does not supply those facts; the complete evidence record does. Does every direct reply qualify? No. It triggers a lead. A bounce or auto-response is not a direct human reply, and a human reply can still fail or leave qualification gates Unknown. Are natural-traffic forms treated differently? They lack campaign attribution but enter the same form-verification and qualification path. Source does not replace identity, fit, or treatment evidence. What if evidence becomes stale immediately after qualification? Preserve the valid transition, mark the affected current state for refresh, and apply the product's review or reversal rule. Do not silently change historical evidence.

10. Sources and methodology

Sources 1 W3C - PROV Overview. Used for provenance relationships among evidence, processing activities, and responsible actors. Accessed August 25, 2026. 2 NIST - Information Quality Standards. Used for bounded information-quality and correction principles. Accessed August 25, 2026. 3 NIST - Digital Identity Guidelines. Used to distinguish claimed, proofed, and authenticated identity concepts, with explicit limits for GTM forms and links. Accessed August 25, 2026. 4 IETF - RFC 9110, HTTP Semantics. Used to bound the technical meaning of a landing-page request. Accessed August 25, 2026. 5 IETF - RFC 5322, Internet Message Format. Used for email message and thread-evidence context. Accessed August 25, 2026. 6 Federal Trade Commission - CAN-SPAM Act: A Compliance Guide for Business. Used for U.S. commercial-email treatment and opt-out context. Accessed August 25, 2026. SellersGPT analysis and framework The SIGNAL-TO-QL Gate, product trigger logic, transition requirements, and example are original SellersGPT editorial and product-specific tools. They do not originate from the cited sources and do not estimate purchase probability. Update policy Review this checklist when SellersGPT trigger, profile-completeness, ICP, freshness, suppression, customer-block, dispute, or state-transition policy changes. Run controlled tests for all three trigger paths.