By industry
Car dealershipsCar rentalDetailers & valetersGarages & MOT centresFashion retailersFurniture storesPet storesJewellersPlumbersElectriciansHVAC & heating engineersCleanersLandscapers & gardenersRoofersHotels & guest housesRestaurantsCafésGyms & wellness studiosTour operatorsEstate agentsLetting agentsProperty managementServiced accommodationAccountantsLaw firmsInsurance brokersMortgage brokersRecruitment agenciesPrivate schoolsNurseriesChildren's activity clubsTraining providersTutoring centresCharitiesMuseums & attractionsReligious & community centresSports clubs

Training provider software. It asks who is asking.

Adoomi answers course questions from the pages you already publish — start dates, entry requirements, delivery pattern and funding routes — 24/7, in the language each enquiry arrives in. It asks whether a learner or an employer is typing, captures what that side needs, and sends the enquiry as an email alert to whoever you name. Eligibility, places and where a course leads stay with admissions.

Learner and employer kept apartNo eligibility decided in chatYou approve every answer
Fig. 01.A · Training providers
24/7
Course and funding pages, any hour
Two routes
Learner and employer, captured apart
Admissions
Keeps every eligibility call
Fig. 02.A · pain quotes
The everyday problem

One course page, two audiences, one small admissions team

Learner enquiries arrive in the evening, after a shift. Employer enquiries arrive mid-morning, in the middle of somebody else's HR meeting. Both land at the same address, alongside enrolment paperwork, awarding-body admin and the chase for funding evidence. A learner who cannot find out whether a course is funded assumes it is not, and an employer whose levy question waits a week has already rung another provider.

Web form07:42
"When does the next cohort start and what do I need to get on it?"
Email21:15
"Would my course be funded, or do I pay for it myself?"
VoicemailWed
"We're an employer — how would the levy work if we trained staff with you?"
What you get

What it settles from your pages, and what it always hands over

01

Tell a learner enquiry from an employer one

It asks which it is speaking to and captures different fields for each. You decide which branch alerts which team, so an employer's levy question never lands in the learner-application pile.

02

Answer the cohort questions from your pages

Next start dates, entry requirements, delivery pattern and the qualification a course leads to — as your own pages state them, evenings and weekends included.

03

Leave every eligibility call to admissions

Funded-place decisions, enrolment and any welfare disclosure go to the person you name, with what was written attached. The assistant states no outcome.

Question coverage

What learners ask, and what employers ask instead

Start dates, entry requirements, delivery pattern, the qualification at the end and which funding route applies — plus the employer set: levy-funded places, the roles worth training and who to speak to. All answered from your published pages, with every decision left to a person.

Start datesEntry requirementsFunding routesLevy-funded placesDelivery patternQualification gainedEnrolling
a
Adoomi
Speaking introduction
ChatVoice
I'm out of work at the moment — would the Level 3 be free for me?
Our funding page sets out the criteria for a fully funded place and the evidence needed for it. Whether you qualify is admissions' call rather than mine, and I'd rather not tell you it's free and be wrong. Shall I pass your details over for them to check?
Okay. Do I need English and maths first? I should say I've not been coping well since I lost my job.
What you have just told me is not something I will answer or advise on — it has gone, in your own words, to the person this provider names for welfare. The entry-requirement page covers the English and maths question, including where functional skills run alongside.
Entry requirementsDelivery patternEnrolling
Type a question… Voice
Buyer intent

Ask who is asking, then capture what that team needs

A learner and an employer need different questions, and one form asking both wastes everybody's time. Adoomi asks a learner where they are now — in work, leaving school, changing trade — which course and level they are looking at, when they want to start and which funding route they think applies. An employer is asked for the organisation, the roles they want trained, whether they pay the levy and who signs it off. Each alert goes to whoever handles that side.

Without Adoomi
Vague enquiries, no context.
Your team chases the basics before they can reply.
Adoomi qualifies in chat
a
Adoomi
Capturing context
Enquiry typeEmployer, levy-paying
Roles to trainOperations team
Start windowWinter cohort
Contactcaptured@…
3 of 4 captured · 1 in progress
With Adoomi
New enquiry · readyEnq 2165
Enquiry typeEmployer, levy-paying
Roles to trainOperations team
Start windowWinter cohort
Contactcaptured@…
One clean handoff.
Your team opens the enquiry and replies — no chasing.
STEP · 01
Ask who is asking
Learner or employer, before anything else
STEP · 02
Capture the timing
Which cohort, and how soon they want it
STEP · 03
Take the funding route
What the enquirer says applies, never a ruling
STEP · 04
Alert the right person
Admissions for learners, business development for employers
Fig. 06.A · after-hours
Out-of-hours

