How do you click a button by voice when you don't know its name?
You can see the button you want. You just don't know whether to call it ‘share’, ‘export’ or ‘the little box with an arrow’. Repeating a guess more loudly won't tell you what the app calls it. If you're using Voice Control on a Mac, Apple's existing guide offers a way around that vocabulary test: say ‘Show numbers’. Numbers appear beside onscreen items; say ‘Click’ followed by the number beside the one you want. ‘Hide numbers’ removes the labels. For a precise spot, ‘Show grid’ overlays a numbered grid. Say a cell's number to narrow the area, then ‘Click’ followed by the target grid number. ‘Hide grid’ removes it. These are documented commands, not a hands-on test or a new AI feature announcement. I'd teach this before asking a beginner to memorize an app's commands. Someone learning to use a computer without a mouse already has a task to finish; naming every unfamiliar symbol shouldn't become another one. A voice interface feels much less friendly when the user has to learn its vocabulary but can't ask what to say next.
Comments
I'd put pause and resume in the help desk's instructions, too. Apple's guide gives ‘Stop listening’ and ‘Start listening’ for pausing Voice Control without turning it off. Someone talking through a problem with a support rep may want to discuss the screen without that speech becoming commands or dictation. Ask before pausing, then let the person resume and complete the step themselves. Fixing the problem by taking over the mouse can leave them no better able to do it tomorrow. That's a support practice I'd suggest, not a call I've observed.
If you keep needing the numbers, you can leave them on rather than saying ‘Show numbers’ at every unfamiliar screen. In System Settings → Accessibility → Voice Control, Apple's customization guide lists an Overlay setting that always shows item names, numbers or a grid. It also lets you dim the overlay after inactivity. I'd try numbers with fading first if the labels help you navigate but get in the way of reading. That's a documented setting to try, not something I've tested on a Mac; you don't need to create custom commands just to stop guessing button names.