Course Enrollment Funnel

Course inquiries are a trickle of high-intent people who then go quiet. Somebody downloads the syllabus, replies to an ad, or asks a question on the phone, and the training provider answers it well. Then nothing happens. The inquirer was interested but not ready, the next intake was eleven weeks away, and there was no reason to decide today. By the time the cohort fills, half the people who asked about it have forgotten the organization exists.

The leak has a specific shape in education. Inquiries arrive on a continuous drip, but enrollment is discrete - it happens against a start date, an application deadline and a payment deadline. A provider with no cohort structure in its follow-up has no reason to ever push. A provider with cohort structure but manual follow-up loses people in the gaps: nobody notices that an applicant started the form and stopped at the funding question, or that a deposit was paid but the balance never was, or that four accepted students have not returned their paperwork and the course starts on Monday. Each of those is a paid seat sitting empty with a human who wanted it.

The second leak is qualification. Training has prerequisites: prior qualifications, English level, employer sponsorship, funding eligibility, visa status for in-person study. When those are checked in a phone call rather than on a form, the admissions team spends its best hours on people who were never eligible, and genuinely eligible applicants wait days for a reply. The build fixes both: a funnel that qualifies on intake, a pipeline that makes every stalled application visible, and a deadline-driven sequence that gives the inquirer a reason to act this week rather than next term.

Pipeline and stages

One pipeline, Course Enrollment, with one card per applicant per cohort. An applicant who defers to a later intake gets a new card rather than a reused one, so cohort conversion stays honest.

• Inquiry - contact details captured, nothing qualified.
• Qualified - eligibility answers in, prerequisites met, course and intake identified.
• Info Session Booked - on a webinar, a campus visit or a one-to-one advisory call.
• Application Started - the long application form opened but not submitted.
• Application Submitted - complete, awaiting an admissions decision.
• Offer Made - conditional or unconditional place offered, clock running.
• Deposit Paid - seat held, balance outstanding.
• Enrolled - Paid in Full and Enrolled - Payment Plan - two closed-won stages so finance can see the mix.
• Deferred to Next Intake - a holding stage with the target intake written to the record.
• Not Eligible and Lost - closed-lost variants, kept apart because they need completely different nurture.

Calendars

• Course Advisory Call - 20-minute slots with the admissions team, round-robin across advisers, with the course and intake passed in from the inquiry so the adviser opens the call informed.
• Information Webinar - a recurring group session per cohort, typically weekly in the eight weeks before a start date, with automatic reminders and a replay link for no-shows.
• Campus Tour or Facility Visit - fixed weekly slots with a capacity limit per slot.
• Interview or Assessment - longer slots used only where the course requires a portfolio review, an entry test or a competency interview, released only to applicants at Application Submitted.

Custom fields

• Course Interest, Delivery Mode (in person, online live, self-paced, blended), Study Load (full time, part time, evening, weekend)
• Target Intake and Intake Start Date - the two fields every deadline calculation reads
• Application Deadline, Deposit Deadline, Balance Deadline, Days To Deadline
• Prior Qualification, Prerequisites Met, English Level, Prior Experience Years
• Funding Route - self funded, employer sponsored, government funded, loan, scholarship applied, undecided
• Employer Name, Employer Approval Status, Purchase Order Number
• Application Status, Documents Outstanding (a list: ID, qualification certificate, reference, employer letter)
• Offer Type (conditional, unconditional), Offer Expiry Date, Conditions Outstanding
• Payment Option Chosen, Deposit Received, Balance Received, Payment Plan Installments
• Seats Remaining In Intake - synced from the cohort record and used for scarcity messaging that is true
• Source Campaign and First Touch Channel - so cost per enrollment can be attributed, not guessed

Tags

