Overview
Remesh Conversations are predominantly text and there is no inherent audio component when the moderator interacts with the participants. Because of this, some moderators are interested in setting up a conference bridge for participants to join to voice over or to host their Remesh Conversation in person. We recommend reviewing the following best practices if you're considering this approach.
Included in this Article
Remesh Alongside A Conference Line
- Set expectations with the participants about how the Remesh Conversation will be run. Let participants know while recruiting that they will be accessing a conference line along with the Remesh conversation in their browser. While they may be listening to the conference bridge for additional context, they'll be typing and submitting their answers on the Remesh platform.
- Control the audio so that you can mute all participants and only have one or two people with the ability to speak on the conference line. If participants are able to interject, things can get side-tracked quickly.
- If a chat feature is enabled, you may want to designate someone to monitor the chat as the conversation is taking place to answer questions or troubleshoot technology issues.
- Make sure what is said on the conference bridge is consistent with what is said/asked on Remesh. Try to replicate, as best you can, what you say verbally with "Speaks" on the Remesh platform. You want to make sure the content is as consistent as possible in case there are any participants on the Remesh Conversation but not on the conference bridge.
- We recommend conducting a test session with your conference line and a Remesh conversation, to ensure there is not a lag in the conference software.
Remesh In Person
- Consider whether the participants will all be in the same room or whether some will be dialed in remotely. If you need to set up a conference bridge for remote participants, make sure you replicate everything said verbally with "Speaks" in the Remesh conversation. You want to try and make sure participants don't lose any content or context simply because they are not in the same room, and it can sometimes be tough to hear on a conference call.
- Share the participant link on a screen at the front of the room and make sure participants know they are able to join the Remesh conversation from a mobile device
- Make sure the moderator is someone who is confident and able to roll with the flow of the conversation. Since participants will be in the same room and viewing responses come through live, the moderator should be mentally prepared for any answers that are critical or might be "awkward" to address in front of a live audience.
- It also might make sense to tag team and divide the moderator and commentator duties, so that one person can focus only on asking questions on Remesh and the other person can do the crowd control and verbal narrating.
- The silence when people are answering questions can feel uncomfortable, so you might want to consider music or have the moderator or commentator up front giving direction and narrating as you go.
- Make sure the question durations are ~15-30 seconds longer to account for participants typing primarily on mobile device. As a reminder, our typical recommendation is 30 seconds for Polls and 2 minutes for Asks, but this should be extended slightly. You can also play this by ear and be flexible as the group becomes increasingly comfortable with the platform.
- If everyone will be on a WiFi network (as opposed to mobile), be sure to test the network in advance to make sure Remesh isn't blocked. Here are the steps to ensure that Remesh can be run successfully.