Registration and RSVP records

Cloudpresenter keeps a list of who registered for a webinar and whether they showed up, alongside the details they submitted at signup. A Beam agent reads this list once registration closes or the session ends, and writes the attendee outcome, such as attended, registered but absent, or joined late, into the connected CRM or spreadsheet the team uses for follow-up. If a registrant's details are incomplete or the session data doesn't match what the calendar invite expected, the agent routes the record to a person instead of logging a guess.

Webinar session scheduling

A Cloudpresenter session is set up with a date, time, presenter, and format before it goes live, and any of those details can change before the event happens. A Beam agent reads a scheduling request or a calendar change and updates the session's details to match, such as moving the start time or swapping the presenter, once the change follows a pattern the team has approved. When a request would double book a presenter, move the session outside the standard window, or conflicts with another scheduled session, the agent routes the change to a person before updating anything.

Post-session engagement data

After a webinar ends, Cloudpresenter holds data on how attendees engaged, such as questions asked, poll responses, or how long someone stayed on the call. A Beam agent reads this data once the session closes and writes a summary, such as an engagement score or a list of questions, into the system the sales or marketing team follows up from. If the engagement data is missing for a session, looks incomplete, or a question needs a substantive answer rather than a routed note, the agent flags the session for a person to review.