> Configuring autoqualify on a signal

TL;DR: Each signal has an Autoqualify toggle. Turn it on and captured records score against your ICP / Persona rules automatically. The Autoqualify column on the Signals page shows the state at a glance.

Expand

What autoqualify does

When a signal captures a record (a person + a behavior + a timestamp), one of two things happens:

• Autoqualify ON — the record runs against your live ICPs and Personas immediately. If it matches, it lands in Leads (or Accounts) with its ICP code, Persona code, and scores populated. From there it's a candidate for audiences, enrichment, and destinations.
• Autoqualify OFF — the record lands in a holding state on the signal itself. You can run qualification on demand from the Signals page (Run qualification) or from Copilot (> qualify the last 200 captures from the Keywords signal).

You almost always want it on. The off mode exists for two cases: (1) you're testing a new signal and want to inspect raw captures before they hit your ICP, (2) the signal's source quality is unknown and you want to avoid polluting your record set.

Turning it on

Two paths.

On the Signals page:

1. Open Signals from the sidebar
2. On the row for the signal you want, look at the Autoqualify column — a checkbox
3. Click to toggle on. The change saves immediately; new captures from this point forward will autoqualify

With Copilot:

> turn on autoqualify for the Replies, Demo Viewed, and Keywords signals

Bulk toggle

The toolbar above the Signals table has an Autoqualify master toggle in the top-right (next to the View switcher). Click to toggle all signals on or off in one move. Useful when you're spinning up a new workspace or pausing all autoqualify for an ICP overhaul.

How autoqualify interacts with your ICP rules

Three rules to internalize:

• Autoqualify uses the LIVE version of your ICPs and Personas. If your ICP is in Draft, captured records won't match it. Publish the ICP to Live before turning on autoqualify on any signal.
• Filter-mode parameters are gates. If a captured record fails a Filter parameter on the ICP, it doesn't qualify against that ICP at all — even with autoqualify on.
• Persona match is required for full qualification. A record can match an ICP but no Persona; it lands in the No persona fit bucket inside Qualification. Useful to see, not actionable for outbound.

Reading the autoqualify column

The Autoqualify column on the Signals page renders one of three states per row:

• Checked — autoqualify is on
• Empty — autoqualify is off; captures wait for manual qualification
• Dash — signal status is Draft / Needs source; autoqualify is irrelevant until the signal can run

When to keep it off

Three legitimate cases:

• Brand-new signal type. First 24 hours, watch raw captures to confirm the source maps cleanly to your model.
• High-volume / low-precision sources. Some 2nd-party signals (Keywords on broad terms, Ad Frequency at the network level) can flood. Keep autoqualify off and run qualification in batches with a sample.
• An ICP rewrite in progress. If you're rewriting an ICP and the new version is in Draft, autoqualify against the old Live version still works — but the captures you autoqualify now won't be re-qualified against the new version automatically. Toggle autoqualify off during the rewrite, publish the new ICP, run a full re-qualification, then toggle back on.

Related

• What signals are
• Setting up your ICPs with Copilot
• Reading the signals table
• Parameter modes — Filter, Score, Exclude