A driving-lesson reminder should tell the student exactly what the instructor will act on: the date and start time, the appointment’s current pickup address or meeting point, the lesson length, what the student must bring, the change or cancellation cutoff, and one monitored way to report a correction. “Your lesson is tomorrow” is not enough when the student has more than one address or the booking was moved.
Use the appointment’s pickup—not the customer’s default address
The common failure is a reminder that pulls “home” from the student profile while the actual appointment begins at school, work, a train station, or the DMV. The reminder should use the pickup saved on that specific booking. Write the full street address and, when needed, the meeting detail: “front entrance on Oak Street” is more useful than “school pickup.”
If the student is expected to check the address, say what action records the correction. A reply that nobody sees before the lesson is not a change process. Route replies to the office or another monitored inbox, and state the deadline for correcting the pickup.
A copy-ready driving-lesson reminder
Replace every bracket with a live booking field or a deliberate sentence. Do not leave optional fields blank in the message.
[School name]: Driving lesson reminder
[Student first name], your [lesson type] is on [day, date] at [time and time zone] for [duration].
Pickup: [full appointment pickup address or exact meeting point].
Instructor: [name]. Training car: [color/model or school identifier, if reliably assigned].
Bring: [permit/license or document the school requires], plus [corrective lenses or other confirmed item when applicable].
Check the pickup above. To correct it, reply [keyword] or use [monitored link/number] by [deadline]. To cancel or reschedule without [fee/lost credit], make the change by [exact cutoff]. After that: [plain consequence].
[Confirmation instruction: Reply C to confirm / confirmation link]. [Sender and required opt-out wording for the school’s messaging program.]
The instructor and car lines should appear only when those assignments are reliable. A confidently wrong vehicle description creates a new problem. If assignments often change, identify the school and give the student one contact method instead; send a separate change notice when a confirmed instructor, vehicle, time, or pickup changes.
Do not make one reminder do three different jobs
A booking confirmation records what was reserved. A change notice goes out as soon as a material detail changes. The reminder restates the latest appointment and asks the student to catch an error before dispatch. Waiting for tomorrow’s reminder to reveal that today’s pickup was changed leaves staff working from two versions of the booking.
Appointment platforms commonly separate confirmations, reminders, changes, and cancellations for this reason. Square’s current appointment guidance also treats reminders as transactional messages and supports distinct change and cancellation notifications. Keep sales offers out of the lesson reminder; they compete with the address and action the student needs to notice.
The cancellation line should repeat the real cutoff rather than linking to a policy with no summary. If the school still needs to choose its rule, use the RouteOS guide to write a cancellation policy customers can understand, then make the booking page, reminder, and staff action match it.
Test the rendered message before turning it on
Preview the real output for a home pickup, a school or DMV meeting point, and a booking whose pickup was changed after confirmation. Check the displayed time zone, blank variables, shortened links, and whether a long SMS breaks in an awkward place. Then send a test reply through every promised change method and confirm that staff can see which appointment it belongs to.
Also test the failure path: if the appointment has no valid pickup, the system should flag the booking for staff instead of sending a polished reminder with an empty address. A reminder cannot prevent the wrong pickup when its source record is already wrong.
For automated texts, follow the messaging provider’s current consent and opt-out rules. Twilio’s Messaging Policy, for example, requires prior consent for informational messages such as appointment reminders, clear sender identification, and prescribed opt-out handling. Those platform requirements are separate from any laws that apply to the school and recipient.
If RouteOS sends the reminder, map the pickup line to the appointment’s current pickup record—not merely the student profile—and make a pickup correction update the same booking the instructor sees. The final check is simple: hand the rendered reminder to someone unfamiliar with the appointment. They should be able to answer where the instructor is going, when the lesson begins, what the student must bring, and exactly how a change will be recorded without calling around.