Transcript:

We will next look at your event from your guest’s perspective. When a guest comes to your landing page, they’ll be asked to sign in for the event. Speakers will have their own join button.

Anyone without an existing remo account will be asked to create a unique login of an email, password, and their name. This is for security and to help you track your event metrics.

The system will then forward your guests to a mini tutorial, showing them the basics about how to move tables and how to turn on/off their microphone and camera. They can also set up their profile card here before they enter the event.

The last step is the gear test where their microphone, camera, speaker, browsers, and systems will be checked for compatibility. This tool currently does not check for firewall or vpn issues.

Once redirected into your event they will also be able to go to the upper right hand corner and update their profile if they did not do so already.

If you notice the guest control bar at the bottom looks a little different than yours. Guests have the camera, the microphone, the chat, the share screen, and the whiteboard features. However, they also have a quit event button.

This quit event button is important for two reasons:

Number 1, if you encourage your guests to use the quit event button, you can redirect them (on certain remo subscriptions) to a unique url that you set up inside your master account settings tab. You can redirect them to your webpage or an exit survey for feedback on your event.

Number 2, using quit event will also help you capture more accurate data about when your guests have entered and left your event. It will also prevent ghost avatars that may occur if a guest closes the browser instead of using quit event.