Request Classification

Interpret the user’s request before choosing a supported school tool.

Book a Demo
SchogleSahayak
Responsibility · Authorised staff

Ask Sahayak

Staff request

Show the timetable for Class VI A.

Sahayak
Looking for a class timetable

Class VI A · Timetable read tool

School information stays within your permissions.
Timetable request identifiedConcept example · confirm availability
Sample records · Concept presentation, not a verified ERP screen.
  1. 01 · InputStaff request
  2. 02 · InterpretationRequest classification
  3. 03 · Next stepSupported school tool

Which supported school tool fits the request?

A staff member asks for school information. Classification identifies a supported tool before the assistant retrieves context.

01Request classification

Keep the record and the reviewer together

Request classification defines who reviews or accesses this part of request classification. Start with the relevant request or record, then use the school’s configured responsibility boundary. This does not imply a multi-level approval chain.

  • Request classification — Supported school request
  • Input — Staff request
  • Interpretation — Request classification
For authorised staff

A request routed into the supported assistant workflow.

SchogleSahayak
Responsibility · Authorised staff

Ask Sahayak

Staff request

Show the timetable for Class VI A.

Sahayak
Looking for a class timetable

Class VI A · Timetable read tool

School information stays within your permissions.
Timetable request identifiedConcept example · confirm availability
Sample records · Concept presentation, not a verified ERP screen.
02Cloud assistant using Gemini and Groq

Keep the record and the reviewer together

Cloud assistant using Gemini and Groq defines who reviews or accesses this part of request classification. Start with the relevant request or record, then use the school’s configured responsibility boundary. This does not imply a multi-level approval chain.

  • Cloud assistant using Gemini and Groq — Supported school request
  • Input — Staff request
  • Interpretation — Request classification
For authorised staff

A request routed into the supported assistant workflow.

SchogleSahayak
Responsibility · Authorised staff

Ask Sahayak

Staff request

Show the timetable for Class VI A.

Sahayak
Looking for a class timetable

Class VI A · Timetable read tool

School information stays within your permissions.
Timetable request identifiedConcept example · confirm availability
Sample records · Concept presentation, not a verified ERP screen.

School context before the next assisted action.

Keep authorised information and human confirmation in the described assistance workflow.

Authorised staff

Understand the request

Teachers

Check access and retrieve context

School administrators

Review and confirm

A clearer workflow.
A considered next step.

What does request classification cover?

Interpret the user’s request before choosing a supported school tool. Its documented capabilities include Request classification, Cloud assistant using Gemini and Groq.

Who benefits from this workflow?

Authorised staff, Teachers, School administrators. A request routed into the supported assistant workflow.

What should we confirm in a demo?

Review supported screens, configuration and current availability with your school’s responsible team.

See this workflow with your school in mind.

Review the relevant records, configuration and current scope with our team.

Book a Demo
PageSchogle
Chat online Request a quote