For students
Receive the school’s enabled booking messages through available channels. Messages about an opening are separate invitations: an available-time offer needs an explicit acceptance before it becomes a booking.
Booking details matter after the calendar fills. RouteOS lets schools configure messages around appointment events, including confirmations, upcoming-lesson reminders and changes, with each channel depending on the school’s connected notification setup.
Delivery uses your configured channels.
Follow an illustrative Monday lesson. The school has enabled a customer confirmation and a reminder one day before the start. Staff choose the workflow, timing, recipient and message; the saved booking supplies the appointment context.
In Automation, the school creates a workflow for a booking event. It can select a customer or staff message action and the available email, SMS or WhatsApp processor. Conditions can narrow which bookings qualify. A reminder can run minutes, hours or days before the booking starts, provided the school has a working scheduled-job runner.
When a booking is successfully created, configured workflows can send or queue a confirmation with the student’s actual lesson details. The office can also configure separate messages for the assigned instructor. A draft, queued job and provider-accepted message are different states; staff can review the job or delivery result when follow-up is needed.
The scheduled job uses the configured offset from the appointment start. A short reminder can point the student to the lesson time, location and school instructions available in the booking template. Schools should keep sensitive identity or permit details out of ordinary email and text messages, and honor each channel’s consent and suppression settings.
If the saved booking changes, RouteOS’s underlying booking workflow removes its pending scheduled jobs and rebuilds eligible reminders using the updated booking. A separate booking-updated workflow can tell the student or instructor about the change. Jobs already sent remain in the history; the office should check results before sending another message.
Illustrative example. Explore each step to see how the workflow connects. This demonstration does not change any school records.
Receive the school’s enabled booking messages through available channels. Messages about an opening are separate invitations: an available-time offer needs an explicit acceptance before it becomes a booking.
Set event rules, message templates and reminder offsets. Check scheduled jobs and notification results, review changed appointments, and follow up directly when a channel is unavailable or a delivery fails.
Receive configured appointment notices when the school enables an instructor workflow. The calendar remains the source for the current lesson time and permitted student context.
Native workflows include booking created, updated, start and end events, plus customer, order and payment-request events. The school can add conditions and schedule actions before or after the selected event.
Appointment reminders, direct booking conversations and Automatic Gap Filler offers have separate actions. A student can review a gap offer without changing an appointment; accepting it invokes the offer’s final availability and booking checks.
Email, SMS, WhatsApp and mobile message push depend on their configured processor, recipient details, consent or preferences, scheduled jobs and provider readiness. A queued or sent notification is not proof that someone read it.
Yes. A booking-start workflow can use a configured offset in minutes, hours or days. The scheduled-job runner and the chosen channel must be working for the message to run.
The booking workflow removes pending jobs for the old booking context and schedules eligible jobs against the saved new context. A separately configured booking-updated workflow can announce the change. Already-sent messages remain sent.
No. Each school must configure its email or messaging processors and enable the relevant workflows. Mobile push for booking reminders should not be assumed; the current mobile push integration is for supported Messages notifications.
No. A reminder is a communication about a booking. Attendance, instruction time, document possession and state readiness need their own recorded evidence and staff checks.
Let’s look at your school
Tell us how your school confirms appointments and follows up. We’ll review event-based messages, reminder timing and your available channels.
Request saved
Your walkthrough request has been saved. Choose a time on Calendly to complete your meeting booking.
Choose a walkthrough timeCalendly opens on its own website and asks for the information needed to book. Your meeting is confirmed only after you complete that step. Calendly provides the time, confirmation and rescheduling details.