Feature Ideas

Trending
  1. ability to see guest passes

    when we check people in we cant see how many guest passes are left

    Marissa J

    0

  2. Automatic junior to adult account creation

    When a customer who is a junior family member on a primary adult profile turns 18, automatically upgrade them to an adult account. This will require an email address, so potentially the initial trigger could prompt an email to the parent account to ask them to upgrade to an adult account by providing an email address. When they go to check-in, if the junior has turned 18 but does not yet have their own account, perhaps a prompt to the team member to detach the junior account and create an adult account would be helpful. This will help the wall staff to identify when juniors are becoming adults, avoiding a scenario where they are checked in as a junior even though they are an adult and should have completed the adult waivers on their own account.

    Jonny W

    0

  3. Waivers that trigger based on competencies

    My idea is for creating the ability for a waiver to trigger based on changes to competency on account. Specifically on changes to the competency of junior family members. This is because we would like to have junior sign-off waivers that can be triggered once we sign off the child as competent post assessment. Previously we tried to have a waiver that triggers after selling a product to achieve this goal but it no longer works and this would be significantly less steps.

    Greg K

    0

  4. Stop adults from adding other adults as family members

    All our adult users are required to have their own accounts and their own waivers. i suggest that customers should not be able to add adults to their family themselves. Currently when an adult adds another adult to their family it does not generate a waiver for the other adult but the adult can still have their own competency and be checked in with no alerts warning the staff member that the person they are signing in has no waivers.

    Tasha T

    0

  5. Operator PIN Code Feature

    The Operator PIN Feature will introduce a flexible authentication system that enables operators to move seamlessly between workstations whilst maintaining security and accountability. Operators will authenticate using 4-digit PINs at any workstation, with the system tracking all actions through comprehensive audit logs. Administrators will manage operator profiles, PIN resets, and permissions through settings, whilst the system will provide granular settings to determine which actions require PIN authentication.

    Phil Parker

    1

  6. Notes Audibly and Visibly alert on checkin for Staff!

    We have these great notes, and we can set the degree of alert, but none of that is helpful if it doesn't alert staff. Ideally, we would have the ability to assign a note to alert to the guest and staff for things like "Hey, we need you to update your payment method", or just Staff (for things like "Keep an eye on their belay technique". And ideally these notes would have a sound and visual pop up when this person checks in. Again, either for the guest and staff, or just staff.

    Brittany B

    0

  7. Drop down for family members on pos screen.

    When checking in a family and applying the entry to a particular family member, adding a drop down box that shows linked family members/connections to make checking in families with mulitple kids faster.

    Centre Staff C

    0

  8. Adding course/ session bookings into a cart to stack booking payments together

    For customers that are booking onto multiple sessions / courses or parents with multiple kids that are all being booked onto a session / course, currently, they have to pay multiple times in order to complete the transaction for each session / course booking. It would be helpful if all of these bookings could first be set to a cart, which, when complete, could be collectively sent to the card reader.

    Jonny W

    0

  9. Punch Pass Sharing

    It would be incredibly helpful to have a way to share punch passes. We have three membership types and shareable punches is one of them. There is currently no way to do that and you can technically share a punch by removing one from the punch holder, but then you cant check in the person who the punch was shared to.

    Kit F

    0

  10. Customer History/Activity section

    New section on customer profile, admin visible only, that will display every customer interaction conducted on the platform. Same functionality as the Trial feature.

    Phil Parker

    1

  11. Relocate account/customer notes on the "Checkins" page

    Relocating an account/customer's notes to the right side instead of underneath the competencies would mean that at a glace when checking people in we can see if there is anything important we need to be aware of. At the moment with them being at the bottom we have to scroll down and more often than not they are missed.

    Peter C

    0

  12. Split Payments

    option to split payments between cash and card

    Till 1 S

    0

  13. Improved Corporate Accounts

    Ability to generate Invoices with a payment link (not pro-forma) & credit notes. Must be a value rather than session or entry credits.

    Mark P

    0

  14. POS Keyboard Shortcuts

    Something that can massively speed up till work is having keyboard shortcuts for specific items - i.e. to steal a few from RGP, alt+c for adding a customer, F12 for "Checkout", etc. Most times on POS I rarely touch the mouse unless I have to. You could also then assign different shortcuts to POS menus in the settings to access sub menus faster.

    Peter S

    2

  15. Autoโ€‘assign the booking customer as the participant so booking email is sent automatically

    Currently, when a customer books and pays for a session, the system allows the booking to be created without assigning a participant. This means the booking is treated as a guest booking and no entry QR code is generated automatically. Operators then need to manually assign the customer as the participant in the backend before the QR code is created. This creates significant admin overhead. Requested behaviour: When a loggedโ€‘in customer books a session, the system should automatically assign that customer as the participant. Or force the customer to assign to everyone climbing before payment is enabled. This would allow the QR code to generate automatically without manual intervention. This would remove the need for staff to monitor and manually assign every booking where the customer has forgotten to click on assign.

    Chikara S

    1