• inquiry-new, qualified, not-eligible, needs-adviser
• course-{{slug}} one per course, and intake-{{yyyy-mm}} one per intake - the two tags that make every cohort campaign a one-click segment
• webinar-registered, webinar-attended, webinar-noshow
• application-started, application-abandoned, application-submitted
• offer-made, offer-accepted, offer-expired
• deposit-paid, balance-outstanding, payment-plan-active, payment-failed
• employer-sponsored, funding-pending, scholarship-applicant
• deferred, waitlist, enrolled

Forms and surveys

• Course Inquiry - the short public form: name, email, mobile, course interest, delivery mode, target intake, and one qualifying question about current experience. Five fields, no more. Everything else is asked later.
• Eligibility Check - a short conditional form that asks only what the chosen course requires: prior qualification, English level, years of experience, funding route. Branches so a self-funded applicant never sees the employer questions.
• Full Application - the long form, saved in sections with resume-later enabled so partial completion is captured rather than lost. Sections: personal details, qualifications, experience, funding and employer, document upload, declarations.
• Employer Sponsorship Request - a separate form the applicant forwards to their manager, capturing the approver name, the purchase order reference and the billing contact.
• Enrollment Confirmation - signed terms, accessibility and support needs, emergency contact, and consent to the handbook.
• Why Not Now - a one-question survey sent to anyone moving to Lost or Deferred: timing, cost, course fit, chose another provider, or no longer needed.

Funnels and landing pages

• A course page per course with the inquiry form above the fold, the syllabus as a gated download, and the next three intake dates pulled live.
• A webinar registration page per intake, with a thank-you page that offers the advisory call booking immediately.
• An application portal page the applicant can return to, showing their stage, their outstanding documents and their next deadline.
• A payment page per course with the deposit, pay-in-full and installment options as distinct products.

BO's role and guardrails

• BO handles the course chat and the admissions inbox out of hours: answers syllabus, duration, delivery mode and start date questions from the course record, runs the eligibility questions conversationally, and books advisory calls and webinar places.
• BO chases documents, confirms deadlines, and sends the payment link for the option the applicant already chose.
• BO may not quote fees or discounts, confirm funding or scholarship eligibility, make or vary an offer, waive a prerequisite, extend a deadline, or give advice on visas, immigration or government funding schemes. Each routes to a named human.
• BO never predicts an admissions outcome. On any question about whether the applicant will get in, BO books the advisory call.
• Any mention of a disability, a learning difference or a support need is acknowledged briefly and handed straight to the student support contact; BO does not record clinical detail in chat.

Numbers and channels

• One admissions sending number per region, used for both transactional deadline reminders and consented marketing, with separate consent flags on the contact.
• The admissions email address routed into the platform inbox so the whole application thread sits on one timeline.
• Web chat on every course page, the fees page and the application portal.
• Payments via Stripe or the provider's gateway for deposits, full fees and installment plans, with the webhook writing Deposit Received and Balance Received back automatically.
• Calendar sync (Google Calendar or Outlook) for advisers, and the webinar platform connection for registration and attendance data.

