Driving schools
Theory block, practical block, cohort seats and an exam date: an order of steps is imposed from outside, and a record has to follow it.
An enrolment gets finished instead of sitting half-done, and a student knows what remains ahead.
7 days, 20 answered calls, no card
At a driving school an instructor spends working hours sitting beside a novice driver: picking up a phone is worse than rude, it is a genuine road risk. At a studio a teacher stands in front of a group. Meanwhile a parent is trying to enrol a teenager ahead of a next cohort.
This add-on finishes an enrolment. It chases missing documents, links a participant to whoever pays, places a person into a session or cohort, and holds an administrative picture: steps cleared, hours or credits left, a next stage on a pathway.
It also acts as memory between sessions. When a lesson is skipped, when a session fills, when two practical lessons remain ahead of an exam, that state lives somewhere beyond an owner's head.
A guardian calling and a participant attending are distinct: age, decision authority and payer are captured separately, so nothing lands on a wrong record.
Signed form, proof of age, learner permit number, parental authorization, declared medical history: a checklist names what is missing and keeps asking while a file stays incomplete.
A participant lands in a real session, against seats left and stated availability. Steps depending on one another are ordered properly.
Hours or credits left, steps cleared, a next lesson: readable by a student, by a guardian and by you, without digging through a notebook.
A Services base identifies which service or class someone wants, books against availability and known entitlements, and explains approved rates plus enrolment steps. It informs; it does not carry a student record over time.
What it adds is a record: documents, administrative progress, and session coordination. Collecting a new payment is not granted here; it requires a payment module, and only within a scope that module covers.
Theory block, practical block, cohort seats and an exam date: an order of steps is imposed from outside, and a record has to follow it.
An autumn session, a teacher, an instrument, a child: enrolment happens over a few September days and evaporates if nobody calls back.
A parent enrols, a child attends, and levels carry from one session into a next. Moving up a level is an administrative step like any other.
You set prerequisites, levels and an order of steps. Zenvox does not assess a student, does not decide a level change, and certifies no hours to any authority: it administers what you decided.
An allowance here covers active students plus document pages.
Fees for an official exam, a certifying authority or an electronic signature provider belong to those bodies and are billed by them.
A status below comes from qualification research. With no qualified connection, a student record lives in Zenvox and this add-on runs.
No. The guardian calling and the participant attending are distinct: age, decision authority and payer are captured separately, so nothing lands on the wrong record.
Signed form, proof of age, learner permit number, parental authorization, declared medical history: a checklist names what is missing and keeps asking while a file stays incomplete.
No. Zenvox does not assess a student, does not decide a level change and certifies no hours to any authority: it administers what you decided, on the prerequisites and the order of steps you set.
No. Collecting a new payment is not granted here: it requires the payment module, and only within the scope that module covers. Checking an existing entitlement ahead of booking does stay included in the base.
Students active in administrative progress, counted while they are, and the document pages filed against their enrolment record. Inbound calls stay metered on the base, separately.
Go back to your business, or read a neighbouring add-on.
Courses and progression