Each person's consent choice is respected in every invitation, reminder, replay message and sales handoff in cRUD Webinar, because it is recorded once at registration and checked again before anything is sent. In a stack built around a meeting link, consent sits in a form service while messages leave from an email tool and a CRM that may never have seen the latest preference. cRUD Webinar keeps each person's agreement, preferences and webinar activity together, so the team can honour a narrower choice without hunting for it.
TL;DR
- Consent is recorded with registration, and CSV imports include consent handling.
- Invitations, reminders, replay messages and follow-up run by rule, with suppression and communication preferences respected.
- Audience Intelligence applies consent, suppression and eligibility before it recommends anything, and a person approves each handoff.
- Retention, controlled recording access and requests for access, export and erasure are part of the product.
How consent drifts across a form, an inbox and a CRM
In a stitched-together setup, the registration form captures a tick box, a spreadsheet merges it with an imported list, and an email tool sends reminders from its own contact database. A week later someone exports attendees into the CRM for follow-up.
Each copy holds a slightly different version of what the person agreed to. An unsubscribe in one tool does not reach the others, and an erasure request has to be repeated in every system that ever received the list. The privacy risk grows with every export, not with the webinar itself.
Consent captured at the moment someone registers
In cRUD Webinar, consent is recorded with registration. CSV imports include consent handling, so imported contacts arrive with their consent state rather than as bare email addresses. Teams set the registration questions, consent wording, approved domains and approval rules before promotion, so the form asks only what admission, delivery and agreed follow-up require. The Right Audience controls show how those rules work together.
Because the consent record sits with the person and the webinar, later activity such as attendance, questions, poll answers and replay viewing is read alongside what that person agreed to. That is the starting point for every follow-up decision.
Preferences honoured in every reminder and replay message
A webinar sends many messages, and each one is a chance to ignore a preference. cRUD Webinar runs invitations, confirmations, reminders, schedule changes, cancellations, follow-up and replay messages by rule, with suppression and communication preferences respected each time.
- Operational messages such as confirmations and schedule changes reach the people who need them in order to attend.
- Promotional follow-up goes only to people whose consent and preferences allow it.
- Suppression and revocation apply when a message is sent, so a person who opted out after registering is not contacted by the next rule.
- Replay messages point eligible registrants to secure replay on Run and Scale, a controlled experience rather than a public link.
Recommendations that start from consent, not from activity
From Run, Audience Intelligence produces person-level and account-level recommendations that show their reasons. Consent, suppression and eligibility are applied first, so a person who declined sales contact does not appear as a recommended lead, however many questions they asked.
Revenue Action then proposes the next action, and a person approves it before CRM sync or an automated outbound workflow sends anything. The consent context travels with the approved event. Sales confirms the named CRM provider for your workflow, and signed webhooks carry approved events to other systems.
Retention, recording access and data requests in one product
Privacy obligations continue after the follow-up. cRUD Webinar supports retention, controlled recording access and requests for access, export and erasure. On Start, recordings are available to download with 30-day retention. Run includes 25 GB of recording storage and Scale includes 50 GB, with secure replay limited to eligible registrants.
The security and privacy page explains how retention follows the product, media and organisation rules that apply to each account, and where privacy requests go. Attendee records are not shared across tenants, so a request about one organisation's webinar is handled inside that organisation's boundary.
The practical benefit is fewer copies of attendee data and fewer manual checks before each send. Marketing keeps the audience it is allowed to contact, and the privacy lead spends less time tracing where a list went.
A training webinar where half the audience declined sales contact
This example is illustrative. A customer education team at an HR software company runs a 60-minute live Webcast on Scale for customer administrators, with registration limited to customer domains and a capacity of 150. The form asks two separate questions, one about product news and one about contact from a customer success manager. Of 128 registrants, 61 agree to that contact.
During the session, administrators ask 34 questions about a new permissions feature. Two days later, one attendee emails the team to withdraw her marketing consent, and the change is recorded against her registration before the follow-up rules run.
The education lead reviews the record before anything is sent. Registrants who missed the session receive the replay notice. Audience Intelligence recommends follow-up only from the 61 who agreed to contact, and the attendee who withdrew is excluded. The customer success director approves 14 account-level actions before they sync to the CRM, and the privacy lead confirms that the recording follows the account's retention rule.
What to ask any platform about consent and data requests
- Is consent recorded with the registration, including for contacts imported by CSV?
- Does a later unsubscribe or suppression stop every following message, including replay promotion?
- Are recommendations filtered by consent before anyone sees them, or afterwards?
- Does a person approve each handoff to the CRM, and does the consent context travel with it?
- Can the team respond to access, export and erasure requests without moving data into another tool first?
Our guide to webinar privacy and consent explains the decisions behind each of these questions.
Summary
cRUD Webinar keeps registration disclosure, participant choices and programme activity connected so teams can interpret webinar evidence within its permission context. The platform can record and enforce selected controls, but the customer remains responsible for lawful purpose, accurate notice, retention and rights handling. Consent should govern use rather than decorate the form.