1. A prospective student searching for a part-time qualification lands on the course page and downloads the syllabus. The Course Inquiry form captures five fields: name, email, mobile, course, and the next intake they are considering.
2. The contact is created, tagged inquiry-new, course-data-analytics and intake-2027-02, and a card appears at Inquiry. Intake Start Date, Application Deadline and Deposit Deadline are stamped from the cohort record.
3. The syllabus arrives by email within one minute, with the Eligibility Check link and the next webinar date in the same message. An SMS follows five minutes later with the webinar link only.
4. She completes Eligibility Check: a relevant degree, four years of experience, self funded. Prerequisites Met is set to yes, the card moves to Qualified, and the tag qualified is applied. An ineligible answer would have routed to Not Eligible with a genuine alternative suggested rather than a dead end.
5. She registers for the Information Webinar. The card moves to Info Session Booked, tagged webinar-registered, with reminders at 24 hours, 1 hour and 10 minutes before.
6. She attends. Attendance syncs back, the tag flips to webinar-attended, and within two hours she receives the application link, the fees page and an advisory call booking option.
7. She opens Full Application that evening, completes the first two sections, and stops at the funding section. The partial submission tags her application-started and moves the card to Application Started.
8. The abandonment sequence picks her up the next day with a resume link straight back to the section she left, and the application deadline stated as a date and a countdown.
9. She finishes and submits. Card moves to Application Submitted, tagged application-submitted, and admissions is notified with a task due in one working day. Two documents are missing, so Documents Outstanding lists them and a chase sequence starts.
10. Admissions reviews and makes a conditional offer subject to the certificate upload. The card moves to Offer Made, Offer Expiry Date is set 14 days out, and the offer pack goes out with the deposit payment link.
11. She uploads the certificate, clearing Conditions Outstanding, and pays the deposit. The gateway webhook writes Deposit Received, tags deposit-paid and balance-outstanding, and the card moves to Deposit Paid.
12. She chooses the installment plan on the payment page. The plan is created in the gateway, the card moves to Enrolled - Payment Plan, tags enrolled and payment-plan-active, and the balance chase sequence exits.
13. Enrollment Confirmation goes out for the terms, support needs and emergency contact. On submission the record is complete and the contact is handed to the student onboarding build.
14. Had she gone quiet after the offer, the expiry sequence would have run at 7, 3 and 1 days out, then released the seat to the waitlist and moved her to Deferred to Next Intake with the Why Not Now survey attached.

1. Inquiry Capture and Instant Qualification

Trigger: Course Inquiry form submitted, or a chat conversation in which BO collects the same five answers.

• Create or update the contact. Write Course Interest, Delivery Mode, Target Intake, Source Campaign, First Touch Channel. Apply inquiry-new, course-{{slug}}, intake-{{yyyy-mm}}.
• Look up the cohort record and stamp Intake Start Date, Application Deadline, Deposit Deadline, Balance Deadline, Seats Remaining In Intake.
• Create the card at Inquiry, named with the applicant's name, the course and the intake.
• Wait 1 minute. Email the syllabus: "Here is the full {{course}} syllabus. Two things worth doing next: a two-minute eligibility check so we can confirm you meet the entry requirements, and the next information session on {{webinar date}}. Eligibility check: {{link}} Session: {{link}}"
• Wait 5 minutes. SMS: "{{First name}}, syllabus for {{course}} is in your inbox. Next info session is {{webinar date}} - save your place here: {{link}}"
• Branch - eligibility not completed after 24 hours: one reminder, then after a further 48 hours route to workflow 7.
• Exit: Eligibility Check submitted, or the card leaves Inquiry.

2. Eligibility Routing

Trigger: Eligibility Check submitted.

• Write Prior Qualification, English Level, Prior Experience Years, Funding Route.
• Branch A - all prerequisites met. Set Prerequisites Met to yes, tag qualified, move to Qualified. Send: "Good news - you meet the entry requirements for {{course}}, {{intake}}. Two routes from here: join the information session on {{webinar date}}, or book a 20-minute call with an adviser. Session: {{link}} Call: {{link}}"
• Branch B - prerequisites not met but a bridging or lower-level course exists. Tag not-eligible, move to Not Eligible, and send one honest message naming the specific gap and the course that closes it: "{{Course}} needs {{requirement}}, which is not quite in place yet. {{Bridging course}} is the usual route in, and it feeds straight onto this one. Details: {{link}}" Add to the long-cycle nurture, not the cohort campaign.
• Branch C - funding route is employer sponsored. Tag employer-sponsored, send the Employer Sponsorship Request form for the applicant to forward, and start a separate chase on Employer Approval Status at 3, 7 and 14 days.
• Branch D - funding route is undecided, government funded or scholarship applied. Tag funding-pending and needs-adviser, assign a task due in 1 working day. BO never answers funding eligibility.
• Exit: card reaches Info Session Booked or beyond, or Not Eligible.

3. Information Session Attendance Drive

Trigger: webinar registration recorded, tag webinar-registered applied.

