Training providers face a recurring operational challenge: qualified course enquiries arrive through multiple channels, but many require office staff review before confirmation. A prospect may need prerequisite verification, an alternative session time, or clarification about group discount eligibility. Without a structured handoff from first contact to enrollment, enquiries stall, staff chase missing information, and bookings slip to competitors. This guide examines how Zanus AI's phone and booking modules can capture course enquiries, route those needing review to the right queue, and move confirmed attendees to your calendar—reducing manual follow-up and accelerating the path from inquiry to enrollment.

Why Course Enquiries Require a Different Workflow

A course enquiry differs from a simple appointment booking. A prospective student calls or submits a form asking whether they qualify for a Microsoft Excel course on Tuesday afternoons. Your enrollment team must verify they have completed the stated prerequisite, check whether the Tuesday cohort still has capacity, confirm whether they are paying their own tuition or whether an employer is, and confirm the group size if they mention bringing colleagues. Until those facts are resolved, a provisional place cannot move to a confirmed booking.

Manual workflows treat all inbound contacts as calendar slots. An automated phone system that immediately books every enquirer wastes the prospect's time and your staff's time, generating follow-up calls to cancel or modify. Instead, a training provider needs to distinguish between enquiries that can be confirmed in the call itself and those that require human review. Zanus AI's architecture supports this distinction through its department policies, queuing, and the handoff between AI and human staff.

Setting Up Course Catalogue Knowledge and Availability

Before any enquiry can be handled effectively, Zanus AI requires a knowledge source describing your course offerings. The system can draw from your website course pages, a structured catalog, or a knowledge document you prepare. This is not a student information system integration (which training providers should manage separately); instead, the AI is trained on the factual course information you publish: course title, duration, schedule, stated prerequisites, cost and any enrollment restrictions.

Begin by documenting your active courses in a format Zanus AI can index. The AI Phone product page confirms that the receptionist answers only from your knowledge pages and price list, saying so when nothing is known and offering a person instead of guessing. For a training provider, this means creating a course list with fields such as course name, next three scheduled dates, minimum prerequisites, maximum cohort size, and tuition. The AI will use this to answer factual questions like "When is the Excel course next running?" or "Is it a prerequisite to complete the Intro course first?"

Set your calendar availability per course session. AI Booking connects to Google or Microsoft calendar, accepts availability rules and buffers, and offers only the free slots of your live calendar. For a training provider, each course session is a slot with a capacity limit. If your Tuesday Excel cohort has 20 seats and 18 are taken, only 2 spots remain. The AI will offer the next available session once the current one fills, preventing overbooking and reducing the staff work of managing waitlists manually.

Distinguishing Enquiries from Confirmed Bookings

Propose separate office routes for course information and enrolment decisions. Ask the supplier to demonstrate how the selected configuration represents the routes and who receives each unresolved request.

Configure two departments within Zanus AI: one for "Course Enquiries" and one for "Booking Confirmation." The Course Enquiries department operates with an AI first policy: the AI answers basic questions about course dates, times, and content from your knowledge base, captures the caller's name, email, and course of interest, and determines the course code. At that point, the AI does not book a calendar slot; instead, it creates a ticket or message for your enrollment team.

The Booking Confirmation department handles callers who are ready to enroll: they have verified their prerequisite status offline, they know which session they want, and they are ready to provide payment details. This department can use the AI to book directly into your calendar and send a confirmation. Alternatively, if payment verification is needed, this department routes to a human staff member who processes the enroll request and calendar placement together.

A caller who says "I'd like to take the Excel course, but I'm not sure if I've completed the prerequisite" is routed to the Course Enquiries queue. One who says "I've taken Excel 101 and I want to enroll in Excel 102 on the 15th" can proceed to booking confirmation or direct enrollment, depending on your payment workflow.

Capturing Attendee vs. Payer Information

Group bookings introduce a common complexity: the person calling may not be the person attending. An employer's training coordinator calls to enroll five employees in a compliance course. Zanus AI must capture both the attendee roster and the billing contact. A single "name" field is insufficient.

During the call, the AI should collect: the name of the person making the enquiry (payer or authorizer), their email and phone; the names and email addresses of each attendee, their job titles or departments (if relevant for prerequisite determination), and confirmation that each attendee has completed stated prerequisites. If the payer is different from the attendees, the AI flags this in the message to your team, noting "Group of 5, payer is John Smith (ABC Corp), attendees are Jane, Mike, Sarah, Chris, David."

Zanus AI's call summary and transcript capture what the caller says. The AI can ask "Who will be attending?" and "Who is arranging payment?" and write both answers into the message. Your enrollment staff then has the full picture before they contact the caller to finalize the booking. This avoids the common error of confirming a seat for the coordinator rather than the actual student.

