Remote Meetings with Live Captions

Set up one shared text window so every remote attendee can read the call.

Voiskey Voiskey Team
Real-Time CaptionsAccessible CommunicationRemote Meetings Live

Choose the Caption Surface and Seat

Remote Meetings with Live captions work best when the team picks one shared text window before the call begins. Use the notes app or message window your group already opens, create a fresh document, and leave the cursor at the insertion point. Decide who will produce the text, usually a hearing facilitator who speaks clearly into that window, and confirm that the host can share it with every attendee. Ask the deaf reader where they will sit and whether they prefer the window full screen or beside the speaker video. Test the view from their seat rather than from the producer's. Write the arrangement in the meeting invite so late joiners see the same plan.

In a remote call, the host shares the caption window rather than the whole desktop, so the reader sees only the text and the speaker. Pin the shared window, hide the participant thumbnails that cover lines, and turn off notification banners before anyone joins. Ask the reader to set their own zoom level; a size that works on the producer's monitor may be too small on a laptop. Keep the window on the reader's main display and move unrelated windows to a second screen. If the reader joins on a phone, confirm that the shared text is legible there and that they can scroll without losing the live line. Recheck the view after the first speaker starts.

Decide who produces text and who types replies. A common arrangement is a hearing facilitator who speaks summary sentences into the window while the deaf participant reads and types questions back. The host then reads each typed question aloud before answering, which keeps the spoken record complete. Agree on who clears the window between agenda items and who reposts a line that scrolled away. If two people produce text, give each a clear domain, such as one for the main discussion and one for action items, so lines do not duplicate. Write these roles into the invite. When the producer must leave, name a substitute in advance and let them run one rehearsal.

Run a two-minute rehearsal before the real conversation. The producer speaks one sentence that contains a person's name and a number, then watches the reader confirm the words on screen. If the reader hesitates, change one variable at a time: text size first, then window width, then screen brightness. Ask the reader to repeat the sentence back in their own words, which tests understanding rather than simple visibility. Note the working settings on a card: app, window size, reader's seat, and preferred pace. Repeat the same rehearsal with any substitute producer. End by naming the first agenda item and the person who will speak first, so the meeting starts with a known handoff rather than a scramble.

Brief the Room Before the Call

Send a short briefing note with the invitation. Explain that the meeting will use a shared text window, name the producer, and describe how attendees should take turns. Ask everyone to join two minutes early for a sound and view check. Include the agenda with numbered items so the reader can predict the reading load and the producer can prepare headings. Tell participants to use the same window for questions instead of side channels, because scattered questions fragment the text. Keep the note to one screen and repeat the key points at the start of the call. People read invitations quickly, so a verbal recap is not redundant; it is the version they will actually follow.

Open the call with a thirty-second etiquette briefing. Ask each speaker to say their name before making a point, to speak one at a time, and to pause briefly after a question so the reader can finish the line. Explain that side conversations are invisible in the text, so side comments should be typed into the window or saved for later. Demonstrate one good turn: name, short sentence, pause. Then ask a volunteer to repeat the pattern. Keep the tone practical rather than scolding; most hearing participants have never worked with a live caption window and will follow a clear model. Post the same rules as the first lines of the shared document.

Assign four roles explicitly. The host runs the agenda and calls on speakers. The producer speaks the text into the shared window. A backup producer watches for missed lines and takes over if the main producer is called away. A timekeeper warns when an item is running long, because rushed items produce dense text that is hard to read. Write the names beside each role in the shared document. If the team is small, one person can hold two roles, but say which two. The goal is not bureaucracy; it is a clear answer to the question of who keeps the text accurate when the conversation speeds up.

Publish a timed agenda in the same window. Use numbered items, one line each, and add a short marker such as a blank line or a heading when the topic changes. Put the hardest or most detailed item early, while everyone is fresh and the producer is not yet tired. Reserve the last ten minutes for decisions and read-backs. Give each item an owner and a target time, and ask the timekeeper to announce the halfway point. A predictable structure reduces the chance that a long digression buries a decision in the middle of the text. The agenda is also the outline the reader will use afterward to find what was agreed.

Run Turns and Crosstalk

Use a visible handoff for every turn. Ask participants to raise a hand or type a single word in the window, and let the host name the next speaker. The speaker then says their name and the point in one short sentence. This sounds formal, but it prevents the most common caption failure: two voices arriving as one tangled line. When someone forgets, the host repeats the name and invites the point again rather than letting the text absorb the overlap. Keep a simple order, such as around the room or by agenda item, so the reader can anticipate who speaks next. Predictable turns are easier to read than clever ones.

Crosstalk needs an owner, not a rescue. When two people speak at once, the producer should stop rather than guess, and the host should pause the discussion, restate the overlapping point in one sentence, and ask one person to repeat it. Write the restatement in the window and mark it as a summary so the reader knows it is not a direct quote. If the point was a quick agreement, record the agreement rather than the exchange. If it was a disagreement, record both positions in order. Trying to capture every word of a collision produces text that is both incomplete and misleading, which is worse than a short, honest pause.

Pace the output in short chunks. Ask speakers to lead with the headline, add one supporting sentence, then stop. A pause after names, numbers, and unfamiliar terms gives the reader time to finish the line before the next one arrives. The producer can also insert a heading when the subject changes, which acts as a visual rest. Watch the reader rather than the screen: scrolling back, leaning in, or a blank expression are signals to slow the next few turns. Voiskey adapts punctuation and formatting to the task, so cleanly spoken sentences tend to arrive with readable breaks. Natural speech at a steady rate beats an exaggerated, halting delivery.

