A quiet protocol for issuing agent commands during live meetings.

Dictating Commands to an agent during a meeting only works when the room understands why your voice is active and what you are trying to accomplish. Start by listing the actions you would normally perform silently: writing action items, opening a reference document, saving a decision note, or queuing a follow-up. Sort them into low-risk actions that can be corrected in seconds and high-risk actions that affect other people or shared records. Keep only the low-risk list for live use. Tell the participants at the start that you will speak short commands to capture tasks, and that they should keep talking if a command fails. A clear protocol prevents the routine from feeling like a private side channel.
Choose commands that produce a visible result you can check without leaving the conversation. Opening a document, inserting a dated action item, or adding a name to a follow-up list are good candidates because a glance confirms the outcome. Avoid commands that require a chain of clarifications or that change something others depend on. If a task needs approval or a judgment call, capture it as a note for after the meeting instead of executing it live. Write the boundary in one sentence on your command sheet. The boundary is the difference between a useful assistant and a distraction the room has to manage.
Decide how you will signal that a spoken phrase is a command rather than a comment. A short lead-in such as note this or a consistent hand movement gives listeners a cue and gives you a clean start. Use the same cue every time, because inconsistency makes people stop and listen to every sentence. Agree with the meeting owner before the first use, especially in external calls. If the owner prefers no commands, capture notes manually and move the routine to a later session. The protocol belongs to the meeting, not only to you, and a small objection handled early prevents a larger interruption later.
Set a limit on how many commands you will issue in one meeting. Three to five is usually enough to capture the important items without turning the conversation into a series of voice actions. Reserve commands for moments when waiting until later would lose the exact phrasing of a commitment. Everything else can go in a rough note and be cleaned up afterward. Write the limit on the sheet and count as you go. Write the count next to the limit so the rule is visible during the call. A limit forces you to choose the highest-value moments and keeps the room comfortable with the occasional short phrase.
Build a command sheet the night before the meeting, not during the first minute. List eight phrases at most, each with one verb, one object, and the exact name of the document or item involved. Add the expected result beside each phrase and the manual fallback underneath. Include the names of the people whose action items you expect to capture, spelled as they appear in the invitation. Read the sheet aloud once to catch phrases that are hard to say quickly. Keep the sheet to one page so you can scan it without losing the thread. A prepared sheet turns a risky live experiment into a short rehearsal you can repeat under pressure.
Test two or three phrases in the same app and document you will use during the call. Confirm that the insertion point is where you expect, that names appear correctly, and that the result is visible without scrolling. If a phrase needs a clarification, rewrite it on the sheet rather than planning to explain it live. Record the version of the sheet and the date of the test. Keep the old version until the new one passes. A command that has not been tested in the real document is a guess, and a meeting is a poor place to discover a missing step.
Prepare the document before the call with a small structure: a section for decisions, a section for action items, and a section for follow-ups. Put the cursor at the first insertion point and leave the document open beside the meeting window. Leave the meeting window sized so the notes area stays visible. If you plan to open a reference file, note its full name on the sheet so you do not have to search mid-sentence. Keep the sheet visible on a second surface or printed beside the keyboard. Preparation removes the small decisions that would otherwise pull your attention away from the discussion.
Share the plan with one colleague who will be in the same meeting. Ask them to watch for two things: whether the commands disrupt the flow and whether the captured notes match what was decided. Give them a copy of the sheet and agree on a subtle signal if you should pause the routine. Agree before the call on how the signal will be given without interrupting anyone. After the call, compare their observations with your own. A second pair of eyes catches the social cost that you are least able to notice while speaking. The colleague also becomes the first reviewer when you revise the sheet.
Wait for a natural pause before you speak a command. The end of a sentence, a shift between agenda items, or the moment after a decision is recorded are good openings. Avoid talking over someone to capture a phrase; the note can wait two seconds and the relationship cannot be repaired as easily. Keep your voice at the level you would use for a short aside, and return your attention to the speaker immediately. If no pause arrives, write a rough note manually and use the command after the meeting. The goal is to support the conversation, not to demonstrate the routine.
Say one action per phrase and stop. A command that includes a name, a task, and a due date in one breath is harder to follow and harder to correct. Put the name first, then the action, then the date if needed. If the name is long, pause after it so the next part is not clipped. If the agent asks a clarifying question, answer with the smallest detail and repeat the original verb. Do not add a second task while the first is unresolved. Short, complete phrases sound deliberate, and deliberate speech is less likely to make the room feel that the meeting has been interrupted.
If a command fails, do not troubleshoot in front of everyone. Note the phrase and the failure on your sheet, say a brief manual note to yourself, and continue listening. Write the time of the failure beside the phrase so the debrief can reconstruct it. Set a rule that you will attempt a correction only once and only after the current agenda item ends. Repeated attempts draw attention and produce worse notes than a calm manual capture. Because the device-task integration is early-stage and under active refinement, some failures are expected; the meeting protocol should assume them rather than treat each one as a surprise. The debrief is where the correction belongs.
Protect the flow with a simple closing phrase that tells the room you are done with the command. Something as short as noted or back to you signals the transition and prevents people from waiting for more. Use the same phrase every time so it becomes invisible. A consistent closing phrase also gives late joiners a clue about what is happening. If you are sharing a screen, keep the notes document out of the main view unless the content is meant for everyone. When someone asks what you are doing, answer in one sentence and move on. Transparency without a lecture keeps the protocol lightweight and easy for others to accept.
Check the result of each command before you issue the next one. A quick glance confirms that the action item landed under the right name or that the document opened in the expected place. If the result is wrong, correct it once with a short phrase, then stop and capture the rest manually. Do not stack commands on top of an unverified result, because a single wrong insertion can make the following notes unreliable. The check takes a second and protects both the record and your credibility in the room. Verification is part of the command, not an optional extra.
Keep the verification silent unless it changes what the room needs to know. A nod or a short noted is enough for routine captures. Speak up only when an action item needs confirmation from the person responsible, such as asking whether the date you recorded is correct. That question is valuable because it prevents a wrong commitment from entering the record. If the person is not sure, read the date back and wait for a yes. Ask it at a natural break and keep it to one sentence. The point is to confirm the substance, not to narrate the mechanics of the routine.
If a command affects a shared document or a visible screen, say what changed in plain language. People should not have to guess why a line appeared or a file opened. Keep the explanation factual: the decision is now in the notes, and the reference file is open. If the action was not what the room expected, correct it immediately and say so. A short correction is far better than a silent fix that leaves someone unsure about the record. Keep the note in the shared document rather than a private scratchpad so the record stays together. Shared visibility is what makes live commands acceptable in a collaborative setting.
When you want a colleague to try the same meeting protocol, have them download Voiskey for Mac or Windows and rehearse the command sheet before their first call. Voiskey places text at the insertion point in the app you are already using, so the sheet transfers cleanly from one person to another. Pair them with someone who has run the protocol once and watch their first two commands. Run the rehearsal in the same kind of document the meeting will use. Keep the same phrases and the same cues until they are comfortable. A shared protocol is easier to refine than a collection of personal habits.
Debrief within an hour of the meeting, while you still remember which phrases worked and where the flow broke. Read the captured notes against the agenda and mark every action item with an owner and a date. Compare the command sheet with what actually happened: which phrases were used, which failed, and which were never needed. Write one sentence about the biggest disruption and one about the biggest save. Schedule the debrief as a standing fifteen-minute block on recurring meeting days. This short review turns a live experiment into evidence you can use the next time. Without it, the routine stays a story rather than a repeatable practice.
Separate command failures from note failures. A command failure is a phrase that did not produce the expected action; a note failure is a captured item that is incomplete or assigned to the wrong person. The fixes are different. Change the phrase in the first case and change the document structure or the capture order in the second. Label each item in the review so the next sheet update has a clear target. Update the sheet with the exact revised wording and a date. Retire any phrase that failed twice. A small, current sheet is more useful than an archive of every variation you have tried.
Share the revised sheet with the people who attend the same recurring meeting. Ask one of them to run the protocol for a single agenda item while you observe. Their experience will expose assumptions that your own rehearsal missed, especially around timing and social cues. Add their notes to the sheet and keep the original version for comparison. Keep one shared copy and note who changed it and when. Keep the note brief so the sheet stays readable. When the group agrees on a shared set of phrases, the meeting becomes easier to chair because everyone knows what a short spoken command means and when it is appropriate.
Decide whether to keep the protocol for the next meeting, narrow it to one recurring agenda item, or drop it. Keep it if the notes are more complete and the room did not lose time. Narrow it if the commands worked but the social cost was high. Drop it if manual notes were faster and cleaner. Before the next cycle, download the latest Voiskey build and rerun a two-minute rehearsal with the revised sheet. Record the decision, the date, and the next reviewer, then close the loop with the colleague who observed the call. A written decision stops the same conversation from repeating before every call.
Yes, if you keep the commands short and low-risk. Voiskey places text at your insertion point in the app you are already using, and it can pass brief spoken instructions to device tasks. Announce the protocol, wait for natural pauses, verify each result quietly, and capture anything sensitive manually after the call.
List no more than eight phrases, each with one verb, one object, and the exact document or item name. Add the expected result and a manual fallback beside each one. Include the names of people whose action items you expect to capture, and test two phrases in the real document before the meeting.
Wait for a pause, speak at aside volume, and issue one action per phrase. Do not troubleshoot a failed command in front of the room; note it and continue listening. Use the same short closing phrase each time so people stop waiting for more, and keep the number of commands per meeting to three or five.
Read the captured notes against the agenda within an hour. Separate command failures from incomplete notes, revise the exact phrase for the first kind, and change the document structure for the second. Retire any phrase that failed twice, and share the revised sheet with the people in the recurring meeting.

Download Voiskey for Mac and Windows and rehearse your meeting command sheet before the next call.
Use it across macOS, Windows, iOS, and Android