Routing Enquiries That Require Staff Review

Some enquiries cannot be resolved in the call. The caller asks about prerequisite requirements for which your knowledge base has no definitive answer, or mentions a circumstance (prior industry experience, auditor approval) that your staff should assess case-by-case. Zanus AI's transfer and queue mechanism handles this.

Configure the Course Enquiries department with a policy that allows the AI to answer basic factual questions, then offer a transfer to a staff member for complex cases. The AI can say: "I see you're interested in the Advanced SQL course. We do require completion of SQL Fundamentals. I can connect you with our enrollment advisor to discuss your background." The AI has already collected the caller's name, phone, and enquiry summary, which appears in your team's queue with context.

Zanus AI's call desk or ticket system (linked via /call-analysis for post-call analysis or /memory for call notes) can be configured with a queue for "Prerequisites to Review" or "Group Discount Enquiries." Each team member working those queues sees the caller's name, the course they asked about, and the AI's summary of their stated background. Your staff member then calls or emails the prospect to clarify eligibility. That exchange can happen offline, and only when staff confirms approval does the prospect move to the booking phase.

Handling Session Preferences and Waitlist Scenarios

A common enquiry is "I want the evening course, but only on Thursdays." Your calendar has Thursday evening slots available in three weeks, but the prospect wants the course to start sooner. Zanus AI can capture this preference and create a message, but moving the prospect onto a waitlist or into a "defer to future session" queue requires staff judgment.

During the call, the AI asks "Which session times work best for you?" and records the response. If no session matches that preference, the AI says "The next available Thursday evening session begins on [date]. Shall I put you on a waitlist for an earlier opening, or would you like to book the [date] start?" The caller's answer goes into the message. Your staff then follows up: if the prospect chose the waitlist, they enter the prospect into your tracking system and send a reminder when an earlier slot opens. If they chose the future date, the booking proceeds.

Waitlist management is manual in this scenario because the decision to defer or hold a spot involves business rules unique to your training model. Zanus AI captures the facts and routes them to your queue; your enrollment team executes the policy.

Recording the Provisional Place and Confirmation States

To avoid confusion, track each enquiry through distinct states. A useful workflow uses four states:

State Meaning Next Step
Enquiry Received AI captured the call; staff has not yet reviewed Staff reviews, checks prerequisites, estimates availability
Provisional Place Offered Staff confirmed the course and session; waiting for attendee decision or payment Attendee confirms enroll and payment, or declines
Booking Confirmed Calendar holds the spot; payment received or terms agreed; calendar invite sent Reminder sent; attendee arrives or no-shows
Declined or Expired Enquiry or provisional place did not convert Archive; re-engage if policy allows

Record the state in a field that Zanus AI can write to, either via the message to your team or through a note in your enrollment system. When staff reviews an enquiry message, they move it from "Enquiry Received" to "Provisional Place Offered" and send a follow-up email confirming the session details and a link to enroll. When the prospect completes enrollment and payment, your team moves it to "Booking Confirmed" and Zanus AI's booking module (if you route it back through the phone system) sends the calendar invite and reminders.

Sample Enquiry Workflow: A Training Provider Conversation

To illustrate how Zanus AI handles a typical course enquiry, consider this indicative exchange. The training provider offers Excel courses at beginner, intermediate, and advanced levels; intermediate requires completion of the beginner course or demonstrated prior experience.

Caller: "Hi, I'd like to take your Excel course."

Zanus AI (Front Desk): "Thank you for calling. I'm here to help you find the right Excel course. We offer Beginner Excel, Intermediate Excel, and Advanced Excel. Which sounds closest to your experience?"

Caller: "I've used Excel at work, but I'm not very confident. I think intermediate might be too hard."

Zanus AI (Front Desk): "Beginner Excel is a great choice if you want to build a strong foundation. Our next Beginner session starts Tuesday, the 18th, at 6 p.m., and runs for four weeks. We also have a Thursday morning session starting the following week. Which works better for you?"

Caller: "Tuesday evenings are perfect. Is there any chance of a weekend option?"

Zanus AI (Front Desk): "We don't currently offer weekend sessions for Beginner Excel. Our next available option after the Tuesday evening class is a Wednesday afternoon session starting in five weeks. I can book you for Tuesday evening, or I can connect you with our enrollment team to ask about waitlist options. Which would you prefer?"

Caller: "Book me for Tuesday."

Zanus AI (Booking): "Great. I'll book you for Beginner Excel on Tuesday, January 18th at 6 p.m. May I get your first and last name?"

