The advising queue
answers itself.
Most of what students ask admissions and advising is already written down — in the catalog, the academic calendar, the handbook, the aid policy. AxiomAI answers from exactly those documents, cites the page it used, and replies in English, Spanish, or Arabic. What it cannot support, it hands to a person.
HECVAT on request · named sub-processors · zero-retention model terms · on-premise available
TWO JOBS, ONE DEPLOYMENT
Admissions and advising are different problems.
Admissions answers a stranger deciding whether to apply. Advising answers a student who is already enrolled and needs to not miss a deadline. Both run off published content — but the second one is where the volume is, and where the compliance questions start.
PROSPECTIVE STUDENTS
Admissions & enrollment
Application deadlines, program requirements, tuition and fee schedules, transfer credit policy, housing, orientation. Answered from your published catalog and PDFs, with the source cited, at the hour applicants actually browse.
- ● Answers cite the catalog page or PDF page they came from
- ● English, Spanish, and Arabic from the same source documents
- ● Captures the inquiry and routes it to the enrollment team
ENROLLED STUDENTS
Academic advising
Degree requirements, prerequisite chains, registration and add/drop dates, aid eligibility policy, petition and appeal processes, tutoring and support hours. The repetitive half of the advising queue, answered from the catalog — no student record required.
- ● Runs entirely on published catalog and handbook content
- ● No SIS connection and no student records in scope
- ● Record-specific advising is roadmap, not a claim — see the page
FERPA, HONESTLY
We will not tell you we are “FERPA compliant.”
FERPA governs education records. A blanket compliance badge from a vendor is close to meaningless, because whether a deployment complies depends on what you connect to it — which is your decision, not ours. So here is the actual position.
The default AxiomAI deployment touches no education records at all. It reads your published catalog, calendar, handbook and policy pages. There is no SIS connection, no transcript, no balance, no roster. A student asking “what are the prerequisites for BIOL 240” is asking about the catalog, not about themselves — and the assistant answers from the catalog.
Students will still paste things they should not. Student IDs, dates of birth, sometimes a full SSN, into a public chat box, unprompted. That is the real exposure, and it is what the governance layer is for: sensitive values are detected and replaced with typed tokens before the request leaves our server for a model provider, then rehydrated in the reply. The model never receives the raw value, and never-emit rules keep it out of the answer text. Every one of those decisions lands in a hash-chained audit trail stamped with the policy version that made it.
Record-specific advising is a different project. Answering “am I on track to graduate” means authenticated access to student records, and that needs an integration, an institutional review and your counsel — not a checkbox on a pricing page. We are happy to scope it. We will not pretend it ships on day one.
FOR IT, PROCUREMENT AND GENERAL COUNSEL
The questions your security review will ask.
Higher-ed procurement runs through more offices than any other buyer we sell to. Rather than make you extract this in a call, here it is up front — every answer links to the page that documents it.
HECVAT
We complete the HECVAT for institutions that require one as part of a security review. Ask for it early in the process — it is the fastest way to get your IT and procurement offices the answers they need.
Request a HECVAT →Where does the data go?
US data centers by default. EU or a custom region can be scoped, up to a fully on-premise deployment on your own hardware running open-source models when sovereignty rules require it. Every sub-processor is named publicly, with 30 days’ notice before any addition.
See sub-processors →Do the models train on our content?
No. Customer content goes to model providers under zero-retention API terms, and nothing you or your students type is used to train general-purpose models. Encryption is TLS 1.3 in transit and AES-256 at rest.
Data practices →What stops it inventing a policy?
An allowed-domain lock keeps replies inside your published material, every answer carries its source, and when the content does not support an answer the assistant says so and hands off rather than guessing at a deadline or a fee.
How governance works →Accessibility
We can prepare a VPAT / accessibility conformance report for enterprise procurement on request — the same commitment published on our accessibility statement.
Accessibility statement →Single sign-on
Google and Microsoft SSO on the Business plan; SAML on Enterprise, alongside custom retention windows and integration scoping.
Plans →WHAT WE DO NOT HAVE
We do not hold SOC 2, ISO 27001, or HIPAA attestation. If your institution requires a completed SOC 2 Type II before signature, we are not your vendor this cycle, and we would rather say so now than waste a procurement cycle finding out. Our SOC 2 roadmap sets out what is in place, in progress, and planned.
WHERE THIS FITS BEST
Community colleges, first.
The advising ratio is the worst in higher education, the student body is the most likely to be working a shift when the advising office is open, and a large share of families are more comfortable in Spanish. That combination is exactly what an assistant that answers the catalog at 11 PM in the student’s own language is for.
It is also the part of higher ed where a deployment can be live in weeks rather than after a year-long RFP — so it is where we would rather start.
HOW IT WORKS
From the course catalog to the first answered question.
01
Point us at the catalog
Course catalog, academic calendar, student handbook, aid policy pages and PDFs
02
Review before launch
Your team checks answers, citations, language behavior and handoff rules in a private workspace
03
Scope the security review
HECVAT, VPAT, sub-processor list and residency settled before anything is public
04
Embed per department
One snippet; admissions, advising, bursar and registrar can each run their own scope
05
Close the content gaps
The unanswered queue shows what students ask that the catalog never says
Departments can run separate scopes off one deployment — admissions answering applicants, advising answering the catalog, the bursar answering fee policy — each locked to its own approved content.
FOR THE WHOLE CAMPUS · SERVICEORBIT
Beyond advising: one front door for every campus request.
AxiomAI answers questions. ServiceOrbit takes the requests: a broken heater, a transcript, a lab induction, a laptop loan. Students and staff ask in plain words, and each request reaches the right office complete, with its own clock.
- No office to find and no form to fill
- Built from the procedures your departments already have
- Named approvers, and every AI step on the record
Pricing: ServiceOrbit is scoped and quoted for each organization, usually starting with a pilot. It is not on the AxiomAI plans.
The working product on invented organizations. Every person and record shown is invented.
SEE IT ON YOUR CATALOG
Send us the catalog. We will show you the answers.
We will build a private demo from your published catalog and advising pages so you can see the citations and the fallback behavior before a single meeting about procurement.