HeySummitHHeySummit
5h ago

Conditional Ticket Availability Based on Prior Purchase

Enable organisers to make certain tickets (e.g. workshops, meetups) available only to attendees who have already purchased another specific ticket (e.g. a subscription or main conference ticket). Use Case: We offer a paid membership ticket that grants ongoing benefits. One of those benefits is access to exclusive, free in-person meetups. However, we want to ensure only paid members can register for these meetups — they should not be visible or purchasable unless a membership ticket has already been bought. Why It Matters: - Prevents abuse of exclusive free content - Supports tiered access strategies (core in SaaS, community, and education models) - Currently requires hidden ticket links and manual enforcement - Clean integration of upsells, bundles, or gated perks improves attendee experience Suggested Implementation: - Add a setting to ticket creation:“Make ticket only available to attendees who have already purchased [select ticket(s)]” - Optionally hide or disable ineligible tickets at checkout - Error message or redirect for attendees attempting to access without prerequisite ticket Impact: Improves monetisation models, rewards loyalty, and supports more sophisticated event and membership strategies
CompletedCompleted
4 hours ago

Should the default be to display restricted tickets? I can always check the box to hide from checkout so in all honesty it is not an issue at all. The functionality does work, but it lets you go a couple of steps before letting you know. Thanks again, this is not important, maybe something to note when documenting the feature later.

4 hours ago

Hey Andrew, Thanks for reaching out. You can already do this for add-ons and donations. When you manage those records, there is an option to optionally limit it to those with particular tickets. Presumably this functionality would work based on what you've just described if we made it available also at the ticket level? If you’re able to confirm, we should be able to add it. Also with regards to per-session attendee limits, we already have this as well. If you head to the Content and Talks list and select Advanced Settings, you'll see that you can specify both online and in-person limits at the individual talk level. I hope these both help! Just let me know if we're missing something from your use case that we don't currently provide from these two areas.

4 hours ago

Sounds like we are already 99% of where we are hoping to get to, i will map out the user journeys but this certainly sounds like it will meet short ad medium term needs, thanks Ben.

4 hours ago

Fab, sounds good!

4 hours ago

Cheers @ben having taken a look yes, that's exactly what we want - thanks! If the same functionality can be extended to work at the ticket level as you've described, that would be perfect. Appreciate the clarification on per-session attendee limits too, that's all clear on our end, and awesome it is already available.

4 hours ago

Great, thanks Andrew for confirming. I'm pleased to say that we've now rolled out this capability. Please see the changelog below. https://heysummit.userjot.com/updates/p/conditional-ticket-a…

4 hours ago

Awesome, that was quick. Do you ever get to some rest Ben? Appreciate you

4 hours ago

Ha. I’m actually technically on holiday with the family this week but just wanted to get this one out of the door. Normal service will resume in a week :)

4 hours ago

On a busmans holiday myself, try and enjoy the rest of your day at least!

4 hours ago

Cheers, and you too. We fly back on Friday so hopefully a few days of relaxation lie ahead. Hope you manage to get some too.

4 hours ago

Another need is the ability to setper-session attendee limits for in-person events, particularly useful for breakout sessions or workshops. While this would ideally be a dedicated feature [displaying how many spaces left, and delegates have ability first come first served to add to their agenda until full] the conditional ticketing request above would also be a functional workaround, if a bit more longwinded to manage, however it would allow us to manage capacity and set clear expectations without introducing yet more new functionality. Thanks for considering it.