You chose OTYS because you wanted one system for everything. Vacancy management, candidate database, career site, multiposting, matching, placement tracking. One login. One workflow. One source of truth.
And for most of the recruitment process, that is exactly what you have. OTYS handles the pipeline from the moment a vacancy is created to the moment a candidate is placed. Every step is tracked, structured, and accessible from the same interface.
Except the interview.
The interview is the one point in your process where the single-system approach breaks down. Your recruiter opens Zoom or picks up the phone. They spend 30 to 45 minutes in conversation. They learn things that will determine whether this candidate gets placed or not. And then they have to manually type all of that into OTYS after the fact. From memory. Under time pressure. Before the next call starts.
In2Dialog connects directly to OTYS to close that gap. Not as another tool to manage alongside your ATS, but as a layer that sits inside your existing workflow and makes the interview part of the same automated process as everything else.
What Manual Interview Admin Does to Your OTYS Data
OTYS is only as valuable as the data inside it. That is true for any ATS, but it matters more for a platform designed to be your single source of truth.
Think about what your candidate records actually look like today. The fields that OTYS populates automatically (application date, source, CV upload, status updates) are always complete and consistent. The fields that depend on the recruiter typing after an interview are a different story.
Some records have detailed notes. Others have two sentences. The salary expectation field is filled in for one candidate and empty for the next. Motivations and concerns that were clearly articulated during the interview get reduced to vague summaries or left out entirely. The quality varies by recruiter, by time of day, by how many calls they had that morning.
That inconsistency has consequences. Managers pulling reports from OTYS get an incomplete picture. Account managers preparing candidate submissions for clients have to call the recruiter to fill in what the record is missing. Matching algorithms work with partial data. The system you chose because it gives you everything in one place is only giving you part of the story.
What Changes When Interview Data Flows Automatically
When In2Dialog is connected to OTYS, the interview becomes part of the automated workflow instead of the exception to it.
The recruiter has the conversation and focuses entirely on the candidate. No split attention between listening and typing. No mental note-taking. After the call, a structured report appears in the OTYS candidate record within minutes. Salary expectations in the salary field. Notice period in the notice period field. Competency scores mapped to your evaluation template. Motivations, strengths, risks, and recommended next steps all organised and ready to use.
The recruiter reviews the report, approves it, and moves on. The 30 to 45 minutes of post-call admin is gone. But more importantly, the data in OTYS is now consistent. Every candidate record has the same depth of information regardless of which recruiter conducted the interview or how busy their day was.
That consistency changes what you can do with your OTYS environment. Reports become reliable. Candidate comparisons become fair. Client submissions can be generated directly from the record without additional formatting. The all-in-one promise that made you choose OTYS in the first place actually applies to the complete recruitment process, interviews included.
Not Just Another Tool. A Different Type of Data.
If In2Dialog only recorded interviews and pushed a transcript into OTYS, it would be useful but unremarkable. Transcription is essentially a solved problem in 2026. The reason this integration matters is what happens between the transcript and the candidate record.
In2Dialog combines the interview transcript with the candidate’s CV and the job description. That is what produces output that is genuinely different from meeting notes. Instead of a summary of what was said, you get an assessment of how what was said relates to what the role requires. Where the match is strong. Where there are gaps. What the recruiter should explore in the next conversation. What the client needs to know.
For OTYS users who value having actionable data in one place, this is the distinction that matters. The report landing in your candidate record is not a transcript someone has to interpret. It is structured hiring intelligence that connects the conversation to the placement decision.
And because In2Dialog captures every type of conversation, video calls, phone screens, and live interviews all produce the same structured output. Your OTYS data does not have gaps depending on whether the interview happened on Teams or over the phone. Every record is complete.
Getting Started
The integration is live and connects to your OTYS environment without requiring changes to your existing setup. If you want to see exactly how a structured interview report lands in an OTYS candidate record, book a demo and we will walk through it using your own configuration.
Using a different ATS? See the full list of integrations.
Related reading
