The candidate profile in TRAFFIT is where you can find all the information you collect from the application forms and during interviews with candidates.
How is a candidate profile in TRAFFIT created?
A candidate profile in TRAFFIT is usually created automatically when he applies via the application form created in TRAFFIT. Such a profile is visible in the Candidates tab.
A candidate profile can also be created:
manually, in Candidates tab (blue Add candidate button in the upper, right corner),
manually, on the list of candidates in a specific job (blue Assign candidate > Add and assign candidate button in the upper, right corner)
manually, in Candidates > From e-mail tab,
manually, using TRAFFIT's sourcing plugin,
manually, by .CSV file import (data migration),
manually, with CV parser - by uploading CV's from your computer,
automatically, when the candidate fills out the spontaneous application form,
automatically, using API,
automatically, using Zapier.
How to open a candidate profile in TRAFFIT?
To open a full candidate's profile in TRAFFIT, click on his avatar on any list.
You can find the full list of candidates in the Candidates tab, but you can also access a candidate's profile from the list of candidates in a specific job or from the quick application preview in a job:
What information can you find on the candidate profile in TRAFFIT?
Every candidate profile in TRAFFIT includes the following tabs:
Summary
Personal data
Jobs
E-mail history
SMS history
Files
Consents
Each tab is described in detail below. Depending on your permission group:
visibility of certain information,
accessibility of certain activities,
on the candidate profile might be restricted. You may, for example, not have access to the e-mail history of the candidate or the possibility to export data to an XLS file.
Summary of the candidate profile
On the left, under the candidate's avatar, you can see:
basic contact information: phone and email (clicking on the email address will take you to the e-mail creation module),
a list of tags assigned to the candidate, with the possibility to assign new tags and delete existing ones,
the list of Talents the candidate is assigned to, with an option to manage them,
a list of application sources - if the candidate applied with application forms; here you will find the history of the applications, with dates and sources,
candidate's id (unique identifier in the database,
date of creation and last personal data update.
What more can you do on the candidate summary?
add a note or other activity related to this candidate (PROTIP: when creating a note, use the "@" sign to tag any user in it),
view a timeline with all the activities on his profile,
view the most recent CV file,
view a list of all the jobs to which this candidate is or has ever been assigned. If there are more than 3, you will find the full list and history in the Jobs tab (PROTIP: Click on the name of the job if you want to see its details or use the icons next to the name of the job to change the stage of this candidate in this job),
send an e-mail to this candidate,
share this candidate's profile,
add a calendar event related to this candidate,
perform any of the additional activities visible under the 3 dots icon:
Personal data on your candidate profile
This tab contains all the candidate information you collect on application forms and during interviews with candidates.
You can manage the list of sections and fields visible in this tab in Settings > Field Configuration > Candidate > Candidate profile.
They are unlimited and you can change them any time to suit your needs!
Jobs on candidate profile
This tab contains a full list of the jobs to which this candidate is assigned - both open and closed. Whether they applied via a form or were manually assigned to that job.
You can select if you want the list to be collapsed/expanded by default and click on the job name to see the entire path of the candidate in this project:
You can manage the candidate's stages in the jobs from the level too - by using the navigation next to the current stage. You can also move the candidate between stages by clicking on the names of other stages.
E-mail history on the candidate profile
If you integrate your mailbox with TRAFFIT, one of the benefits of this integration will be access to the history of your e-mails with the candidate right in this tab.
You will see chronologically arranged correspondence between the candidate and you or other users who decided to integrate their mailboxes:
Each email will also appear on the candidate's timeline in the Summary tab.
SMS history in the candidate profile
Along with the e-mail history, here you will see the history of SMS messages:
sent,
scheduled to be sent
from the system to this candidate:
Here you can find instructions on how to start using TRAFFIT's integration with SMSApi.
Files on candidate profile
This tab contains the applicant's files which:
were uploaded by the candidate on the application form,
were uploaded manually by the user,
were added automatically using the API (e.g. as a result of integration with other systems).
You can download these files, view them (file preview will only be possible for documents), and share them along with the candidate profile to Hiring Managers:
You can attach as many files as you like here (max. 10 files at a time), and the weight of a single file cannot exceed 20MB.
Consents on candidate profile
Here you can check:
active
withdrawn
expired
candidate's consent and if and when the legal obligation has been fulfilled:
The top part of this tab contains a summary of consents, including the dates and jobs in which they were given. You can full information about the consents given Below the summary - including the content of the consents on the date they were given.
You can use the Add Consent to Candidate button visible under the 3 dot icon in this tab to manually assign consents to this candidate - e.g. when the consent is given in writing or a private message on LinkedIn:
This tab contains the applicant's consent which:
were given by the applicant on the application form,
were added manually by the user,
were added automatically by the API (e.g. as a result of integration with other systems).