Different classes of registrations #66
-
Assuming the tooling here will eventually support some sort of event registration, I'd love to see support for different classes of registrants, such as:
The SQL Saturday tools always annoyed me in that the attendance limit combined everyone, and if (and I do mean if) sponsors registered their people, it took spots away from attendees, or I had to adjust my maximum numbers to compensate. I think being able to at the very least separate out attendees for purposes of "maximum attendance" would give significant flexibility. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
The current vision is more about building integrations for existing tools that do these things well: ex) Eventbrite for attendees, Sessionize for Speakers, etc. I think we should keep in mind that Speakers & Sponsors are attendees for some purposes (ex, capacity for physical space, lunch, etc)... But you often want to segment other communications separately so that Speakers/Sponsors get their "special" instructions, without getting the "standard" instructions, which may not apply to them. Implementation details may vary, but this could be as simple as creating a "turnkey" way to ensure selected speakers from Sessionize get auto-registered into a special "Speaker" ticket type in EventBrite. (or some other mechanism completely) |
Beta Was this translation helpful? Give feedback.
-
I would agree with @amtwo here. The idea is to integrate with existing services here where possible, rather than building. If someone wants to build this, great, but for now, I'd look to integrate with
|
Beta Was this translation helpful? Give feedback.
The current vision is more about building integrations for existing tools that do these things well: ex) Eventbrite for attendees, Sessionize for Speakers, etc.
I think we should keep in mind that Speakers & Sponsors are attendees for some purposes (ex, capacity for physical space, lunch, etc)... But you often want to segment other communications separately so that Speakers/Sponsors get their "special" instructions, without getting the "standard" instructions, which may not apply to them.
Implementation details may vary, but this could be as simple as creating a "turnkey" way to ensure selected speakers from Sessionize get auto-registered into a special "Speaker" ticket type in EventBrite…