Skip to main content

Configure project settings

From a project's Configuration tab, you can adjust all targeting and communication settings.

General settings​

Politeness and tone​

  • Politeness — Choose formal or informal tone for your messages
  • Period — Temporal context used in messages (e.g., "at the beginning of this year")

Job offer details​

  • Job title — Title of the open position
  • Vision — Short description of the opportunity
  • Grade — Hierarchical level of the position

This information is automatically used in your message templates via Jinja2 variables.

Targeting filters​

Experience​

FilterDescription
Target experience min/maxMonths of experience in positions matching the tags
Total seniority min/maxTotal months of professional experience
Maximum CV gapMaximum duration (in months) between two positions

Location and companies​

FilterDescription
LocationTarget geographic area
Excluded companiesCandidates currently working at these companies are ignored
Required companies (current)The candidate must currently work at one of these companies
Required schoolsThe candidate must have studied at one of these schools
Required past companiesThe candidate must have worked at one of these companies

Message templates​

Messages are Jinja2 templates that are automatically personalized for each candidate.

Available variables​

VariableDescription
{{candidate.firstname}}Candidate's first name
{{candidate.lastname}}Candidate's last name
{{candidate.title}}Candidate's current position
{{candidate.company}}Current company
{{recruiter.firstname}}Your first name
{{recruiter.lastname}}Your last name
{{offer.title}}Job title
{{offer.vision}}Opportunity description
{{politeness}}Greeting formula
{{booking_url}}Interview booking link

The 5 contact scenarios​

The library is organised by contact scenario: the conversational situation a message answers. Each scenario holds a sequence of messages, sent in order.

ScenarioKeyWhen it is sent
Outreach — first contacthunt_1, hunt_2, …After the invitation is accepted, in sequence, for as long as the candidate stays silent
Follow-up after a replyreconnect_1, …The candidate replied, then the conversation stalled
Booking a meetingmeet_1, …To schedule a call — carries the {{booking_url}} link
Answering a refusalnot_interested_1, …The candidate declines the opportunity
Asking for clarificationwaiting_precision_1, …The candidate's reply is ambiguous or incomplete

The key prefix names the scenario, the numeric suffix the rank in the sequence: hunt_3 is the 3rd message of the outreach sequence.

Where your messages come from​

You do not have to write anything to get started: a standard library ships with the product. Three levels stack, from the most specific to the most general:

  1. The campaign's messages — what the Templates tab shows. They are copied when the campaign is created and belong to it: editing them affects that campaign only.
  2. Your organisation's library — Organisation → Campaign defaults. It pre-fills every new campaign. Editable by an organisation administrator.
  3. The RecrutAuto standard library — the shipped baseline, used until your organisation defines its own.
A change only applies to campaigns created afterwards

Editing your organisation's library does not touch campaigns that already exist: each keeps its own copy. To change a message on a running campaign, edit it in that campaign's Templates tab.

Likewise, a candidate already engaged in a sequence carries on with the messages computed when they entered it.

Using a message in a conversation​

From the inbox, the right message is one click away:

  • RecrutAuto pre-fills the composer with the message matching the candidate's current stage. A Suggestion banner flags it; ✕ dismisses it.
  • The templates icon opens the campaign's full message list, grouped by scenario.

Either way the message arrives already personalised (first name, company, booking link…) and stays freely editable before you send it.

tip

Preview your messages before launching the campaign. Use a personal tone and avoid overly generic messages.