Learner questions land at night, employer questions mid-morning

Neither rhythm matches an admissions desk. Adoomi answers the published detail at both — next start dates, entry requirements, whether a course runs on day release, in the centre or online, how long it takes and which qualification it leads to — 24/7 and in the enquirer's own language. Anything turning on eligibility is captured rather than settled, so a learner gets the criteria your funding page states, not a promise the paperwork later contradicts.

20:40
"When does the next cohort start?"
Answered from your course page
21:15
"Would this be funded for someone like me?"
Criteria quoted, decision left to admissions
22:30
A message about a young learner at home
Not answered — routed to your named person
08:00
The admissions morning list
Learner and employer enquiries already apart
Time back

Stop retyping the entry requirements for every intake

The questions repeat cohort after cohort: what a course expects on entry, whether functional skills can run alongside, the delivery pattern, how assessment works and who awards the qualification, which documents enrolment needs, and the funding routes your page lists. All of it is published already. Adoomi serves it from there, so the day goes on enrolments, employer visits and the learners already on programme.

Before Adoomi
  • Entry requirements and start dates get retyped for every intake, in last intake's words.
  • "Is it funded?" arrives with nothing admissions could check it against.
  • Employer levy enquiries queue behind learner applications at the same address.
  • A disclosure about a young learner turns up in the routine enquiry pile.
With Adoomi
  • Published start dates, entry requirements and delivery patterns answered as they are asked.
  • A funding enquiry arrives with the learner's situation and intended start already captured.
  • Employer enquiries reach business development with the organisation and roles on them.
  • A welfare disclosure gets no automated reply — your named person has it, with the words.
Fig. 08.A · controls
Trust & safety

It quotes your funding criteria. It never rules anyone eligible

The boundary is every decision. Adoomi repeats what your funding, entry and employer pages publish; it does not rule a learner funded, confirm a place, waive a requirement or promise a job at the end. A message about a learner's welfare is not answered at all: it routes to the person you name with what was written attached, as do additional-needs questions. Chats stay on EU servers, with GDPR export and deletion, and no content in logs — which matters where learners are under eighteen.

01

Your published pages, nothing else

Start dates, entry requirements, delivery patterns and funding criteria come from pages you approved. General knowledge is not a fallback.

02

No eligibility ruled in chat

Funded-place decisions, enrolment and acceptance stay with admissions. The assistant explains the criteria and captures the enquiry; it states no outcome.

03

Welfare wording is never answered

A disclosure about a learner routes to the person you name, unanswered, with what was written attached. It discharges no safeguarding duty of yours.

04

You approve it, and it stays approved

Nothing reaches a learner until staff have read it, and any answer can be switched off. Conversations sit on EU servers, are handed back or wiped on request, and no tracking cookies are set.

How it works

How this training provider software works on your own website.

01
Connect content
Connect your course pages, entry requirements, funding criteria and employer pages. Anything not published there is a question it declines rather than attempts.
02
Add the snippet
Name who takes learner enrolment, who takes levy and employer enquiries and who takes a welfare message. Email alerts go where you set them; a handover can carry on with your team on WhatsApp.
03
Test & go live
Read every answer before a learner sees one, block what you disagree with, then add one line to your website. The whole setup, from connecting to publishing, runs to ~10 min.
FAQ

FAQs about AI chatbots for training providers.

The assistant asks near the start and branches from there. A learner is asked about their situation, the course and start window and the funding route they think applies; an employer about the organisation, the roles being trained and who signs off. Each alert goes to the team that handles it.

Why this matters

Claims that hold because the design leaves no alternative

No learner numbers, no conversion rates, nobody else's inbox. What is true by construction: every answer traces to a page your staff approved, an eligibility question is captured rather than settled, a welfare message is routed rather than replied to, and a question your pages do not cover ends in a handover rather than a plausible guess.

Course questions answered out of hours

Start dates, entry requirements and delivery patterns given from your own pages, in the enquirer's language, whenever they ask.

Learner and employer captured apart

Each side is asked different questions and alerted to a different person, so a levy enquiry never arrives dressed as an application.

An eligibility call made in chat

Funding and place decisions are captured and passed to admissions, with the criteria your pages publish quoted back and nothing added.

Start free

Put your funding question to it before a learner does

Point Adoomi at your course pages, entry requirements, funding criteria and employer pages, then name who takes learner enrolment, who takes levy and partnership enquiries, and who takes anything about a learner's welfare. Read what it proposes and block whatever you dislike. Starting costs £0 a month with 50 message credits, and connecting, reviewing and publishing runs to ~10 min.

Free plan: £0, 50 creditsAdmissions keeps the decisionsNothing live until you approve
Fig. 12.A · Training providers