This feature is currently under development and is not yet available to configure and start using. This documentation will be updated when it is ready to activate.
Overview
Entry tickets are one-time passes to attend certain activities. They will be valid only for a specific date and the user is allowed to buy any number of tickets based on the requirement.
Booking Entry Tickets
First, the user should select the preferred Region and/or Facility from the available filter drop-down menus to see the corresponding view of entry tickets.
The user is then presented with a list of available entry tickets, where they need to select how many tickets they want to book.
Once the selection is done, the next step is to choose the specifik slot.
The entry tickets are then added to the cart and the user will have to check out and pay.
When there is a resource allocation
If a resource allocation is available, based on the resource availability, a grid view of time slots will be shown to the user. Here, the user should click on a specific time slot on a given day to see the available entry tickets on that day for the selected time.
When there isn’t a resource allocation
If a resource allocation is not available, then the whole day is considered as a one slot and the user should click on the ‘Book Now' button of the preferred day to see the available entry tickets.
Configure Slot Entrances
How slot entrances are configured is described here:
Cancel & Refund Entrances
Customers can view their booked entrances in the app (and web) under My bookings. From there, they will have the possibility to cancel and refund their entrance bookings if that has been enabled.
Settings
Setting | Value / Description |
|---|---|
Activate the possibility to cancel entrances from My bookings (allowCancellationOfEntrances) | Yes |
(allowRefundOfEntrancesUntil) | Default: -1 Decides how many hours before users can refund an entrance ticket. If the value is -1, refund is not allowed. If the value is 0, refund is allowed for entrance bookings which has not yet begun. |
User flow
-portrait.png?version=2&modificationDate=1718354088172&cacheVersion=1&api=v2&width=230&height=468)
-portrait.png?version=1&modificationDate=1718354218444&cacheVersion=1&api=v2&width=230&height=468)
-portrait.png?version=1&modificationDate=1718354227083&cacheVersion=1&api=v2&width=230&height=468)