...
About this doc (Delete this table when the doc is finalized.)
...
Reader
...
Technical Support
...
Reader goal
...
Know what to check for in a Greenroom
...
Contributors
...
...
JUNO version
...
N/A
...
Reviewers (check the box when you’re done!)
...
...
Notes for reviewers
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Instructions
This document can be used by the individual to keep track of what they are looking for in Greenrooms. Additionally, CSMs can use this as a starting point to create client specific checklists if their client requires additional steps or special attention from the TS group.
Some people like to mentally use the checklist. But if you want to actually check the boxes, you can! Please create your own copy of this page first. (See instructions below.) Note that any updates made to this original checklist won’t be reflected in your copy.
| Expand | ||
|---|---|---|
| ||
|
Early Check
- Join 30 minutes before “live”
- Introduce yourself in the Mod
- Test Chat
- Check for Polls if applicable
- Check for Resources if applicable
- Click “Edit”
- Check for Presenters being attached
- Check for pre-roll and note the length
- If length > session time, ask a CSM to verify that you can extend
- Return to page
- Put yourself on screen so they know somebody is there
- Let the Internal slack channel know that you are in the GR
- If no speakers are there by the 15 minute mark, let the CSM know
- Depending on the client, you may also alert the Gameday channel
With Speakers
...
The JUNO support team uses this process to prepare a session before it starts. Other support staff are welcome to use it as an example.
| Info |
|---|
Some details should be adapted to your team’s communication process. For example, the checklist says, “tag the Client Success Manager in the internal channel.” Internal channels are only accessible by the JUNO team. Instead, you should follow the escalation process outlined by your team. |
Escalate issues
Our issue escalation procedures are documented here: Gameday issue escalation process
...
1. Join the session
Join 30 minutes before “live” unless noted otherwise by the CSM (Client Success Manager). 30 minutes is the default.
Introduce yourself in the Mod chat. For example, "Hello everyone I am
namewithJUNOand will be available throughout the session to help with any issues or questions you may have!”
2. Check the content
Test Chat by sending a simple message. Then delete it so that attendees won’t see it.
Check for Polls by selecting Choose a question to send. If there are any polls in the list, make sure you can send them. If polls are missing, add them in the session editor.
Check for Resources by scrolling down the page. If there are any, select them to make sure they download correctly.
Select Edit to check more content.
Check that the Presenters section matches what is on the Run of Show. If it does not, tag the lead CSM in the internal channel to verify who should be a presenter.
Check for Pre-roll and note the length. Learn how to check the pre-roll.
If the length is greater than the session time, tag the lead CSM in the internal channel to verify that you can extend the session.
Select Return to page to leave the editor.
3. Get ready for speakers
Put yourself on screen in a presentable and professional manner, so that speakers know somebody is there. You can use a profile image in place of a video.
Let the Internal Slack channel know that you are in the greenroom.
If no speakers arrive by the 15-minute mark, tag the CSM in the internal channel and let them know. For example, “15 minutes left in the greenroom for
session linkand I have not seen missing speaker.”You may also optionally alert the Gameday channel.
4. Check video and audio with speakers
Have speakers test their Microphone by talking with you. To troubleshoot see People have trouble hearing me.
Have speakers test their Camera by turning it on. To troubleshoot see My camera doesn't work.
Ask if they’ll be sharing their screen, then check Screenshare. If there are issues, see Screen sharing in a multiple monitor environment or Screen sharing in a single monitor environment
If applicable, make sure they know how to share their screen with sound
...
.
If they need to leave the screen
...
, show them how
...
: More
...
> Leave
...
> Continue Watching
...
5. Review session features with speakers
Walk through these features if they are applicable to the session:
Breakouts: Walk through how it works.Send attendees to breakout rooms
Raise Hand: Walk through how it works from both perspectives.
Moderator perspective: Live sessions how-to for speakers and moderators
Attendee perspective: Ask to speak in a session
Q&A: Walk through how it works. Make sure they understand their different options and how to respond by text. Let the speaker and their moderator decide how they want to handle questions.
Poll: Have the speaker send a poll. Then delete it so that attendees won’t see it. (It can be resent again at the right time.)
Mod chat: Verify that they see the Mod chat, and tell them that’s where they can reach you. Tell them it’s a private chat that’s only available to speakers, presenters, and site admins. Attendees can’t see it.
Pre-roll: Walk through what the transition will look like. “Abrupt” is a good word
...
to describe the cutoff. Transition from pre-roll to live: Support guide
6. Leave the screen
Announce that you’re leaving the screen now. Remind everyone that you’ll be there and available in
...
Escalation
Our Escalation procedures are documented here:
...
the Mod chat.
Leave the session: More > Leave > Continue Watching
...
Helpful links
Common error messages
Top troubleshooting tips
Screen sharing in a single monitor environment
Edit sessions