Use this when... you are reading or replying to parent, student, tutor, or internal messages and need to make sure the right context is used without exposing sensitive information.

Before you start... remember that conversations can include personal, financial, safeguarding, learning, or operational details. Use messages to communicate, but store durable decisions in the correct TuitionFlow record.

Use Messages to understand recent communication before changing records.

Conversation context helps admins avoid repeating questions, missing parent concerns, or changing records without understanding what has already been agreed. It is especially useful before editing attendance, cancelling lessons, sending invoices, assigning tutors, or replying to complaints.

However, messages are not the best place to store final operational truth. If a parent agrees to a schedule change, update Scheduling. If a payment is received, update Billing. If a student support need is disclosed, use the correct compliance or student record process.

Before replying, confirm whether the message is with a parent, student, tutor, employee, or internal team member. Check the related family, student, tutor, or invoice before sharing information.

Expected outcome: the reply goes to the right person and only includes information they should receive.

Scan the latest messages and any linked context. Look for cancellation requests, payment promises, tutor changes, safeguarding flags, trial questions, or unresolved complaints.

If the conversation changes something operational, update the owning record. For example, a cancellation should be reflected in Scheduling, a credit in Billing, and a tutor change in the student or session record.

When a conversation changes a lesson, update the schedule rather than relying on the message thread alone.

If a conversation includes safeguarding, learning needs, medical, consent, or GDPR information, avoid copying it into general notes. Use the correct restricted area and follow your organisation policy.

You cannot see enough context: open the linked family, student, tutor, session, or invoice record before replying.

A teammate gave conflicting information: pause and check the source record. Then reply with the corrected position and update the record if needed.

A message includes sensitive disclosure: follow your safeguarding, GDPR, or compliance process and avoid continuing the detail in broad conversation threads.

Use internal notes for team context that should not be sent to the parent, student, or tutor. Use messages for communication with the person involved. Do not put sensitive conclusions in a general message thread if only a safeguarding, compliance, or finance owner should see them.

Before sending a reply, check the recipient, tone, and action. Make sure you are not revealing another family, tutor, student, or payer detail. If the message refers to an invoice, session, cancellation, or tutor change, include enough detail for the recipient to understand the point without exposing unrelated records.

If the reply commits the team to an action, complete or assign that action immediately. Messages are easy to lose during a busy day, so turn decisions into record updates, tasks, or follow-up ownership.

If another teammate needs to continue the conversation, leave a clear internal handoff: what the user asked, what has been checked, what has been promised, and what the next owner should do. This prevents parents or tutors from repeating themselves.

Use clear wording in replies and internal notes so the team can search later. Include the relevant invoice, lesson date, tutor, or student name where appropriate, but avoid adding sensitive details that do not belong in the conversation.

After replying, update any affected TuitionFlow records and leave concise internal context where your team expects it. If the matter is urgent or sensitive, escalate to the responsible owner rather than leaving it buried in messages.