• Move to Info Session Booked. Confirm immediately by email with the calendar file and the joining link.
• Wait until 24 hours before. SMS: "Tomorrow at {{time}} - the {{course}} information session. We cover the syllabus, the schedule and the fee options, and you can ask anything. Link: {{link}}"
• Wait until 1 hour before. SMS: "Starting in an hour. Join here: {{link}}"
• Wait until 10 minutes before. SMS: "We are opening the room now - see you in there. {{link}}"
• Branch A - attended. Tag webinar-attended. Wait 2 hours. Email: "Thanks for joining. You asked good questions. Here is the application form, the fee options, and a link to book a one-to-one if you would rather talk it through first. Applications for {{intake}} close {{application deadline}}. Apply: {{link}}" Wait 48 hours, and if no application has been started, one SMS nudge.
• Branch B - no-show. Tag webinar-noshow. Wait 1 hour. Email the replay with a timestamp index, plus the next session date and the advisory call link: "Sorry we missed you. The recording is here, and the next live session is {{date}} if you would rather ask questions in person." Wait 72 hours, and if nothing, re-register them for the next session automatically and tell them.
• Exit: card reaches Application Started, or three consecutive sessions missed, at which point route to workflow 7.

4. Application Abandonment Recovery

Trigger: Full Application partial save recorded, tag application-started applied.

• Move to Application Started. Write the last completed section to Application Status.
• Wait 4 hours. Email with a resume link that returns to the exact section: "Your {{course}} application is saved and waiting - you got as far as {{section}}. Pick it up here, nothing is lost: {{resume link}}"
• Wait 24 hours. SMS: "{{First name}}, your application for {{intake}} is still open. About six minutes left to finish. {{resume link}}"
• Wait 48 hours. Branch on the stalling section. If it was funding or employer, send the funding-options email and an adviser booking link. If it was documents, send the list of what is needed and accepted formats. If it was qualifications, offer the advisory call. The generic nudge converts far worse than the specific one.
• Wait 72 hours. Email with the real deadline: "Applications for {{intake}} close on {{application deadline}} - {{days to deadline}} days. After that the next start is {{next intake date}}. {{resume link}}"
• Wait 5 days. Tag application-abandoned, assign a call task to the admissions owner, and stop automated messaging on this thread.
• Exit immediately on submission, on an adviser call being booked, or on tag not-eligible.

5. Submission, Document Chase and Decision

Trigger: Full Application submitted.

• Move to Application Submitted, tag application-submitted, notify the admissions channel, and assign the review task due in 1 working day.
• Confirm to the applicant within 2 minutes: "Application received for {{course}}, {{intake}}. Reference {{application id}}. We review applications within one working day and will be in touch with the outcome or any questions."
• Branch - Documents Outstanding is not empty. Send the list with accepted formats and an upload link. Chase at 2 days, 5 days and 8 days, then assign a call task. Each chase names only the documents still missing, never the full list again.
• Branch - course requires an interview or assessment. Release the Interview or Assessment booking link and run the same reminder cadence as workflow 3.
• If the review task is not completed within 2 working days, escalate to the admissions manager. An application sitting unreviewed is the most expensive stall in the funnel.
• Exit: an admissions decision is recorded.

6. Offer, Expiry and Seat Release

Trigger: card moved to Offer Made by a human.

• Set Offer Expiry Date to the agreed window from today, write Offer Type and any Conditions Outstanding, tag offer-made.
• Send the offer pack immediately: the offer letter, the conditions if any, the payment page link, and the start date. "Congratulations - you have a place on {{course}}, {{intake}}, starting {{start date}}. To hold it, pay the deposit by {{deposit deadline}} using the link below. Your offer stands until {{offer expiry}}."
• Wait 48 hours. SMS if no deposit: "Your place on {{course}} is held until {{offer expiry}}. Secure it here: {{link}}"
• At 7 days before expiry, email with the practical detail that actually unblocks people: the installment option, the employer invoicing route, and the adviser booking link.
• At 3 days before expiry, SMS: "{{First name}}, your offer for {{intake}} expires {{offer expiry}}. {{Seats remaining}} places left on this cohort. {{link}}" Include the seats figure only when the synced value is accurate.
• At 1 day before expiry, assign a call task to the admissions owner. A human call beats a fifth automated message.
• On expiry with no deposit: tag offer-expired, release the seat to the waitlist, move to Deferred to Next Intake with Target Intake rewritten to the following cohort, and send the Why Not Now survey.
• Branch - conditional offer, conditions still outstanding at 7 days from the start date. Tag needs-adviser and escalate; conditions are never auto-waived.
• Exit: deposit received, or the card reaches Deferred or Lost.

