Advanced course prompts
Timed offers to graduates, showing the prerequisites they already meet and the next start date.
A coding camp rarely ends at graduation. Alumni look for the next course, employers ask about the program and past students can recommend a friend to the next cohort. A customer retention app for coding camps keeps those relationships active with timely, specific messages rather than a generic alumni newsletter.
Two months after graduation, a former student receives a message in the app with a link to her project review and a short note from her mentor about a strong piece of work. The message asks whether she would like to hear about the advanced cohort and offers a short call with an alumni advisor.
She opens the advanced course outline. The app shows the prerequisites she already meets, the next start date and the deposit timing. It also offers a referral link: if she brings a friend who enrolls, the app records the referral and shows the reward rules before she shares anything.
She books the advisor call. Afterwards the app logs the outcome, and the program team can see that she enrolled after an alumni message. Her next prompt waits for a clear milestone in the course, so she is not contacted every week.
Most coding camps keep applicant and alumni records in a customer relationship tool or a student management system, and they send campaigns through an email platform. The retention app should read from those systems and write back consent and preferences, rather than create a fourth list of contacts.
Alumni activity often lives in the learning platform, on GitHub and in the cohort chat. Where a camp shares graduate project links, the app can show them as evidence of progress without copying anyone's code.
Referral tracking needs a clear link between the referrer and the new enrollment. The enrollment record should carry that reference, so a reward is calculated from confirmed enrollments rather than from a spreadsheet.
Alumni messages are marketing. Email sent in the United States must follow the CAN-SPAM Act, with a working opt-out, an accurate sender and a physical address. Text messages need consent recorded with its date and source under the Telephone Consumer Protection Act (TCPA), and opt-outs should apply across every channel straight away.
Some alumni were under 18 when they started. A learner under 13 cannot be marketed to through an account without verifiable parental consent under COPPA. Referral rewards and testimonial requests should be explained clearly, and any public use of a graduate's name or project needs written permission.
If the camp takes federal student aid, FERPA covers the education records the retention app might read. Share only what each graduate has agreed to, and keep grades and conduct notes out of marketing views entirely.
Timed offers to graduates, showing the prerequisites they already meet and the next start date.
A short call with an alumni advisor, booked from the same message as the course outline.
Referral links tied to confirmed enrollments, with the reward rules shown before anyone shares.
A graduate's project and mentor note shared with their consent, as evidence of progress.
Retention activity follows the cohort calendar. Graduation weeks suit invitations to the next course and requests for reviews, while the weeks before a cohort starts suit referral reminders. Sending an advanced-course offer during a graduate's final project review would be badly timed.
Application seasons create a different load. A surge of applicants can crowd out alumni follow-up, so the app should keep the two queues separate and show the marketing manager how many alumni prompts are waiting.
Quiet periods between cohorts are the right time for re-engagement. A short, useful note with a project idea or a community event keeps alumni connected without a sales push.
Start with the graduate list: names, cohort, track, completion date and consent status for email and text. A clean list with consent recorded is more useful than a large one with unclear permissions, so agree how missing consent will be handled before launch.
Share the advanced course outlines, the prerequisites, the referral reward rules and the start dates for the next two cohorts. Mentors should supply a short progress note for any graduate who wants to hear from them.
Access follows role. Alumni see their own records, referral status and offers. The marketing manager sees campaign results without student grades, and the program director sees the whole list.
Launch with one clear reason to open the app, such as an advanced course with a confirmed start date. Mentors can mention the app during a graduate's final review, but only where the graduate has agreed to hear about future courses.
Give the program team a weekly list of graduates who responded, booked a call or referred a friend. Use that list to refine the next message, and retire any prompt that does not earn a response over a fair period.
The CRM holds the records, and the app decides what each graduate sees and when. It times prompts from the cohort calendar, collects consent and tracks referrals against confirmed enrollments, which a basic CRM rarely does on its own.
Set the frequency by segment. Graduates considering an advanced course hear more than those who have not replied. Keep the default light, and let graduates change their preferences in the app at any time.
Rewards can be calculated automatically from confirmed enrollments. Payment still runs through the camp's own process and its tax and payout rules, so the app shows the amount and status rather than moving money itself.
Advanced course prompts and advisor booking give the clearest return, because they tie a message to a concrete next step. Referral tracking and showcase links can follow once consent and records are clean.
Begin with a free scoping call and get a written scope before any build.