NYC Big Windows Phone Twitter competition

Microsoft has started up a Twitter competition which will be running today, between 12:01 a.m PT and 11:59 p.m. PT. The prizes are 20 Windows Phones to be given away to 20 lucky winners (1 per person). So how does one enter? It's easy:
- Sign into Twitter (register an account if you haven't got one).
- Tweet a message to @windowsphone that includes, RT this for a chance to win a Windows Phone. "There's a #bigwindowsphone in Herald Square in NYC. Check it out. #WPNYC".
Please note that this competition is only available for those who reside in the U.S. Good luck!
Source: Windows Phone Blog (opens in new tab)
Windows Central Newsletter
Get the best of Windows Central in in your inbox, every day!
Rich Edmonds was formerly a Senior Editor of PC hardware at Windows Central, covering everything related to PC components and NAS. He's been involved in technology for more than a decade and knows a thing or two about the magic inside a PC chassis. You can follow him on Twitter at @RichEdmonds.
-
The problem with contests like this is that, if you win, you're likely to get an AT&T phone, which really sucks if you are on any other carrier, especially if you're on Sprint or Verizon.Then the phone is ZERO use, I am not going to switch to the worst US carrier's network to use a free phone.
-
Well with the message you have to include you get about 7 characters to use... But hey a free phone would be great I'd love a Focus S :D
-
wait so, if u win, are they also paying your 2 year contract?
-
No.
-
so much for winning. All the moola will go towards cp bills.
-
It's possible they could be unlocked. Or one could unlock it.
-
This contest rules does not make any sense. It says that each day there will be a "word" of the day. Huh? It then says they will contact winner by email, phone or mailing address. How are they going to do that with Twitter?
-
If you win they send a tweet and ask you to DM them.
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.