Connecting the Volnamista.cz Publication Channel

A publication channel is used to share job listings across systems, or to create a collaboration point with agency portals. Here we will show how the XML principle works when setting up a publication channel for the Volnamista.cz portal. For other portals operating on the XML data principle, it is similar.

Here is a link to the article with an overview of portals and integration methods.

1. Creating a publication channel for publishing positions on the Volnamista.cz portal

The first step is to create a new publication channel. In the "Settings" menu, select "Publication Channels" (link)

You can create a channel using these steps:

• select "Add new publication channel"
• enter the publication channel name - in this case, e.g., "volna mista"
• you can also enter an email address for notifications about new positions (not desired in this case)
• finally, select the listing format, which is the format in which position data will be displayed on this channel - in this case for Volnamista.cz, we will leave the default setting

The automation feature allows you to add or remove tags depending on the candidate's status - typically when creating a candidate's response to a specific position, you want to add a certain set of tags, and conversely, remove them upon rejection.

Another typical scenario is sharing with hiring managers or HR business partners - you know that you share candidates only when they progress, for example, past the pre-screening stage - you can now set this up and don't have to handle it manually.

SMS Queue

In addition to recording information in the action history for a specific candidate, the mobile app also has an SMS queue. This stores both SMS messages to be sent (you must send the SMS from the queue directly on your phone - clicking send will open the standard SMS sending dialog), as well as sent SMS messages. The red icon with a number then shows how many SMS messages you have in the queue to send.

💡 Since operating systems do not allow monitoring of SMS sending, information about sent SMS in the action history and in the SMS queue in the Recruitis app means that the SMS was sent from the queue in the Recruitis mobile app, not necessarily that it was physically sent to the recipient from your phone in your SMS app.

3. Adding a position to the publication channel

After the portal, in this case Volnamista.cz, activates the publication channel on their side, you can start publishing positions. Publishing is done by selecting the "volna mista" publication channel for a specific position. The method differs for newly created positions and already existing positions.

1. Setting up publication while creating a new position

In the last step when creating a position, we enable the "volna mista" channel in the "Publish to custom publication channels" section. For the given channel, we can also set the required expiration date.

2. Setting up publication for an already existing position

In the actions menu for the given position, click on the icon named "+ Set publication channels".

Here we enable the publication channel in the "Add listing to these XML outputs" section, set the expiration date, and save with the "Save changes" button.

Alternatively, the position ID can be obtained directly from the link in the browser if you have the detail of the given position displayed, e.g.: https://app.recruitis.io/zadavatel/inzeraty/detail/123456

Adding a webhook from Volnamista.cz

To add a new webhook, open Settings | Webhooks. First, select the webhook type and insert the full URL address of the page from the Volnamista.cz settings where you want to receive notifications about changes. If the entered page actually exists and can receive notifications, clicking "Test" will test the connection. After successful testing, the button will change to "Save".

Purpose

The purpose of this report is to display activity with candidates according to various criteria and filters.

Principle of Value Display

The report displays activity with candidates that occurred in the monitored period and which we measure through movement within the recruitment flow. Thus, each "1" in the report means that 1 candidate was moved to a given state in the recruitment flow.

In other words, the report does not show only the current state where the candidate is, but their history of movement through recruitment process states. If a candidate was moved 3 times to the next state in the given filtered period, they will be recorded 3 times, once in each state they were moved to.

I can therefore track, for example:

• Quantitative indicators of the recruitment process such as:
  • How many new candidates we had
  • How many interviews we conducted
  • How many offers we made
  • How many candidates we hired

• Performance of candidate sources such as:
• • What were the sources of candidates for back office positions who got at least to an interview in the current quarter?

• Analysis of rejection reasons
• • How quickly were we able to find out that a candidate has higher salary expectations for IT positions at headquarters over the past year?
  • What are the rejection reasons and their frequency in individual recruitment phases for IT positions at headquarters over the past year?

The report's explanatory power and conclusions we can draw from it are closely related to the recruitment flow setup and also to the care and systematic approach to state changes. Thus, if you move every candidate who receives an offer to a "Selected" state, you can then easily draw conclusions about the number of offers.