A phone number can belong to several candidates, a household, or a recruiting contact shared by a group. Use it to search for candidates, not as a globally unique identity key.
Define matching policy before enabling automatic creation. Keep person identity, contact methods, applications, and client vacancies separate. One person can have multiple applications without being a duplicate candidate.
Use conservative creation and merge boundaries
Search within the authorized organization or client context and use approved confirming facts. If several candidates remain plausible, create a review item rather than attaching the call to the first result or merging records.
Greenhouse's candidate API documentation describes candidate profiles and their application relationships. The exact operations vary by ATS, so verify the current model and supported matching fields for your implementation.
Work through a fictional shared household number
Two siblings use the same home number and apply for different jobs. A call about interview availability returns both candidates. The agent clarifies the intended person and vacancy under the approved process.
It should not overwrite one sibling's email, combine applications, or create another profile merely because the first search was ambiguous. If identity remains unresolved, staff receive the call context and matching question without unnecessary disclosure of the other candidate's data.
| Match situation | Required result |
|---|---|
| One clear verified candidate | Use existing profile |
| Shared number, several people | Limited clarification or review |
| Same person, new vacancy | New application decision, not assumed new person |
| No reliable match | Approved staged creation or review |
| Duplicate-looking records | Staff-owned merge process |
Make retries safe as well as matching accurate
Persist the intended creation action and resulting remote identifier. If creation times out, reconcile before sending another request. Good identity policy cannot prevent duplicates caused by blind retries after an uncertain write.
Strict review creates recruiter work, while loose automatic matching can corrupt records and expose another person's application. Set the boundary according to the action and quality of the available evidence.
Test shared numbers, changed names, recycled contact details, and several applications. Review duplicate remote-action prevention for creation recovery.
Questions about candidate duplicates
Should email be the only identity key?
It can be a useful signal but should follow the organization's approved matching process and account for changes or shared addresses.
Can the agent merge records automatically?
Leave consequential merges to an authorized reviewed process that preserves history and relationships.
What should staff receive for an uncertain match?
The candidate-provided facts, relevant vacancy, safe contact route, candidate ambiguity, attempted actions, and owner. Avoid copying private information from every possible match.