Gecko supports a ton of unique event statuses, which can be used to track how students interact with your event and to create workflows that react accordingly.
Some actions, like scanning a student accepting an invite or your team scanning a student's QR code ticket with the Visit app, automatically update event statuses. You can also edit any student's status manually from within the event.
Whilst you're free to interpret event statuses however you please, there are some unique status features you can learn about below.
Invited
🔎 What: When viewing their RSVP page, students marked as Invited can accept or decline the invitation. Accepting will mark the student as Registered, and declining will mark the student as Cancelled. If the student declines, they cannot change their mind and accept the invite.
An easy way to communicate with invited students is to set up an event workflow condition to target any student with the Status = Invited.
Registered
🔎 What: The student has signed up for the event, and their attendance is expected come the start date/time of the event. When setting up an event field or when adding students manually into your event, the default status to add them is Registered.
An easy way to communicate with registered students is to set up an event workflow condition to target any student with the Status = Registered.
Attended
🔎 What: The student attended the event. There are multiple ways to capture attendance at an event; the visit app, the capture app, workflows, imports, and many more.
An easy way to communicate with students who attended your event is to set up an event workflow condition to target any student with the Status = Attended.
Engaged
🔎 What: The student attended the event and was super engaged. This information can be captured on the visit app or manually updated on Gecko.
An easy way to communicate with students you engaged with at events is to set up an event workflow condition to target any student with the Status = Engaged.
Waitlisted
🔎 What: Waitlists can be enabled by going to Edit > Attendee Options and toggling Enable a waiting list to on. If the Maximum number of attendees is met, any additional registrants for your event will automatically be added to the waitlist. Guests are always counted when calculating the maximum number of attendees.
If any of the original maximum attendees are removed from the event or cancel, Gecko will automatically change the status of the first student on the waitlist to registered.
Waitlists can also be enabled, and maximum attendee numbers can be set up on a session-by-session basis.
An easy way to communicate with students on the waitlist is to set up an event workflow condition to target any student with the Status = Waitlisted.
Cancelled
🔎 What: Students who decline an invitation or use the Cancel Booking button on their RSVP page will be marked as cancelled within the event.
Students marked as cancelled cannot rebook onto the event through their RSVP page.
An easy way to communicate with students marked as cancelled is to set up an event workflow condition to target any student with the Status = Cancelled.
Removed
🔎 What: The Removed status can only be achieved by your team manually marking a student as removed. Students who are removed cannot rebook onto the event.
An easy way to communicate with students marked as removed is to set up an event workflow condition to target any student with the Status = Removed.
Did Not Attend
🔎 What: The Did Not Attend status is reserved for students who didn't attend your event, despite being registered for it. The most common way of using this status is to create a workflow that waits until the end of the event and then updates all students still marked as registered to the did not attend status. Watch the video above to learn how to set this up.
An easy way to communicate with students marked as did not attend is to set up an event workflow condition to target any student with the Status = Did Not Attend.
Any questions? Start a live chat with a support team member, or feel free to explore the rest of our academy. Spotted an error or want to suggest a future article for the academy? Let us know here.