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.
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.
Fig. 01.A · Training providers
Fig. 02.A · pain quotesLearner 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.
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.
Next start dates, entry requirements, delivery pattern and the qualification a course leads to — as your own pages state them, evenings and weekends included.
Funded-place decisions, enrolment and any welfare disclosure go to the person you name, with what was written attached. The assistant states no outcome.
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.
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.
With Adoomi
Fig. 06.A · after-hoursNeither 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.
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.
Fig. 08.A · controlsThe 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.
Start dates, entry requirements, delivery patterns and funding criteria come from pages you approved. General knowledge is not a fallback.
Funded-place decisions, enrolment and acceptance stay with admissions. The assistant explains the criteria and captures the enquiry; it states no outcome.
A disclosure about a learner routes to the person you name, unanswered, with what was written attached. It discharges no safeguarding duty of yours.
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.
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.
Funding eligibility is never settled in chat. The assistant quotes the criteria your funding page publishes, captures what the learner has said about their situation, and passes it to admissions to confirm. It states no outcome and no cost your pages do not already publish.
Levy questions are answered as far as your employer pages go, then handed over. The assistant explains the published route, captures the organisation and the roles they want trained, and alerts your business-development contact. It cannot see a levy account or any funding system.
Outcome promises sit outside what it may say. The assistant repeats what your pages state about the qualification and the progression routes, and declines anything predicting a result for one person — including whether someone would pass assessment or be taken on afterwards.
Welfare wording is not answered. The conversation routes to the person you name with what was written attached, and additional-needs questions go the same way. Where learners are under eighteen that rule matters most, and it is absolute. None of this discharges a provider's safeguarding duties.
Starting costs £0 a month with 50 message credits, moving to £8 for 200, £20 for 500 and £75 for 4,000 as volume grows. Setup runs to ~10 min: point it at your course and funding pages, read what it proposes, then publish. Conversations are EU-hosted and deletable under GDPR.
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.
Start dates, entry requirements and delivery patterns given from your own pages, in the enquirer's language, whenever they ask.
Each side is asked different questions and alerted to a different person, so a levy enquiry never arrives dressed as an application.
Funding and place decisions are captured and passed to admissions, with the criteria your pages publish quoted back and nothing added.
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.
Fig. 12.A · Training providers