Preventing Misuse of Personal Invites ('Request Your Own Invite' Feature)

When you send an invite to an individual or a contact list for one of your Seatrobot events, that invite is personal to the recipient. This means that the 'accept / decline' buttons in the invite email 'know' the recipient they are intended for - allowing the recipient to accept or decline an invite to your event without having to go to an anonymous page and fill in their personal details. This 'one-click accept' feature is very useful and increases your response rate by up to 35%.

Occasionally an invite recipient may forward their personal invite email to someone else who may not understand that the invite is not personalized for them. This could cause confusion if they accept / decline using this forwarded email and see the original recipient's information in their confirmation. It could also create false information in your event GUEST LIST.

To minimize this behavior, Seatrobot has added a guardrail feature, 'Request Your Own Personalized Invite', which works as follows:

1. Whenever anyone clicks on an Accept or Decline button in a personalized invite, they first land on a confirmation page, personalized to them, asking them to confirm their selection, and, if accepting, which registration option they prefer. This confirmation page contains a check, asking people not to sue the page if they are not the original recipient, as below:

2. If a user is not the original recipient and clicks to receive their own personalized invite, they are presented with a form to add their details:

3. When they submit this form, two emails are sent automatically:

a. One email goes to the event manager, including the details of the requester, and also the details of the original invitee the requester used to send the form (the individual who forwarded them the email invite):

b. Another email goes to the requester, confirming that their request has been sent:

As the event manager, when you receive this notification, you can choose whether or not to send an invite to the requester.

NOTE: this feature includes a common sense feature which checks whether the requester is already associated with the GUEST LIST for the event:

a. If the requester has no association with the event, the emails above are sent

b. If the requester is already confirmed for the event, Seatrobot re-sends them their confirmation email instead

c. If the requester has already declined for the event, Seatrobot re-sends them their original invite email, from which they can 'un-decline' (if this function has been activated for the event by the event manager)

d. If the requester has been previously invited and did not RSVP, Seatrobot re-sends them  their original invite email, from which they can 'accept'.