3 ms·
Yes, we did a "token" approach where a non-user could RSVP via yes/no links in the email. Unfortunately, the problem is further up the chain -- the event host n
by mvkel 15y ago
Yes, we did a "token" approach where a non-user could RSVP via yes/no links in the email. Unfortunately, the problem is further up the chain -- the event host needs to know sign ups AREN'T required before they even start making an event. It's more than just a/b testing some "warning" language, too.
- bricestacey 15y agoI think you're right. Even places that allow you to invite/interact with non-registered users - I usually don't. I don't know their email so I'd have to look it up. Even if it interfaced with gmail to pull my contacts, I definitely wouldn't trust it. Nor would I necessarily trust the service enough to expose my friend's email in the first place.
- mvkel 15y agoThe problem is even more higher up than "trust," as it's the simple fact that at this point, you're well beyond the convenience of email/fb message. Why would a person go to the trouble of filling out everything on WhereBerry, connect their Gmail, connect their Facebook, go through both lists, etc.? The only thing WhereBerry has done is introduce an extra step without adding any incentive to do so. The event host is still getting the same information that they would if they posted on their FB wall, or shot an email out. I hate beating up on WhereBerry, but this is just the tip of the iceberg when it comes to figuring out this problem. We went well beyond these first steps and still didn't figure it out.