Who it is for and why
These recommendations are for the plant director and the safety manager who are considering a voice assistant pilot for employees. The assistant lets a logged-in user move by voice to the sections they have permission for, instead of clicking through the menu. This matters where hands are busy, in gloves or in noise, and the screen is small.
The assistant is at the pilot stage on a single server and is enabled by a flag on the server side. On installations without the flag the widget does not appear, so the pilot can run on a chosen installation without affecting the others.
1. Set the scope: navigation, nothing more
The assistant is used only to navigate between sections and performs no operations beyond opening a screen. This is the most important sentence for anyone assessing risk: a voice command will not approve a permit, close a report or send a message.
Write down the pilot scope as a list of sections that employees will open by voice, and confirm it with the safety department. Do not promise employees functions the assistant does not have.
2. Base permissions on roles, not on voice
The language model's answer is matched against the list of sections allowed for a given user. The refusal rule for a role always takes precedence over the access rule, so a person without permission to a section will not reach it even with a correctly phrased command.
Before the pilot, check the role matrix: whether an employee, an external company worker and a supervisor see in the assistant what they see in the menu. A mismatch indicates an error in the roles, not in the assistant.
3. Test behaviour with an unsaved form
When a user has an unsaved form on screen, the assistant asks for confirmation with the word yes before moving to another section, instead of silently discarding the entered data. For an employee in noise it matters whether the confirmation is unambiguous and whether no answer leaves the form untouched.
Test this scenario with users under hall conditions: in noise, in gloves, with the microphone of a phone or tablet. Record how many times the confirmation had to be repeated.
4. Adopt the way answers are played back
The assistant performs the navigation first and only then announces it, so that it does not announce a move that was blocked. The answer is played back sentence by sentence in a queue. For the user this means the message matches what they see on the screen.
During the pilot, collect feedback on the length and pace of answers. Short messages work better in noise, so agree with the team whether the assistant's persona is understandable to employees.
5. Measure usage from day one
The usage analytics panel has a Voice tab with the most frequent intents, a daily trend and a comparison of routes opened by voice and by click. Voice data uses the existing table of interface events, so there is no need to build a separate measurement system.
A voice command repeated right after the previous one is treated as a signal that the first one did not work, and it goes into a log for later review. This is the best source of improvements: review it every week and add the missing phrasings.
- Most frequent intents: what employees most often want to open.
- Daily trend: whether usage grows after the team's training.
- Voice versus click: whether routes opened by voice differ from clicked ones.
- Repeated commands: where the assistant did not understand.
6. Define the criteria for ending the pilot
Before the start, decide how you will know the pilot succeeded: the share of voice commands in all navigation, the share of repeated commands and feedback from employees on the floor. The plant sets the threshold values itself, based on the first weeks, because there is no universal number.
The pilot runs on a single server and is enabled by a flag, so ending it means switching the flag off or moving to a wider rollout after the director's decision.
Video
Frequently asked questions
Can the assistant approve a permit by voice?
No. The assistant is used only to navigate between sections and performs no operations beyond opening a screen.
How do we run the pilot on one installation?
The assistant is enabled by a flag on the server side. On installations without the flag the widget does not appear.
What about an unsaved form?
Before moving on, the assistant asks for confirmation with the word yes, instead of silently discarding the entered data.
Considering a voice assistant pilot?
Invite us to a talk about the scope, roles and measurement of a pilot on one installation at your plant.
Let's talk