A learner has paid for a course, then messages your academy on WhatsApp: “I can't attend the Saturday cohort. Can I move to Thursday?” Saying yes immediately feels helpful, but it can promise a seat that is already taken or a financial adjustment nobody has approved. A transfer request is not a confirmed transfer until the policy, capacity and responsible staff have been checked.
A cohort transfer is not a cancellation
Moving to another session of the same course, switching to a different program, and cancelling an enrollment can have different consequences. Payment does not automatically make every transfer permissible, nor does it mean a refund or credit has been approved.
For an Egypt-specific example, the AUC School of Continuing Education FAQs discuss class transfers in relation to timing, seat availability and consultation with the department. That is AUC's policy, not a rule for every Egyptian training provider. UCLA Extension's transfer guidance illustrates how third-party payment and fee differences can complicate transfers, but its US procedures should not be copied as Egyptian requirements.
What should enrollment staff verify?
Identify the enrollment using the academy's approved verification process. Capture the current course and cohort, the requested cohort, the relevant start dates, and the reason only if it affects an established exception rule. Check the actual payment record, whether sessions have already been attended, and any transfer deadline.
Do not ask learners to send sensitive identification or payment credentials over chat just because a transfer is requested. If an employer paid for the course, confirm whether its approval is needed separately from the learner's preference.
Three possible outcomes, with different messages
Eligible and approved: A staff member verifies an actual seat, checks the published terms, confirms any fee difference and updates the enrollment system. Only then should the learner receive a confirmed new schedule.
Pending review: Explain what is being checked and what information is missing. Share a response time only if the team can meet it. The message should not imply that a seat is reserved.
Not eligible under the policy: Explain the relevant condition respectfully and present only genuine alternatives, such as a waitlist or a separate cancellation review. Do not invent a refund entitlement or offer an unapproved discount.
A short example that avoids a false promise
Learner: “I paid last week and need to move to the Thursday group.”
Initial response: “I can help submit a cohort-transfer request. Please share your enrollment reference and the group you want. Our team will check seat availability and the transfer conditions, then confirm the decision. Your registration has not been moved yet.”
Once an authorized person approves the request and the system is updated, the final message can state the new cohort, any approved fee adjustment, and what happens to previously attended sessions. This is an illustrative workflow, not a real customer's case.
Track the decision, not just the conversation
A useful request record distinguishes new, missing information, academic review, financial review, approved, declined and completed. Approval and completion are separate: a team might approve the move but still need to change attendance and payment records.
Assign an owner and a next step. Monthly, review transfer volume, time to decision, incorrect confirmations and complaints about conditions learners did not understand before paying. These are operating indicators, not proof that AI increased revenue.
How Mr. AI can assist
Mr. AI can explain approved academy information, collect the relevant request details, summarize the chat, follow up and hand cases requiring judgment to a person. It should not be described as automatically changing enrollment records, refunding payments or guaranteeing seats. The academy's enrollment register remains the source of truth.
For full cohorts, see managing course waitlists. For entry requirements, see course-fit checks before enrollment. Follow-up messaging must respect consent and the WhatsApp Business Messaging Policy.
Review ten anonymized real transfer requests and write the approved response for each outcome before you test the customer conversation.
