A practical etiquette guide for speaking to devices near others

Voice Command Etiquette in shared spaces starts with reading the room before the first sentence. A spoken request is audible to everyone nearby whether or not they are part of the task, so the decision to speak is also a decision to include them. Before you start, scan for three things: who can hear you, whether the room is designated quiet, and whether anyone is in a call or a focused block. If any answer suggests interruption, move the task to text or wait. This takes five seconds and prevents the most common complaint about voice tools, which is not accuracy but noise that other people did not choose.
Agree on a simple zone map for your office or home. Mark areas where speaking is welcome, areas where speaking is allowed only for short requests, and areas where silence is the norm. Put the map where people actually look, such as the room booking note or the team page. Zones work better than asking people to judge each moment, because judgment varies with mood and deadline. Review the map when the layout changes or when someone new joins. A map that everyone helped make is easier to follow than a rule delivered from above, and it gives a quiet colleague a legitimate way to point at the boundary without a confrontation.
Choose your moments rather than narrating your whole day. Voice work is most disruptive when it is continuous, and least disruptive when it is short and predictable. Batch your spoken tasks into a few blocks instead of scattering them through the morning. Tell the people around you when a block is starting if they are likely to be affected. Use a brief phrase such as two minutes of dictation rather than a long explanation. Predictability lets colleagues plan around you, and planning is the currency of shared space. The person who announces a short block is easier to accommodate than the person who is silently unpredictable.
Treat the microphone as a visible signal, not a hidden one. If your setup shows when dictation is active, watch for that signal before you speak and make sure it is off when you finish. A stuck microphone is an etiquette problem even when the content is harmless. Add a closing habit to every session, such as a glance at the indicator and a short confirmation that the text landed. Agree with your team on what an active microphone should look like, especially if several people use voice in the same room. Visible signals reduce accidental speech, and they give everyone a shared way to notice a problem without blaming a person.
A command that travels well is short, specific, and free of context only you possess. Say the object, the action, and the destination in that order, then stop. Avoid pronouns and references to what is on your screen, because listeners hear a fragment and may assume it is addressed to them. A well-formed request sounds like a complete instruction even to someone who cannot see your display. Write ten of your common requests and read each aloud to a colleague. Ask them to repeat what they think you asked for. Where their version differs, rewrite the request. This small exercise improves clarity, and a self-contained sentence rarely needs a loud explanation.
Lower the volume by increasing the precision. A person who speaks quietly and clearly is less disruptive than a person who repeats a vague request at full volume. Practice saying the exact token once, slowly, rather than three times quickly. If the result is wrong, correct the specific part instead of restarting the entire sentence at a higher volume. Use a consistent phrase for a repeated task so colleagues learn to tune out the familiar and notice the unusual. Precision is the politest form of brevity in a shared room, and it reduces both the duration and the annoyance of each request.
Keep personal and sensitive content out of shared-space speech. Speak names, figures, and personal details only when the room is appropriate for them. If a task requires that content, move to a private space or switch to typing for that portion. Announce the switch rather than explaining the reason. A simple phrase such as switching to keyboard for this part tells colleagues what is happening without disclosing anything. Agree on this habit as a team so nobody has to make a lonely judgment under pressure. The norm protects everyone, including the person who might otherwise be overheard and not realize it until later.
Use a shared vocabulary for requests that recur in a shared room. If several people ask for the same task, agree on one phrasing and use it consistently. Consistency shortens requests, reduces mishearing, and makes it obvious when a request is outside the norm. Write the shared phrases in the team etiquette sheet and review them monthly. Voiskey supports 100+ languages and translation, so a team with mixed languages should agree on which language each shared phrase uses rather than switching mid-sentence. A shared vocabulary is a courtesy to listeners as much as an aid to the speaker, because it makes the soundscape predictable.
Quiet zones need a clear definition, not a hopeful sign. Specify the hours, the area, and the kinds of speech that are allowed. A quiet zone that permits short requests but not dictation is easier to follow than one that permits nothing and is broken daily. Write the definition in the same place as the zone map and include an example of an acceptable exception, such as a one-word confirmation. Give people a way to signal that a zone is being violated without a confrontation, such as a small card or a shared status marker. A quiet zone with a clear rule and a gentle signal survives; one that relies on goodwill alone erodes within a month.
In shared meetings, decide before the meeting who may speak to a device. A room where three people dictate simultaneously is unusable for everyone. Choose one person to handle spoken requests, or move dictation to a note-taker role with an explicit turn. Announce the arrangement at the start so remote participants are not confused by one-sided speech. If the meeting includes a deaf participant, use the readable text approach deliberately: a hearing speaker talks and the words appear as readable text for the deaf reader, with a screen everyone can see. Agreement at the start prevents the awkward correction in the middle.
Handle calls and recordings with an explicit boundary. Do not dictate near a live call unless the call participants know and agree. Do not assume a muted microphone makes speech invisible, because the people in the room can still hear you. If you need to speak a request during a call, use a text channel or step away. Write this rule into the etiquette sheet in plain language, without exceptions that require a judgment call in the moment. A clear rule is easier to follow than a nuanced one, especially when the room is busy and the pressure to finish quickly is high.
Give quiet colleagues a real option, not a token one. If the only quiet space is a distant room or a booked booth, the quiet zone exists in name only. Identify at least one accessible quiet spot near the work and make sure it is usable during peak hours. Ask the people who need it whether it actually works, and adjust the location or the hours based on their answer. A shared-space policy that ignores the people most affected is a policy that will be quietly abandoned. The test of a quiet zone is whether someone can use it on a normal afternoon without negotiating.
Install the app with the shared-space rules already written. Download Voiskey, install it, and set up the shortcut with the team's zone map open beside you. Test a short request at a normal volume and check that the text appears where you expect. Practice the closing habit: confirm the result, then check the microphone indicator. Voiskey works at the system level, so the same behavior applies in every app and text field, which makes the etiquette easier to teach. A new colleague only has to learn one habit, not a different routine for each program they open during the week.
Download or write a one-page team etiquette sheet and keep it where the team already looks for norms. Include the zone map, the quiet hours, the shared phrases, the meeting arrangement, and the microphone signal. Add a line about what to do when someone forgets, preferably a gentle reminder rather than a complaint. Keep the sheet short enough to read in two minutes. A sheet that requires a meeting to explain is already too long. Ask one person who works quietly to review the draft, because they will notice gaps that the people who speak often will miss, and their edits will make the sheet easier to defend.
Run a short practice session with two or three colleagues in the actual room. Ask one person to speak a request while the others listen and note whether they could tell who the request was for. Repeat with a shared phrase and with a deliberately vague request. Discuss the difference and update the sheet. This exercise reveals whether the phrases travel, which is hard to judge from a written list. Keep the session under thirty minutes and end with one change. A short, concrete rehearsal in the real space is worth more than a long discussion in a meeting room.
Write a newcomer checklist that covers setup and etiquette together. Include the download source, the shortcut, the zone map location, the shared phrases, and the quiet-zone signal. Add a line asking the newcomer to observe one experienced colleague before speaking their first request in a shared area. Observation is a fast way to learn the unwritten rhythm of a room. Review the checklist at the end of the newcomer's first week and note what was missing. A checklist that improves after each new person becomes a living document rather than a formality, and it keeps the etiquette from depending on memory.
Agree on norms in a short meeting with the people who share the space, not in a document written by one person. Start with the problems people actually experience, such as a request that was too long or a microphone left on. Turn each problem into one sentence of guidance. Keep the list to eight items or fewer, because a long list of norms is a list nobody remembers. Assign an owner for the sheet and a date for the next review. A norm that everyone helped write is easier to enforce gently, and enforcement is the part that determines whether the norm survives the first busy week.
Review the norms monthly and treat the review as a real appointment. Ask three questions: what worked, what was ignored, and what needs to change. Pay attention to the items that were ignored rather than defended, because ignored norms often describe a rule that does not fit the work. Change or remove those items instead of repeating them louder. Add at most one new item per month. A slow, steady revision keeps the sheet credible, while a burst of new rules after a single incident makes the whole document feel punitive and easy to dismiss when the next busy week arrives.
Measure the soundscape, not only the compliance. Count the interruptions people mention, the quiet-zone signals used, and the times someone had to leave the room to speak. These numbers are rough, but they show whether the norms are reducing friction or merely moving it. Share the counts at the monthly review without naming individuals. A team that can discuss noise without blaming a person is a team that can improve the norm. If the counts do not move after two months, the problem is probably the layout or the schedule, not the people, and the next change should address the space.
Close each review with one change, one owner, and one date. Write the change in the etiquette sheet and tell the team what to expect. If nothing needs changing, say so and keep the date, because a predictable review is itself a norm. When someone new joins, give them the sheet and the newcomer checklist and invite them to the next review. Participation is the difference between a policy that people follow and a policy that people route around. A shared space improves through small, regular adjustments, and the review is where those adjustments become decisions rather than complaints that circulate for a month and then fade.
Decide before you speak whether the room can hear you, and choose a short, specific request over a long narration. Agree on quiet zones, use consistent phrases so listeners can tune out the familiar, and check that dictation is off when you finish. Voiskey places text where you are typing in any app, so one habit covers every program your team uses.
Yes. A hearing speaker can talk and the words appear as readable text for a deaf reader, with filler words and false starts removed. Agree in advance who speaks to the device, place the text where everyone can see it, and pause at natural boundaries so the reader can follow the discussion.
The zone map, quiet hours, shared phrases, the meeting arrangement, the microphone signal, and what to do when someone forgets. Keep it under two minutes of reading, review it monthly, and let quiet colleagues review the draft so the rules reflect the people most affected by noise.
Meet monthly, ask what worked, what was ignored, and what needs to change, and revise one item at a time. Count interruptions and quiet-zone signals without naming individuals, and change the layout or schedule if the counts do not move after two months.

Download Voiskey for Mac and Windows and agree on shared-space norms first.
Use it across macOS, Windows, iOS, and Android