Students answer a few questions about where they are right now. Soria turns that into a clear self-portrait, points to the resources their own institution already offers, and shows the next concrete step — not a static directory.
Most institutions already have the services students need. What students don't have is a way in. They don't know which office handles what, so they start from "I need…" and end up at a list of department names.
Soria inverts that. The entry point is the student's own situation, expressed in their words. Behind it, a scenario engine maps that situation to the teams, programs and documents your institution already maintains — and links out to those sources rather than replacing them.
How it works
A student can go from landing page to a booked appointment without ever creating an account or completing a questionnaire they didn't want to start.
The student picks a situation, answers a short questionnaire, or just types a question. Any of the three is a valid entry point — and direct access to the resource catalogue stays open for students who already know what they need.
Results come back short, visual and readable — simple indicators across the dimensions of student life. The language is descriptive, never a score, a label, or a prediction.
Each indicator is dynamically associated with resources your institution actually offers, with the office, the delay and the link to the official source. Options, not verdicts.
Every result ends with clearly displayed next actions — book, apply, read the rule in plain language, or talk to a person. Students can bookmark a resource and ask to be reminded in a few days.
Coverage
Each institution chooses which dimensions to activate and how to word them. These are the ones most often configured.
Workload, study strategies, course load, program progression and the supports attached to each.
Stress, sleep, mental health and the campus and community services that respond to them.
Bursaries, financial aid, budgeting support, and the deadlines that govern each of them.
Student life, mentorship, peer groups — and targeted paths for first-generation and international students.
Employment during studies, dependants, part-time enrolment and returning to school later in life.
Grade appeals, absences, extensions, accommodation requests — each with its steps and its official reference.
Results & routing
A self-positioning tool earns trust by refusing to judge. Soria's result view is designed so no student reads it as an evaluation, a prediction, or surveillance.
Guided paths
Frequent cases ship as guided paths: a decision tree that leads to the right resource, the steps involved, the delays to expect, and a plain-language summary of the rule with a link to the official text.
Who to talk to first, what the deadline is, what evidence helps — and where the regulation actually says so.
Which absences are covered, what documentation is required, and which office receives the request.
Eligibility questions up front, the application window, and the supporting documents needed.
The decision tree between an extension, an incomplete and a withdrawal, with the consequences of each.
How to open a file with the accessibility office, what the process looks like, and how long it typically takes.
Refund dates, academic record impact, and the advising conversation that should happen first.
Soria can summarise a regulation in everyday French or English so a student understands it, and every summary displays a link to the official institutional text. Where the answer is ambiguous or the stakes are high, the agent does not improvise: it routes the student to the human who owns that decision.
Contextualisation
A bursary deadline matters in September and is noise in February. Soria places every resource on a timeline of critical milestones and surfaces it when it's relevant.
Per-institution setup
Networks need both: shared foundations so no one starts from zero, and real autonomy so each institution reflects its own services, rules and voice.
| Layer | Shared common base | Configured per institution |
|---|---|---|
| Questionnaires | Generic templates and validated question banks. | Wording, dimensions activated, branching, and per-cycle or per-program variants. |
| Resources | A common taxonomy so content can be exchanged. | The institution's own services, owners, links, delays and eligibility rules. |
| Guided paths | Starter paths for frequent procedures. | Local steps, local deadlines, local regulation references. |
| AI | Common guardrails and escalation logic. | Enabled, limited or disabled — per module and per content area. |
| Branding & access | One accessible design system. | Institutional identity, SSO, roles, permissions and observer access. |
| Hosting | One maintained, evolving codebase. | Hosted by the institution or in Canadian cloud infrastructure. |
Built on the platform
Nothing here is bespoke. This is the Soria platform configured for one need — which is why a second use case costs configuration, not a project.
| Platform capability | In this use case |
|---|---|
| Conversational agent | The chat entry point, on the web and inside Moodle, in French and English from one agent. |
| Vector stores & SharePoint indexing | Regulations, service pages and procedures your teams already maintain become the agent's only source of truth. |
| Tool definitions & MCP | Booking an appointment, opening a ticket, checking a deadline — the agent calls your systems instead of describing them. |
| Scheduled agents | "Remind me in five days", milestone reminders, and campaigns timed to the academic calendar. |
| Webhook agents | Events from the SIS or the LMS update what a student sees without anyone refreshing a page. |
| Roles & delegated content | Observer access for support teams; each service maintains its own resources under draft-review-publish. |
| Multi-tenancy | A shared base across the network, configured per establishment, per cycle, per program and per department. |
| Audit & run logs | Every agent action on the record, plus the unanswered questions that become your content backlog. |
Bring one procedure your students get stuck on. We'll walk through what the path, the result view and the escalation to your team would look like.
Book a Demo
