Trust
Before you hand us your bookings.
Your bookings sit between your business and its income. Here is how EnrolHub is built, run and looked after.
01The platform
One platform, built as a system.
- Your website, your bookings, your payments and your console run on one platform, not a chain of separate tools.
- EnrolHub's database is in Sydney. The console and the API work on one RTO's records at a time, the database's own rules stop anyone signed in from reaching another RTO's records, and an automated test checks those rules.
- Your team signs in with a link sent to their email. There are no passwords to share or lose.
- Every change made in the console is recorded: who made it and when, and who asked for it when it answered a request.
- Your website
- Bookings and payments
- Your console
- The EnrolHub platform, in Sydney
02Payments
Payments go straight to your business.
- Your customers pay on a secure checkout, into your business's own payment account, and the money is paid out to your bank account.
- Card details are handled by Stripe, the payment provider behind every checkout, and never touch EnrolHub or your website.
- A booking paid by card is confirmed only when the payment is; one paid by invoice, when the invoice is issued to a business you've approved for invoicing.
- Payments are refunded from your console, back to where they came from.
- Your customer
- Secure checkout
- Your business
03Your students
Your students' details, handled as they should be.
- Students read and accept the government's VET privacy notice, with your name in it, before they pay for an accredited course, or in their own account when someone else booked for them.
- Their enrolment details are asked for after payment, in their own EnrolHub account.
- A student's USI is never shared between RTOs.
- Their EnrolHub account holds their bookings with every RTO on EnrolHub, and it's where they ask you to change or cancel one they made themselves.
04What stays yours
What's yours stays yours.
- Every payment, made to your business and paid out to your bank account.
- Your domain.
- Your courses, your prices and your words.
- Your bookings, which export from the console to a spreadsheet whenever you like.
05Support and development
Looked after, every month.
- We run your platform with you: your Google Ads and Google Business Profile managed, and your brand kept consistent wherever it appears.
- Every improvement we make to EnrolHub reaches your console and everything behind your site.
- Support with your website, your bookings and the technology around your business.
06Built for training
Made for vocational training.
- The government's privacy notice before payment on every accredited enrolment.
- Course codes and titles from training.gov.au.
- The issuing RTO named on every accredited course, including when you deliver for a partner RTO.
- Business bookings, private groups and staff named after booking: the way training is bought.
- The console and client sites checked by automated accessibility scans whenever their code changes.
Who's responsible for what.
You're the RTO. Your obligations under the Standards, your scope, your assessments and your certificates stay yours. You decide what your site and courses say, and EnrolHub checks what it can, such as unit codes against training.gov.au.