Feature Request: More Options for Customer Communication Based on Live Event Attendance and Recipient Segmentation
Hello Skilljar team,
We would like to submit a second feature request, related to customer communication within Skilljar.
Current limitation
At the moment, we can only use the completion state of a course as a trigger for communication, for example in a thank-you email. This is not sufficient for our use case. Not every course has a completion state that fits, and a completion-based trigger does not allow us to reach all relevant learners at the right moment.
Our use case
After a live event has taken place, we want to:
- Make the event recording available as the next lesson in the relevant course.
- Communicate with learners in a way that depends on their participation:
- Learners who attended the live event should receive a different message than learners who did not attend.
- Learners who registered but neither attended nor completed the course must also be informed about the recording and should not be excluded.
In both cases, every relevant learner needs to be notified about the recording, but the content and tone of the message should reflect whether they took part.
What we would like to request
- Attendance-based segmentation: The ability to distinguish between registered, attended, and not-attended learners for live events, and to use this as a condition for communication.
- Additional triggers: Communication triggers beyond course completion, such as a live event being completed, a lesson being published, or a registration status change.
- Targeting of registrants: The ability to send communication to users who are registered for a course or event but have neither attended nor completed it.
- Message variants per segment: The ability to create different email content for each segment within the same workflow or campaign.
These options would allow us to automate recording distribution reliably, communicate in a more relevant way, and avoid manual follow-up work for each live event.
Could you let us know whether any of these options are planned or already available in another form? If there is a workaround, or a related feature request we should follow, please point us to it.
Thank you for considering this request.