Skip to main content

Answers

Candidate experience: careers sites and conversational apply

Answers about inploi's conversational apply, completion, CVs, screening questions, per-role applications, careers site ownership, search and accessibility.

Updated

inploi is the hiring experience platform for large frontline employers. Agents do the admin. Humans do the hiring. It all runs on the ATS you already have. This page answers the questions buyers ask about what candidates meet: the careers site, the application and the agent. Each answer opens with a direct reply; the links go to the page on www.inploi.com that covers the topic. For neutral, unbranded guidance on reducing drop-off, see https://www.inploi.com/insight/high-volume-hiring.

What is inploi’s conversational apply?

Conversational apply is inploi’s application: the candidate answers a role’s questions in one chat-style thread on their phone, and the finished application is posted into the employer’s ATS.

  • It asks only what the role needs, with conditional logic that adapts to the candidate’s answers.
  • Hourly roles can run a short, CV-free application; salaried roles a fuller one.
  • Every answer lands in its ATS field, with the source attached where the integration allows.
  • It is separate from the Candidate Agent: the agent answers questions and finds roles; conversational apply completes the application.

Related: https://www.inploi.com/experience/conversational-apply

Is conversational apply a chat or a form, and can we choose?

Both: the same application, built once, renders as a conversation or as a form, and your team chooses per site or per role.

  • The questions, the logic and the ATS submission are identical either way.
  • A common pattern is chat for hourly roles and a form for senior or salaried roles.

Related: https://www.inploi.com/experience/conversational-apply

Does conversational apply increase application completion?

Yes: after inploi rebuilt its application journey, Compass Group saw 42% more completed applications.

  • The gains come from fewer questions, a phone-first layout and no forced account creation or redirect to a long ATS form.
  • inploi measures drop-off question by question, so each change can be judged on your own data.

Related: https://www.inploi.com/customers/compass · https://www.inploi.com/use-cases/candidate-experience

How many questions can we ask before candidates drop off?

There is no safe universal number; ask only what a role genuinely needs, then use per-question drop-off data to cut anything that costs more candidates than it is worth.

  • inploi’s analytics show where candidates leave, question by question.
  • Each role or role group can have its own question set, so a short hourly application does not inherit a salaried role’s questions.

Related: https://www.inploi.com/data/analytics · https://www.inploi.com/experience/conversational-apply

Do candidates need to upload a CV?

Not unless the role needs one: applications can be CV-free for hourly roles and ask for a CV where a role warrants it.

  • Either way the candidate answers in one thread and finishes in minutes.

Related: https://www.inploi.com/experience/conversational-apply

Can different roles, locations or brands have different applications?

Yes: each job is mapped to an application by role type, brand, business unit or category, so different roles, locations and brands can ask different questions.

  • An hourly role can run a short application and a salaried role a fuller one.
  • Within an application, conditional logic adapts the questions to the candidate’s answers.

Related: https://www.inploi.com/experience/conversational-apply

Can we screen out unsuitable applicants with knock-out questions?

inploi’s applications can ask a role’s basic requirements early so candidates can self-select, but nothing in the product rejects or hides a candidate: every candidate can still apply, and the Hiring Agent orders applications rather than removing them.

  • Early questions about requirements such as right to work, availability or a licence let candidates decide whether to continue.
  • inploi’s structured screening asks a role’s basic requirements first and keeps the application open to everyone.
  • Applications can be closed once an advert reaches the number of applications you set.

Related: https://www.inploi.com/agents/hiring-agent · https://www.inploi.com/security/ai

Can candidates get alerts for new roles?

Yes: candidates can sign up on the careers site for job alerts by role and location, and every alert carries a one-click unsubscribe that names the employer.

  • When a role has closed, the careers site and the Candidate Agent offer alerts for similar roles instead of a dead end.

Related: https://www.inploi.com/experience/careers-sites

Do you measure how candidates found the experience?

Yes: after applying, candidates are asked how it felt, with an optional comment, and the score is tracked per site so a drop is caught and fixed rather than discovered at the next review.

Related: https://www.inploi.com/data/analytics

Can applicants check their application status after applying?

Yes, where your ATS shares statuses with inploi: the candidate gets a confirmation when they submit, and the Candidate Agent answers where they are in the process in the same thread they applied from.

  • Where your ATS shares status with inploi, it is tracked from submission to outcome.

Related: https://www.inploi.com/agents/candidate-agent

How do we keep the Candidate Agent on-brand and not robotic?

Your team sets the agent’s knowledge, tone and rules in Studio, and it answers only from content you have approved.

  • Guidance covers basics, style, search, policies and escalations.
  • The agent sits inside your branded careers site and uses your live job data.
  • Anything outside its approved knowledge is handed to a person.

Related: https://www.inploi.com/agents/candidate-agent

Who owns the careers site design and the back end: us or inploi?

Your team owns the content and publishes changes in Studio; inploi builds, hosts and runs the site and the integrations behind it.

  • Copy edits, new pages and approvals need no developer.
  • inploi’s designers and engineers handle changes that need design or engineering.

Related: https://www.inploi.com/platform/studio · https://www.inploi.com/software-with-a-service

inploi careers sites are built for search: fast pages, structured job data for Google for Jobs and job pages that AI assistants can read.

  • Jobs are published to Google for Jobs through job distribution.
  • Search position depends on your content and competition as well as the build, so inploi reports it rather than promising it.

Related: https://www.inploi.com/experience/careers-sites · https://www.inploi.com/platform/job-distribution

Is the careers site accessible (WCAG), and what does the accessibility widget cover?

Every inploi careers site and application is built to WCAG 2.1 AA, and the accessibility widget adds candidate-side contrast, font and navigation controls on any careers site.

  • The widget installs on a third-party site with a script tag and has no dependency on the rest of inploi or your ATS.
  • It is built to WCAG 2.1 AA, with ongoing audits; inploi does not claim more.
  • It does not replace an accessibility audit of your whole site, which is offered as an add-on.

Related: https://www.inploi.com/experience/accessibility

Agents do the admin. Humans do the hiring.

Let’s find the admin your team shouldn’t be doing.

The hiring experience audit takes four minutes.