Date: Wednesday, 5th May 2021
There’s nothing more annoying than a ‘Duplicate Delegate’ - when someone is registered twice in a system.
It can lead to inaccurate reports, overbooked events and general frustration for administrators. That is why our Learning Management System (LMS) is designed to stop this happening as much as possible.
Our LMS prevents duplicate delegates through a mixture of automatic system actions and actions carried out by the administrator.
To make it easier to understand how both these actions work, we created the below diagram.
It also explains how our intuitive system manages the registration process, handles forgotten passwords, notifies administrators about potential duplicate delegates and merges records – all to prevent duplicate delegates.
In blue are the changes we at Phew do systematically. And those items in purple are the actions a client needs to undertake as part of the process.
A primary email address is the main email address a delegate uses for communication. This is also the delegates LMS username.
A secondary email address is the additional email address a delegate used to create a secondary account. Once the delegate has set their primary email address, they cannot then log in via the secondary email.
There are a number of steps carried out by our LMS to try and stop duplicate delegates occurring. These are as follows:
Once you merge two delegates (see below image), the system will take the two records and creates a new, single delegate record.
It also remembers the other email addresses, so they can’t register again using the other emails. The new delegate record will have all bookings and evaluations from both accounts.
Email us at firstname.lastname@example.org and we will be able to give further clarification on any questions.