Overview
Remesh Conversations are text-only, 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 so everyone can have a voice-over.
Best Practices
- Set expectations with the participants about how the Remesh Conversation will be run. Let participants know 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.
- Feel free to reach out to your Customer Success Manager to discuss in more detail!