How conversational apply changes who finishes applying
Why a conversational application that adapts to the role keeps the right frontline candidates to the end, and lets the wrong fit find out early.
Conversational apply changes who finishes an application by removing the reasons good candidates give up: the long form, the irrelevant questions and the CV they do not have on their phone. It also changes who does not finish, because an application that asks the right questions early lets someone who cannot work the shifts or lacks the qualification find out in a moment, rather than after your team has read their application.
Both halves matter. Most conversations about application design are about completion rates, as if more finished applications were always better. For a high-volume employer the real question is whether the people who finish are the people you want to hire.
Who a traditional form selects for
A typical ATS application is built around the recruiter’s data model. It asks every candidate the same questions in the same order, whatever the role, and it was designed on a desktop. Put that in front of someone applying for a front-of-house role on their phone during a break, and you are selecting for patience, a good signal and a spare half hour. None of those predicts whether they will be good at the job.
The people who drop out are not a random sample. They are disproportionately the candidates with other options, the ones applying to three employers that evening who will go with whichever one lets them finish first. That is why a clunky application does more damage than its completion rate suggests: it loses the people you most wanted and keeps the ones who had the least choice.
What conversational apply does differently
Conversational apply is the application itself, delivered as a single thread rather than a set of pages. The first questions are the same for everyone: name, contact details, right to work. From there, the application reads the role and the region and asks only what that job needs. A fitness coach is asked about their qualification, a kitchen team member about their food hygiene certificate, and an evening role about evening availability. A candidate never sees a question that does not apply to them.
Every answer shapes the next question. Someone who already holds the qualification skips the questions about working towards it. Someone who does not is shown roles that may suit them better, and can still apply. And when they finish, the completed application is posted into the employer’s ATS with every answer in its field, so nobody re-keys anything and the ATS stays the system of record.
The same application can render as a conversation or as a traditional form, so a team can choose what suits the device and the moment. What stays constant is the logic underneath.
Friction is a setting, not an accident
The part people find surprising is that a good application is not always the shortest one. Where a role genuinely needs commitment, the application should ask for it, and ask early. A question about the role’s basic requirements near the start tells a candidate in a few seconds whether the role fits, and they can still apply. We call this deliberate friction, and it is something a team chooses role by role rather than something that happens because a form was never revisited.
That is how conversational apply changes the mix of who finishes. The good candidate in a hurry gets through quickly because nothing is wasted. The candidate who was never going to be a fit finds out before they have invested their evening, and is often shown a role that suits them better. The pile your team receives is smaller relative to the interest, and more of it is worth reading.
What the results look like
The evidence we can point to is about the front of the process, where this change happens. When Compass Group rebuilt its application with inploi, it saw 42% more completed applications. PureGym’s application now completes in under a minute. Neither changed its ATS. You can read how Compass approached it in the Compass Group story.
Because every step is measured, a team can also see exactly where people still leave and test two versions of an application side by side to find out which one finishes more often. That turns application design from a matter of taste into something you can improve week by week.
Where it sits alongside the agents
It is worth being precise about names, because this area attracts a lot of loose language. Conversational apply is the application. The Candidate Agent is different: it answers candidates’ questions from your policies, around the clock, helps them find roles that fit, and can start an application, which conversational apply then completes. They share one thread and one candidate record, but they do different jobs.
Once applications land, the Hiring Agent scores every one of them with reasoning your team can read. Nobody is screened out by it: it orders the queue, explains why, and a person makes the call. Structured screening, which asks a role’s basic requirements before the full application, is in development with design partners. Agents do the admin, and humans do the hiring.
What to do next
If you want to know whether your application is selecting for the right people, apply for one of your own frontline roles on your phone and count the questions that did not apply to you. Then look at where candidates drop out, step by step. If you cannot see that, it is the first thing to change.
You can see how the application works in more detail on the conversational apply page, read about the wider problem of candidates dropping off before they apply, and find the rest of our writing under candidate experience.
