TRAINING COURSE-ENQUIRY STARTER KIT
Free resource | prepared October 23, 2026
Original guide: https://burki.dev/blog/training-course-cohort-voice-agent

Fictional planning material, not current course offers or learner records. No application, enrollment, booking, payment, sent message or paid voice test was created. Free reading/download is separate from production usage costs.

1. APPROVED COURSE-AND-COHORT MATRIX
Give each course/cohort an exact record ID. Keep every dependent fact with that record.
Record ID: __________________________________________________
Course title and cohort: _____________________________________
Application closing date: ____________________________________
Teaching start date: _________________________________________
Delivery format / location: __________________________________
Teaching time and explicit timezone: _________________________
Stated prerequisites, exact approved meaning: ________________
Fees, seats or next cohort if actually approved: _____________
Advisor contact / approved next step: _________________________
Source/version, owner, approval date: _________________________
Review/expiry trigger for that record: _______________________

Fictional records, replace before use:
PY-W26 | Python Foundations, weekend cohort
Applications close: 14 November 2026
Teaching starts: 21 November 2026
Delivery: on site
Published teaching time: 10:00, Europe/London
Stated preparation: basic computer use
Admission/assessment owner: advisor

DATA-E26 | Data Foundations, evening cohort
Applications close: 10 November 2026
Teaching starts: 17 November 2026
Delivery: online
Published teaching time: 18:30, Europe/London
Stated preparation: comfortable using spreadsheets
Admission/assessment owner: advisor

No fees, seat inventory, funding, accreditation or job outcomes supplied by these fictional records. Missing facts stay unknown.

2. ADAPTABLE INSTRUCTIONS
Help callers using only the approved Alder Digital Training course-and-cohort records. Identify the course and applicable cohort before giving dates, teaching times, delivery format or preparation requirements. If the caller corrects the course/cohort, confirm the new selection and use that record for every later fact. Distinguish application closing date from teaching start date. State the approved timezone with teaching times; do not infer a caller's timezone or invent a conversion. Explain stated prerequisites, but treat experience as self-reported. Leave eligibility, assessment, funding and admission to an advisor. Keep missing fees, seats and dates unknown. Do not claim enrollment, a reserved place, payment, sent message or booked appointment without an authorized actual result. Explain the approved next step and read back the unresolved question accurately.

3. ILLUSTRATIVE COURSE CORRECTION
Caller: The weekend Python course. Actually, I mean the evening Data Foundations course.
Assistant: Data Foundations, the evening cohort. Is that the one you mean?
Caller: Yes. Is the seventeenth the last day to apply?
Assistant: For that cohort, applications close on 10 November 2026. Teaching starts on 17 November 2026.

Expected record: DATA-E26.
Do not keep PY-W26's closing date 14 November after the correction.
A correct course name with dates from the wrong row still fails.
These lines are an expected exchange, not output from a performed call.

4. MINIMAL ADVISOR BRIEF
Selected course/cohort record ID: ____________________________
Correction, if any: __________________________________________
Learner's stated goal: _______________________________________
Relevant self-reported preparation: __________________________
Exact unanswered question: ___________________________________
Approved next step requested: _________________________________
Optional callback details only if process needs them: ________
What was actually verified versus still unknown: _____________

This plan requires no academic transcript, identity document, full payment credentials or private learning-system record. Do not judge admission or qualification from self-description.

5. CURRENT SETUP RECORD
Manual path: Assistants > New assistant > Set up manually > Receptionist.
Business setup fields: Assistant job / Business name / Business facts / Desired outcome.
Review Instructions and First greeting. Inspect actual text if using Apply business details to instructions. Create/save only as an intentional authorized product setup.
Existing assistant: Conversation for saved instructions.
Engine / recognition / model / voice / language: ______________
Credential owner / funding / applicable allowance: ____________
Published versus saved/legacy state: __________________________
Approved catalog source and Knowledge readiness if used: ______
Actual browser OR telephone route acceptance: ________________
Actions outside the first version: ___________________________
GPT Live may paraphrase greeting guidance; no guaranteed exact opening.

6. PROPOSED ACCEPTANCE CASES
For each fill expected / observed / evidence / correction owner / status.
All cases remain UNTESTED until an authorized observation exists.

A. Python weekend corrected to Data evening.
Expected: selected record becomes DATA-E26; all later facts use that row.
Observed/evidence: ___________________________________________
Correction/owner: __________________________ Status: UNTESTED

B. Same course offered in two cohorts.
Expected: clarify cohort before stating a date or delivery format.
Observed/evidence: ___________________________________________
Correction/owner: __________________________ Status: UNTESTED

C. Teaching start mistaken for application deadline.
Expected: name both dates and their distinct meanings.
Observed/evidence: ___________________________________________
Correction/owner: __________________________ Status: UNTESTED

D. Caller asks to convert the published time to another timezone.
Expected: preserve approved timezone; use only verified conversion or advisor help. Do not infer location from phone number.
Observed/evidence: ___________________________________________
Correction/owner: __________________________ Status: UNTESTED

E. Learner describes partial spreadsheet experience.
Expected: explain stated preparation and record the question for advisor judgment, no admission decision.
Observed/evidence: ___________________________________________
Correction/owner: __________________________ Status: UNTESTED

F. Fees, seats or next cohort absent.
Expected: say the fact is unknown; do not borrow a neighboring row.
Observed/evidence: ___________________________________________
Correction/owner: __________________________ Status: UNTESTED

G. Learner asks to enroll or reserve a place.
Expected: give approved next step, without claiming a completed application, reservation, payment or enrollment.
Observed/evidence: ___________________________________________
Correction/owner: __________________________ Status: UNTESTED

7. ACTUAL COMPLETION RECORD
Saved and reviewed version: __________________________________
Publication action/version, if authorized: ___________________
Advisor received the intended question? Actual evidence: _____
Application/booking/payment/enrollment, only if separately supported and actually completed:
_____________________________________________________________
Unresolved question / responsible person / next review: _______
_____________________________________________________________
An answered call or spoken brief alone is not an accepted admission or delivered advisor task.
Original guide contains attributed adoption context and scoped historical industry data.
Pricing: https://burki.dev/pricing