Back to case studies
Business schoolAdmissions and open days

Answer admissions questions and guide candidates to an open day

How to read this page

This page describes an implementation pattern. It publishes neither a testimonial nor a quantified client result.

The context

A business school wants to make admissions information accessible in the conversation and suggest the next step without replacing its team.

What the flow needs to cover

  • Answer from programmes, admissions rules and FAQs approved by the school
  • Present open-day dates published by the institution
  • Keep useful context when the team takes over the request

The mechanism

Skolbot uses institution-approved content, clarifies the candidate's request and prepares the handover.

  • The candidate asks questions in the widget on the school's website.
  • Answers use only information supplied and approved by the institution.
  • Open-day intent can open the registration flow defined by the school.
  • The record and conversation summary are sent through the workflow agreed with the team.

Organisation and responsibility

The admissions team remains responsible for appointments, special cases and keeping published information up to date.

Explore this approach for your school

Book a demo

One night, played twice.

Read the transcript

At 11:47 pm, LĂ©a, seventeen, is looking for a school. An advert takes her to a website, but a fifteen-field form stops her. Six hours pass: she is not in any CRM. The same night starts again with Skolbot. At 1:12 am, she asks about work placements and gets an immediate answer. She leaves her first name and number. In the morning, her record and a summary of the conversation are waiting in the CRM. Today, LĂ©a starts her course.