A receipt is not course access

Decide which system confirms the purchase and which grants the enrolment. An unfinished checkout should not trigger the same action as a completed order.

Keep an enrolment identifier so repeated notifications don't create repeated accounts or messages. Define how refunds and cancellations are reviewed, too.

Send the message they actually need

Give the student a sign-in link, a clear first step and a support address somebody reads. Save the extra offers for another message.

Test with a new email outside your organisation. Follow the instructions on a phone. If you need to explain a missing step over a call, put it in the welcome message.

Know who is still waiting

An enrolment with no access or a failed welcome email needs a visible support task. Someone should own that list, especially when orders arrive outside office hours.

IXM's ELDT Nation work includes course onboarding, email workflows and cloud automation. For any course business, test a new student, a returning student and a duplicate event before trusting the process.

Quick audit

  • Confirmed purchases reach the correct course.
  • Repeated events do not duplicate enrolments.
  • The welcome message works on a phone.
  • Failed access or email delivery has an owner.

Sources used