From a request to the right form, in one step

“Create the August class for this course.”

That is a simple request. In most systems, it still starts a long trip through the menu.

Leave the course. Open Classes. Start a form. Find the same course again. Select it. Then enter the class details.

The RTObase Admin Agent removes that trip. It opens the real form and carries across the details it already knows.

Start from the work in front of you

If you are viewing a course, ask the agent to create a class for it. The New Class form opens with the course selected.

If you are viewing a student, ask to start an enrolment or booking. The correct form opens with the student already selected. Where supported, the class, date or other known details can come across too.

The same pattern works for common jobs:

• start a class from a course;
• enrol a student into a class;
• open a booking for a learner;
• start an employer invoice;
• open forms for students, trainers, locations and complaints.

Your team does not need to remember which menu holds each form. They can start with the job they want to do.

The real form still matters

The agent does not create the record in the background.

It opens the same form your team already uses. Staff complete any missing details, review the record and press Save.

That matters because many RTO records need a human choice.

An enrolment may need funding details or support requirements. A booking may need a suitable trainer, asset and time. An invoice needs the right line items and due date.

Those decisions should stay visible. The agent removes the searching, not the checks.

Carry the context forward

This becomes more useful after the agent has already found the work.

Suppose the morning admin list shows a booking request that needs action. Your team can open the booking workflow from that conversation. They do not need to copy the learner's name, close the chat and search again.

The agent also knows which page is open. Short requests such as “create a class for this course” or “book a session for this student” can use that page as context.

The result is simple: fewer menu steps and less repeated entry.

Your team still decides whether the record is correct. They still choose the trainer, confirm the funding and save the form.

Starting admin work should feel like stating the job, not remembering the route.

Next Friday: how the agent prepares a small update for review when an existing record needs to change.

If finding the right form slows your team down, see how RTObase keeps the work together.