All articles
Tracker & Signals

Configure signal scoring

Configure signal scoring so the team can distinguish person, company, and market context and apply P1, P2, P3, and DQ consistently. Use definitions with positive, negative, and boundary examples.

Before you start

  • Agree which events matter to the offer.
  • Collect known relevant and irrelevant signals.
  • Choose the AI output language.
  • Define the action permitted for each priority.

Signalist Configure signal scoring step 1 product view.

Three signal categories

Lead updates concern a person, such as a role change or relevant public statement. Company updates concern the target organisation, such as expansion, hiring, or partnerships. Industry updates describe market or regulatory context.

Priorities need examples

Give each priority a title, definition, and several examples. Keep P1 rare and define DQ clearly for personal, generic, unsupported, or irrelevant activity.

Steps

  1. Open Signal Scoring and review the Deep Research Prompt.
  2. Set the intended AI output language.
  3. Define Lead, Company, and Industry Updates without unnecessary overlap.
  4. Configure P1, P2, P3, and DQ with definitions and examples.
  5. Use Test Configuration with known positive, negative, and boundary cases.
  6. Compare evidence, category, and priority; change one rule at a time.
  7. Save only when reviewers can explain the edge cases and verify the saved result.

Signalist Configure signal scoring step 2 product view.

Safety checks

  • The entity, source, date, company fit, persona fit, and priority were reviewed.
  • The saved configuration or status was verified after refresh.
  • Ownership and the next action are explicit.
  • Outreach remains separate until recipient, copy, sender, limits, and history are reviewed.

Signalist Configure signal scoring step 3 product view.

Troubleshooting

ProblemSolution
Personal or irrelevant posts become signalsAdd them to DQ examples and restrict Lead updates to relevant business context.
Company and Industry updates are confusedCompany updates must primarily concern the target organisation; Industry updates concern wider market or regulatory context.
Priority changes are lostVerify the saved state after reload and preserve the test case for support if it does not persist.

Frequently asked questions

What belongs in Lead updates?

Person-level business changes or statements relevant to the approved use case.

What belongs in Company updates?

Events primarily about the target organisation.

What belongs in Industry updates?

Wider market, technology, or regulatory context that is relevant to the account strategy.

How should P1 be defined?

Use the strongest approved threshold and concrete examples; keep it rare.

Why use negative examples?

They help reviewers and configuration distinguish plausible but irrelevant or unsupported activity.

When is configuration ready?

When representative tests are stable, saved correctly, and reviewers can explain boundary cases.