Caller: "Sarah Chen."

Zanus AI (Booking): "Thank you, Sarah. And your email address?"

Caller: "It's sarah.chen@example.com."

Zanus AI (Booking): "Perfect. Sarah, I want to confirm: Beginner Excel starts Tuesday, January 18th at 6 p.m. and runs for four consecutive Tuesdays. Is that correct?"

Caller: "Yes, that works."

Zanus AI (Booking): "Excellent. I've provisionally placed you in the course. You'll receive a confirmation email at sarah.chen@example.com with details about payment and how to join the first class. Is there anything else I can help with?"

Caller: "No, that's great, thank you."

Zanus AI (Booking): "You're welcome, Sarah. We look forward to seeing you. Goodbye."

In this example, the AI moved the caller from interest to a provisional booking within one call. The caller's information (name, email, course code, session date) is captured and automatically sent to your enrollment team. A staff member reviews the booking, confirms payment terms or send a payment link, and updates the calendar. If the caller had requested a weekend option that required staff discussion, Zanus AI would have offered a transfer: "Let me connect you with an enrollment advisor who can discuss options for weekend training." The transfer would pull the advisor into the conversation with the caller's history already visible.

Integrating with Your Office Queues and Follow-Up

Zanus AI does not directly integrate with your student information system, but it can create messages and tickets that populate your team's workflow. Set up queues in your internal project management tool, email system, or Zanus AI's own call analysis and ticket features to organize enquiries by type and urgency.

Create distinct queues for your enrollment team:

  • New Enquiries (Prerequisites Unknown): Caller asked about a course but did not complete a prerequisite verification. Staff should call or email to discuss background.
  • New Enquiries (Group Booking): Multiple attendees, one payer. Staff should confirm the attendee names, send separate calendar invites, and coordinate billing.
  • Provisional Bookings Pending Payment: Caller booked a course; awaiting payment link completion or card confirmation. Staff should send or resend payment terms.
  • Session-Full Waitlist Adds: Caller preferred a time when no slots were available. Staff should confirm waitlist placement and trigger a reminder when space opens.

Each message from Zanus AI should land in one of these queues, tagged by the AI or by a keyword you agree on. For example, if the AI transcript includes "group of three," staff knows to check "New Enquiries (Group Booking)." If the AI successfully booked the caller, the message lands in "Provisional Bookings Pending Payment." This sorting saves staff time scanning every message to understand priority and next action.

Acceptance Criteria and Handoff Checkpoints

Before deploying this workflow, define what constitutes a successful handoff. An "Enquiry Received" message should include:

  • Caller's name and contact email (confirmed by read-back)
  • Course name and requested session(s)
  • Any stated prerequisite background
  • Group size and payer name (if applicable)
  • Special requests or time constraints
  • AI's assessment of whether prerequisites are likely met (based on your knowledge base) or require staff review

A "Provisional Booking" message should include all of the above, plus:

  • Course date and time the AI booked
  • Session code or ID for your internal system
  • Payment status (pending, link sent, awaiting confirmation)
  • Any notes about waitlist preference or other context

Before staff moves a provisional booking to "Confirmed," they must verify that the enrollment email was sent to the correct address and that the prospect understands the payment deadline. If the prospect received the booking but has not clicked the payment link within 24 hours, staff should send a courtesy reminder.

Failure Scenarios and Remedies

Test your workflow by simulating common failures. In one scenario, a prospect calls and says "I'd like the Tuesday course, but I haven't actually completed the prerequisite course." The AI should recognize this from the script and not immediately confirm the booking; instead, it should offer a transfer to staff or create an enquiry message flagged "Prerequisites Not Met." Your staff then calls the prospect to discuss whether they can complete the prerequisite before the course start date, whether the provider offers an accelerated path, or whether they should defer to a future session.

In another scenario, the caller provides an email address that the AI mishears. The booking confirmation email bounces or reaches the wrong person. Zanus AI's transcript should capture the spoken email; your staff should recognize the bounce and follow up by phone to correct the address. To minimize this, configure the AI to read back email addresses digit by digit. Zanus AI can confirm callback numbers by reading them back digit by digit, and the same capability applies to email addresses.

If a caller books but then never completes payment, and no payment reminder brings action, a staff member should follow up. Zanus AI can be configured to send a text reminder to the booking contact, but training providers should have a fallback manual call or email sequence. If a course is 10 days away and the prospect still has not paid, staff should either collect payment or release the spot to the waitlist.

Scaling to Multiple Courses and Instructors

