Skip to main content

The problem this solves

A recruiter opens a job on Monday, has a shortlist by Tuesday, and then loses an afternoon writing a connection request, three emails and two LinkedIn messages before the first person is contacted. Most of that writing is the same every time: who you are, what the role is, where it is, why it is worth a conversation. Yena now writes that first draft for you, from the job you already entered. You keep the last word on every sentence, and nothing goes out until you switch sending on.

One click on the job

Campaigns tab of a job in Yena with the New campaign button and two existing campaigns

The Campaigns tab of a job lists its campaigns; New campaign creates one from the job in one click

  1. Open the job and select the Campaigns tab.
  2. Select New campaign.
  3. A small window asks Add people from. Pick a pipeline stage to put the people in it into the campaign, or Start empty. The window says how many people will be added and that nothing is sent until you start the campaign.
  4. Select Create campaign.
Create a campaign for Head of Finance: Add people from Screening (1), 1 person will be added

Add people from a pipeline stage, or start empty. Nothing is sent yet.

Yena names the campaign after the job, links it to the job and its company, builds the sequence, and opens it. The same happens when you pick Add to campaign on a Sourcer slate and choose the job.

What you get

Sequence editor in Yena showing the generated steps: LinkedIn connection request, then email two days later

Six steps, pre-filled from the job, ready to review

The sequence always has the same six steps. LinkedIn first, then email and LinkedIn take turns, about two weeks in all: Every message is filled in. The text uses the job title, the company, the location and the facts in the job description. It never invents a fact that is not in the job, and it never uses a candidate’s own data: personalization comes from the six insert fields, so First name and Formal salutation (German) are filled per person at send time. Language. If the job text is mostly German, the sequence is written in formal German (Sie). Otherwise it is English. If Yena cannot tell, it uses your workspace language. Sender. If you have exactly one connected LinkedIn account and one mailbox, they are set on the steps. Otherwise the step says Connect LinkedIn or Choose a sender, and the setup strip names what is missing.

The rules built into the sequence

  • A reply ends everything. Any reply, on any channel, takes the person out of the campaign. The remaining steps are cancelled.
  • Not accepted within 7 days: move on by email. If the connection request is not accepted after seven days, that step is skipped and the person continues with the email steps. The LinkedIn messages wait for an acceptance and are skipped if it never comes.
  • Already connected: no request. If the person is already a first-degree connection, the request is skipped and the messages go straight through.
  • Unanswered requests are withdrawn after 30 days. Too many open requests can get a LinkedIn account restricted. You can change the number of days, or turn this off, in the sequence settings.

Review before you start

Read the six messages the way the candidate will. Change any sentence. Use Test one message to see one step rendered for one real person. Then switch sending on: the same readiness checks apply as for any campaign, so a missing sender or an empty step blocks the start and says why.
Add people first, then read the messages once more with a real name in mind. A sentence that reads well in the editor can land differently for a candidate two levels above the role.

Read the campaign from the steps

Once the campaign runs, every step card ends with one line: N people waiting here · N sent · N replied after. Below the last step: N people finished all steps. Each number is a link. Select it and the People tab shows exactly those people; Show all clears the filter. “Replied after” credits the step that was sent last before the person answered. It is the fastest way to see which message does the work.

The job is the hub: replies move people on the pipeline

A campaign that is linked to a job does not live next to your pipeline. It works on it. When someone in the campaign replies, Yena moves them on the job’s pipeline to the stage you chose for campaign replies.

A day with it

Laura is an executive search consultant in Munich. She runs a Head of Finance mandate with a campaign to 40 people in the pipeline stage Screening. Before, she watched her Inbox and dragged each person who answered to the next column by hand. On busy mornings the board was an hour behind her Inbox.
1

Once, an admin chooses the campaign stage

In Tenant Admin → Stages, the admin points at a stage, for example Interview, and clicks Make this the campaign stage. The stage now carries the badge Campaign stage. Only workspace admins can set it. Hired and Rejected cannot be the campaign stage.
Candidate stages with a Campaign stage badge on Screening and the icons shown when hovering Interview

Hover a stage and use the campaign stage icon. Screening carries the badge Campaign stage here.

2

Laura works as usual

She starts the campaign and reads the answers in the Inbox. A reply still takes the person out of the campaign, exactly as before.
3

The person moves on the job's pipeline

When a person replies, Yena moves them to the campaign stage on every job the campaign is linked to. The job’s activity records it, for example: moved them to Interview on Head of Finance after they replied to a campaign. A person who has no application on that job gets one, in the campaign stage.
4

Laura opens the board and sees who answered

The board refreshes when she returns to the tab and about once a minute. The people who replied are in one column, ready for her call.
What Laura gets: the pipeline reflects the campaign without her touching it, and she sees at a glance who answered.

Rules

  • Only forward. A person is moved only if they are in an earlier stage than the campaign stage. Someone you have already moved further is never moved back.
  • Never into Hired or Rejected. If the campaign stage is later turned into one of those, replies are not moved.
  • Without a campaign stage, nothing moves. That is how it works until an admin chooses one.
  • Choosing or changing the stage. People who replied earlier move once, to the stage chosen now. Changing the stage later does not move people again.
  • Link after the reply. If you link a campaign to a job after people replied, those repliers move too.
  • Unlinking a campaign does not move anyone back.
To take the setting away, click the x on the Campaign stage badge (Unset the campaign stage). Replies then no longer move anyone.

Where to go from here