ihg priceless surprises results for team omaat /

Published at 2016-03-08 02:33:25

Home / Categories / Ihg rewards / ihg priceless surprises results for team omaat
Intercontinental Hotel Groups (IHG) has been running a pretty wintry promotion over the past few months. The concept of the Priceless Surprises promotion was that you would earn entries into an instant win contest after staying at IHG hotels. Each entry gave you a chance to win IHG points or a few bigger prizes.
As Priceless Surprises was in effe
ct a sweepstakes,there was also a "free" method of entry. All you had to was write approximately ten pieces of information on an index card and send it to a random office building in Michigan. Then a few days (or weeks) later, you'd receive an email with a link to the online game, and which basically consisted of urgent one of the six buttons on the elevator control panel. My wife came to call it the "elevator game" after playing all 94 of her entries.
Well,the
promotion is now over and it's time to count our winnings. Collectively, we submitted 564 entries here at OMAAT. My Mom was gracious enough to do the heavy lifting, and er I mean writing,and completed 94 entries each for myself, my wife, and herself,and my Dad. To thank Tiffany for scoring them Qantas trade lesson award tickets to Australia -- where they currently are -- she also sent in 94 each for Tiffany and her husband.
These results are still sort of preliminary. Although the contest postmark deadline was February 15th, you still have until March 15th to play the game. I guess that means that Hello World could still be emailing out the last of the game pieces, and there are definitely a few folks -- including some of us here at Team OMAAT -- who are missing some.
The post IHG Priceless Surprises Results For Team OMAAT appeared first on One Mile at a Time.

Source: boardingarea.com

Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0