7. Payment Completion and Failed Payment Recovery

Trigger: gateway webhook for deposit received, balance received, or payment failed.

• On deposit received: write Deposit Received, tag deposit-paid and balance-outstanding, move to Deposit Paid, decrement Seats Remaining In Intake, and confirm: "Your place on {{course}}, {{intake}} is confirmed. The balance is due by {{balance deadline}} - you can pay in full or set up installments here: {{link}} Next step is the short enrollment form: {{link}}"
• Balance chase at 21, 14, 7 and 2 days before Balance Deadline, escalating from email to SMS, each naming the deadline date and the installment alternative. At 1 day, assign a call task to finance.
• On balance received or installment plan created: move to Enrolled - Paid in Full or Enrolled - Payment Plan, tag enrolled, exit every chase sequence, and hand the contact to the student onboarding build.
• On payment failed: tag payment-failed, notify finance, and send a neutral message with no implication of fault: "The payment for {{course}} did not go through - usually a bank check rather than anything wrong. You can retry here: {{link}} or reply and we will help." Retry prompts at 24 hours and 72 hours, then a finance call task. Never suspend a place automatically on a failed payment.
• Exit: card reaches an Enrolled stage, or finance records a withdrawal.

8. Long-Cycle Nurture and Next-Intake Re-engagement

Trigger: card moved to Deferred to Next Intake, Lost, or application-abandoned with no reply.

• Send Why Not Now once: "One question, one tap - what stopped you joining {{intake}}? Timing, cost, course fit, you chose another provider, or no longer needed." Write the answer to the record.
• Branch - timing. Enroll in a light monthly value sequence: one useful piece of content per month, no selling, with the next intake date in the footer. Re-engage properly at 8 weeks before the next start date.
• Branch - cost. One email on funding routes, employer sponsorship and installments, then the monthly sequence. Never a discount offer in an automation.
• Branch - course fit. Route to the adjacent course nurture, tagged for that course instead.
• Branch - chose another provider. Suppress from active nurture for 6 months, then one re-permission email. Notify the marketing owner, because repeated answers here are competitive intelligence.
• At 8 weeks before the next intake start date, everyone tagged deferred for that cohort gets a personal-sounding re-open message: "{{First name}}, {{course}} runs again from {{start date}} and applications are open until {{application deadline}}. Your earlier answers are still on file, so your application will be short. {{link}}" Then they re-enter workflow 4.
• Exit: the contact re-enters the funnel at Inquiry or beyond, or unsubscribes - which stops the nurture entirely and is never overridden.

Every inquiry has a next step with a date on it. No applicant sits in an inbox waiting for somebody to remember them. The cohort start date generates the application, deposit and balance deadlines, and the deadlines generate the follow-up, so the urgency in the messaging is real rather than manufactured.

Admissions time goes to eligible people. The eligibility form filters before a human is involved, and the advisory call calendar fills with qualified applicants who already know the fee structure and the start date. Ineligible inquirers get a straight answer within minutes instead of a week of hope.

Partial applications are recoverable. The single largest silent loss in course sales is the half-finished form. Capturing it as a stage, with a resume link to the exact section, turns a dead record into a recoverable one.

Finance sees the cohort before it starts. Deposits, balances and installment plans are visible per intake, so the provider knows in week six whether a cohort will run rather than finding out in week one.

