Webinars
Webinars runs the webinars and meetups Contacts attend, online or in person: invitations, registrations, attendance and follow-up.
Webinars runs the live sessions and meetups Contacts attend, online or in person: invitations, registrations, attendance and follow-up. Each attendee’s questions land in CRM, and each no-show gets the recording.
Summary
| Part | This System |
|---|---|
| Group | Marketing |
| Status | Beta: it works, and its Verbs may still change |
| Shelf | Front: offered from a Startup’s first days |
You can ask:
- “Host a webinar next Thursday”
- “Invite our customers to the meetup”
- “Who registered but did not show up?”
- “Follow up with everyone who attended”
What you get
| Part | This System |
|---|---|
| Starts | Opt-in: it wakes with the Product Templates that need it. |
| Built from | Email delivery, Workflows, Database, Payment rails |
Nouns it owns
| Noun | Definition |
|---|---|
| Gathering | A Gathering is a scheduled session many people attend at once, such as a webinar, a workshop, or a launch call, hosted by a Startup. |
| Registration | A Registration is one person’s place at a Gathering: invited, requested, or waitlisted, then registered, then attended or no-show. |
Verbs
Events
| Direction | Event | How |
|---|---|---|
| Emits | Meeting.booked | By Meeting.book |
| Emits | Gathering.registered | By Gathering.register |
| Emits | Registration.approved | By Registration.approve |
| Emits | Registration.admitted | By Registration.admit |
| Emits | Registration.attended | By Registration.attend |
| Emits | Registration.missed | Raised when a date passes |
States
The lifecycle of a Registration:
| State | Meaning | Moves to |
|---|---|---|
invited (first) | Offered a place, by the host’s invitation or the Gathering’s public Page, and not yet taken. | registered by Gathering.register; waitlisted by Gathering.register; requested by Gathering.register |
requested | Asked for a place at a Gathering whose host approves each one. | registered by Registration.approve; waitlisted by Registration.approve |
waitlisted | Next in line for a place, in the order they asked. | registered by Registration.admit |
registered | Holds a place; the reminders and the join link go to the Contact. | attended by Registration.attend; noShow on Registration.missed |
attended | Joined the Gathering. | None: it ends here. |
noShow | Held a place and never joined before the Gathering ended. | None: it ends here. |
Who operates it
| Part | This System |
|---|---|
| Accountable | Marketing Lead |
| Team | Marketing Team |
| Seat | A role agent holds it until a Human is seated. |
| Autonomy | supervised |
| Also calls its Verbs | Sales Engineer |
Approvals and limits
| Verb | Rule | Detail |
|---|---|---|
| Gathering.register | A person says yes first | None. |
Processes that use it
| Process | How it uses it |
|---|---|
| Inbound sales | A step calls Meeting.book |
Rail underneath
None.
Views and dashboards
| View | Shows | Metrics |
|---|---|---|
| The Marketing Lead’s view | The Metrics its accountable Role answers for. | Play-sourced Customers, Fully loaded acquisition cost, Organic share, Referral share, Spam rate, Play payback |
Access
What each Access level may call here.
| Access level | May call |
|---|---|
owner | Every Verb (15) |
admin | Every Verb (15) |
member | Every Verb (15) |
viewer | Read only (4 of 15) |
Import and export
None.
Fees and pricing
None.
Availability and limits
| Part | This System |
|---|---|
| Status | Beta: it works, and its Verbs may still change |
Compliance notes
Controls it carries:
Related Systems
Example
A b2d Headless SaaS for e-signatures hosts a monthly 30-minute session on signing flows. Webinars invites 2,000 Contacts, books 140 seats as Meetings, and sends the recording to the 80 who missed it. Three attendees who asked about volume pricing become Deals.