A governed AI layer for school operations—grounded in authorized context, designed for bilingual teams, and explicit about what is available today.
Availability depends on the school’s subscription, configuration, role permissions and approved provider setup.
Which campuses are configured, and is the Academic structure ready?
Two active campuses are configured. The current Academic structure is available for review, with one readiness item still pending.
Sources: school profile · campuses · Academic structureASK INTELLO
The implemented Assistant answers from a permission-scoped, read-only snapshot of school setup and Academic information. For authorized Super Admin use, it can also explain AI readiness, usage and credits.
Ask in natural language and receive a concise answer grounded in the sources available to your role.
Record, review and edit a transcript before it enters the question field. Voice is currently restricted to a controlled owner preview.
Return to your own recent conversations inside the same authorized school context.
Responses identify canonical sources and keep school-specific access within the active tenant and user permissions.
AI ACROSS WORKFLOWS
Each implemented workflow uses its existing permissions and canonical service. INTELLO AI does not create a parallel path around school controls.
Summarize an authorized Academic structure, find a grade, or prepare structure and annual-rollover plans for review.
Example request: “Prepare next year from the current structure and show conflicts.”
Authorized platform teams can resolve an existing CRM lead or supplied school details and prepare the canonical onboarding proposal.
Example request: “Prepare onboarding for the approved lead, without activating the school.”
Ask about school profile, campuses, setup readiness and Academic structure. Super Admin responses may also include AI provider readiness, usage and credits.
Example request: “Why is AI not ready for this school?”
FROM REQUEST TO REVIEWED ACTION
Supported write workflows use a governed action plan rather than an invisible automatic change.
The request is normalized into a registered action and bounded input.
A proposal explains what would happen, what would not happen, conflicts and affected counts.
Permissions, tenant scope, entitlements, prerequisites and the current state fingerprint are checked.
An authorized human reviews the exact proposal before a supported canonical change can run. Stale plans are rejected.
The public examples on this page are static. They never call a provider, consume credits or modify records.
ENGLISH + ARABIC
The interface and Assistant support English and Arabic content, including RTL layouts and mixed-direction values. Users can choose English, Arabic or automatic answer language where the implemented workflow allows it.
Voice language selection is implemented, but universal accent or dialect accuracy is not claimed.ما الفروع المهيأة، وما حالة جاهزية الهيكل الأكاديمي؟
Which campuses are configured, and what is the Academic readiness status?
PRIVACY + CONTROL
CAPABILITY OVERVIEW
Labels reflect the implemented contracts in INTELLO EDU today.
PRACTICAL QUESTIONS
No. Availability depends on the subscribed AI module, enabled school settings, approved provider and model, usage controls and the user’s permission. Some capabilities are restricted further.
The implemented Assistant uses an authorized read-only snapshot that may include school profile, campuses, Academic structure and setup readiness. Super Admin context may additionally include AI readiness, usage and credits.
No. Tenant, effective user, capability, entitlement and action-specific prerequisites are checked by the governed action layer.
No. Every request and response shown here is static presentation content. It reads no private school data, spends no credits and performs no action.
Voice recording, editable transcription and review are implemented, but production use is currently limited to a controlled owner preview with specific configuration.
The operational Assistant answers authorized school and AI-readiness questions. Academic summaries and reviewed planning actions are implemented. CRM-led school onboarding is available only to authorized platform teams. Other role assistants remain planned.
Supported write actions require an exact saved proposal, permission and prerequisite checks, explicit human confirmation and a fresh state fingerprint before execution.
The interface supports English and Arabic, RTL presentation and mixed-direction values. Answer language can be English, Arabic or automatic in the implemented Assistant; no universal dialect-accuracy claim is made.
SEE IT IN YOUR SCHOOL CONTEXT
Request a demo to review configuration, eligible workflows and the controls that apply to your school.
