The voice assistant that answers parents and prospective students and schedules school visits
For admissions and student services teams: admissions questions and visit requests go to the assistant, so your team can focus on meeting families.
Common problems on the phone line
Phone peaks during admissions
During admissions, the same program and enrollment questions arrive back to back; the line is often busy.
Visit requests get lost
Visit requests taken over the phone stay on sticky notes, and follow-up is slow.
Sensitive information, right person
Student-specific information must be shared only with authorized, verified people; that distinction needs care on every call.
How it works in this sector
Every call follows the same four steps; the assistant acts only with defined permissions.
- 01 / 04
Greets
Greets the parent and listens to the admissions or visit request.
- 02 / 04
Understands and verifies
Confirms the name and phone number by reading them back.
- 03 / 04
Takes action
Checks the admissions team's available times.
- 04 / 04
Confirms or hands off
Creates a meeting request with approval; routes student-specific matters to the authorized office.
What the assistant takes on
Handles parent and prospective student calls and routes admissions requests.
- Admissions and programme information
- School visit scheduling
- Routing parent requests
- Name and phone number read back for confirmation
- Request passed to the admissions team
Example call
A fictional scenario: what the caller says, what the assistant understands and how it replies.
- Caller
- “I would like to visit the school for my child. Is Friday available?”
- Detected request
- School visit · Parent request · Friday
- Assistant response
- I can check the admissions team's availability and submit a meeting request with your approval.
Student-specific information is shared only with authorised, verified people.
Illustrative example · Not live system data
Related integrations
The assistant connects to your systems only with defined permissions; your PBX setup is reviewed during discovery.
Netgsm 0850 / SIP Trunk
Carrier line (SIP Trunk)
Inbound and outbound calls
Answering, information and confirmation calls
Operator handoff
Calls that need a person, plus fallback routing
Call summary to the CRM
The call summary is written to the relevant record
Runs on your own server
- Your data stays in-house.
- A single GPU server is enough.
- Several calls at the same time, on the same system.
The architecture supports your compliance processes with restricted API access, configurable retention and operator fallback. Compliance depends on the deployment configuration, data processing practices and your organizational procedures.
The path of a call
- 01Phone lineNetgsm 0850 · SIP Trunk
- 02PBXAsterisk
- 03Your serverSTT → LLM → TTS
- 04Your systemsCRM
Frequently asked questions
- Who does it share student information with?
- Student-specific information is shared only with authorized, verified people. The verification steps are defined together with your school.
- Where do parents' meeting requests go?
- The request is created with the caller's approval and passed to the relevant team with a call summary; the summary can be written to the CRM.
- Does voice data leave the organization?
- No. Speech-to-text, response generation and speech synthesis run on your own server; your data stays in-house. Calls arrive through your telephone carrier and PBX.
- What if the agent can't resolve a request?
- Calls that need a person are transferred to an operator, with fallback routing in place.
Request a demo
Your sector is preselected in the form. Briefly describe your call scenario, and we will schedule an online meeting at a time that suits you.
Let's plan your phone line together
In a discovery call we go through your call flows and the systems to connect.
* Footnote: Latency values were measured on real call recordings (from the moment the caller stops speaking until the first sound arrives, server side). Internet latency adds 0.05–0.3 s. Word error rate was measured on the public FLEURS-tr dataset (200 sentences, 8 kHz telephone audio). Language support is at model level. Live validation was done in Turkish; in other languages, voice and recognition quality may vary by language.