Consort ATS

Integrations

The system fits into your stack

Job boards and messengers bring applications, calendars and mail schedule meetings, 1C payroll and e-signing onboard the hired. Data moves between systems by itself, with no manual copying.

Why it matters to you

Work in your own systems: the request flies into the ATS, the candidate leaves it into your stack

Nobody switches to a new interface for the sake of hiring. The hiring manager files a request where they are used to, HR ops get the employee in 1C, and the system connects everything in between

The request comes from your systems

Portal or API: a hiring request lands in the ATS and goes down the approval chain. The hiring manager sees the status in their cabinet

Candidates and meetings run in your channels

hh, the career site, Telegram and WhatsApp merge into one funnel with the source set. The interview is scheduled in the system and lands in everyone's Google, Outlook and Yandex calendars

The hire leaves into your stack

Documents collected in advance, the offer signed via e-signing, the employee created in 1C payroll with one click, the staffing table synced back into the system

The circuit

Five groups of connections and an open API

0integrations already live
0on the way, the plan is open
APIfor everything not on the list
app.consort-ats.com/settings/integrations

Job boards · Circuit · Consort ATS

Vacancy published on hh+3 applications in an hour
Dmitry K. · application · source: hh
Avito · soonRabota.ru · soonLinkedIn · soon

Circuit status

The full list with honest statuses

Green works today. Amber is in the open plan: you can see what we connect next.

Calendars & mail7/7
Google CalendarOutlook CalendarYandex CalendarExchangeGmailOutlook MailYandex Mail
Channels & bots3/3
Telegram BotWhatsApp BotCareer site
Job boards1/6
HeadHunterAvitosoonRabota.rusoonLinkedInsoonIndeedsoonBaytsoon
HR back office2/2
1C payrollE-signing
Government services0/3
GosuslugisoonEnbek.kzsoonMyGovsoon
livesoonOpen API: we connect whatever is missing
Scenario 01

An application becomes a candidate by itself

Wherever the person came from: hh, a bot, the career site, they end up in one funnel with the source set. A phone duplicate is never born: a repeat application attaches to the history.

  • Every channel into one funnel
  • The source records itself
  • Duplicates merge by phone
app.consort-ats.com/vacancy/pipeline
hh · application
Telegram bot · form
Career site · application
New: +3 candidates
Sources set, no duplicates
Scenario 02

An interview is scheduled once

The recruiter picks a slot in the system, the rest happens by itself: events land in the recruiter's and the manager's calendars, the candidate gets an invitation and a bot reminder. No forwarding and no 'does it work for you?' in five chats.

  • The slot is picked once, in the system
  • Events reach every participant at once
  • The bot reminds the candidate itself
app.consort-ats.com/calendar

HR interview · tomorrow 3pm

RecruiterManagerCandidate
The bot will remind 2 hours before
All calendars updated
Scenario 03

The hire closes in the HR back office

After the offer the routine does not restart: documents are signed electronically, the employee is created in 1C ZUP by a button, and the staffing table syncs back into the system. The loop closes without manual transfer.

  • The offer is signed electronically
  • An employee in 1C ZUP by a button
  • The staffing table returns by itself
app.consort-ats.com/candidate/hiring
Offer accepted
E-signing: done
1C ZUP: employee created
Staffing table updated
The loop is closed: no manual transfer

What it gives the business

Work in your own systems

What the link with your systems gives you: the requisition arrives on its own, the hired person moves into the HR contour without manual re-entry, and the data stays with you.

Requisition

A request from your portal, the status in your cabinet

A hiring request comes from the familiar system and goes down the approval chain: hiring manager, C&B, security. Nobody switches to a new interface for the sake of hiring.

Shown by:Request approval time

HR ops and 1C

From the market to 1C: the employee created with one click

Documents collected in advance, the offer signed via e-signing, the staffing table synced back into the system. The employee's start stops being manual work.

Shown by:Days from offer to start

Security

Data in your perimeter

Cloud with data in your country or On-Premise on your servers. Open API and webhooks for internal systems, data export at any time.

Shown by:Where the data lives, API

Numbers that agree

The source is set automatically, the numbers agree

Applications from hh, the site, Telegram and WhatsApp land in one funnel with the source set, the interview is scheduled once across all calendars. Source analytics comes out honest.

Shown by:Cost per application by source, meetings without clashes

Consort Group has been in recruiting since 1992. We close vacancies in this system ourselves every day, so every feature is proven on live hiring

Discuss the link with your systems
60 minutes live

Integrations, live

A request from your portal, applications from hh and Telegram, the hire landing in 1C payroll: the whole path on the demo stand

Expert15 min
Mass15 min
Analytics15 min
Agents15 min

Let's start

Let's map your systems

We draw the map: where the request comes from, where candidates and calendars live, where the hire goes. We say plainly what connects right away, what goes through the API and what is on the roadmap.

1Map of your stack2Scenario presentation3Integration plan

Or write to us

The quickest reply comes to a request through the form: it reaches the team right away together with your topic.

Request: integrations

By submitting the form you agree to the privacy policy.