As your training program grows, you may offer multiple courses simultaneously. Zanus AI's architecture supports this by creating a separate calendar and booking rules for each course or instructor. During the call, the AI asks the caller which course they are interested in, then offers dates from that specific course's calendar. If you have two instructors each teaching Intermediate Excel on different schedules, the AI can differentiate: "We have an evening session with Instructor Chen on Tuesdays and a morning session with Instructor Martinez on Wednesdays. Which works better for your schedule?"

Each course or instructor can have their own department policy. For example, if Intermediate Excel always requires a live prerequisite conversation, that course's policy is "operator first," and every prospect goes to a staff member. Beginner Excel, with no prerequisites, uses "AI first," and the AI books directly. This granularity helps you optimize for each course's enrollment rules without forcing a one-size-fits-all approach.

Key Metrics to Track

Once the workflow is live, measure its effectiveness:

  • Measure how many reviewed enquiries reach the next agreed state. Record the reasons for unresolved cases and use the provider’s own pilot evidence to choose appropriate acceptance criteria.
  • Track whether a provisional place becomes a confirmed arrangement under the provider’s actual process. Review the reasons for a delay instead of assuming a typical conversion percentage.
  • Time from Enquiry to Confirmation: Measure the median hours from first call to confirmed booking and calendar invite sent. (With AI handling basic steps, this should be under 24 hours for most bookings.)
  • Compare observed follow-up work with the baseline from the same office and request types. Do not assume a percentage reduction before the trial.
  • No-Show Rate: Once attendees are confirmed and reminders are sent, what percentage attend? (Reminders sent by Zanus AI should improve this.)

Frequently Asked Questions

Q: Can Zanus AI check whether a prospect completed our prerequisite course in our student information system?
A: No. Zanus AI answers from your published knowledge and approved documents, not from live queries to your student database. If you want the AI to verify prerequisite completion, you would need to export a list of completed students and include that in your knowledge base (with privacy consideration), or route those enquiries to staff. Most training providers route prerequisite verification to staff as a deliberate policy step.

Q: If a prospect books a course but then changes their mind, can they cancel through Zanus AI?
A: Yes, if you configure a "Cancellations" department with an AI or staff-first policy. A caller who says "I need to cancel my course" can be routed to that department. The AI can ask the course date, retrieve the booking, and process the cancellation if your policy allows. Alternatively, you can route all cancellations to staff to ensure you record the reason and offer alternatives.

Q: How do group bookings work if attendees are in different locations or time zones?
A: During the call, the AI collects all attendee names and emails. Your staff then sends individual calendar invites to each attendee in their own time zone (if the course is offered multiple times) or confirms a single time that works for the group. Zanus AI handles the call inquiry; your staff handles the logistical coordination offline.

Q: What if a prospect calls back after their provisional booking to change the date?
A: Zanus AI can recognize returning callers (if their phone number is in the system) and offer to reschedule. The AI can check the calendar for alternative dates and move the booking if a slot is available. If not, the AI offers a transfer to staff. This feature reduces the friction of rescheduling and improves the prospect's experience.

Q: Can Zanus AI send course materials or syllabus documents after booking?
A: Yes, via email. After a booking is confirmed, you can configure Zanus AI (or your team manually) to send an email with attached documents. The email can include your course syllabus, joining instructions, required materials, and any housekeeping details. This reduces inquiry overhead by answering common questions proactively.

Next Steps: Pilot and Refinement

Start with one course or one department. Have Zanus AI answer enquiries for your most straightforward offering—a course with clear prerequisites and regular sessions. Run a one-week pilot, capturing every enquiry and monitoring the messages your staff receives. Review the AI's handling against your acceptance criteria: did it capture the correct information, ask clarifying questions appropriately, and route complex cases to staff?

After the pilot, refine your knowledge base, adjust your routing policies, and train staff on the new queue discipline. Then expand to additional courses. This staged approach lets you optimize the workflow without overwhelming your team and ensures the handoff between AI and staff is smooth before scaling.

A well-configured Zanus AI phone and booking system transforms course enquiries from a manual, interrupt-driven process into a structured pipeline. Prospects get immediate answers about course availability and move smoothly from interest to booking. Your staff spend time on genuine decisions—prerequisite assessment, group logistics, payment collection—rather than repeating information or chasing missing details. The result is faster enrollment, fewer dropped enquiries, and a more professional experience for every prospect.

Official sources and related guides

This independent Sysevo guide uses the following official documentation. The workflow and trial scenarios are evaluation proposals, not reported customer results or a hands-on benchmark.

Compare the same requirements with the relevant Sysevo product, Voice Agents and CRM. Review Sysevo plans and pricing or book a demo to discuss the proposed setup. Sysevo sells its own business software and is not affiliated with the competitors discussed here.