The rule for choosing and running parent-communication software: verify three things — messages to authorised destinations, consent records, and contact-data accuracy. The real risk of communication software is not in its features — it is private data reaching a wrong number, messages without consent, and whose hands the data ends up in.

What to verify: a policy checklist for authorised destinations

The contact-governance checklist:

# Check Question
1 Authorised destination does the system guarantee messages go only to authorised guardian numbers?
2 Consent record is there a record of which guardian consented to which channel?
3 Accuracy is there a mechanism to catch number/email entry errors?
4 Data ownership is all contact data exportable if we leave?
5 Privacy does any message expose sensitive student information publicly?
6 Roles are message authorship and sending permissions separable?

The destination policy is the core protection: when composing any notice, the system should show only the authorised guardian-number list — not hand-typed numbers. Hand-typed numbers are the main source of wrong-destination accidents.

A usable sample: the contact governance checklist

Verify these 6 fields when choosing software:

  1. Does the software support a consent line on the admission form?
  2. Can per-guardian channel consent be recorded?
  3. Do message templates send from the authorised number list only?
  4. Privacy: individual results to individual numbers — system-guaranteed not to groups?
  5. Data export: can all contact data leave with the institution?
  6. Role split: can message authorship and sending permission be separated?
  1. Year-start campaign: a test notice to every guardian number — corrections for failures.
  2. Keep the message policy (what goes on which channel) written — see the planning article.
  3. Limitation: software supports consent and accuracy, does not guarantee them — the year-start verification campaign is the guarantee.
  • Is there a consent-record field?
  • Is the destination list visible before sending?
  • Is data export free and complete?

See communication features and gateways in the communication module; number-accuracy work in attendance documentation; price comparison on the pricing page.

Messaging policies exist by country [VERIFY: current Bangladesh rules] — keeping a consent line in the policy is both safer and more respectful.

Is contact data sensitive?

Yes — data containing student+guardian names and numbers, if leaked, puts student safety at risk; ask about gateway security and export controls.

Sensitive data went to a wrong destination — what now?

Immediate phone call + a written incident note + number correction — and prevention in the entry method (selection only from the authorised list).