An adult learner who asks about a trial class has not enrolled. A confirmed place is not attendance, and attendance is not a decision to take the course. Useful trial class booking follow up keeps those states separate.
That distinction prevents awkward messages: no enrolment congratulations while someone is checking the timetable, and no promotional sequence after they decide the course is not right. The provider needs a visible state, one owner and an honest next step.
Name the four states before messaging
Use four records: interest, confirmed trial place, attendance outcome and enrolment decision. Interest shows that the person asked. Confirmation reserves a place. Attendance records what happened. Enrolment records a later choice and the provider’s completed process.
The wider adult education journey may include discovery, applications and support. Here, resist combining every stage into one label such as active lead.
| Current state | Evidence to keep | Useful next action | Do not assume |
|---|---|---|---|
| Interested | Course and question raised | Answer the question or offer a trial place | A place is reserved |
| Trial place confirmed | Session, time and explicit confirmation | Send practical attendance details | The learner will attend |
| Attended or missed | Recorded session outcome | Ask whether a specific next step would help | The learner wants to enrol |
| Enrolment decided | Clear choice and completed provider process | Continue the agreed course journey or close | Marketing permission has changed |
Confirm a place without claiming enrolment
A confirmation should identify the course, date, start time, location or joining method, and how to change plans. Explain any fee, cancellation rule, accessibility arrangement or equipment requirement first.
Keep the message narrow. “Your trial place is reserved for Tuesday at 18:30” records a booking. “Welcome to the programme” suggests a decision that may not exist. Keep replies in the same WhatsApp conversation so the learner need not repeat the details.
Examples are hypothetical. The provider remains responsible for its timetable, fees and obligations.
Send facts that help someone arrive
The best reminder removes uncertainty. Confirm the entrance or joining route, duration, what to bring and where to report a problem. Leave the full sales pitch out.
Replace an old location everywhere the team sees it. Record cancellation instead of leaving the place confirmed. If the provider cancels, name the owner for alternatives and payment consequences.
A shared team inbox can keep conversation, assignment and notes together. Record only useful context, such as “needs step-free entrance details”, not sensitive information merely because a field exists.
Record attendance as an event not a verdict
Attendance proves only that the learner came. It does not prove satisfaction, fit, payment or enrolment. A missed class may reflect a travel problem, changed mind or cancellation through another route.
Use a neutral outcome such as attended, cancelled, provider cancelled or no confirmed attendance. Connect it to the contact and lead record without overwriting the question. Verify external connections separately; do not claim an unverified native integration.
Follow up from the learner’s actual decision
After an attended trial, a useful message might say: “You asked whether the evening pace would work around shifts. Would you like the next timetable, or have you decided not to continue?” It gives the learner two legitimate outcomes.
After a missed session, avoid guilt. Ask whether they want another available trial, the information originally requested, or no further follow up. One relevant question is better than a sequence that treats silence as indecision.
WhatsApp’s Business Policy requires a supplied number or username and opt-in for subsequent contact, and requires businesses to respect stop requests. Business-initiated Platform conversations use approved templates outside the customer service window. Template approval does not replace permission.
The official marketing-message overview describes lead nurturing as marketing after opt-in. A trial booking supports operational information about that booking, not automatic permission for unrelated promotions. Local requirements still matter.
Give every reply an owner and a stop rule
Before using automation, test confirmation, cancellation, attendance, enrolment, a reply and an opt-out. Replies need a visible owner, and queued reminders must not contradict a changed state.
Measure correct details, changes handled before class, assigned replies and clear decisions. Do not present delivery or attendance alone as enrolment success.
Frequently Asked Questions
Is a trial booking the same as an application?
No. A trial booking reserves or requests a session. An application or enrolment has its own evidence and process. Keep separate states even if one person moves through them quickly.
What should a trial class reminder contain?
Include the course, date, time, place or joining method, duration, useful preparation and a route for changes. Leave unrelated promotion out.
Should we message someone who missed the class?
Only when purpose and permission support it. Ask one neutral question and offer a clear way to stop. A missed class is not consent to repeated reminders.
How should a team judge the workflow?
Check accurate details, handled changes, owned replies and recorded decisions. Keep those measures separate from enrolment.
Want help applying this guide?Ask the DripTell team
From reading to action
Want help applying this to your business?
Share your details. We will read the article you are on and start with a useful answer for your team.
DripTell Editorial
Practical guidance reviewed by the DripTell product and customer workflow team.
See how DripTell checks product claims, uses primary sources and handles corrections.
Editorial and source policy
