Skip to main content

Answers

What inploi is and what it does

What inploi does for candidates and recruiters, how it sits above the ATS, Studio, the Candidate Agent, job distribution and source-to-hire attribution.

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 inploi is, what each part does and how it fits with the systems an employer already runs. Each answer opens with a direct reply; the links go to the page on www.inploi.com that covers the topic in full.

What is inploi?

inploi runs the candidate side of hiring for large frontline employers: the careers site, the application, an AI agent that answers candidates’ questions, job distribution and source-to-hire reporting, with every application delivered into the employer’s own ATS.

  • Built for employers who hire at volume, mainly in the UK: hospitality, restaurants, retail, fitness, holiday and leisure, services and the public sector.
  • The Hiring Agent scores each application against the employer’s criteria with reasoning a recruiter can read. It ranks and recommends; it never rejects.
  • It sits above the applicant tracking system (ATS), which stays the system of record.
  • Teams configure it in Studio, with inploi’s people alongside for design and engineering.

Related: https://www.inploi.com/ · https://www.inploi.com/use-cases

What does inploi do for candidates and for recruiters?

For candidates inploi is the careers site, the application and an agent that answers their questions; for recruiters it is scoring with readable reasoning and one view of what is happening across their systems.

  • Candidates: a careers site that is fast on a phone, conversational apply that asks only what the role needs, and the Candidate Agent for questions about roles, shifts and benefits.
  • Recruiters: every application scored against their criteria, with the score and reasoning in Studio and, where the integration supports it, in the ATS.
  • Hiring managers: notifications when a person’s judgment is needed.
  • Talent leaders: analytics and attribution from first click to hire.

Related: https://www.inploi.com/experience/careers-sites · https://www.inploi.com/agents/hiring-agent

Does inploi replace our ATS?

No: your ATS stays the system of record, and inploi is the layer above it.

  • inploi pulls live jobs from the ATS and pushes completed applications back into it.
  • Agents rank and recommend; they never reject, and a person on your team makes every hiring decision.
  • “Hiring” in Studio is a view of jobs, applications and candidates between the candidate experience and your ATS. It is not a second ATS.
  • No ATS yet? Studio runs the pipeline itself.

Related: https://www.inploi.com/use-cases/more-from-your-ats · https://www.inploi.com/enterprise

Why use inploi instead of the careers site and assistant our ATS provides?

An ATS’s own careers site and assistant are built around that one system and its release cycle; inploi gives candidates a branded, role-specific experience that stays the same across brands, countries and ATS changes.

  • Many ATS apply buttons open the ATS’s own form, built for the recruiter’s data model rather than for a candidate on a phone. inploi asks only what the role needs and posts the finished application into the same ATS.
  • One inploi site can front several brands and several ATSs at once, which suits groups built by acquisition.
  • If you change ATS later, the site, the application and the agent stay; only the integration is redone.
  • For a single brand on one ATS with simple roles, the ATS’s own front end can be enough. The way to decide is to measure where candidates drop off on your current journey.

Related: https://www.inploi.com/use-cases/more-from-your-ats · https://www.inploi.com/use-cases/replace-a-retiring-careers-site

What is Studio and who in our team can use it?

Studio is where your team runs inploi: editing careers site pages, configuring the agents and reading the analytics, without waiting for a developer.

  • Used by the talent team, the people who own the careers site, and hiring managers who need to see their roles.
  • Roles and single sign-on decide who can see what and who can publish.
  • Comment mode lets anyone leave notes on the page itself; the page owner resolves them and publishes.
  • Every release is a numbered version attributed to the person who made it, and every agent action has an audit trail.

Related: https://www.inploi.com/platform/studio

Can we keep our existing careers site and add only the Candidate Agent or the application?

Yes: the Candidate Agent ships through the inploi SDK and can sit on a careers site you already have, and conversational apply can sit behind existing job pages.

  • The agent can be added with a few lines of code, alongside job search and analytics if you want them.
  • The accessibility widget also installs on any careers site with a script tag.
  • A full inploi careers site is not required to start.

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

Can one careers site cover several brands, countries and languages?

Yes: one inploi careers site can carry several brands, every location you hire in and the languages your candidates speak, each with its own pages, job search and application.

  • Your team manages the content for every brand in Studio.
  • Analytics can be split by brand, location and language.
  • Different brands can send applications to different ATSs from the same site.

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

What does the Candidate Agent do?

The Candidate Agent answers candidates’ questions from the employer’s approved content and live job data, around the clock, helps them find roles that fit and hands over to a person when judgment is needed.

  • It answers from the knowledge and policies your team adds in Studio (benefits, locations, interview process, rules on topics such as salary) and from the job on screen. It does not answer from the open web.
  • When it cannot answer, it says so and routes the candidate to your team through the contact route set in Studio.
  • It searches and matches roles, and hands candidates straight to the job’s application.
  • It does not replace the application: conversational apply asks a job’s questions and posts the result to your ATS.
  • Where your ATS shares statuses, it tells candidates where their application is, in the same thread they applied from.

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

What does job distribution include, and do we keep our job board contracts?

Job distribution puts every live role on Google for Jobs, Indeed, Adzuna and the aggregators from one connection to your ATS, with sponsorship on paid boards as an add-on; most clients keep their own job board contracts.

  • Paid boards include CV-Library, Totaljobs and ZipRecruiter. Job distribution is deeply connected to Appcast, so sponsored roles reach its publishers.
  • Paid budget follows applications, not clicks, and is set per segment in Studio.
  • Every application is attributed back to the channel that brought it.
  • A managed service, run by an inploi expert inside your software, is available on top. Media spend is separate from inploi’s fees.

Related: https://www.inploi.com/platform/job-distribution · https://www.inploi.com/platform/job-distribution/managed-service

Can we see where candidates come from (source-to-hire attribution)?

Yes: inploi tracks every candidate from first click through to application and shows which source, campaign or channel brought them, and through to hire where your ATS shares outcomes.

  • Visible in Studio and segmented by job, location, brand or date range.
  • Attribution data is sent back to your ATS where technically possible.
  • Hires appear once the ATS reports them; the outcome feed depends on the ATS integration.

Related: https://www.inploi.com/data/analytics · https://www.inploi.com/use-cases/prove-hiring-roi

Does inploi work for disabled and neurodivergent candidates?

inploi careers sites and applications are built to WCAG 2.1 AA, and the accessibility widget gives candidates their own contrast, font and navigation controls.

  • Contrast, keyboard navigation, screen-reader labelling, focus states and reduced-motion behaviour are in every template, and the application is held to the same standard.
  • The widget works on any careers site, including ones inploi did not build.
  • The widget does not replace an accessibility audit of a whole site; that is offered as a separate piece of work.

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

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.