AI chatbots for language and swimming schools: schedules, fees and make-up lessons
Prepare a school chatbot for real parent and student questions. Separate course information, individual records and booking changes, with sample answers and a launch checklist.
An AI chatbot can explain your course offer, fees, locations and make-up lesson rules while your team teaches. It can also guide parents and students to the right next step. An individual absence, available place or booking change needs an authorised connection to the relevant system, or a member of staff.
That distinction matters because school enquiries often combine both. “How do make-up lessons work?” is a question about a policy. “Can you move my daughter's lesson to Friday?” is a request concerning a particular enrolment. A useful chatbot recognises the different requirements instead of giving both questions the same confident answer.
The examples below describe an illustrative school. They are templates to adapt, not results from a customer deployment. Prices, deadlines and course details are fictional.
Start with the questions reception actually answers
Ask the person managing your inbox to list recurring questions before preparing the bot. Language and swimming schools often need to explain similar administrative details, even though course selection differs.
| Topic | Language-school example | Swimming-school example |
|---|---|---|
| Course choice | “I studied English years ago. Which level should I choose?” | “My child is comfortable in water but cannot swim independently. Which group fits?” |
| Schedule | “Are there lessons during the school holidays?” | “Does the course run on public holidays?” |
| Fees | “Are course books included?” | “Does the fee include pool admission?” |
| Preparation | “Do I need to take a placement test?” | “What should we bring to the first lesson?” |
| Absences | “Can I attend another group if I miss a class?” | “How do I request a make-up lesson?” |
| Changes | “Can I switch to the evening group?” | “Is there space in Saturday's class?” |
The last row needs more than a general course description. Treat it as a separate workflow from the information the bot can answer immediately.
Prepare one clear source for each term
Create a current course overview with the term dates, locations, lesson length, intended audience, price and inclusions. Write the year as well as the month. State whether holidays and planned closures are included in the timetable.
An example source could say:
Adult English conversation, autumn 2026, Riverside branch. Twelve 60-minute lessons, Tuesday at 18:00. The course fee is €240 and includes digital materials. A printed workbook is optional and paid separately. The published course calendar lists the dates when lessons take place.
For swimming, include the meeting point, arrival instructions and whether a parent accompanies the child. For both, identify the exact calendar that overrides the general weekly description. “Every Tuesday” is incomplete if the school closes for part of the term.
Keep the bot's material focused on the current offer. Remove expired registration campaigns or clearly label historical material so last term's discount is not presented as today's price. After an update, check the processed source and ask the corresponding question again. The guide to training your chatbot covers the preparation process.
Explain make-up rules before offering a change
A make-up policy needs to answer four questions: how an absence is reported, the deadline, who is eligible and how the replacement is arranged. Also state any limits and whether an unused entitlement expires.
Here is a fictional rule suitable for a source document:
Report an absence through the student portal by 18:00 on the day before the lesson. An absence reported on time may be replaced once, subject to capacity in an eligible group during the same term. Reception confirms the replacement. Sending a request does not reserve a place.
From that source, a helpful answer to “My lesson is tomorrow; can I replace it?” would check the relevant timing, explain the portal step and distinguish the request from a confirmed replacement. It should not promise a place on Friday merely because Friday appears in the timetable.
If the rule does not cover late reports or an exceptional situation, send the question to staff. Do not make the chatbot invent a compassionate exception or an automatic refusal. Your team owns that decision.
Keep course guidance within the evidence
A language chatbot can explain the published level descriptions and link to a placement test. It should not promise that a short chat is equivalent to your school's assessment. If two levels overlap, offer the assessment route or a conversation with the coordinator.
For swimming, describe the entry requirements exactly as your instructors have approved them. Avoid deciding from a few messages that a child is ready for a particular class. The bot can explain the assessment or trial-lesson process; the school makes the placement decision.
You usually need the intended course, approximate level and preferred location to guide an enquiry. You do not need to ask visitors to describe a child's health history in an ordinary chat. Direct personal or sensitive matters to the school's appropriate contact process.
What Breezaro can connect
You can provide website pages and documents for course information, then let your team review conversations and take over when needed. See the human takeover guide and the knowledge-base documentation.
For an individual record or booking workflow, Breezaro offers Custom Actions connected to HTTPS APIs. This is a configurable connection, not a ready-made integration with every school management system. Your system must expose a suitable operation, and you must define who can access each enrolment. Verifying a parent's email alone does not prove access to any child record the visitor names.
For a supported booking change, the intended process is: retrieve authorised options, show the proposed change, obtain confirmation and check the returned result. Data-changing actions in Breezaro require a confirmation button in the web widget. They are not offered in WhatsApp, Messenger or Instagram. Without the necessary connection, the bot should explain how to submit a request or involve reception.
Test the awkward cases before launch
Use separate conversations to test these cases with your own rules:
- A parent asks about last term's price and the current term in the same message.
- A student reports an absence immediately before and after your deadline.
- Someone requests a class that exists but is full.
- A visitor asks about a named student without being authorised to see their record.
- A family asks for a human when reception is closed.
- A booking operation fails after the visitor confirms it.
Write the expected next step beside each question. Check for correct dates and conditions, an honest description of any uncertainty and no unconfirmed booking promises. The chatbot testing checklist can help extend the set.
Begin with one course family and its current documents in Breezaro. Once the answers are reliable, add more courses and consider a connected action for the most frequent administrative request. Reception will have a clear role throughout: own the rules, handle exceptions and confirm what requires a person.