The Wiggli sourcing workflow: from prompt to first reply
Sourcing in Wiggli isn’t a single feature, it’s a sequence: search, shortlist, enrich, engage. Each step feeds the next, and the handoffs are automatic.
PUBLIC · Concept Explainer
Why it matters
Section titled “Why it matters”Most sourcing stacks force you to switch between tools that don’t talk to each other. You search in one place, save names in a spreadsheet, look up emails in another tool, draft outreach in a third, then track replies in your ATS. Every handoff is a chance to lose context, or lose the candidate.
The Wiggli workflow treats search, shortlisting, enrichment, and outreach as one continuous motion. The payoff isn’t fewer clicks. It’s a shorter path from “this looks like a fit” to “they replied.”
The four stages
Section titled “The four stages”1. Search
Section titled “1. Search”Start with a Smart Prompt, a job description, a sample CV, or manual filters. Refine with AI title suggestions, location radius, and industry. Bulk-add the strong profiles to a Project.
2. Shortlist
Section titled “2. Shortlist”Inside the Project, the AI Co-pilot screens like a junior recruiter. Career summaries, open-to-work checks, and custom Intelligence Columns assess profiles against criteria your filters can’t capture. Bulk-filter down to a real shortlist.
3. Enrich
Section titled “3. Enrich”Reveal contact information. Wiggli queries 20+ data providers in sequence until it finds verified emails and phone numbers. Credits are spent only when contact info is found.
4. Engage
Section titled “4. Engage”Push the shortlist into an outreach campaign. Multi-step, multi-channel: email, LinkedIn, WhatsApp. Campaigns auto-stop on reply. When a candidate is ready, push them to the ATS in one click.
Common misconceptions
Section titled “Common misconceptions”You don’t have to use all four stages. Some recruiters go search, enrich, outreach and skip projects. Others go search, project, ATS and skip outreach. The sequence is a default, not a forced path.
You’re only charged when contact info is found. Search, project creation, AI Co-pilot work, and pushing to the ATS don’t consume credits. Credits are spent only when a reveal returns a verified contact and you save it.
A project is not a campaign. Projects are for screening and shortlisting. Campaigns are for outreach. You move profiles from project to campaign once they’ve passed screening.
Adding someone to a campaign doesn’t send anything yet. New campaigns start OFF by default. You build, review, and turn them on when you’re ready.
Order matters: enrich before campaign, not after. Adding profiles to a campaign before revealing their contact information leaves them stuck with a contact details needed flag, and the campaign can’t send to them. The fix: select those profiles in the campaign, remove them, go back to the project, reveal contacts, then add them back to the campaign. No work is lost. The cleaner habit is to do all reveals from inside the project (one bulk action) before pushing the shortlist to a campaign.
Related articles
Section titled “Related articles”Still stuck?
Your customer success manager reads faster than any search bar.