Player guest Mary has been playing video poker for 3 days. She has accumulated enough points to move up to the Platinum level. The database notices this (we told it to watch for this) and triggers(1) a text to Mary’s cell phone “Hey Mary, you just made it to the platinum club. We are sending you a free Room offer as your first reward”.
The database also triggers(2) a personalized letter sent that day welcoming Mary to the platinum level with her Free Room night in it. This letter goes out by noon at the completion of her trip because the database triggered the data to merge and print directly on a waiting, automated press; hands-free.
She gets this offer letter 1 or 2 days after she gets home, not a month later when ‘the batch’ goes out.
The database also triggers(3) an email to be sent in 1 week later telling Mary that she earned some freeplay for her next trip (segmented and personalized based on your reinvestment plan). If she makes her reservation this week we can upgrade her to a 2-night stay.
The final scenario the database is looking for is to see if Mary comes back in or redeems our offers. If after 6 weeks Mary has not returned for a trip the database triggers(4) an increased reinvestment mailer where she is offered a free dinner for her and a friend if she books her room this week.
Design many trigger scenarios easily
Marys’ sample story is just that, a sample.
Triggers(1-4) included :
- Text on her cell phone (if she provided it)
- Personalized Bounceback letter
- Personalized Email offer coordinated with her letter
- An increased reinvestment mailer
You could have even triggered a text to her host to visit her on the floor if possible.
You can design as many scenarios that you can think of to create an endless array of personalized and automated triggered guest experiences that run all year long instead of bulk batches of mailings done monthly. Guests don’t always think in monthly batches like we do. They are all on their own individual journeys and when we treat them that way we get our best results.