Skip to content
All guides

Business tools

Give Text-First Participants a Discord Channel That Outlasts the Zoom Chat

Some participants contribute mostly in writing. Zoom's chat can be saved, but only partly and by someone. Decide when a persistent Discord text lane, run by a chat steward account, is worth adding.

Contents

Text-first participants and the meeting chat

In most remote workshops a few participants contribute mainly in writing: people on a noisy connection, people who think better in text, people who are not comfortable speaking in a large group. The meeting chat is their channel, and what happens to it after the session decides whether their questions get answered.

Facilitators tend to treat the chat as a side window. For these participants it is the main door, so its record deserves the same planning as the slides. Ask in the invitation whether people prefer to contribute in writing; the answer tells you how many participants depend on the chat and whether a dedicated steward is needed at all.

What saving a Zoom chat keeps

Zoom documents three ways to keep in-meeting chat. A local save keeps the chats the person saving could see, including messages sent directly to them. A cloud save keeps only chats sent to everyone, and only messages sent while the meeting was being cloud recorded. Auto-saving works only for the host, so the host has to be in the meeting for a local transcript to be saved. If the setting allowing users to save chats is cleared, nobody can save it, the host included.

In practice, a text-first participant's question can easily miss the record: sent privately to a co-facilitator, sent before recording started, or sent while the host had stepped out.

When the meeting chat is enough

For a single session where the host stays in the meeting, saves the chat and answers open questions by email afterwards, the Zoom chat alone is adequate. Adding another tool for a one-off event mostly adds a sign-in for participants and a second place to watch.

The same holds for short series where every question is answered live. The case for a second lane starts when questions outlive the call.

When to open a Discord text lane

A persistent lane earns its place when questions keep coming between sessions, when answers should be visible to the whole group later, or when text-first participants should not depend on whether someone saved a file. A Discord text channel keeps that conversation in one place across the whole course.

Discord's slowmode helps such a channel stay readable: it adds a per-user cooldown between messages, from five seconds to six hours, while everyone can still read and react. Facilitators can be given a role with the permission that exempts them from slowmode, so their answers are never held back.

Keep the lane small: one channel for questions and one for resources, both readable by every participant. A lane split into many channels recreates the original problem, because questions again end up in places nobody is watching.

A three-session course, worked through

Hypothetical: a data-literacy course runs three evening sessions for 25 participants, several of whom write rather than speak. During each session, a chat steward, a separate role from the facilitator, copies every question from the Zoom chat into a questions channel on the course's Discord server and marks it answered or open. The channel has a short slowmode, and the facilitators' role is exempt from it.

Between sessions participants add questions directly, and the facilitator answers in threads before the next evening. The steward still saves the Zoom chat locally each night, but the Discord channel is the record people return to. Participants without Discord keep using the meeting chat, because the steward carries their questions across.

At the end of the course the questions channel stays readable for a period announced in the first session. After that, the facilitators change the channel permissions so nobody can post, and the answered questions remain as a reference for anyone who took part.

Accounts the steward setup needs

The setup needs a Zoom host account where chat saving is allowed, and a Discord account for the steward that is used only for this server, so the steward's personal servers and messages stay out of the course. Discord permissions are set per role, and channel permissions override server permissions, so the questions channel can be readable by every participant while only facilitators manage it.

Discord's terms say accounts are not to be sold, lent or transferred, and Zoom's terms keep host rights with one individual, so each role holder signs in with their own account and the steward account stays with the steward.

Comparing steward and host accounts on rStock

rStock is an independent marketplace that has no affiliation with Zoom or Discord. For the steward account, the listing details to compare are whether the email and phone can be moved to your control and whether any servers come with the account, since a clean account is easier to dedicate to one course. For the host, check the plan the Zoom listing names and whether it is a standalone account.

If a listing leaves those points open, choose a better-documented one, because rStock offers no pre-purchase messaging with stores. You pay from your rStock balance, and the delivery record on your order page opens the window shown there for checking the login. Then compare the Discord and Zoom accounts your text lane needs.

Frequently asked questions: Give Text-First Participants a Discord Channel That Outlasts the Zoom Chat

Keep reading