Enrollment consulting and trial-lesson appointment automation for education providers
Trial-lesson bookings, enrollment consulting, conflict prevention, automatic reminders, and no-show reduction — an appointment engine for courses and private tutoring.

At a course or private-tutoring institution, the start-of-term inbox always fills with the same questions: "My child is in 6th grade, which day can we come for a trial lesson?", "Do you have a weekend group?", "Is it one-on-one or group, and what is the fee?". Most of these questions lead to an appointment: first a placement test or a trial lesson, then a talk with the consultant, then the enrollment conversation. But the message that arrives after hours goes unanswered, the trial-lesson appointment is written in a notebook, someone forgets to call, and the parent does not show up. This article explains how to build your course's appointment engine in inTusell with education appointment automation — from trial-lesson bookings to enrollment consulting, and from reminders to fewer no-shows. It is the appointment-and-engine leg of the education vertical in our sector-based "how to train your AI" series; for the education cornerstone, see how to train the inTusell AI.
Quick answer
inTusell's appointment engine has four parts: (1) appointment types (trial lesson, placement test, enrollment meeting — duration + buffer), (2) working hours and exceptions, (3) conflict checking that blocks double-booking, and (4) multi-channel reminders 1 day and 2 hours before. When a student does not show up for a trial lesson, their slot is re-offered to suitable WhatsApp contacts in follow-up. Google Calendar is optional and works one-way (inTusell → Calendar).
Why appointment automation
There are two reasons to move trial lessons and enrollment meetings into inTusell: no request gets lost, and no appointment goes without a reminder. In manual mode, everything depends on one person's memory and working hours. In automatic mode, appointments come in 24/7 and reminders go out on their own.
The concrete difference looks like this:
| Situation | Manual appointment | Automatic appointment (inTusell) |
|---|---|---|
| Booking a trial lesson | During working hours, by phone | 24/7, through the channel the person wrote in |
| Conflicts | Prone to human error | Blocked by the system (no double-booking) |
| Reminders | By hand, one by one, can be forgotten | Automatic 1 day + 2 hours before |
| No-show | Empty slot, lost consultant hour | Re-offered to a contact in follow-up |
| Calendar | A separate planner | A one-way copy to Google Calendar |
This is where inTusell's "not a chatbot, but an experienced enrollment consultant" position becomes concrete. A good consultant does not hand out a trial lesson off the cuff — they check the calendar. They do not forget to call the parent; they send a reminder.
Who is it for?
- Test-prep centers, study centers, language schools, software/coding bootcamps, music and art courses.
- Teachers and small teams who offer one-on-one private tutoring.
- Institutions that run trial lessons and placement tests by appointment, where no-shows waste consultant hours.
- Teams that manage different durations and formats (one-on-one trial, group intro lesson, enrollment meeting).
No technical knowledge is required; you do the whole setup from the panel. To shape the AI side with your services and tone, see how to train the inTusell AI.
1. Setting up appointment types
The foundation of the appointment engine is appointment types. You define a type for each kind of meeting; a type has three important settings:
| Setting | What it does | Example |
|---|---|---|
| Duration | How many minutes the appointment lasts | Trial lesson 45 min, Enrollment meeting 20 min |
| Buffer | The gap left after the appointment | 10 min of classroom prep after the lesson |
| Color | Distinguishing it on the calendar | Trial lesson blue, enrollment meeting purple |
Duration matters because it lets the AI calculate the slot correctly. If you define "Trial lesson 45 min", the AI looks for a 45-minute opening. The buffer leaves breathing room between lessons for classroom prep and transitions. You can also add a fee to the type for informational purposes. Remember, though, that the AI never makes up the fee of a package it does not know — the how to use inTusell article covers price and enrollment-meeting behavior in detail.
2. Working hours and holiday exceptions
You define working hours so that the AI only offers appointments during the hours you are open. This has two layers:
- Weekly working hours: Opening and closing times for each day of the week (for example, weekdays 14:00–20:00, Saturday 10:00–17:00, Sunday closed). You mark closed days as "unavailable".
- Exceptions (overrides): A special rule for a specific date. To close the institution for a public holiday, a mid-term break, or an exam day, add an "unavailable" exception for that day and write a reason ("Mid-term break — closed"). You can also change the hours for a single day.
This way the AI does not offer appointments during a mid-term break, and a student cannot book a time after the evening lessons are over. Whatever your operating schedule, appointments follow it.
3. Conflict prevention: two students cannot share the same time
This is the appointment engine's most important safeguard. Before creating an appointment, inTusell checks two things: is the requested time within working hours, and is that slot full? If there is a conflict, it does not open the appointment.
One important detail: cancelled (cancelled) and missed (missed) appointments free the slot up again in this check. When a parent cancels, that time automatically becomes available and can go to another student. Scheduling two trial lessons for the same time — the most common mistake of a manual planner — becomes mathematically impossible. It also stops a teacher in one-on-one tutoring from promising the same slot to two students.
4. The reminder engine: 1 day + 2 hours before
This is the part that actually reduces no-shows. Two reminders are scheduled automatically for every appointment:
- 1 day before: "Hi [name]! 👋 You have a trial-lesson appointment tomorrow at [date time]. See you then! 😊 — [assistant name]"
- 2 hours before: "Hi [name]! ⏰ You have an appointment today at [time] — 2 hours to go! We're looking forward to seeing you 😊 — [assistant name]"
The message is signed with your institution's assistant name (ai_persona_name) and carries a one-tap cancel/reschedule link (/manage-appointment/...). If the parent tells you in advance that they cannot make it, the slot does not go to waste — the consultant can give that time to another meeting.
The reminder is not tied to a single channel; it works through a fallback chain:
- The channel the person wrote in (WhatsApp, Instagram DM, Telegram, Facebook Messenger).
- If the native channel fails, SMS.
- If SMS fails too, email.
- For those using web chat, the message is recorded directly into the conversation history.
You can turn reminders on or off for each appointment (reminders_enabled). An appointment booked on the same day, for example, may not need the 1-day reminder. The system sends each reminder only once and prevents the same reminder from going out twice.
5. No-show and re-offering the freed-up slot
If the student does not show up for the trial lesson despite all the reminders, you mark the appointment missed. That mark triggers a series of automatic steps:
- Pending reminder jobs are cancelled (they are no longer needed).
- The Google Calendar event is deleted if there is one.
- The freed-up slot is re-offered automatically to suitable contacts among the most recent interested or follow-up people.
- The parent moves into the follow-up flow ("follow-up needed").
Unlike the multi-channel reminders, this re-offer currently goes out via WhatsApp, and only to a few suitable contacts in follow-up. The system keeps no separate waiting-student list; it routes the opportunity to the warmest leads. A no-show therefore becomes a second chance rather than a lost consultant hour. For parents who have not yet had the enrollment meeting, it is a second point of contact.
6. Enrollment consulting: from trial lesson to enrollment
The appointment engine does not just fill the calendar; it is the first link in the enrollment chain. When a trial lesson is booked or takes place, the person becomes a record in the CRM and enters the follow-up flow. A clear line defines the AI's role at this stage:
- The AI advises on topics it knows: the program, days and times, format (one-on-one or group), and the terms in the knowledge base.
- On fees and special enrollment conditions, if there is no match in the knowledge base, it makes up no amount. It connects the person to the consultant team.
- The human-handoff mode is yours: fully automatic (
ai_only), AI and human together (hybrid), or human only (human_only). If you want a human to run the enrollment meeting from start to finish, the AI only books the appointment and the consultant handles the rest.
This way the bridge between the trial lesson and enrollment holds: the AI books the appointment and sends the reminder, while the consultant discusses enrollment with a warm lead. The how to use inTusell article shows how this flow is managed in daily operations, and Instagram and WhatsApp automation covers the channel side.
7. Google Calendar sync (one-way)
If you want your team to see their day in their own Google Calendar, connect the calendar with one-click OAuth. Let's be clear about how the sync works: it is one-way (inTusell → Google Calendar).
- When an appointment is created, an event titled "Appointment — student/parent name" drops into Google Calendar.
- When an appointment is rescheduled, the event is updated.
- When an appointment is cancelled or marked no-show, the event is deleted.
The reverse does not happen: a change you make by hand in Google Calendar does not flow back to inTusell, and conflict checking does not look at Google Calendar's busy times. inTusell always calculates conflicts from its own appointment book. That is why Google Calendar is a viewing convenience, not the appointment source. Even if you never connect it, appointments, reminders, and conflict prevention work exactly the same. You can review the integrations on the integrations page.
What it isn't
- It is not a student information system (SIS) or LMS. inTusell manages trial-lesson and enrollment-meeting appointments and reminds you of them; it does not keep grades, attendance, lesson content, or exam records.
- It is not a two-way calendar. It writes to Google Calendar but does not read from it; it calculates conflicts from its own book.
- It is not an e-Okul or MEBBİS integration. It does not connect to official education systems; it is the institution's operations and communication layer.
- It is not an education-specific priced product. You can enable the appointment engine on every package, and the pricing model is based on messages and voice minutes and does not vary by sector. For package details, see the pricing page.
Frequently asked questions
How is a trial-lesson appointment booked?
When a parent or student writes in via WhatsApp, Instagram DM, Telegram, Messenger, or web chat, the AI checks the trial-lesson type, its duration, and the available time slots, suggests a suitable slot, and creates the appointment. It opens no appointment outside working hours or in a slot that is already full.
When and through which channel are reminders sent?
Automatic reminders go out 1 day before and 2 hours before every appointment. The message goes first through the channel the person wrote in (WhatsApp, Instagram, Telegram, Messenger); if they cannot be reached there, SMS kicks in, and if that fails too, email. For web chat, the message is recorded in the conversation history.
Can two trial lessons be scheduled for the same time?
No. inTusell checks your working hours and busy slots and blocks any conflicting appointment. Cancelled or missed appointments free the slot up again in this check.
What happens when a student does not show up for a trial lesson (no-show)?
When you mark the appointment "missed", pending reminder jobs are cancelled, the Google Calendar event is deleted if there is one, the freed-up slot is re-offered automatically to suitable WhatsApp contacts in follow-up, and the parent moves into the follow-up flow.
Does the AI quote the course fee?
The AI quotes a fee only from the price and terms information you upload to the knowledge base. It makes up no amount for a package it does not know; it connects the person to the consultant team instead. The AI follows whatever your pricing policy is, and you can leave the fee conversation entirely to a human if you prefer.
Do I need separate software for the appointment system?
No. Appointment types, working hours, reminders, and calendar sync all come built into inTusell. Google Calendar is optional; even if you never connect it, trial-lesson appointments and reminders still work.
Next step
Once the appointment engine is set up, you can go in two directions. To shape the AI with your programs, tone, and enrollment limits, read how to train the inTusell AI. To see how incoming appointments and enrollment meetings are managed in daily operations, move on to how to use inTusell. The education solution page covers every part of the education solution, and the blog holds every article.
This engine uses the same backbone whatever the sector. To see how similar setups read across different verticals, look at the tour agency AI training and clinic AI training cornerstone articles.
If you would like us to set up your appointment and trial-lesson system together, Get a demo or write to hello@intusell.com. In 20 minutes we'll set up your working hours, your appointment types, and the first reminder together.
You read the blog — now see it live.
Test inTusell live with your own sector scenario in a 20-minute demo.