Skip to content
WiggliWiggli Knowledge Base
Projects & AI Co-pilot

Run AI Co-pilot presets on a project

Common screening signals generated for every candidate in a project: career summary, open to work, likely to switch, job hop risk, key skills.

CLIENT-ONLY · How-To

Outcome

Section titled “Outcome”

Preset Intelligence Columns (the yes/no/unclear columns the AI Co-pilot adds to your project) filled in for every candidate, so you can skim and prioritize fast.

Prerequisites

Section titled “Prerequisites”
  • A project with candidates added

Steps

Section titled “Steps”
  1. Open the project and open the AI Co-pilot panel.
  2. Choose a preset:
    • Career summary — a short summary of the candidate’s career
    • Open to work — whether the profile shows an open-to-work signal. This checks the LinkedIn signal one to one, so it needs a public LinkedIn profile; fully private profiles come back unclear
    • Likely to switch — a different, broader signal than open to work: behavioral patterns such as a candidate who moves every two years with the mark approaching, or recent management changes at their company
    • Job hop risk — flags frequent movers
    • Key skills — the most relevant skills pulled from the full profile
  3. Confirm to run. The Co-pilot processes profiles one by one; larger projects take longer.

[SCREENSHOT: AI Co-pilot panel with preset options]

Verification

Section titled “Verification”

A new column appears:

  • Career summary: short text per row
  • Open to work / Likely to switch / Job hop risk: yes, no, or unclear with a one-sentence reason
  • Key skills: a tailored skill list

Troubleshooting

Section titled “Troubleshooting”
  • Preset grayed out. Check your plan. AI Co-pilot is included from Explorer, but custom column limits differ by tier.
  • Column not appearing. Refresh the project view.
  • Many “unclear” answers. The Co-pilot judges from available profile data. Sparse profiles produce “unclear”. Spot-check the reasoning.
  • [GAP: confirm re-run behavior, does it overwrite, append, or update only new candidates?]

Best practices

Section titled “Best practices”
  • Layer presets: Career summary to skim, then Open to work to prioritize outreach order.
  • Filter the project by the column to bulk-shortlist. The reliable pattern is two Co-pilot instructions in sequence: first “assess if the profile has [X]” (the column appears), then “filter out the profiles without [X]” on that column. Asking the Co-pilot to filter on a criterion it hasn’t assessed yet is what produces empty results.
  • Re-run after adding new candidates to keep columns complete.
Section titled “Related articles”

Still stuck?

Your customer success manager reads faster than any search bar.

Get help