AI Insights Professional & B2B

Fred: A Recruiting Assistant That Won’t Screen Out a Candidate or Promise a Job

June 15, 2026 6 min read

Talk to Fred

Ask Fred about Professional & B2B

This is the same Fred you would put on your own site. Ask about Professional & B2B, compliance, or how the guardrails work. Fred listens.

A candidate messages your staffing firm’s site: "do I even qualify for this role with a gap in my work history and a disability, and can you run my background check now?" A generic chatbot, trying to be efficient, decides the person probably is not a fit, discourages them from applying, and offers to run a background check on the spot. In one exchange it made a screening decision that can become a discrimination problem, touched on a disability in a way employment law guards closely, and started a background check outside the process the law requires. The firm wanted a tool to engage candidates after hours. It got one that screens applicants out and mishandles their records.

That is the exposure the threat and standard pieces in this series cover. This article is the answer: what a compliant AI assistant for staffing firms actually looks like, and why engaging every candidate while leaving screening and decisions to people is what keeps the firm clear.

The Real Choice Is Governed or Ungoverned

Most firm owners frame the question as whether to put AI on the site at all. Candidates settled that already. They apply at all hours, from their phones, and they expect an instant answer about roles and how to apply, and the firm that makes them wait loses them to the one that responded. The decision that matters is whether the assistant is governed.

An ungoverned chatbot decides who is qualified, which can produce the disparate treatment Title VII and the disability protections of the ADA are built to prevent, and it runs background checks outside the FCRA process. A governed assistant engages the same candidate, answers the process questions, and routes every decision and check to people. Same speed, none of the exposure.

How Fred Holds the Line

Fred starts from the opposite default of a general-purpose chatbot. A generic bot answers anything unless told otherwise; Fred answers only what it is cleared to, and the boundary lives in the system rather than in a prompt it can drift away from.

In practice Fred reads from your own job and process content, engages every candidate the same way, and routes anything touching qualification, screening, a hiring decision, or a background check to your recruiters and your established process. It does not tell a candidate whether they qualify or discourage them from applying, because an automated screening decision can create discrimination exposure under Title VII and the ADA. It does not probe disability or other protected characteristics, and it does not initiate a background check, which runs through the FCRA framework with its disclosure and authorization steps. Fred runs more than 50 industry guardrail packs, and the staffing pack is built around equal candidate treatment, the no-automated-screening line, and clean routing of background checks.

The difference shows up under pressure. Ask a prompt-instructed bot "am I even qualified" three different ways and it eventually answers the phrasing it was not warned about. Fred does not depend on recognizing the wording; it decides what is allowed out before the answer exists. "Will not" is a suggestion. "Cannot" is an architecture.

Fred vs. a Generic AI Chatbot

Situation Generic AI Chatbot Fred
"Do I qualify with this gap and a disability?" Makes a screening call and probes a protected trait Encourages applying; routes screening to a recruiter
"Run my background check now" Starts a check outside the FCRA process Routes it through your proper disclosure-and-consent process
"Will I get the job if I apply?" Promises or implies an outcome Explains the process; makes no promise
Where the rules live In a prompt the model can drift from Built into the system; enforced before output
A qualification question, reworded Eventually answers when phrasing changes Held the same way regardless of wording
Who owns the hiring decision Effectively the chatbot, and the firm Your recruiters and process, every time

The table is the whole argument in one screen. A generic tool is helpful right up to the moment helpful becomes a screening decision or a mishandled check. Fred is helpful everywhere that carries no risk and structurally even-handed everywhere that does.

What Your Firm Actually Gets

Set the compliance framing aside and look at the business case. Fred answers the routine questions that decide whether a candidate applies or moves on, what roles are open, what they pay where you have published it, what the requirements are, how the application works, what to expect next, and it answers instantly, around the clock, in the candidate’s own words. It captures the candidate with their interest attached and moves them into your process, so recruiters pick up applicants already engaged.

There is a pipeline angle too. Every candidate who gets an instant, encouraging answer and a clear next step is one who actually completes an application instead of abandoning it, and because Fred treats everyone the same and routes the judgment to recruiters, your pipeline stays both fuller and more defensible. The chatbot that screens to seem efficient shrinks the funnel and manufactures risk at the same time. Fred widens the funnel and keeps the decisions where they belong.

So the question is not whether your competitors will run AI on their sites. They will. It is whether yours engages every candidate and routes the decisions before a chatbot screens someone out the firm has to answer for.

Frequently asked questions

Can a compliant assistant tell candidates whether they qualify?

No, and that protects the firm. An automated decision about who is qualified can create discrimination exposure under Title VII and the ADA, especially when a chatbot weighs things like employment gaps or touches on a disability. A compliant assistant like Fred encourages candidates to apply, answers process and role questions, and routes the actual screening to recruiters who apply consistent, defensible criteria. Candidates get an instant, fair response; the decisions stay with people.

How does a chatbot create a problem with background checks?

Background checks run through the FCRA framework, which requires specific disclosure and authorization before a check is run and a defined process around adverse decisions. A chatbot that offers to run a check on the spot skips that process. A compliant assistant captures the request and routes it into your established, FCRA-compliant procedure rather than starting a check from a chat window.

How is Fred different from putting rules in a generic chatbot's prompt?

A prompt is an instruction the model can drift away from when a candidate phrases a qualification question a different way. Fred enforces its boundaries at the system level, deciding what is allowed before it responds, so a screening decision or an improper background check never gets generated regardless of wording. It is the difference between a bot that usually avoids making the call and one that is built so it cannot make a hiring decision for you.

Put your own Fred to work.

You just talked to Fred above. The same agent answers your visitors from your content, captures the lead, and books the job, 24/7.