An accurate place count, a waitlist that promotes people by itself and joining links that work come built into cRUD Webinar, because registration is handled as each person signs up rather than reconciled by hand afterwards. A team running sign-ups through a meeting link and a separate form spends the week before a session counting rows and answering emails. In cRUD Webinar, each registration then carries straight into attendance, replay and follow-up, so the list checked before the session is the one reported on afterwards.
TL;DR
- Run and Scale add a public registration page with approval, domain and business-email rules, while Start adds attendees by CSV import and invitation.
- Capacity is checked as each registration is saved, and the waitlist promotes the next person automatically when a place opens.
- Confirmations, reminders, schedule changes, cancellations and replay messages run by rule, with suppression and preferences respected.
- Attendance, questions and replay viewing join each registration rather than arriving later as separate exports.
Why sign-ups sprawl across forms, inboxes and exports
The usual alternative is a form tool for sign-ups, a spreadsheet for the place count, an email tool for reminders and a meeting tool for the session. Each handoff is a copy. When someone cancels by replying to a reminder, a coordinator has to update the sheet, find the next person on the waitlist and send them a link by hand.
Errors follow predictable lines. Two people take the last place. A schedule change reaches the people in the email tool but not those added later. The attendance report uses different names from the form, so nobody is quite sure who came.
A place count that is right at every moment
In cRUD Webinar, capacity is checked as each registration is saved, so a session never takes more people than it has places, even when a newsletter sends a rush of sign-ups in the same minute. Registrations awaiting approval hold a place, and cancelled or declined ones release theirs straight away.
When a place opens, the waitlist promotes the next person automatically and sends their joining details, so nobody has to watch the list. Attendee limits apply per webinar, up to 100 on Run and 200 on Scale. When a team needs one more live session than its allowance includes, an Event Pass arranged through Sales adds one standalone live Webcast of up to 60 minutes and 100 attendees.
Status messages sent by rule, not drafted at midnight
Invitations, confirmations, reminders, schedule changes, cancellations, follow-up and replay messages run by rule from the webinar itself, as part of cRUD Webinar's operations automation. Each message reflects the person's current status, so a waitlisted registrant receives a waiting confirmation and a promoted one receives joining details.
- Confirmation states whether the person has a place, is on the waitlist or is waiting for approval.
- Reminders carry each person's own joining link, so attendance is attributed to the right registrant.
- Schedule changes and cancellations reach every affected registrant at once, including people added after the first invitation.
- Replay messages go only to eligible registrants once the recording is ready, on Run and Scale.
Suppression and communication preferences are respected throughout, and consent is recorded with each registration rather than inferred later.
Imported customer lists and public sign-up pages
Some audiences arrive through a public page and some are already known. On Start, attendees are added by CSV import and invitation, with consent handling on the import, which suits a 30-minute customer Microcast for up to 50 people. Run and Scale add the public registration page, where the approval, domain and business-email rules described on the Right Audience page apply as each person signs up.
Either way, the registration lands on the same webinar record. A customer imported from a CSV and a prospect who found the public page follow the same capacity, waitlist and messaging rules.
A year-end payroll session that had to move
The figures are illustrative. A customer education lead at a payroll software company on Run schedules a 60-minute live Webcast on year-end filing changes for finance administrators at customer firms. Registration runs through the public page with a business-email rule, capacity is set at 100 and the waitlist is switched on.
Two things happen. The session fills in four days and 38 people join the waitlist. Then the guest speaker, a tax specialist, asks to move the session forward by one day. The schedule change notice goes to every registrant and waitlisted person by rule. Fourteen people cancel, and the first fourteen on the waitlist are promoted and receive their joining links without anyone touching a spreadsheet.
After the session, the education lead reviews one record. Eighty-one people attended live, and the 19 confirmed registrants who missed it receive secure replay access once the recording is ready. The 24 people still on the waitlist are offered a repeat session the following week, which the lead approves after checking that none of them has opted out of contact.
The registration list as the start of the record
A registration in cRUD Webinar is not a row that gets exported and forgotten. Attendance, live duration, questions, poll answers, call-to-action choices, resource downloads and replay viewing join it as separate facts about the same person and webinar. Run adds webinar and workspace reporting, and Scale adds account-level and programme reporting.
That is the operational benefit. The team stops reconciling lists from three tools, registrants receive accurate messages and the people who follow up start from what each person actually did. On Run and Scale, Revenue Action proposes a next step with its reasons, and a person approves it before CRM sync or an automated outbound workflow sends anything.
What to ask about registration handling
- Is capacity enforced as each registration is saved, or counted after the form closes?
- Does the waitlist promote people and send their joining details without a coordinator?
- Do schedule changes reach everyone affected, including people imported later?
- Does each registrant get a personal joining link, so attendance is attributed correctly?
- Can the same rules govern an imported customer list and a public sign-up page?
The plain-language guide to webinar registration management covers form design, reminders and the measures to watch before you compare platforms.
Summary
cRUD Webinar connects registration, approval, capacity, waitlist and attendee access on one programme record. State changes can drive accurate communication without separate spreadsheets or silent assumptions. The platform enforces the selected rule, while the organiser remains responsible for the fields, disclosure and fair criteria used to decide who may join.