update webinar handbook with ON24 steps for simulated live 2 nuances
Why is this change being made?
💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.Please add the details saying why, not just what in this section. Example:
We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.
- The purpose of this MR is to update webinar handbook with ON24 steps for simulated live 2 nuances.
- Upon reviewing, I also noticed inconsistencies with the naming switching from
On24
andON24
. Updated that to the correct name of the tool and to maintain consistency across the page. -
Slack thread - https://gitlab.slack.com/archives/C041F6L748M/p1718035345564969 - Issue - https://gitlab.com/gitlab-com/marketing/demand-generation/campaigns/-/issues/5103
- ON24 Support Case 288638:
- poll Qs are not available as a functionality in either format; we tested in live and and simu-live formats as well as in two TEST events
- opened a Support Ticket (#288638) with ON24 to confirm as it’s not answered in FAQs
- ON24 response:
There isn’t any way to do exactly what you’re asking, but there are some options to consider. It’s not possible to have a poll available before the Simulive recording starts or after the event ends. Possible options would be: Since your event is a Sim2Live, you could create a poll question during set up, then hide it on the storyboard so it won’t be part of the recorded event. Then when it rolls over to live, your presenters could unhide and push the poll. Another option would be to create a Survey and set it to pop up when the event ends. Instructions for the Survey tool can be found here: https://support.on24.com/hc/en-us/articles/21420749567259-Take-Survey-Tool
Author and Reviewer Checklist
Please verify the check list and ensure to tick them off before the MR is merged.
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
For transparency, share this MR with the audience that will be impacted. -
Team: For changes that affect your direct team, share in your group Slack channel -
Department: If the update affects your department, share the MR in your department Slack channel -
Division: If the update affects your division, share the MR in your division Slack channel -
Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR - For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter
-
Commits
- Update file _index.md