S-360 already provides the possibility for a season ticket holder to keep the same seat across the whole season if all the performances contained in the season ticket use the same logical configuration. This will often be the case for a championship season ticket containing the home games taking place in a given arena but more rarely in the life entertainment domain where seat configurations may vary. The Fest Abo pushes the "fixed seat" logic one step further by guaranteeing the same seat across several logical configurations belonging to the same physical configuration. This new logic has also been implemented in the season ticket renewal process and the management of the preferred seat.
Geographical scope
Although initially foreseen for the German and Austrian markets (Fest Abo is the German word for fixed seat season ticket), this new feature may be used by any customer.
Solution
Set-up of the Fest Abo
When creating a new season ticket, the operator will have to choose its type:
The types Calculated price and Predefined price already exist. The new type Fixed seat season ticket that matches the Fest Abo is basically a Calculated price season ticket that includes the fixed seat logic described in this page.
The season ticket type of an existing season ticket is recalled at the top of the Parameters tab:
The Fest Abo can only be defined as a season ticket without (fixed) seat category. This means that the operator will define a global quota for a given Fest Abo and not a specific quota for each seat category. The reason for that is that a given seat (selected by an end customer for the whole season ticket) may have a different seat category for different performances if these performances use different logical configurations. The price paid by the end customer takes the actual seat category into account.
Sales at box office
The sales process is basically the same as for a calculated price season ticket. After having selected the product, the operator selects (as usually) the seat category, contingent, tariff and quantity. The only difference is that the seat category will apply on the first performance of the season ticket, as illustrated below.
In the second step, the operator selects, as usually, the performances to be purchased inside the season ticket.
The 3 first events use 3 different logical configurations belonging to the same physical configuration (and same space). The last event takes place in a different space, implying a different physical configuration.
S-360 displays a grouped map displaying the seats that are available for both 3 events sharing the same physical configuration. By clicking on the information icon, the operator can see for which performances he's selecting a seat and on which performance the displayed seat map is based. For instance, the seat map above is based on Mozart concert of 29.11.2025 and S-360 will automatically select a seat that is in the selected seat category (in this example, seat category 2) for the Mozart concert. The selected seat (seat 135 of row AA) could be in another seat category for one of the other performances (in this example, Bach concerts).
Finally, the operator selects a seat for the last performance taking place in another space.
The operator may override the behaviour above and select the seats separately for each performance by selecting the map by map option as illustrated below:
However, SecuTix doesn't recommend this option since it breaks the fixed seat logic.
Preferred seat
After the purchase process, the selected seats are stored as preferred seats. For a given contact, there may be one preferred seat per physical configuration. If a preferred seat already exists for the given contact and physical configuration, it will be overridden by the newly selected seat. Preferred seats may be viewed in the Contact module with the new menu entry Preferred seats. The operator may delete a preferred seat, this action having no impact on the purchased tickets. Preferred seats are only stored during a purchase process. They can't be defined directly from the screen below.
If multiple season tickets are purchased at the same time, the preferred seats will be stored for each cultural contact specified.
Preferred seats will be used during the purchase of another Fest Abo using the same physical configuration(s) and during season ticket renewal.
Currently no support of preferred seats for single entries
In this first version, the preferred seat isn't taken into account when buying single tickets that don't belong to a Fest Abo. This feature will be implemented in a future release.
Fest Abo renewal
Physical configuration | Identified seat based on origin season ticket | Identified seat based on preferred seat | Action | Rationale | ||
|---|---|---|---|---|---|---|
| Physical configuration of target season ticket exists in origin season ticket | Seat is available | Seat has same category | Seat is available | Seat has same category | ||
Current restrictions
STX-133464
Getting started
You don't have anything to do to benefit from the Fest Abo. It's directly available.
