Session Notifications vs Event Notifications

Can you describe what issue(s) you are trying to solve?

​@lrnlab ideally we would like an alert to go out when the enrollment does but not multiple times, so that the learner is aware (and their manager and the admins, as programmed in the digests) but not again so soon afterward when the digest goes out (currently set to daily at noon). But we also did not want to disable the alerts because once our integration with LInkedIn Learning is set up, we anticipate staff enrolling in more than one course at a time and do not want to overwhelm their inboxes individually. Happy to provide more information if it would be helpful!

​@lrnlab I just realized this was a response to a different issue I was having. Apologies. In the case of this post, we found that only one admin is getting the digest and other notifications when VILT sessions are happening. The instructor is not getting the reminder we set up, but the learners are. No other admins are other than one, although the notification is set.

​@armaan01 Here is the notification cadence we use for ILTs…

• “User Enrolled in ILT session” is sent at the time of the event for all ILT courses
  • This notification includes the calendar invite.
• “Digest: user enrolled in a course” is sent Daily at 20:00 for both all ILT courses as well as all e-learning courses.
  • Yes, this does mean they are technically notified twice in the same day, but given it sends in the evening, and could include other enrollments, it tends to not feel redundant...unless they enrolled at 19:45, I suppose. 😅
• “ILT session starting” is sent three days prior to the session at 7:00 for all ILT courses.
  • We use this a reminder. Still includes the calendar invite. Also has instructions on how to switch sessions if there is a conflict.
• “ILT event starting” is sent one hour prior to the event for all ILT courses.
  • We use this as a final reminder. This one lets users know how to join the session.
     

Is this helpful?

​@shanejacques thanks! I will compare this to what we have and see if that fixes the functionality for us.