Skip to content

HR and Recruitment CRM

When a position closes, the dozens of qualified candidates interviewed for it close with it. When the same profile is sought again months later, the process starts from scratch.

Every candidate is a record; the CV, the position applied for and the interview score sit on one card. A rejected candidate is not deleted — mark the pool field and they return for the next opening.

HR and Recruitment CRM
  • Gather CVs arriving from careers sites and e-mail into a single candidate database, by hand or with a bulk import
  • See the candidate flow of every open position step by step, and measure how many candidates were rejected at which point
  • Digitise the interview calendar and the assessment forms, and tie the scoring to the candidate card
  • Take rejected but qualified candidates into the talent pool, and look there first for a new position
  • Run correspondence with candidates over a single business number and the team inbox, so the history stays on the record even when staff change
Candidate RecordEvery candidate is a record; the position applied for and the application source sit in its fields, and the CV file is attached to the same record; past applications accumulate under the same card.
Recruitment StagesA position is a record and candidates are tied to it; the stage is a field, and how many candidates were rejected at which step is read from the report on that field.
Interviews and AssessmentAn interview is an activity tied to the candidate record; the date, the interviewer and the score are in its fields, and the assessment form is recorded on the same record.
Talent PoolA rejected candidate is not deleted; once the pool field is marked, they appear on a list filtered on that field when a new position opens.
Offer Letter and Acceptance RecordThe job offer made to a candidate is an offer tied to the candidate record; salary, start date and validity period sit in fields, the candidate who accepts signs on the signature screen in the mobile app, and the reasons for rejected offers accumulate on the same record.

In recruitment, information scatters channel by channel: the application sits on the careers site, the reference comment in e-mail, and the interview score in the notebook of the person who ran the meeting. At the weekly meeting, the answer to the question of where each position is stuck is compiled by hand every single time — and it cannot be compiled at all when the person who compiles it goes on leave.

Rapitek CRM grows the candidate record in the same file from application to offer; the form and score of every interview are recorded in that file, and the funnel itself is not prepared separately. The processing and storage of candidate data is carried out in line with KVKK requirements; because the application date is a field, candidates whose retention period has expired drop onto a list and are closed out with a bulk deletion or anonymisation step.

Frequently asked questions

Can it pull CVs in automatically?
We connect your careers site and your e-mail inbox to the CRM — we build the connection. There is no out-of-the-box module: because the access and field structure of every careers site is different, the connection is built specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export; its scope and cost are shared in writing in the discovery call. Even without this connection, the candidate record and the CV file are added to the candidate card by hand or with a bulk import; after that, the position stages, the interview form, the scoring and the talent pool all run on the same card.
How are interview assessments done?
You can create customisable assessment forms and gather interviewer notes and scores digitally.
Is it KVKK compliant for Human Resources?
The storage and processing of candidate data is carried out in line with KVKK requirements. Because the application date is a field on the candidate record, candidates whose retention period has expired drop onto a list on that field; you close the list out with a bulk deletion or anonymisation step. There is no deletion engine that runs by itself; you define the period and the step, and the operation leaves a trace in the change history. Hosting is in the European Union: the database in Finland, media files in Frankfurt. This counts as a transfer abroad under KVKK art. 9; that is why we run disclosure and explicit consent processes.
Can more than one person in the Human Resources team use the same WhatsApp number?
On the Human Resources side, correspondence with candidates runs from a single business number; even when staff change, the history stays on the record. Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. Meta invoices you directly — we do not sell message bundles or credits.
Made with RapitekGO

We would like to use optional cookies to measure your visit. The site works exactly the same if you decline. Cookie policy