School announcements are most useful when the right parent or guardian receives one clear, timely message. A class meeting notice, transport change and school-wide update need different audiences. Preparing those audiences carefully matters as much as writing the text.
This guide uses a fictional school and invented event details. Keep private student information out of general announcements and use an appropriate individual conversation when a message concerns one family's circumstances.
Set up a clear audience and sender
You need access to Contacts and campaign management, an available SMS sending identity, and sufficient spendable balance. Confirm who may prepare an audience, who checks the wording and who handles parent questions after the send.
In Contacts, create groups that correspond to a real announcement audience: “Class 4 meeting — current term,” “Bus Route A guardians,” or “Open-day attendees.” Use a current register supplied through the school's established process. Verify the intended guardian's complete phone number rather than assuming an old list is still correct.
A parent may have children in several classes. For one whole-school announcement, prepare a consolidated audience and check duplicates instead of sending the same message independently to every class group. Duplicate checks within one group do not prevent repeated messages across separate campaigns.
Review communication preferences. Unchecking subscription does not currently exclude a contact automatically from messaging campaigns. Remove contacts who should not receive the planned message from the target group and use the applicable blocking controls.
Prepare a message that answers practical questions
Use the school name, event or change, exact date and time, location and next step. Check these facts with the staff member responsible for the activity. Avoid relying on “tomorrow” when the message might be sent late or read the next day.
Example:
Example School: Class 4 parent meeting is on 21 October at 15:00 in Hall B. Please bring your questions. For help, contact the school office.
Use a verified office contact in the final message if recipients may not already have it. Do not tell parents to reply to an SMS sender name unless you have confirmed that the selected identity supports replies and someone monitors them.
For notices in different languages, prepare and review each complete version. A Swahili notice should be checked by someone able to verify both the wording and the school details. Keep the audience and sending plan clear so a bilingual parent is not accidentally sent several copies.
Test before sending to parents
- Create a small test group containing authorized staff numbers that you control or have arranged to use for testing.
- Open Marketing → Campaigns and the campaign creation form.
- Select the school SMS Sending identity and the test Contact Group. Paste the final Message and inspect the preview.
- Check the estimated cost and balance. Selecting Create Campaign without a future Schedule starts processing, so treat the test as a real send.
- Inspect the received SMS on a phone. Confirm the visible sender, school name, date, time and contact instruction. Check the individual message result in the workspace.
- Correct any issue before preparing the parent campaign. Keep the approved wording together with the audience rule and the person who reviewed it.
A long notice can occupy several SMS segments. Test the final copy, particularly after adding personalized names or additional language text. Use SMS budget planning to understand the estimate and provider-reported segments.
Schedule the parent announcement
Create the live campaign with a specific name, such as “Class 4 meeting — 21 October notice.” Choose the checked parent group and the same tested sending identity. Recheck the count against your register.
Set a future Schedule if staff need time to review the final audience. Confirm the saved sending date and time. Send Interval spaces dispatch between recipients, so allow enough lead time for the whole group. Leave Recurring campaign off for a single meeting notice.
If you need regular reminders, use a finite series and review membership before each run. Recurrence sends to the group's current contacts; it does not know when a student changes class or a guardian's responsibility changes. Follow recurring SMS campaign guidance before enabling it.
Handle delivery problems and corrections
Review the campaign's individual message results after dispatch. “Sent” and “delivered” describe different stages, and neither proves that a parent has understood or acted on the announcement. Arrange another appropriate contact method when a particular family's response is essential.
If Hall B changes to Hall C after sending, create a correction for the affected audience: “Correction to the Class 4 meeting notice: the venue is Hall C. The date and time are unchanged.” Check those remaining details again before sending.
Pause or cancel any pending duplicate notice where available, then inspect what was already queued. Restart can send fresh messages to everyone in the group; it is not a failed-recipient-only retry. Use delivery troubleshooting for failures and contact import checks when numbers or group data need correction.