School administrators
Prepare the message or request
Schogle · Communication & approvals
Message Inbox & Divert
Manage incoming messages and their approval-linked diversion.
Communication & approvalsSchool task · Message Inbox & Divert
Message Inbox & Divert
Message Inbox & Divert
Parent · Who should I speak to about the school activity?Sample school record
- 01 · EntryMessage Inbox
- 02 · RoutingMessage Divert
- 03 · BoundaryDiversion approval
Who should review this incoming message?
A school message enters the inbox. Where configured, diversion follows its own approval-linked workflow rather than an assumed automatic forwarding chain.
01Message Inbox
Read the question with its school context
Start with the incoming question and the people involved. The inbox gives the school a place to review messages before deciding whether another team needs to handle the request.
- Parent — Who should I speak to about the school activity?
- School office — An incoming question needs the right school team.
- Next responsibility — Review the incoming message; routing is a separate task.
For school administrators
Messages routed through the documented review process.
Communication & approvalsSchool task · Message Inbox & Divert
Message Inbox
Message Inbox
Parent · Who should I speak to about the school activity?Sample school record
02Message Divert
Review where this message needs to go
A parent’s question may belong with a different school responsibility. Keep diversion separate from reading the inbox, and follow the configured review process rather than assuming every message is forwarded automatically.
- Parent — Who should I speak to about the school activity?
- School office — The request belongs with the activity coordinator.
- Next responsibility — Follow the configured diversion review before routing.
For school administrators
Messages routed through the documented review process.
Communication & approvalsSchool task · Message Inbox & Divert
Message Divert
Message Divert
Parent · Who should I speak to about the school activity?Sample school record
03Diversion approval
Keep the record and the reviewer together
Review the proposed diversion before the message follows its next path. The responsible reviewer keeps the decision attached to the request; this is not a multi-level approval chain.
- Diversion approval — Incoming school message
- Entry — Message Inbox
- Routing — Message Divert
For school administrators
Keep the decision with the responsible school team.
Communication & approvalsResponsibility · School administrators
Diversion approval
Review in school contextResponsible role · Defined scope
Diversion approvalIncoming school message
EntryMessage Inbox
RoutingMessage Divert
Human review remains a separate step
Diversion approval · Incoming school messageSample 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 message inbox & divert cover?
Manage incoming messages and their approval-linked diversion. Its documented capabilities include Message Inbox, Message Divert, Diversion approval.
Who benefits from this workflow?
School administrators, Teachers, Parents and students. Messages routed through the documented review process.
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.
See this workflow with your school in mind.
Review the relevant records, configuration and current scope with our team.