School administrators
Prepare the message or request
Schogle · Communication & approvals
Approval Events
Retain shared approval history across communication requests.
Communication & approvalsResponsibility · School administrators
Approval Events
Review in school contextResponsible role · Defined scope
Approval EventsRecorded school decision
RequestMessage, appointment or diversion
DecisionResponsible reviewer
Human review remains a separate step
Approval Events · Recorded school decisionSample school record
- 01 · RequestMessage, appointment or diversion
- 02 · DecisionResponsible reviewer
- 03 · HistoryShared approval events
Which decision belongs to this school request?
The school keeps supported message, appointment and diversion decisions in shared approval history. This history does not establish a multi-level approval chain.
01Approve Messages
Keep the record and the reviewer together
Approve Messages defines who reviews or accesses this part of approval events. Start with the relevant request or record, then use the school’s configured responsibility boundary. This does not imply a multi-level approval chain.
- Approve Messages — Recorded school decision
- Request — Message, appointment or diversion
- Decision — Responsible reviewer
For school administrators
Keep the decision with the responsible school team.
Communication & approvalsResponsibility · School administrators
Approve Messages
Review in school contextResponsible role · Defined scope
Approve MessagesRecorded school decision
RequestMessage, appointment or diversion
DecisionResponsible reviewer
Human review remains a separate step
Approve Messages · Recorded school decisionSample school record
02Approve Appointments
Keep the record and the reviewer together
Review appointment requests through the school’s responsible team. Confirm the available decision actions and notification behaviour in a demo.
- Approve Appointments — Recorded school decision
- Request — Message, appointment or diversion
- Decision — Responsible reviewer
For school administrators
Keep the decision with the responsible school team.
Communication & approvalsResponsibility · School administrators
Approve Appointments
Review in school contextResponsible role · Defined scope
Approve AppointmentsRecorded school decision
RequestMessage, appointment or diversion
DecisionResponsible reviewer
Human review remains a separate step
Approve Appointments · Recorded school decisionSample school record
03Message Divert approval
Keep the record and the reviewer together
Message Divert approval defines who reviews or accesses this part of approval events. Start with the relevant request or record, then use the school’s configured responsibility boundary. This does not imply a multi-level approval chain.
- Message Divert approval — Recorded school decision
- Request — Message, appointment or diversion
- Decision — Responsible reviewer
For school administrators
Keep the decision with the responsible school team.
Communication & approvalsResponsibility · School administrators
Message Divert approval
Review in school contextResponsible role · Defined scope
Message Divert approvalRecorded school decision
RequestMessage, appointment or diversion
DecisionResponsible reviewer
Human review remains a separate step
Message Divert approval · Recorded school decisionSample school record
04Shared approval_events log
Recorded school decision
Use shared approval_events log to review or prepare the recorded information from approval events. Recorded school decision remains the subject of the review, so the output stays connected to the school task rather than becoming a separate register.
- Request — Message, appointment or diversion
- Decision — Responsible reviewer
- History — Shared approval events
For school administrators
Keep the decision with the responsible school team.
Communication & approvalsRecord area · Approval Events
Shared approval_events log
Review in school contextResponsible role · Defined scope
RequestMessage, appointment or diversion
DecisionResponsible reviewer
HistoryShared approval events
Human review remains a separate step
Request · Message, appointment or diversionSample school record
Connected school responsibilities
The right context for the next conversation.
Keep publication, requests and review responsibilities visible rather than losing the process inside separate messages.
Teachers
Review the audience or approval
Parents and students
Publish and follow up
Before your school gets startedA clearer workflow.
A clearer workflow.
A considered next step.
What does approval events cover?
Retain shared approval history across communication requests. Its documented capabilities include Approve Messages, Approve Appointments, Message Divert approval, Shared approval_events log.
Who benefits from this workflow?
School administrators, Teachers, Parents and students. Approval events recorded across supported request types.
What should we confirm in a demo?
Review supported screens, configuration and current availability with your school’s responsible team. Multi-level approval chains are pending. Current send-channel configuration and registered screens need demo confirmation. Multi-level approval chains are pending.
See this workflow with your school in mind.
Review the relevant records, configuration and current scope with our team.