From application to first contact

Two roles, one candidate record

Arthur reviews applications and analyses experience. Lisa contacts candidates and guides them through recruitment. Their applicant tracking system (ATS) centralises records, but finding the history, comparing information and recording analyses takes time. They want to keep their working methods without endless copying and pasting.

An analysis guided by the role’s criteria

Arthur selects the Recruitment / Analysis context in Witkeep and asks it to prepare unprocessed applications he can access. The context’s documents and skills describe the job criteria and expected format. Configured masking rules are applied to the relevant personal data. Witkeep proposes a structured analysis of experience and points to explore; Arthur remains responsible for the assessment.

Arthur edits, Witkeep saves

Arthur reviews the analysis, checks the information and adds his observations directly to the answer. He then asks Witkeep to save this version to the candidate records in the connected ATS. Available actions depend on the connector and his permissions. He verifies that it has been saved, then shares the conversation with Lisa.

Lisa takes over with the history

Lisa can see Arthur’s analysis and changes. She selects the Recruitment / Contact context and asks for draft messages. The method includes checking previous contact in accessible sources. Witkeep can therefore highlight a past exchange to take into account, instead of treating the candidate as a new contact.

Messages to review before use

Lisa adjusts the tone and content, then decides what happens next. Sending and scheduling options depend on the available connections. The analysis, candidate record and contact preparation remain linked, while recruiters retain control over communication and decisions.

What changes

This use case shows how application analysis, ATS data, message preparation and teamwork are closely connected.