Feb 082011
 
 Posted by on PST2011.02.08Tue at 17:34 Meetup.com LFFLFN, RSVP Qs LGBSVE  Add comments

LGBNFF: 7 Meetup RSVP private Qs LGB2XZ (asking full name, cell, email, & zip, plus getting participation) http://1.JotHere.com/146#LGBNFF

  1. LGB2XZ: The 7 Qs

    1. What’s your CURRENT (1)CELL# +(2)EMAIL (at least 1 reaching u during event), &(3)ZIPCODE? –unless we already have it. This is so we can find everyone +give u data-access&local-alerts&carpool; and all-but-zip is private (only event hosts can see it).
    2. What’s the FULL NAME of YOU&your GUESTS off your/their photo ID? –unless we already have it. This info is is private (only event hosts can see it ) & for further trust +required if putting you on a guest list which checks ID (eTickets,nightclubs).
    3. Did you include a constructive ideally-enthusiastic comment in your public RSVP saying especially WHY you’re RSVPing NO or MAYBE or YES? –put it there, please. If RSVPing NO, see http://2.LoveRules.Info/46 for how.
    4. If you might not be there from start-to-finish (as arrive late, leave early, etc), did you put & update your times in your public RSVP saying what time range you’ll likely be there (when arriving & when leaving)? –put it there, please.
    5. Will you be bringing everything on the TO-BRING list in the event listing (read its links)? –do, please.
    6. Could you possibly post an offer to carpool, as the event listing describes how (read its links)? –do, please.
    7. On your group profile, (1) Does your main picture clearly & accurately ID you and (2) Are all the questions there fully answered with your current info? -insure so, please, as this is required plus very helpful to other members.
  2. LGBPK2: Pros thru Cons:

    1. MBPS80: Notable PRO: Proven since ~20010 to dramatically increase member participation including taking the group & event serious.
      1. MBPSC1Most notably, not suprisingly, people aren’t serious & remindably reachable, until they actually give their email address & especially cell # for an event, but, without these Qs,  Meetup doesn’t collect this at all.
    2. LGB8ZJ:Seems to cover all the common situations and in a universally useful form. Would work for:
      1. LGBP76: dance club guest lists as in http://Meetup.com/AsianFriendster
      2. LGBP87: Technical regular professional meetings of http://Meetup.com/OCAndroid
    3. LGBQA9: Pro: The bulk of the questions (the last 5 of 7) are just a simple & automated way to individually insure done key points of Etiquette & Things-To-Know when RSVPing to any Meetup Event LEVV22 especially given in many cases it probably won’t be read, but these RSVPs likely will.
    4. LGBPUG:Pro: makes one’s full name a separate Q and maximally optional
      1. LGBPVP: As it should be (though is rarely done)
      2. LGBPW2: as else I would be a hypocrite (as I use a handle in my profile and don’t give out my legal name online to strangers unless a very good reason)
    5. LGBPQT: Pro: gathers full name, cell, email, & zip as long done with 1 Meetup RSVP private Q LGBLHW (asking full name, cell, email, & zip) but now better & more.
    6. LGBPJO: Pro: I designed it with the full goals of  Meetup RSVP private Qs to elicit cooperation & participation & from members, especially attendees in mind, including It seems tough to ask & get name, phone, & even email from Meetup members.
    7. LGBS53: Pro: ordered from most to least essential & immediate.
    8. LGBRZM: Small pro: for speed to the reader, puts the question first & the explanation for the info (if any) 2nd, as the reader may not need the explanation and indeed nothing seem so-out-of-line that it needs explanation before it’s asked.
    9. LGB8Z1: Tiny pro: instead of “Please <command/>” (which sounds begging), always used the form “<command/>, please” (which sounds modest & polite)
    10. LGB8OX: Tiny pro: removing “If you’re RSVPing YES or MAYBE” per Private Qs asked only on YES RSVP.
    11. LGBRWN: Tiny pro: whenever sub-questions, they’re numbered.
    12. LGBSEO: All but perhaps new Meetup users will probably balk at the number of private questions (Meetup events generally as 0, where as here we’re asking 7). They’re justified & quick, but will members realize that?
  3. LGB8OL: These Qs are a combination & intended-replacement & improvement of 1 Meetup RSVP private Q LGBLHW (asking full name, cell, email, & zip) plus 1st (& prior) set of 7 Qs with also considerable edits including
  4. LGBP9A: Testing: results not in.

    1. LGBP9W: I am 1st testing these in the Meetup.com/OCAndroid 9th/2111.02.09(Wed) Meeting.
  5. LGBO0G: 1st (& prior) set of 7 Qs:

    1. LGBOF1: I designed & installed these Qs but
    2. LGBOLS: I never got a chance to test them per my immediate redesign of this post.
    3. LGBOMM:Meetup software manged them so I had to & merge two sources in order to recover them:
      1. LGB2X4: http://Meetup.com/OCAndroid 7th/2011.01.12(Wed) Meeting (copy) ended up with 6 private Qs:

        Only Event Hosts will be able to see the answers

        [So we can find everyone &give u local-alerts+data-access &carpool, What's your (1)CELL# +(2)EMAIL (at least 1 reaching u during event), &(3)ZIPCODE? --unless we already have all your current info. All but zip are private (only event hosts can see).]

        2 characters left

        [To put you on guest lists which check ID & for further trust, What's the FULL NAME of U&Ur Guests (off your/their photo ID)? --unless we already have all your current info. This info private (only event hosts can see) but optional for this event.]

        4 characters left

        [Did you include an enthusiastic constructive comment in your public RSVP saying especially WHY you're RSVP? --put it there, please.]

        119 characters left

        [If RSVPing YES/MAYBE, but you might not be there from start-to-finish, did you put in your public RSVP what time range you'll probably be there? --put it there, please.]

        82 characters left

        [If RSVPing YES/MAYBE, will you be bringing everything on the TO-BRING list in the event listing? --please do.]

        141 characters left

        [Does your profile's main picture clearly & accurately ID you? Are all your group profile questions fully answered with current info? -please insure, these are required in this group.]

        68 characters left

        .

        1. LGBNZQ: The 2nd prior (2011.01.12) meeting private Qs answers shows one example answer:
          Thom Hallgren
          So we can find everyone &give u local-alerts+data-access &carpool, What’s your (1)CELL# +(2)EMAIL (at least 1 reaching u during event), &(3)ZIPCODE? –unless we already have all your current info. All but zip are private (only event hosts can see).
          “Thom Hallgren / 310-XXX-XXXX / tXXXX@fiinex.com”
          Not Going Dec 29, 2010 1:32 PM

          –only the 1st Q was answered in all cases as the new Qs were put in just before meeting time so seemingly everyone who was going to RSVP YES already had.

      2. LGB21R: http://Meetup.com/OCAndroid the next (future) 10th/2011.02.23(Wed) Meeting still had them (visible in edit), well well oddly just most of them:

        Only Event Hosts will be able to see the answers

        [Did you include an enthusiastic constructive comment in your public RSVP saying especially WHY you're RSVP? --put it there, please.]

        119 characters left

        [If RSVPing YES/MAYBE, but you might not be there from start-to-finish, did you put in your public RSVP what time range you'll probably be there? --put it there, please.]

        82 characters left

        [If RSVPing YES/MAYBE, will you be bringing everything on the TO-BRING list in the event listing? --please do.]

        141 characters left

        [If RSVPing YES/MAYBE, could possibly put in your public RSVP comment else Talk post an offer to carpool and try to carpool, as the event listing describes? --please do.]

        82 characters left

        [Does your profile's main picture clearly & accurately ID you? Are all your group profile questions fully answered with current info? -please insure, these are required in this group.]

        68 characters left

        .

  6. MBPS28Additional Document history (in order)
    1. MBPS2H: Initial TBA.
    2. MBPS2R: Updated title to present format to have doc give & included title & URL: “7 Meetup RSVP private Qs LGB2XZ (asking full name, cell, email, & zip, plus getting participation) http://1.JotHere.com/146#LGBNFF“; MBPS80: added.

7 Meetup RSVP private Qs LGB2XZ (asking full name, cell, email, & zip, plus getting participation)

  One Response to “7 Meetup RSVP private Qs LGB2XZ (asking full name, cell, email, & zip, plus getting participation)”

  1. [...] 7 Meetup RSVP private Qs LGB2XZ (asking full name, cell, email, & zip, plus getting participati… (most of them just a Y/N [...]