Lead detail

What this page shows

The lead detail page is the full record for one person — their score, every signal they generated, their evaluation history, role assignments, and the feedback controls. You reach it by clicking View on any row in Browsing leads, or from the Leads section of an account detail page.

Header and score badge

The page header shows the person's name and job title. When the lead has at least one completed evaluation, a colored badge appears in the top-right corner of the header card:

• Hot (red)
• Warm (amber)
• Cold (blue)

The badge reflects the most recent evaluation. If the lead has never been evaluated, no badge appears.

Status alerts appear above the header card when needed:

• Evaluation Failed (red alert) — the latest evaluation attempt produced an error. The alert shows the attempt count, the last error message, and a Retry Evaluation button when a retry is permitted.
• Evaluation In Progress (spinner alert) — an evaluation is queued or running; the page polls and refreshes automatically when it completes.
• Excluded from AI Evaluation (orange alert) — the lead failed one or more evaluation rules and was not scored. The alert lists each failed rule, the field, the expected value, and the actual value. See Signals overview for how evaluation rules are configured.

Info card

The large card on the left covers the lead's identity and account context:

• Email address
• Linked account name (links to the account detail page when a target account exists) and domain
• Organization Propensity — the propensity score of the account the lead belongs to (High Propensity / Medium Propensity / Low Propensity) with a confidence percentage and brief reasoning text, when the account has been evaluated
• Last active date
• Created date

Lead Stats card

The smaller card on the right shows four counters:

Fields that depend on a completed evaluation are omitted when the lead has not been evaluated yet.

Tabs

Six tabs sit below the cards. Some are conditional and only appear when the relevant data exists.

Signals

A table of every signal event linked to this lead, with columns: Type, Source (shown as a source badge), Name, Description, and Date. Rows are sorted by date descending. The tab label shows the signal count.

For how signal types are configured and what each source badge means, see Signals overview.

Evaluations

A chronological list of evaluation records. The tab label shows the total count.

Each evaluation entry shows:

• A score badge (Hot / Warm / Cold) and, when the evaluation was run against a specific ICP, an ICP chip naming that profile
• The evaluation date
• Confidence percentage (shown to the right of the score)
• AI Assessment Reasoning — a plain-language explanation of why this score was assigned
• Key Scoring Factors — the individual factors that drove the score, each labeled positive (green), negative (red), or neutral (gray) with a weight

When a lead has been evaluated against more than one ICP, each ICP's evaluation appears as a separate entry in the list, each with its own score, confidence, reasoning, and scoring factors.

Below the scoring factors for each entry, the Provide Feedback form appears when you are eligible to submit feedback (see below).

Lead Profile

System identifiers and metadata, organized into three sections:

Lead Identifiers — Lead ID, email, name, and title.

Organization Links — Target Org ID (links to the account detail page when present), CRM Account ID, Product Org ID, and Account Name.

Timestamps — Created and Last Active datetimes with full date and time.

Product Org

Appears only when the lead has a product-workspace record linked. Shows the workspace name, plan, user count, MRR, trial status, last active date, enabled feature flags, and any custom fields from your product system. If none of those fields are populated the tab shows a brief empty-state message.

CRM Account

Appears only when a CRM account is linked to this lead — either directly by CRM account ID, or indirectly through the lead's linked target account. Shows the account name, domain, industry, market segment, employee count, region, and any CRM custom fields.

When the link runs through the target account (not a direct match), a badge reads via Target Org (N% confidence).

Role History

A log of every role correction that has been applied to this lead — additions, rejections, and retractions — drawn from the primary ICP associated with the lead's roles.

Each entry shows:

• The correction type (e.g., Add, Reject)
• The role affected
• Whether it came via in-app action or CRM
• A retracted label when the correction was later undone
• The optional reason the submitter provided
• What the system originally had for that role at the time of the correction (whether the role existed and at what confidence)

If no corrections have been made, the tab shows "No role corrections yet."

For how to add, reject, or undo a role assignment, see Role corrections.

Buying Group Roles section

Below the tabs, the Buying Group Roles card shows the person's current role assignments, grouped by ICP.

For each ICP the person has roles in, a group header names the ICP and shows the role count. Below it, each role card shows:

• Role name
• Primary badge (on the one role chosen as the person's primary role for that ICP)
• Behavioral, Demographic, or Mixed basis badge — showing whether the match came from activity, profile, or both
• Confidence percentage — replaced by "Set by user" on the right-hand side of the card when a team member has corrected the role in-app (the card also gains a Corrected badge); you may occasionally see "Set in CRM" instead if your team has configured CRM-sourced roles
• Reasoning text
• Behavioral signals — the specific signal events that contributed (when the basis includes activity)
• Profile match — the title keywords or attributes that contributed (when the basis includes profile)

An Add role control and a Reject button appear on each group and card for team members who can submit corrections.

For the full reference on what Behavioral, Demographic, and Mixed mean, how primary is chosen, and how to read the confidence score, see Role attribution. For how to correct a role assignment, see Role corrections.

Provide Feedback form

The Provide Feedback form appears below the scoring factors in each evaluation entry in the Evaluations tab.

Who can submit: team members with the Owner, Admin, or Editor role. Viewer accounts see a note explaining they do not have permission.

When it is available: only for evaluations completed within the last 30 days. Evaluations older than 30 days show a note indicating the window has passed.

One submission per evaluation: once feedback is submitted for a given evaluation, the form is replaced by a confirmation message. The form does not reopen.

What to write: explain why the score looks wrong, or add context the model may not have had — for example, that the person is a contractor rather than a direct employee, or that the account is a known competitor. The field accepts 10–1,000 characters.

Submitted feedback goes into the model-refinement pipeline. For how feedback influences future evaluations and how to track model-refinement usage, see Model refinement and Evaluation feedback.

Next steps

• Browsing leads — filter and navigate the full leads list
• Account detail — the account-level view, where all leads for one company are grouped
• Account coverage — propensity, buying-group completeness, and the at-risk pattern
• Role attribution — how TrailSpark assigns people to buying-group roles
• Role corrections — override or reject a role assignment
• Model refinement — how submitted feedback changes future evaluations
• Evaluation feedback — tracking and managing the feedback you submit