It is unavoidable that an invitation will be forwarded, but as a user you can find out. For example, in the guest list you see names that do not appear to be known, or an invitee indicates that the registration is unsuccessful. Then look at the details of the guest and see that the name and / or email address has been changed, you know that a forwarded invitation is the cause.
You send an invitation with a personal link to the registration form. But what happens when that personal invitation is forwarded? We explain the consequences on the basis of 3 scenarios.
Scenario 1: The guest registers himself and then forwards the invitation to a colleague
- The colleague sees the message on the event site: "This invitation has already been confirmed."
- The initial registration cannot be overwritten. The colleague can only register if the registration form is public
Scenario 2: The guest does not register himself and forwards the invitation to a colleague
- The colleague can register successfully. Data automatically entered on the registration form can be overwritten by the colleague. It can be prevented that the e-mail address can be changed.
- The initial guest can no longer register. He can only register if the registration form is public and must use a different e-mail address than was used by the colleague.
Scenario 3: The guest forwards the invitation to a colleague who has also received an invitation
- The colleague can register via his own invitation as well as via the guest's invitation. However, different email addresses must be used. In this case, the same guest appears twice in the guest list.
- The initial guest can no longer register. He can only register if the -ERR:REF-NOT-FOUND-registration form is public and must use a different e-mail address than was used by the colleague.