COACHING MANAGEMENT · ENQUIRY OPERATIONS
Coaching Enquiry Follow-Up: A Practical Process for Counsellors and Centre Managers
How coaching teams can record enquiries responsibly, assign follow-up, avoid duplicate contact and hand the right context into admission.
Conceptual product view · no customer records or performance figures
THE SHORT ANSWER
A useful enquiry process captures only relevant, known information, gives each next step an owner and keeps follow-up proportionate. Use consistent status meanings, check existing records before creating another and record meaningful contact history. An enquiry becomes an admission only when the institute’s own decision and process say so; the software should support, not invent, that threshold.
01 / USEFUL ENQUIRY RECORD
Capture enough context to support a relevant conversation.
An enquiry record should help a counsellor understand what the person is asking about and what information has already been shared. Record the programme or course interest and contact context that is genuinely known. Avoid speculative labels or personal notes that do not help the next responsible person.
Explain to staff which information is required, which is optional and how the institute handles a request to update it. A record should not become a catch-all profile simply because an individual contacted the centre once. Keep collection proportionate to the institute’s purpose and privacy practices.
02 / SOURCE & STATUS
Use status labels that describe a real process step.
Enquiry source may help the institute understand how people find a programme, but it should be recorded only when known. Do not guess a source to complete a field. Agree what each status means—for example, awaiting a response or conversation completed—and train staff to apply it consistently.
A status is not a judgment of a person’s intent or a guarantee of future admission. Keep the definition visible and change it when the underlying interaction supports the change. Confirm the product’s current status model rather than publishing an invented set of stages as a CodePex feature.
03 / FOLLOW-UP OWNER
Make the next conversation specific, assigned and proportionate.
For each enquiry that needs follow-up, state what information is pending and who will contact the prospective learner. A vague ‘call again’ note is difficult to act on and may result in several staff members making duplicate calls. Assign responsibility and a sensible timing based on the person’s request and the centre’s own contact policy.
Check recent contact history before reaching out. Respect a request not to be contacted and avoid excessive messages. Where a communication channel does not support replies in the same system, provide the institute’s separate contact route rather than implying that a response will be monitored there.
04 / HAND-OFF TO ADMISSION
Transfer context only when the institute’s admission decision is made.
A prospective learner may ask questions, compare courses or pause before applying. Do not treat every enquiry as an admission. Define the institute’s threshold and the person authorised to confirm it. Once admitted, pass forward the programme interest and relevant contact context without copying unnecessary conversation history.
Check that the learner’s identity is matched to an existing record before creating a new one. Resolve duplicates carefully and protect information about other family members. The hand-off should make it clear which details are verified and which remain to be completed by the admissions team.
05 / REVIEW & DATA QUALITY
Review unresolved enquiries as a process queue, not a staff ranking.
A centre manager can review which enquiries lack a next step, have outdated contact information or are waiting on a requested answer. Confirm date range, programme mix and status definitions before comparing teams. Raw counts do not explain why an enquiry did not proceed.
Use the review to fix process friction: unclear course information, unassigned follow-up or a status that means different things to different staff. Do not use an incomplete record as proof of counsellor performance. Speak with the people involved and interpret the data in the context of the centre’s work.
06 / PRIVACY CHECK
Keep prospective learner information limited and appropriately accessible.
Prospective students and families may share contact information before deciding to enrol. Restrict it to staff who need it for the enquiry and follow the institute’s retention and contact practices. Do not export enquiry lists broadly or reuse them for unrelated purposes without an appropriate basis.
Set a process for stale enquiries and information that no longer serves the original purpose. Confirm the product’s actual access and history controls during evaluation. The institution, not a status field, remains responsible for deciding what information to retain and how to use it.
A FIELD GUIDE FOR YOUR TEAM
An enquiry-to-admission follow-up review
Use this at daily team review to identify genuine next steps without turning each enquiry into repeated, unstructured contact.
| Lens | Question to ask | What to record |
|---|---|---|
| USEFUL ENQUIRY RECORD | Capture enough context to support a relevant conversation. | A minimal, useful record with clear purpose and verified contact context. |
| SOURCE & STATUS | Use status labels that describe a real process step. | Shared status definitions and an explicit rule for changing them. |
| FOLLOW-UP OWNER | Make the next conversation specific, assigned and proportionate. | One next step, one owner and a respectful contact cadence. |
| HAND-OFF TO ADMISSION | Transfer context only when the institute’s admission decision is made. | An institute-defined admission decision and a checked identity hand-off. |
| REVIEW & DATA QUALITY | Review unresolved enquiries as a process queue, not a staff ranking. | A short unresolved-work list with cause checks before performance conclusions. |
| PRIVACY CHECK | Keep prospective learner information limited and appropriately accessible. | A purpose-limited record, role-appropriate access and retention review. |
CODEPEX IN CONTEXT
Useful guidance begins with clear scope.
Campus declares enquiry records, source and programme interest context, follow-up, statuses/history and transition to admissions. Confirm exact fields, status options, assignment behavior and channel support. Do not imply that CodePex.com is a CRM; these are coaching product workflows discussed for institutional use.
Product-specific statements are based on the current owner-controlled capability declaration. Ask CodePex to confirm any institution-specific configuration or unlisted requirement.