The new lottery application widget is the first step towards providing a brand new, versatile and much simpler lottery process. No need to synchronize contacts to a separate module and re-integrate reservations/sales after the draw. The new process relies on existing tools of the core S-360 system and will allow you to run your lottery in different ways.
- BV2 Purchase invitation lottery: in the "purchase invitation" mode, customers register their interests to certain match and seat categories, but do not define the precise tariffs and quantity. Winners are then invited to purchase within a certain time-frame. It is possible to organize subsequent windows to ensure the full quota is sold out. Earlier winners have a higher chance to get exactly what they want compared to later winners. The main advantage of this strategy is that the quota can be fully sold, whereas in the classic mode reservation might not be paid or credit card payment may fail. Moreover, up-selling options can be made available to winners in order to drive additional revenue.
BV3 Automated payment lottery: in the classic mode, customers define precisely what they are applying for, including the tariffs and quantity, and the system will automatically create a reservation for each winners. Automatic payment can be done if credit cards alias have been captured.
The application widget now supports capturing the quantities and tariffs. However, the draw process and automatic payment require an ad hoc process.
- ZV1 Application confirmation email: upon creating, updating or deleting an application a user will receive a confirmation email with the details of the application.
Solution
The new widget lets you customer register their requests inside the waiting list table
The new process relies on the following tools:
- APPLICATION: New widget based on the waiting list to capture application requests.
- DRAW: SAM targets and its randomized sub-targets to find winners
- PAYMENT:
- Purchase invitation mode: Link the winners (targets) to the corresponding advantages to invite them to purchase online.
- Automated payment mode: Coming soon... Run a batch to immediately create a sales (or reservation) for the winners.
Currently the new widget only supports multiple events/competitions with multiple performances/matches. It does not support other product families.
Getting started
Initial configuration
In the sales periods of the activity profile, a new function has been added to define the competition and matches available for request.
You need to activate the link in the navigation menu, (which also activates the widget) through the following POS configuration key: config.presales.waitingList.activated = true
For capturing the tariffs and quantity, the organization needs to be configured accordingly.
Application email configuration
A new "Application confirmation" document class has been added. The email is triggered when creating, updating and deleting an application. For the first two cases, the content of the application can be displayed in the email.
Applying online
The new widget is integrated in the following page:
- https://yourDomain.com/account/lotteryApplications
The first screen can be configured to provide information about the lottery process. It also serves as the summary page, once an application has been submitted.
The second screen lists all the matches available and provides the following filters:
- Venues
- Teams
Users can expand specific matches and select one of the available seat categories. Once all requested matches and seat categories are selected, the user can click on the continue button at the bottom of the screen.
The last screen of the process displays all the specific contact criteria with visibility level "Lottery application" to provide some additional options.
Users must then accept the terms and conditions to save their application.
Applications can be later edited or fully cancelled.
Reviewing applications in the back-office
All requests can be reviewed and managed from the waiting list screen of the contact module.
SAM targeting can be used by relying on custom queries.
The query builder does not support direct targeting of the waiting list data. However, custom queries can be built to create a SAM target.
