WhatsApp follow-ups for Graphy academies: a practical message plan
A useful WhatsApp follow-up plan gives every academy message a reason, an owner and a stopping point. Start with the learner's request, connect it to the right course or booking, and decide what should happen when they reply, book, reschedule or opt out.
Create a message map before creating templates
List the situations your academy actually handles: a course question, a requested demonstration, a confirmed booking and a missed appointment. For each situation, write the trigger, the information needed, the intended recipient and the action that ends the workflow. This is an operating checklist, not a claim that every sequence is already configured in CloudFolks CRM. Begin with one course or team so you can inspect the outcomes before expanding.
Check permission separately from course interest
WhatsApp's Business Messaging Policy requires the recipient to have provided their contact information and opted in to subsequent communications. A public number, course enquiry or enrolment alone should not be treated as permission for every later message. Use your academy's verified permission process, retain the relevant evidence and respect opt-out requests. Choosing an approved template does not replace that permission check.
Choose the message type for the current conversation
The WhatsApp Business Platform policy distinguishes an approved template used to initiate a conversation from a reply within the customer service window. Outside the 24-hour window following a user's message, approved templates are required. Confirm the applicable message purpose before sending; a booking confirmation should provide the booking details the learner expects, rather than quietly become a promotional sequence. Recheck the current policy and template status when configuring your account.
Separate an invitation from a confirmed booking
An invitation asks someone to choose a time. A confirmation refers to a booking that actually exists. Keep the booking identifier, scheduled time, timezone and current joining link together. Do not insert a fixed sample meeting URL into a reusable workflow. If a joining link is unavailable, route the record for staff attention instead of sending a reassuring message with an empty or incorrect link. A website visit or booking-button click does not establish that an appointment was completed.
Use a simple sequence with clear stopping rules
Consider a fictional learner who asks for a demonstration and chooses Friday afternoon. An agreed process might send a confirmation after the booking is recorded and a reminder before the appointment. If the learner reschedules, cancel the old pending reminder and use the updated booking details. If they reply with a question, assign it to a person. If they decline or ask to stop, end the relevant sequence. A missed appointment should lead to the agreed rescheduling process, rather than an open-ended chain of repeated invitations.
Prepare variables with the data they represent
Map the recipient's name, appointment date, local time, joining link and rescheduling link independently. A booking identifier is not a person's name. Test names containing punctuation, a missing optional field, an international mobile number and a changed appointment time. Use fictional samples during template review and isolated tests. Before rollout, inspect the actual rendered message so that a technically successful request does not conceal the wrong greeting or an outdated meeting link.
Keep send attempts and learner outcomes distinct
Queued, accepted by a provider, delivered and read are different states. Store the provider result and show uncertainty explicitly when a response is lost. Before repeating an uncertain request, reconcile the original attempt and use the same stable intent identifier where the integration supports it. Do not create a new sending intent simply because the first response was slow. Your staff should be able to see a failed or held attempt and decide the next action without guessing that the learner received it.
Review the workflow with your team
Keep dated conversation notes, a named owner and the next follow-up date alongside the lead. Review which requests need a staff response and which scheduled messages should stop. If Graphy data is part of the workflow, confirm API access and the exact events or fields available in your account; a field visible in the LMS is not automatically available to every integration. Bring an anonymised example to a CloudFolks CRM walkthrough and check how your academy's enquiry, booking, reminder and rescheduling process should work together.