Chat is a parallel conversation, not an interruption

Treat the text channel as a second room running alongside the first, with its own value.

The most common mistake with chat is to treat it as a queue of interruptions to be processed at the end. Chat is not a waiting room for questions. It is a conversation happening at the same time as the spoken one, and it frequently contains the more useful material: the practical caveats, the corrections, the links to what someone already tried, the quiet admission that a point did not land. A session that ignores this channel is running two events and only attending one of them.

Handled well, chat becomes the participation layer that the format otherwise lacks. Attendees answer each other, which is faster and often better than waiting for the speaker. Themes emerge that can redirect the session. People who would never speak aloud will type, which widens participation rather than narrowing it to the confident few. The speaker does not need to read every line, but somebody must, and the room needs to hear back from it periodically so that typing feels like being heard rather than shouting into a void.

It needs light structure to stay useful. Seed it with a specific opening question rather than a vague invitation. Name the moments when chat is the main activity and the moments when it is background. Repeat aloud the questions being answered, so that anyone listening rather than reading is not excluded. And close the loop on anything raised that could not be handled live, either later in the session or in what follows it.