An applicant-tracking integration should attach call outcomes to the correct candidate and vacancy without changing hiring status unintentionally. Candidate identity and application context are separate parts of the mapping.
Define the permitted outcomes first: availability captured, callback requested, contact correction, question for recruiter, or verified interview scheduling. Keep stage changes and selection decisions outside this administrative path unless separately authorized.
Verify the current ATS model
Greenhouse's current candidate reference distinguishes a person's profile from applications. Its note-creation reference describes linking notes to a candidate and optionally an application. Review current documentation, permissions, and account configuration for your chosen platform rather than copying an old integration example.
Use stable identifiers and validate that the application belongs to the candidate and intended client. A name match or shared phone number is insufficient for a consequential write.
Work through a fictional multi-application call
A candidate has two active applications and asks to change interview availability for one role. The integration identifies that application, records the candidate's stated windows, and creates the approved coordinator task or note.
It does not overwrite availability for the other application or advance either hiring stage. After a timeout, it reconciles the note or action before retrying, using supported identifiers and local action history.
| Integration case | Required evidence |
|---|---|
| Several applications | Correct vacancy context |
| Candidate-level correction | Approved profile-field scope |
| Application-specific question | Correct application linkage |
| Write outcome unknown | Reconciliation before duplicate action |
| Permission denied | Visible pending task and owner |
Keep call status separate from ATS status
A completed call can leave a pending remote update. Track local intent, attempted operation, remote identifier, and final result. Staff need a recovery queue rather than a silent success flag.
Direct writes reduce recruiter entry work while requiring careful field mapping and access controls. A staff-reviewed staging queue can be a better first release when matching or permissions are uncertain. Grant only the operations the approved workflow needs.
Review duplicate action prevention for retry and uncertain-write handling that also applies to recruitment integrations.
Questions about ATS connections
Should a call completion advance an application?
Not unless an explicit authorized workflow requires that transition and its conditions are verified.
Can summaries be stored as interview feedback?
Use the platform's intended operation and the organization's approved purpose. Administrative notes should not masquerade as a formal assessment.
What should recruiters see when synchronization fails?
The original administrative request, correct context if verified, attempted update, outcome category, and owner for reconciliation.