How We Handle Feedback and Feature Requests

Your feedback and requests are very important to us! When you submit feedback or feature requests, they are sent to our internal documentation to be reviewed by the product team. Feature requests can be anything from UI improvements, to new product features, or even feedback for current product features.

How to Submit Feedback

To submit a feature request to Check-in Pax, you can use our Feedback option, located in the help widget on the bottom-right corner of all our administration pages.

Look for the chat or support icon, click it, and select Send Feedback or Feature Request.

Use a Category

There are four categories to choose from. These are required and provide us with the necessary information to sort and route feedback to the correct team.

1. I have an idea (Feature request)

Use this option when you have a request for changes or improvements to the product.

Examples: "It would be great to have a dark mode for the Check-in App" or "Can we add a way to export guest lists as PDF?"

2. I'm confused (Usability / onboarding issue)

Whether you're unsure how to find something or just have a general question, ask us anything with this category.

Examples: "I can't find where to rename my device" or "The reporting filter is not working as I expected."

3. It's broken (Bug / performance)

Find some buggy behavior or something isn't working how you'd expect? Let us know here!

Examples: "The QR code scanner crashes when I switch between modes" or "The guest list takes too long to load."

4. Other (Feedback / kudos)

Anything else can be communicated in this category – let us know how we're doing!

Examples: "Love the new multiple check-in buttons feature!" or "Your support team was incredibly helpful today."

Be as Descriptive as Possible

Please provide as much information as possible in your feedback. This includes:

• Use-case information for feature requests – tell us how you plan to use it
• Why it is important for you and your event – the more context, the better
• Describe any problems with as much detail as possible – steps to reproduce are very helpful
• Use screen recordings and screenshots – a picture is worth a thousand words

Example of good feedback:

*"We run multi-day conferences with 2,000+ guests. Currently, we have to manually switch between Day 1 and Day 2 check-in buttons. It would save us hours if we could automatically reset all check-in statuses at midnight. This is important because our volunteers often forget to switch buttons, causing inaccurate attendance data."*

Example of poor feedback:

"Add more features."

How We Choose What Is Implemented

We would love to implement every request that comes our way, but this is unfortunately not possible. When you submit a feature request, it is being considered for future updates, but this does not guarantee that it will be implemented.

When considering feature requests, we have to think about the impact it will have for our clients as well as for our own product. We keep track of:

• How many times a feature is requested
• Why it is important (use cases)
• How it will improve Check-in Pax for everyone
• How feasible it is to implement

The more detail you can provide, the more information we have to consider!

What Happens After You Submit Feedback

Note: We cannot respond personally to every feature request, but we read every single one. If you need a follow-up, please include your email address in the feedback.

Pro Tips for Getting Your Feature Request Noticed

• Be specific. Vague requests like "make it better" are hard to act on.
• Explain the problem, not just the solution. "We need to track session attendance" is better than "Add 50 check-in buttons."
• Show us how many people are affected. "This affects our 50-person volunteer team" helps us understand impact.