Someone who attended your open day needs a different message from someone who missed it or has already applied. Useful open day follow up messages connect that difference to the learner’s actual question, not simply their presence on a registration list.
For adult learners, the unresolved detail might be whether classes fit around work. Sending another course introduction does little if the person is waiting for a timetable. Start there rather than rebuilding the whole admissions conversation.
Separate attendance from the question
Attendance tells you what happened at the event. It does not tell you what someone needs now. An attendee may still be comparing schedules; an absent registrant may already know which course they want.
Before drafting, distinguish attendance, the question raised, application progress and permission to contact. Keep these separate so that changing one does not silently change the others. Registering for an event is not the same as requesting every future course promotion.
For broader context, the adult education journey covers the surrounding conversation. Here, focus on the handover from an open day to a useful decision.
Match the message to a real decision
The following examples are hypothetical. They describe adult learners and suggested actions, not actual student records or promised results.
| Situation | Actual question | Useful follow up | When to stop |
|---|---|---|---|
| Attended | Can classes fit around work? | Send the requested timetable | Resource delivered unless another step was agreed |
| Could not attend | What did the session cover? | Offer a short recap | Recap declined or no further step agreed |
| Attended and comparing | Which course covers the relevant topic? | Share the relevant syllabus section | Question answered |
| Application started | What must I complete next? | Explain the outstanding application step | Step completed or adviser takes over |
| No longer interested | Can you stop messaging? | Acknowledge and end follow up | Immediately |
Do not move an applicant backwards into an event promotion simply because their registration remains on the list. Equally, missing the event should not automatically mark someone as uninterested. Ask what would help if contact permission allows it.
Write one message that earns its place
For a hypothetical attendee, try: “You asked whether the evening course fits around shift work. Here is the timetable. Would you like an adviser to explain the attendance requirements?”
For a hypothetical absent registrant: “You couldn’t join the open day. Would a short course recap help, or would you prefer to leave it here?” Avoid making them explain their absence.
For a hypothetical applicant: “You asked what remains before submitting. Would you like help understanding the outstanding step?” Do not request sensitive identifiers or application documents in an ordinary message thread.
Each example offers a limited, relevant action. None assumes that silence means permission for a sequence. Check the WhatsApp channel context before choosing how the message will be sent.
Keep event permission distinct from marketing
WhatsApp’s Business Policy requires both a supplied number or username and opt-in permission for subsequent contact. It also requires businesses to respect requests to stop, including requests received outside WhatsApp.
Check what the learner actually agreed to receive. Permission for event arrangements should not be stretched into an ongoing course promotion programme. Applicable local requirements still matter.
The official marketing overview describes lead nurturing and re-engagement as marketing uses after opt-in. Calling a promotional message an “open day update” does not change its purpose. Business-initiated Platform messages require approved templates; template approval does not replace permission.
Give replies somewhere useful to go
An adviser needs the original question and the promised action, not a transcript to decipher. Use shared inbox assignment and notes to make responsibility clear. Record only useful context, such as “requested timetable explanation”.
In DripTell, contacts and lead stages can sit alongside shared inbox assignment and notes; journeys can be configured to pause or end. Those settings need deliberate configuration, not an assumption that every reply stops everything.
Keep attendance separate from application progress. Before enabling automated follow up, test a reply, a completed step and a stop request. Confirm that queued messages no longer contradict the conversation. Any connection to an application system needs separate confirmation.
Frequently Asked Questions
Should everyone receive a thank you message?
Not automatically. Check permission and purpose first. A requested resource may be more useful than a generic thank you, while someone who declined contact should receive no further promotion.
What should we send after no response?
Do not invent another reason to contact them. Follow an expressly agreed next step if one exists. Otherwise, let the conversation rest rather than treating delivery or read status as renewed interest.
How should we judge the follow up?
Look for whether the question was answered and the agreed action became clear. Separate delivery, reading and replies from application progress. A learner deciding not to proceed can still mean the conversation did its job.
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
