You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Preventing Duplicate Candidates

edited Jul 13, 2017 1:23PM in Taleo Enterprise 5 comments

Summary

Duplicate Candidate Check SetUp

Content

Hi Everyone,

Since we have gone live with Taleo (Sep/2015) we continue to have so many duplicate candidates (sometimes candidates creating up to five profiles).   I checked our duplicate check and we are set to

First Name AND Last Name AND Phone Number OR Email Address OR Social Security Number.   We don't collect SSN at time of application, so that really isn't necessary.

My question is how is your duplicate candidate check set up?  Is it successful in preventing duplicate candidates?

I'm thinking we should do Email Address AND First Name AND Last Name (and maybe Phone Number).

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!