Events record who said yes. Webinars record who turned up.
They look like one feature and they hold two different things. An event carries intentions, and the product will not turn those into an attendance figure it did not measure.
Both need Command or HQ. The calendar file is the one part that is on every plan.
EventWard handover briefing
- Going44
- Maybe12
- Declined7
Attended not recorded
WebinarInfection control update
- Registered68
- Joined51
Joining is written against the person
The missing figure is deliberate. There is no attended flag on an event, so there is no number to show and the panel shows none.
Five moments, and none of them configurable.
The reminders, the processing and the recap all happen on a schedule set in code. That is a limit, and it is also the reason nobody has to remember to do any of it.
- 24 hours beforeThe first reminderAn email to everyone who registered.Email
- 1 hour beforeThe second reminderThe same list again. Two is the whole schedule.Email
- The sessionJoining is recordedWritten against the person. The one place the product records turning up.Recorded
- AfterwardsMux transcodes itThe replay shows a processing state rather than a dead player.Processing
- Within the hourThe recap goes outA link to the replay, sent by an hourly job rather than instantly.Email
Three people, and what each of them gets.
- Dr Tessa PalmerHead of clinical governance
Creates the ward briefing as an event and the infection-control update as a webinar, and can see who registered for the second one and who joined it.
Comms Admin - Simon NaylorRegistered nurse
Says Going to the briefing, downloads it into his own calendar, registers for the webinar and gets the two reminders before it.
- Amelia DawsonRegistered nurse
Was on shift and missed it. The recap email arrives within the hour with a link to the replay, which is the whole of catching up.
Five things, and the plan each one needs.
- Events with RSVP
A title, a description, a location, a start and an end, and an optional Space. Members answer Going, Maybe or Declined.
Command and HQ - The calendar file
Any event downloads as a standard .ics file and imports into Google Calendar, Apple Calendar or Outlook.
Every plan - Registration and reminders
Members register for a webinar in the app and get an email about a day before and again about an hour before it starts.
Command and HQ - The replay, and the recap that links to it
The session is recorded, and once Mux has finished processing it the recording is available to replay in the app. Everyone who registered gets an email with the link, so missing it live costs one email rather than a conversation.
Command and HQ - Upload and schedule
An admin can upload a recording and schedule it to air as a premiere, an evergreen session, or on demand.
Command and HQ
What a date in the calendar will not do.
Every line here traces to something in the code, including the parts it would be easier to leave out.
- An RSVP is not attendance
An event records that somebody answered Going. Nothing records whether they turned up, and no figure is produced afterwards about who did. If you need to know who was in the room, that is a webinar.
- An event sends no reminder
Creating an event does not schedule anything. It appears in the list and in the calendar file somebody downloads, and after that the product says nothing more about it.
- The calendar file is a download, not a sync
Changing the time here does not update an entry somebody already imported, and there is no two-way connection to any calendar account. Moving an event means telling people it moved.
- Reminder times are fixed
Roughly a day before, and roughly an hour before. An organiser cannot change the schedule, add a third, or send one on demand.
- The recap carries a link, not a summary
It contains the replay link and nothing generated: no summary, no chapters, no transcript. It also goes out on an hourly job rather than the moment the session ends.
- Registration is for people already in your workspace
A webinar is for signed-in members. There is no public registration page and no way to invite somebody who does not have an account.
What sits either side of a date.
- The recordAn acknowledgement asks somebody to confirm they have read something. An RSVP asks for an intention, and the two are different records.
- Spaces, chat and peopleAn event can belong to a Space, which means the Space decides who sees it in the first place.
- AnnouncementsA date in a calendar and a message that has to be read before a date are different jobs, and the second one is an announcement.
Run one webinar and see exactly what it records.
Kayden Connect is invitation-only before launch. Tell us about your workforce and we will show you the demonstration workspace.
Request early access- Command and HQEvents and webinars both.
- RecordedWho registered, and who joined.
- Not recordedWhether somebody who said Going turned up.