New features available
with Allalinhorn V1.
New features and improvements
Freshly out
Season ticket holder management
Improve your data quality with the improved season ticket holder management creating only beneficiaries instead of a contact sheet when your customers are only providing a last name/first name.
New scrollable terms and conditions
You can now activate a more integrated way of user interaction for them to accept your terms and conditions with a scrollable popup. With this new feature, online users can read, scroll to the bottom of the popup and accept the terms and conditions without having to switch to another Browser Tab to read the content.
Visit timeslots
Copy all the existing timeslots from one visit space to another. This new feature accelerates a lot your setup when all your visit spaces have a similar timeslot configuration.
Voucher
A new parameter is introduced to Voucher, which allowing to keep the remaining amount in the Voucher for next use (instead of sending to Credit note or debtor profit).
Ticket template
Print a test ticket based on a real ticket directly from the ticket list screen.
Touch sales
New questions (gender and year of birth) is asked together with Contact Origin at Box Office or Touch Cart.
Newsletter for guest check-out
A guest registering to a newsletter during the checkout process will systematically receive this newsletter, because he's considered to have given his explicit consent for communication from the organisation.
Producer portal
Producers can manage the real time sales and availability of their visit passes and time-slot products on Producer Space by using Dashboard.
Price mapping for external interfaces
Recently SecuTix has introduced a new pricing model where each product comes with a rate table. A new price mapping feature is introduced in order to simplify the external interfaces configuration.
JSON validation for comfort variables
If you are extensively using SecuTix public API with comfort variables and storing data in JSON format, this feature ensures that your JSON syntax will always be right.