what are you trying to communicate to your users? Just the fact that they havent logged in yet? or something else?
So looking at the notifications, there is an even for “user has been created” and then you can schedule it to trigger to happen a certain amount of hours after the event in the scheduling portion of the notification set up.
Or another option which is what we do, is we enroll our users into a “welcome learning plan” of sorts that gives them info about the company and how to use the platform, we have our platform set that the second they are created in Docebo they are enrolled automatically. From there you could create a notification that “User has been enrolled in Learning Plan” set it to happen 6 hours after the enrollment. In the notification you can provide whatever login info they will need and a link to the learning plan, that way they get right to the spot that lets them know how to use the platform from the notification.
We have 3 learning plans that they need to progress through as part of their 6 week induction. At each week, they should be focusing on different areas of the learning plans (and beyond once they reach week 5 and 6). The notifications are to remind and guide them through their learning, plus drip feed them some of the other features, such as booking onto a certain course, encouraging them to share content, browse the reward shop etc.
We have 3 learning plans that they need to progress through as part of their 6 week induction. At each week, they should be focusing on different areas of the learning plans (and beyond once they reach week 5 and 6). The notifications are to remind and guide them through their learning, plus drip feed them some of the other features, such as booking onto a certain course, encouraging them to share content, browse the reward shop etc.
The “learning plan expiring” template might be your best bet if you are using a due date for your LP’s. You would need to create several copies each going out at different times (x days/weeks before the due date)
@CharlieCromp1- the challenge you are going to find is the drip.
What bring a person to the next level if it isnt self driven and is date based could be potentially solved by using the create a new user notification because you could “post date” a notification after the person has started - needing nothing other than that new user notification to drive the drip. So on user creation you send your on creation. You send along a LP enrollment notification as well. On day 8 you send X with your new user notification (fashioned with learning information) to get to the next level. On day 15 you send Y. Leveraging that, a combination of enrollment rules and deeplinks to your LPs you can develop a type of drip cadence based on timing of a new person coming into your organization and not on completion.
If you have access to your integration and an HRIS team? In theory you may need a flag for a custom user field set by your HRIS team to tell you certain milestones as well - and use that to map individuals. As in something that is telling you that a person is a new hire (and is within their first 30 days), - but going further other flags - for example a 60 day flag, a 90 day flag and a 365 day flag - to support doing more of this with enrollment rules and LPs notification. Unfortunately, there isnt a great math evaluator/logic with groups, or I would tell you to set a single counter field. But alot can be achieved with the equal to and not equal to operators.
In terms of progress? There are a few ways you can skin it down - via a weekly digest if you need to keep nudging them along to the next level...but you don’t want to think about it too much after. Be careful - you can inundate a person with these eventually.
Good luck - let us know the approach you settle into.
Last note - we use @lrnlab’s model - but there is a caveat to using LPs with validity. When they “conk out” - they do lock. Best to give it an impossible date (999 days) and use some math to expire down your notifications (if you want to nudge a person weekly do that math - 992 days nudge, 985 days nudge, etc).
So looking at the notifications, there is an even for “user has been created” and then you can schedule it to trigger to happen a certain amount of hours after the event in the scheduling portion of the notification set up.
Or another option which is what we do, is we enroll our users into a “welcome learning plan” of sorts that gives them info about the company and how to use the platform, we have our platform set that the second they are created in Docebo they are enrolled automatically. From there you could create a notification that “User has been enrolled in Learning Plan” set it to happen 6 hours after the enrollment. In the notification you can provide whatever login info they will need and a link to the learning plan, that way they get right to the spot that lets them know how to use the platform from the notification.
Not sure how manual of a process you’re looking to take on, but you can leverage automatic group to identify new users based on their affiliation with a certain branch, then use that group to:
- enroll users into courses associated with a learning plan and apply an enrollment deadline
- enroll same group into the learning plan
The enrollment deadline will enforce a soft deadline and encourage completions while not locking them out of the courses should the deadline expire. Even ask the group grows, the platform will prevent multiple enrollments into courses or learning plans. If only new users take these courses and they’re suppressed from a catalog, then you could associate those reminder emails with the course or learning plan enrollments.
