Fixed quote after a free call

An AI recruitment chatbot that answers candidates without making hiring calls

We build an AI assistant for your careers site, text line or WhatsApp that answers routine questions from candidates and temps (how to apply, where a role is based, when pay runs, how to submit a timesheet) from your own approved answers, collects availability updates and passes anything about suitability, pay disputes or complaints to a consultant. It says it is automated and never assesses candidates. Projects typically cost $2,500 to $7,500 and take five to eight weeks.

The problem

What a recruitment chatbot should and should not do

Consultants answer the same questions all day: is this role still open, what does it pay, when do I get paid, how do I send my timesheet, can I work Saturday. Temps on assignment call the branch for answers that are already written down somewhere.

An AI recruiter agent can take that load, but in hiring it must be narrow. It cannot judge suitability, promise roles or rates, or collect information an employer should not use. It answers from approved wording, discloses that it is automated and hands people to a consultant.

What we build

What our AI recruitment chatbot includes

Approved answer library

Application steps, pay schedule, timesheet process, office hours, policies and role facts written and approved by the agency.

Careers site and text line

A chat widget on your careers pages and, optionally, the same assistant on SMS or WhatsApp.

Availability updates

Temps and candidates update availability, location or shift preferences, written back to the CRM.

Live job answers

Answers about open roles drawn from the published job ad in your ATS, never invented.

Hand-off to a consultant

Suitability questions, pay disputes, complaints and safeguarding concerns go straight to a person.

Clear AI disclosure and logs

It says it is automated, offers a person at any time and logs every conversation for review.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Question asked

    A candidate or temp asks on the careers site, by text or on WhatsApp.

  2. 02 Automated

    Answer from your library

    The assistant answers only from approved wording or the published job ad.

  3. 03 Automated

    Details captured

    Availability or contact updates are collected and written to the CRM.

  4. 04 Consultant review

    Consultant follows up

    Consultants pick up hand-offs and questions the assistant could not answer.

  5. 05 Recruiter or director decides

    Hiring decisions

    Suitability, offers and pay are decided by recruiters, never the assistant.

How it behaves

How the recruitment chatbot behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the candidate sees

  • A note that they are chatting with an automated assistant
  • Short answers from the agency's own wording and job ads
  • A consultant whenever they ask about suitability, pay or a problem

What consultants see

  • Hand-offs with the conversation attached
  • Availability updates already in the CRM
  • A weekly list of questions to add to the library

What the automation does

  • Retrieves approved answers and live job text
  • Refuses suitability and pay decisions and hands over
  • Logs every conversation

Edge cases and fallbacks

Question not in the library
It says it does not know, offers a consultant and logs the question.
Candidate shares sensitive personal data
It does not store or act on it and hands over to a person.
Safeguarding or harassment report
Immediate hand-off to the named manager with the transcript.
AI provider outage
The widget falls back to a contact form and the text line to a holding reply.

Architecture

An AI recruitment chatbot at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Candidate or temp Web, SMS, WhatsApp Assistant service n8n or Laravel Language model Claude, Gemini, GPT Approved answers And live job ads CRM update Availability Consultant Hand-offs Transcripts Weekly review
  • Input
  • Logic and services
  • AI step
  • Data
  • Output
  • People

How it flows

  1. 1 A candidate or temp asks a question and is told they are talking to an automated assistant.
  2. 2 The assistant service retrieves approved answers and live job ad text and passes them to the model with fixed rules.
  3. 3 Routine questions are answered and availability updates are written to the CRM.
  4. 4 Suitability, pay disputes and complaints go to a consultant, and every conversation is logged.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

AI recruitment chatbot for candidates and temps project plan

Typical time to launch: about 6 weeks, then support

  1. 01

    Discovery

    About 1 week

    Collect real questions from calls, texts and emails; agree what the assistant may never answer.

  2. 02

    Answer library

    About 1 week

    Write and approve answers, hand-off rules and disclosure wording.

  3. 03

    Build

    About 2 weeks

    Widget or text line, retrieval, job ad lookup, CRM updates, hand-offs and logging.

  4. 04

    Test

    1 to 2 weeks

    Real, tricky and out-of-scope prompts, including bias probes; consultants sign off.

  5. 05

    Launch

    2 to 3 days

    Soft launch for temps on assignment, then the careers site.

  6. 06

    Support

    Ongoing

    Weekly transcript review at first, then monthly library updates.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

Claude, Gemini or OpenAI models n8n AI Agent node or Laravel Careers site chat widget Twilio SMS or WhatsApp Business Bullhorn, JobAdder or Loxo API Slack or Microsoft Teams hand-off alerts

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and answer library

    Real questions collected, answers written and approved.

    $500 – $1,200

  • Build

    Assistant service, widget or text line, retrieval and hand-offs.

    $1,200 – $4,000

  • Integrations

    ATS job ads, CRM updates and messaging.

    $300 – $1,000

  • Testing and evaluation set

    Real, out-of-scope and bias-probe prompts before launch.

    $300 – $900

  • Launch and training

    Soft launch, transcript review and consultant walkthrough.

    $200 – $400

  • Total project estimate

    $2,500 – $7,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. A WhatsApp or voice channel adds build and running cost. Model usage and messaging are billed to your accounts directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • AI model usage: Billed by the provider per use; short answers are usually a small monthly amount.
  • Messaging: Twilio at its published per-message rates, or WhatsApp Business Platform charges if you add that channel.
  • Hosting: n8n Cloud from about €20 a month, or your own server.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

EU: tell people they are talking to AI

Article 50 of the EU AI Act requires AI systems that interact with people to inform them they are interacting with an AI system, from 2 August 2026.

Source: artificialintelligenceact.eu

EU: no assessing candidates

AI used to screen, evaluate or select candidates is high-risk under Annex III, so this assistant answers questions and never assesses anyone.

Source: artificialintelligenceact.eu

NYC: automated employment decision tools

Tools that substantially assist hiring decisions in New York City need a bias audit and notice, another reason the assistant stays out of decisions.

Source: www.nyc.gov

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

AI recruitment chatbot for candidates and temps questions, answered.

An assistant that answers candidate and temp questions on your site or text line from approved answers, collects updates and hands decisions to people. Ours never screens or scores candidates.

No. Shortlisting is a recruiter decision, and AI that evaluates candidates is regulated as high-risk in the EU and needs a bias audit in New York City. We keep the assistant to questions and updates.

Yes. It says so at the start and offers a consultant at any time. The EU AI Act requires this from 2 August 2026 and we do it everywhere.

Yes, through the WhatsApp Business Platform or a text number. Many temps prefer it to calling the branch.

It only answers from your approved library and the published job ad in your ATS. If the answer is not there, it says so and hands over.

Transcript logs, a weekly list of unanswered questions, the share of conversations resolved without a hand-off and the number of availability updates captured.

Free 20-minute call

Want this for your recruitment agency?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call