Author Topic: SDCC 2018 Hotel Request Form Lottery - Submission Times  (Read 20670 times)

Offline mark

  • Volunteer HQ
  • ******
  • Join Date: Mar 2015
  • Posts: 3917
  • Karma: 0
  • Liked: 2023
Re: SDCC 2018 Hotel Request Form Lottery - Submission Times
« Reply #180 on: April 20, 2018, 02:12:11 PM »
You are not allowed to view links. Register or Login
Update: I received a waitlist email today for my earlier form, but my husband did not receive a waitlist email for the later form. This is odd because there's no way they would have flagged one as a duplicate. I used my work address, while his listed our home address, listed different phone numbers on each, used each other's middle names when submitting roommate names, and used our own member ID. Not a big deal because we already have our room taken care of from being gifted a MMM, but still weird. OnPeak strikes again.

Thanks for the update! Did he check his junk mail folder? Some people reported finding it there.

Offline clambert1273

  • Gaming Lounge
  • ****
  • Join Date: Jul 2017
  • Posts: 379
  • Karma: 2
  • Liked: 196
Re: SDCC 2018 Hotel Request Form Lottery - Submission Times
« Reply #181 on: April 20, 2018, 02:48:24 PM »
Mark...  just to update mine

Got waitlist email on all 3 forms :)


Sent from my iPhone using Tapatalk

Friends of Comic Cons

  • Guest
Re: SDCC 2018 Hotel Request Form Lottery - Submission Times
« Reply #182 on: Today at 08:10:52 AM »

Offline Violet

  • Gaming Lounge
  • ****
  • Join Date: Jul 2013
  • Posts: 328
  • Karma: 0
  • Gender Biased Reviews www.gbreviews.com
    • Gender Biased Reviews
  • Liked: 118
Re: SDCC 2018 Hotel Request Form Lottery - Submission Times
« Reply #182 on: April 23, 2018, 09:45:50 AM »
You are not allowed to view links. Register or Login
Thanks for the update! Did he check his junk mail folder? Some people reported finding it there.

It was not in his junk folder. However, it did end up showing up in his regular inbox later, with the same timestamp as the email I received (11:01am). So it may have been a Yahoo server issue.