Handle questions through a single queue. Ask attendees to type questions into the shared window and let the host read each one aloud before answering. This gives the reader the question and the answer in the same linear text, instead of a spoken question that appears only after someone repeats it. Number the questions so the host can refer back without rereading the whole line. If a question is too long, the host summarizes it in one sentence and says so. When an answer spawns a follow-up, add it under the same number. At the end, read the list of unanswered questions and assign each one an owner and a date.

Repair Misreads and Keep Records

Even a careful setup produces misreads. Names, acronyms, and numbers are the usual suspects. Repair in three steps: say the correct word alone, use it in a short sentence, then continue from the next idea without replaying the paragraph. Voiskey removes filler words, stutters, false starts, and self-corrections, so a clean restatement usually lands better than a long apology. If a word fails twice, switch methods: type it once in the window or describe the thing before naming it. Keep your tone even. A correction is routine maintenance, not a failure of the reader, the producer, or the app. The conversation should continue as if the repair were part of the plan.

Know when to stop speaking and start typing. If the reader is far behind, if the room has become noisy, or if the topic turns into a list of spellings, hand the conversation to the keyboard for a moment. Type the key sentence yourself, let the reader catch up, then resume speaking. This is a change of tool for a change of task, not a retreat. The producer may use Voiskey for the spoken portions and type the difficult spellings by hand. Then say one sentence that connects the typed note to the next spoken point, so the reader knows where the conversation is going rather than wondering whether the topic changed.

Keep a running decisions list inside the same window. After each agenda item, the producer adds three lines: the decision, the owner, and the date. The reader confirms the lines before the group moves on. This small ritual catches the most expensive caption error, which is a decision that sounds settled but was never written in a checkable form. Use plain verbs: approve, reject, defer, investigate. Avoid vague phrases such as circle back, which hide whether anything was decided. If the group cannot state the decision in one line, the item is not finished. Mark it open and give it a place on the next agenda.

Make the tooling easy to repeat. Voiskey runs at the system level: the producer presses a shortcut, speaks, and text appears at the insertion point in the shared window, with no copy and paste between apps. That means the same habit works whether the team meets in a notes document, a message window, or a whiteboard tool. When a new producer joins, have them download Voiskey, run the two-minute rehearsal with the reader, and keep the same shortcut. Do not rely on memory for settings; write the app, window size, and pace on the setup card. A repeatable setup survives vacations, room changes, and new team members.

Close the Loop After the Meeting

Reserve the last five minutes for a read-back. The producer reads the decisions list aloud, one line at a time, and the reader confirms or corrects each entry. The host then reads the open questions and assigns an owner and a date to each. Anyone who missed part of the meeting can follow the same lines without asking for a summary. Keep the read-back short and factual; this is not the place for new discussion. If a correction appears, fix the line immediately and note the change so the record stays trustworthy. End by stating when the notes will be shared and where they will live.

Turn the shared text into the meeting record. Save or copy the window into the team's usual notes location, keeping the headings and the decisions list intact. Move action items into the task list your team already uses, with the owner and date from the read-back. Send the link to every attendee, including those who joined late or read the text instead of listening. Do not rewrite the text into polished prose; the value is in the traceable lines, not the style. If the meeting produced a document or a draft, attach it beside the notes. A record that someone can scan in two minutes is more useful than a long narrative nobody opens.

Review the session while it is fresh. Ask the reader which passages were hardest to follow and write down the answer. Note the names and terms that were misread, then add them to the vocabulary the producer uses. Voiskey learns names, jargon, acronyms, and spelling preferences, so repeated corrections should become rarer over time. Check whether the window size, seat, or pace drifted during the call. If a repair pattern worked, keep it; if it caused a delay, replace it. Store these notes with the setup card. Over a few weeks, the notes become a short list of team habits that make captions reliable for this team.

Prepare the next person to run the setup. Write a one-page guide that names the app, the window size, the seating position, and the repair phrases that work. Include the reader's preferences and any words that need special handling. When a colleague takes over, have them download Voiskey, walk through the guide once, and run a short test with the reader before a real meeting. Give the reader a way to flag a problem without stopping the call, such as a typed repeat or a raised hand. Review the guide every quarter and remove steps that no longer help. A written setup can survive a vacation, a room change, or a new team member.

FAQ s

Voiskey is an AI voice typing app for computers. A hearing facilitator presses a shortcut and speaks, and the words appear as text at the insertion point in the shared window. The deaf reader follows that text on screen. It also removes filler words and false starts, so each line is easier to scan during a fast call.

It cleans up what one speaker says: filler words, stutters, false starts, self-corrections, and grammar slips. It cannot separate two people who talk at the same time, so the host should still pause the discussion, restate the overlapping point, and ask one person to repeat it. Clean input from one voice at a time produces the most readable line.

Yes. Voiskey works at the system level, so you press a shortcut, speak, and text appears at the insertion point in any app or text field. The team can keep the notes document or message window it already shares rather than learning a separate tool. The producer's shortcut and window habits stay the same from one call to the next.

Voiskey learns names, jargon, acronyms, and spelling preferences. When a producer corrects a name once, later mentions are more likely to arrive as intended. For unusual names, the repair habit still helps: say the correct term alone, use it in a short sentence, then continue. Add recurring names to the team's shared glossary so substitutes start with the same vocabulary.

Say less. Get more
Say less. Get more
Say less. Get more
Say less. Get more
VoiskeyVoiskey

Your voice, amplified.

Download Voiskey for Mac and Windows to turn every spoken turn into readable meeting text.

Use it across macOS, Windows, iOS, and Android

Use it across