01
Ask which side, before anything else
Hiring or job-hunting is settled in the opening exchange, because the fields captured, the desk it reaches and the answers allowed all depend on it.
AI chatbot for recruitment agencies that sorts clients from candidates.
Two very different people use your website and both open with 'hi'. Adoomi settles which side the sender is on first, then answers what your pages publish — the sectors and roles you cover, permanent, temp or contract, how your fees work, what registering involves — 24/7 and in the sender's own language. A vacancy goes to the desk that covers it as a brief; a jobseeker goes to registration with their details captured. Pay, placement odds and right-to-work questions go to a person.
Hiring or job-hunting, asked firstSalary talk → a consultantYou sign off every answer
Fig. 01.A · Recruitment agenciesBoth sides
Client or candidate, sorted first
24/7
Briefs taken after the desks shut
Never
A salary figure given in chat
Fig. 02.A · pain quotesThe everyday problem
One inbox, two jobs that look identical on line one
A vacancy brief and a jobseeker's first message land in the same place and read the same until somebody opens them. The one opened second goes cold: a hiring manager who briefed another agency that afternoon, or a candidate who registered somewhere else the same evening. And underneath both, the questions your site already answers — which sectors, perm or temp, how the fee works — keep arriving anyway.
Web07:42
“Opened it expecting a vacancy. It was a candidate. Opened the next one expecting a candidate.”
WhatsApp21:15
“'What should we be paying for this role?' — the one thing the website cannot say for us.”
EmailSun
“A live brief and a CV enquiry, filed in the same folder, worked in the wrong order.”
What you get
Sorted first, answered second, refused where it should be.
02
Answer what your site already says
Sectors and roles, perm, temp or contract, the fee structure you publish and what registering involves — in the sender's own language, at any hour.
03
Leave pay and right to work alone
Salary benchmarks, placement odds and visa questions are declined in the chat and captured for the consultant or compliance contact you name.
Question coverage
What each side asks before they get in touch.
Employers ask which sectors you cover, whether you do temp as well as perm and how the fee is charged. Candidates ask what registering involves and whether you have anything near them. All of it is published already; the difference is that the assistant knows which of the two it is talking to.
Sectors and rolesPerm, temp or contractHow the fee is chargedRegistering with youAreas you coverWhich desk picks it upSend a brief
a
Adoomi
ChatVoice
We need two warehouse supervisors for a new site in Wakefield. How do your fees work, and what should we be paying them?
Two questions there. Our fees page sets out how permanent placements are charged and how temp margins work, so I can point you at that. What to pay them I won't put a number on — that's one for a consultant here, not for me.
Fair enough. Who picks this up?
You've come through as a hiring enquiry rather than a candidate one, so it goes to the desk that covers industrial roles instead of the registration inbox. I'll send the brief across with what you've written. Whose name should be on it?
How the fee is chargedWhich desk picks it upAreas you cover
Type a question…● Voice
Buyer intent
Different fields for the two sides of the desk.
A hiring enquiry needs the role, the site or postcode, whether it is permanent, temporary or contract, and when they want someone starting. A candidate enquiry needs the job title they are chasing, the sector, how far they can travel and how they would like to be contacted. Adoomi asks for the set you configured for each side, so the consultant opens an enquiry that already knows what it is.
Vague enquiries, no context.
Your team chases the basics before they can reply.
a
Adoomi
EnquirerHiring — client side
RoleWarehouse supervisor, permanent
SiteWakefield — new unit
Contactcaptured@…
3 of 4 captured · 1 in progress
With AdoomiNew enquiry · readyEnq 7645
EnquirerHiring — client side
RoleWarehouse supervisor, permanent
SiteWakefield — new unit
Contactcaptured@…
One clean handoff.
Your team opens the enquiry and replies — no chasing.
STEP · 01
Hiring or job-hunting
Settled before anything else is captured
STEP · 02
The role itself
Job title, sector, and the site or the travel distance
STEP · 03
Perm, temp or contract
And when they need someone starting
STEP · 04
To the desk that covers it
Client brief to a consultant, candidate to registration
Fig. 06.A · after-hoursOut-of-hours
Candidates look in the evening; managers write briefs before the desks fill
Your website is read for many more hours than it is staffed. A candidate browsing between shifts and an employer typing up a vacancy before their own working day both get what your pages publish at that moment, in their own language: sectors covered, contract types, the fee structure you publish, what registering involves. Each one is sorted by side and captured with the fields you set, so nothing has to be triaged before it can be worked.
19:20
“'Do you cover industrial roles in West Yorkshire?'”
Answered from your sectors page
21:05
“'How does registering as a candidate work?'”
Answered, then routed to registration
22:40
“'What should we be paying a site manager?'”
Declined — brief to the industrial desk
07:30
“Overnight queue”
Client briefs and candidate enquiries, already split
Time back
Consultants stop reading the inbox in order to sort it
Which sectors you cover, whether you place contract as well as perm, how a temp margin is charged, what happens in the days after someone registers: asked constantly, and already written on your site. Adoomi answers those, so what reaches a consultant is live briefs and registered candidates rather than a pile that has to be opened one by one to find out which is which.
Before Adoomi
- Candidates and clients land in one inbox, and someone has to open every message to find out which is which.
- 'Do you do industrial?' and 'do you place contract?' are answered on the site and still arrive in the enquiry form.
- A hiring manager's fee question waits behind live roles, and gets its reply after they have briefed somebody else.
- Salary questions from both sides go to a consultant who is in interviews for the rest of the afternoon.
With Adoomi
- Which side the sender is on is established first, before a single other detail is captured.
- Client briefs reach the desk that covers the role; candidate enquiries go to whoever handles registration.
- Sectors covered, contract types and your published fee structure are answered from your own pages, in the sender's language.
- Salary and right-to-work questions arrive as captured questions for a person, never as answers the assistant gave.
Fig. 08.A · controlsTrust & safety
What it answers for each side, and where it stops.
The assistant answers from your published pages: what your desks cover, contract types, your fees, how registering works. It benchmarks no salary, rates nobody's placement chances and settles no right-to-work or visa question. Each reaches the consultant or compliance contact you name, in the enquirer's words, by email alert or WhatsApp. None of this makes an agency compliant with anything. Candidate and client data is EU-hosted, with GDPR export and deletion; nothing typed is logged.
01
Your own pages, both sides of the desk
Sectors, contract types, the fee structure you publish and what registering involves come from your site, not from general knowledge about the market.
02
Salary talk goes to a consultant
What to pay, what someone is worth and whether they would be placed are declined in the chat and captured as questions for a person to answer.
03
Right to work is never decided here
Visa and eligibility questions go to the compliance contact you name, recorded word for word. Nothing here lifts a single right-to-work duty off the agency.
04
Nothing live until you sign it off
You read every answer before a client or a candidate sees it, and can change it whenever your terms, your desks or your sectors change.
How it works
How an AI chatbot for recruitment agencies works.
01
Connect content
Point Adoomi at the pages both sides read: sectors and roles, your fee structure, how registration works. What isn't published there is something it declines rather than attempts.
02
Add the snippet
Set the split — which desk takes which sector, who handles registrations, who gets the compliance questions — then add one line to your website.
03
Test & go live
Read a week of enquiries, change the fields each side is asked for, block any answer you'd rather a client didn't read. Setting it up takes ~10 min.
FAQ
FAQs about AI chatbots for recruitment agencies.
Client and candidate enquiries separate in the opening exchange, and a different set of fields is captured for each: role, site and start date for a hiring enquiry; job title, sector and travel distance for a jobseeker. Each goes to the desk you named for it.
Salary benchmarking sits outside what the assistant may say. It declines in the chat, records the question inside the enquiry, and routes it to a consultant, so nobody is quoted a figure the agency never published and the person who can talk about pay still gets the conversation.
The chat window takes no attachments, so a CV cannot be uploaded into it. The assistant captures the role, sector and contact details and points the candidate at however you take CVs; a CV reaches your team only if the candidate sends it after the conversation moves to WhatsApp.
Right-to-work and visa eligibility are never settled in the chat. The assistant captures the question in the enquirer's own words and passes it to the compliance contact you name. Adoomi makes no agency compliant with anything; the checks and the obligations stay yours.
Candidate data is hosted in the EU, with GDPR export and deletion built in, so a deletion request is something you can action. Nothing a candidate types is written to logs, and the chat window sets no tracking cookies on their device.
The Free plan is £0 a month with 50 message credits; paid plans run £8 for 200, £20 for 500 and £75 for 4,000. Getting started is ~10 min of work: connect the site, read the answers drafted for each side, add one line to your website. Nothing is live until someone at the agency approves it.
Why this matters
The test is which desk it lands on.
Most chat tools sold to agencies treat every visitor as one kind of lead and hand your team a list of names to sort out later. The design point here is the first thing the assistant establishes — hiring or job-hunting — because everything after it differs: the fields captured, the desk it reaches, and the questions it refuses to answer. And every answer either side is given was read by someone at the agency first.
Client and candidate, kept apart
The assistant establishes whether the sender is hiring or job-hunting before it captures anything else.
Enquiries taken after hours
Evening and weekend messages arrive as briefs and candidate registrations, already sorted by side.
A pay figure quoted in chat
Pay, placement odds and right-to-work questions reach the person you named — captured, never answered.
Start free
Send it a mixed week and watch it split.
Give Adoomi your sectors page, your fee page and your registration page, then put the two messages you get most through it: a manager asking what to pay a warehouse supervisor, and a candidate asking whether you have anything near them. The first should be refused and routed to a consultant; the second should be answered and registered. Change whatever you don't like before either reaches a desk. The Free plan is £0 with 50 message credits.
No card neededSorted by side, not by inbox~10 min setup
Fig. 12.A · Recruitment agenciesExplore
More Professional Services chatbots
- AI chatbot for AccountantsSee how Adoomi handles enquiries for accountants.
- AI chatbot for Insurance brokersSee how Adoomi handles enquiries for insurance brokers.
- AI chatbot for Law firmsSee how Adoomi handles enquiries for law firms.