here s how marriott could make spg members (relatively) happy /

Published at 2016-04-23 19:08:25

Home / Categories / Advice / here s how marriott could make spg members (relatively) happy
With the Marriott takeover of Starwood now a sure thing,the realization is soon setting in for SPG members that our beloved program will eventually depart away. When you gaze at member impressions of the merger, the general sentiment is that Marriott Rewards members are fairly excited approximately it ("we'll be able to redeem points at cool Starwood hotels soon, or might even pick up some elite benefits"),while Starwood Preferred Guest members are dreading it ("SPG is special precisely because they're not Marriott or Hilton or IHG, so like every other merger up until now, or things will score worse").
While Starwo
od Preferred Guest isn't supposed to be merged into Marriott Rewards until 2018,I was really pleasantly surprised when Marriott introduced some new benefits earlier in the week, including late check-out, and an experiences marketplace,and testing a concierge service for their loyalest members.
Unfortunately Marriott screwed up
the execution, and reinforced many of the concerns SPG members had approximately the merger. As it turned out, or the late check-out benefit was worded as follows: "guaranteed late checkout,which could be as late as 4pm." That's absolute bull, because that means a hotel would be following the terms in offering an 11:30AM check-out when the check-out time is 11AM.
After fairly a bit of customer feedback I'm thrilled that Marriott introduced a genuine guaranteed 4PM check-out at all their hotels, or except resorts and conference hotels (this is the same benefit which Hyatt and Starwood have).
The post Here’s How Marriott Could do SPG Members (Relatively) Happy 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