Metrics to watch

• Inquiry to qualified rate, and the share rejected at eligibility - if that second number is high, the advertising is targeting the wrong people.
• Webinar registration, attendance and attend-to-apply rate. Attendance is the single strongest predictor to track in most course funnels; measure it rather than assuming it.
• Application start to submit rate and the section at which applications are abandoned - the form itself is usually the problem.
• Offer to deposit rate and median days from offer to deposit.
• Deposit to full enrollment rate, and the paid-in-full against payment-plan mix.
• Seats filled per intake against capacity, tracked weekly from eight weeks out, so a soft cohort can be rescued with time left.
• Cost per enrollment by source campaign, using Source Campaign and First Touch Channel.
• Deferral rate and deferral conversion - how many deferred applicants actually enroll in the next intake, which tells you whether deferral is a save or a polite loss.
• Reason mix from Why Not Now, reviewed each intake. Timing and cost need different answers.

Course and cohort data

• A cohort record per intake holding the start date, the application deadline, the deposit deadline, the balance deadline, the capacity and the seats remaining. Every automation in this build reads those fields; if they live in a spreadsheet nobody updates, the deadline messaging goes wrong in public.
• Written entry requirements per course, expressed as answerable questions. "Suitable for motivated learners" cannot be automated; "a level 4 qualification or three years in a relevant role" can.
• A fee schedule with the deposit, the full fee and the installment structure defined as distinct products in the payment gateway. The build never states amounts in message copy; it links to the payment page.
• Decided policy on deferrals, refunds, cooling-off and seat release. The offer-expiry workflow releases a seat, so somebody must own that rule before it runs.

Integrations

• Payment gateway (for example Stripe) with webhooks for successful payment, failed payment and subscription or installment events, writing back to Deposit Received, Balance Received and payment-failed.
• Webinar platform connection for registration and attendance sync, or run sessions on the platform's own scheduling if attendance tracking is adequate.
• Calendar sync for every adviser (Google Calendar or Outlook) with real working hours and buffers, so the advisory calendar does not double-book.
• Student information system or LMS connection for the handoff at enrollment. If there is no API, agree the export format and the frequency before launch rather than after.
• Document storage for uploaded certificates and ID, with access limited to admissions staff.

Numbers, messaging and compliance

• Provision the admissions number and complete A2P 10DLC registration in the United States before launch. Register the brand and a campaign that covers both the transactional deadline reminders and the consented marketing nurture; the sample copy you submit should match what the build actually sends.
• Capture SMS consent explicitly on the inquiry form with clear wording, and store marketing consent separately from the applicant's agreement to receive transactional admissions messages.
• Honor STOP, UNSUBSCRIBE and HELP on every number. An opt-out must stop nurture without stopping the deadline and payment notices an active applicant needs, and the fallback to email must be explicit in the build.
• Set quiet hours so no automated SMS sends outside roughly 08:00 to 20:00 local time, and respect the applicant's timezone - online cohorts routinely span several.
• Applications collect sensitive data: identity documents, qualifications, declared support needs and sometimes financial circumstances. Define who can see each field, how long documents are retained, and how an unsuccessful applicant's data is disposed of.
• Where the provider operates under GDPR, UK GDPR, FERPA or similar regimes, confirm the lawful basis for the nurture sequences, the privacy notice, the retention schedule, and the rules on marketing to applicants who did not enroll. Accessibility and support-need information needs tighter handling than the rest of the application.
• None of this is legal advice. Have the client's own counsel and data-protection adviser confirm the consent wording, the retention policy and any sector-specific regulatory requirements before launch.

People and process

• A named admissions owner per course with a stated response standard for new applications, and a decision-maker for offers, prerequisite waivers and deadline extensions.
• A weekly cohort review from eight weeks out, reading seats filled against capacity and the stage mix, with agreed actions when a cohort is behind.
• Scoping and pricing are per build. Book a call at bookings.appbo.io to work through the cohort data model, the payment structure and the system handoff.