LanguageENES

AI chatbot for schools and universities

Admissions questions, answered on the page they are asked on

An admissions office answers the same forty questions from September to January, in several languages, while the answers sit published on a website nobody manages to navigate. An assistant reads that same site and answers on it.

The situation before

Deadlines, fee schedules, entry requirements and accommodation rules are all published, spread across a site built by four departments. So applicants email the admissions address, and somebody retypes the deadline four hundred times.

What to feed it
  • The prospectus and course catalogue
  • Fees, funding and scholarship pages
  • Entry requirements and deadlines
  • Accommodation and student life policies

What it does

The whole site, not one page

The crawler reads the prospectus, the fees page and the policies, so one answer can combine what three departments published separately.

Answers in the applicant's language

The same knowledge base answers in the language of the question, which matters when a third of the applications are international.

Enquiries become records

A question that needs a person becomes a lead with the transcript, routed to the right office instead of a shared inbox.

Questions people ask

Is it safe to put in front of applicants?

It answers from what you published and cites it, and it says it does not know rather than guessing at a deadline.

Can departments have their own?

Yes. A knowledge base and a widget per department, each on its own pages.

What about dates that change?

Update the page and the crawl picks it up on its schedule, or push the change through the API immediately.

Connect it to