What gets synced between Intelligence and ATS
A defined set of candidate data flows from Intelligence to the ATS, not the entire profile, so both systems stay clean.
CLIENT-ONLY · Concept Explainer
Why it matters
Section titled “Why it matters”Most sourcing-to-ATS handoffs are either too thin (only the email passes, recruiters re-enter everything) or too messy (every search result floods the ATS). Wiggli’s integration sits in between: a deliberate set of fields carries over, the rest stay in Intelligence.
The result is an ATS holding qualified, contactable candidates against real vacancies, not a graveyard of sourced profiles.
What syncs to the ATS
Section titled “What syncs to the ATS”When you add a candidate, the following move with them:
- Full name, current job title, current company, location
- Revealed contact info (primary email and phone, when present on the profile)
- LinkedIn profile URL
- Notes added during export
- Source attribution (sourced via Wiggli Intelligence)
- Vacancy and pipeline stage assignment
- Wiggli generated CV
What doesn’t sync
Section titled “What doesn’t sync”- Real-time profile updates (the ATS holds a snapshot from export time)
- AI Co-pilot Intelligence Columns (these stay in the project)
- The search criteria that found the candidate
How updates work
Section titled “How updates work”The integration is one-way, Intelligence to ATS. After a candidate is in the ATS:
- ATS-side changes (stage, scorecards, interviewer notes) stay in the ATS
- Profile changes in Intelligence (new job, new skill) don’t auto-refresh the ATS record
- Re-adding the same candidate to the same vacancy will update the existing profile
ATS awareness in Intelligence
Section titled “ATS awareness in Intelligence”While candidate data flows one way (Intelligence to ATS), Intelligence does surface a small set of signals back from the ATS to help recruiters avoid duplicate work and credit waste.
- Already in ATS tag. When a profile in a search result or project view is already present in your connected ATS, Wiggli shows an
Already in ATStag next to the profile, alongside the ATS logo (e.g. Wiggli ATS, TeamTailor). This appears before you reveal contact info, so you can decide whether to spend credits on someone you already have. The tag reflects the connected ATS only; profiles in other systems aren’t flagged. - Profile activity history. Each profile carries a per-profile activity log visible in the slide-out view. The log shows what teammates have done with this profile: added to a project (which one), reveal performed, outreach sent (channel and date), pushed to ATS (vacancy and stage). The history is workspace-wide, so a recruiter picking up a profile can see whether a colleague has already touched it.
Both signals are passive. Wiggli does not actively notify you when a teammate contacts a profile, and there’s no inbox view for these events. They appear inline when you’re viewing the profile or scanning a list.
Common misconceptions
Section titled “Common misconceptions”It isn’t two-way. Intelligence pushes to the ATS; the ATS doesn’t push back (yet 😉).
The ATS record doesn’t auto-update. It’s a snapshot from export. To refresh, re-add or update the ATS record manually.
Projects don’t sync automatically. Adding to a project is internal. ATS push is a separate, explicit action.
Intelligence Columns don’t appear in the ATS. Co-pilot work stays in the project.
Related articles
Section titled “Related articles”Still stuck?
Your customer success manager reads faster than any search bar.