Demo guide · CRM & customer operations
Run Event Registration and QR Check-In in GoSeedly
Follow the event demo from ticket setup to guest registration, QR check-in, and attendance review, with a rehearsal checklist for your own event.
To run an event in GoSeedly, configure the event and ticket capacity, save the public registration page, register a test guest, and check that guest in at the desk. The September 11 DevLaunch walkthrough shows those screens in a demo account. This guide turns that walkthrough into a rehearsal you can repeat before inviting attendees.
1. Start with an installed Events module
You need your own Seedly CRM installation with the GoSeedly Event Tickets & Check-In module installed. Use the installation guide linked below for the host requirements and setup commands. This walkthrough begins inside the installed module.
Create a practice event with a recognizable test name. Use contact details you control and a free test ticket for the first rehearsal. That lets you check the registration and admission path without treating a successful booking as evidence that a paid checkout has been tested.
2. Set the event details and admission rules
In Settings, enter the event details, date and time, and ticket types. Set a finite capacity appropriate to the event. Review the attendee policy, including whether transfers and organizer-approved refund requests should be available. The demo exposes these as choices; choose the policy for your event before publishing it.
Write down what the guest needs to know: where to arrive, when doors open, which ticket to choose, and who can answer a booking question. Put those answers on the page before spending time on colors.
3. Save and inspect the public registration page
Open Settings → Public page. The demo changes type style, colors, cover imagery, and layout, and shows content sections for highlights, FAQs, and photos. Start with the event description and arrival information, then preview both mobile and desktop.
Save before opening the public page in a separate tab. In the recording, the presenter explicitly notes that the design changes were not saved, so the separate page still shows the earlier design. Use that moment as a check: the public page must show the version you intend guests to see.
4. Register a guest and decide how to use CRM contacts
Open the public event page and complete a test registration. Check the ticket and QR code, then locate the guest in the attendee list. Compare the selected ticket with the attendee record.
The demo shows attendee management, imports, and a choice to sync attendees to CRM contacts or keep them within the event tool. Decide which record your team will use for follow-up before importing a guest list. For the rehearsal, confirm what one registration creates before adding a larger batch.
5. Rehearse QR and manual check-in
Open the check-in desk and test the QR camera using the device your team will use at the door. Then rehearse finding a guest manually, because the demo includes that admission path too. The installation guide specifies online admission for V1, so test with a working connection at the venue.
The following are suggested rehearsal checks, rather than results established by the recording:
| Try this | Check the result |
|---|---|
| Scan a valid test ticket | The correct guest and ticket are identified. |
| Scan the same ticket again | Staff can recognize the existing admission and avoid admitting twice. |
| Find the guest manually | Staff can resolve the booking without a readable QR code. |
| Use a ticket for a different event | Staff cannot mistake it for admission to this event. |
| Review the attendee record and activity log | The recorded admission matches what happened at the desk. |
6. Review attendance before reusing the event
Compare registrations, check-ins, and the activity log. Resolve any practice records before opening a real event. If you duplicate an event, review its date, location, capacity, ticket options, and public copy instead of assuming everything should carry forward.
Paid tickets, refunds, reminders, and other connected providers need their own end-to-end checks in your installation. The screen walkthrough demonstrates the workflow and controls; it does not establish how your accounts or venue devices will behave.
Do attendees have to become CRM contacts?
The demo shows a choice between keeping attendees in the event tool and syncing them to CRM contacts. Choose based on how your team will manage the relationship after the event. Check a single test attendee before importing or syncing a larger list.