Jan
23
Saying Non-Transferrable doesn't make an invite non-transferrable
We've seen a lot of the old "Please don't forward this invite" and the "RSVP at RSVP@myBrandedEvent.com" lines at the bottom of an invitation email.  Both these lines point to missed opportunities and extra work that Event Farm specifically addresses, let's see how:

 

1.  "This Invitation is Non-Transferable"  This rarely stops someone from forwarding to a friend, who then forward it on again.  Next thing you know you have people showing up at your event waving your "private" email.  Event Farm  avoided this scenario years ago with the creation of "Invite to RSVP."  If your intended guests forward and Event Farm invite, the unintended guests can only RSVP for the original recipient.  It's one thing to say "This Invitation is non-transferable" and it's another to actually make it non-transferable.

 

2.  "RSVP at rsvp@myExclusiveGenericEvent.com"  Ever take rsvp's by email?  Not the most enjoyable process.  Combine that with an exclusive list, and you have enough cross-checking work for a couple of motivated interns.  If you know who is supposed to be invited, why not import the list and use invite to RSVP?  Clicking a link and checking a box is more user friendly than hitting reply and typing out a quick and often awkward RSVP message. 

 

Bonus:  One of our favorites seen at Sundance this year:  "Inform all others for whom you have RSVP'd, as we do not have their email addresses."  Talk about broadcasting that your branded event is disorganized. If you have reached out to VIPs and other key trend-setters to help promote your event, treat them AND their guests properly.  A Ticket Block is ideal for this scenario.  If someone is a point person for an important group, empower them to invite their guests in case there is an important event update.  The Event Farm system can easily message guests across all of your important Ticket Blocks (or just message specific groups).