ManuVox Talk to your robots.
ManuVox lets anyone on a warehouse or plant floor ask what a robot is doing, look back at what it did, give it new work, or pause it — just by speaking into the phone or handheld they already carry. And when a machine gets stuck, it calls the right person.
No more walking to a terminal to find out what a robot is doing.
People on a robotic floor need four things from the machines around them — and the machines need one thing back. ManuVox handles all five by voice.
One box. Your floor.
Every machine.
A small server sits on your site network. People reach it from phones and handhelds; it talks to the systems that already run your robots. It asks those systems to act — it never goes around them.
Uses what you already have
Plant phones dial an extension. Handhelds open an app. No new radios, no new badges, no public phone numbers.
Never a second boss
Every command goes to the system that already runs the robot. Its traffic rules and interlocks keep the final say.
Your data stays home
Robot history lives on the box at your site. Nothing on the internet can connect in.
The AI listens. The rules decide.
The AI is great at understanding “send one-seven home after it drops this tote.” It is never the part that decides you said yes. Here is every step a command takes.
Safe direction fast. Risky direction confirmed.
When someone sees a robot heading for a spill, waiting for the cloud and a “confirm?” costs seconds. So a one-word “Stop one-seven” is recognised right on the box and the pause request leaves at once. Pausing can always be undone; that is why it gets to be instant.
Anything that starts motion, cancels work or touches more than one robot is read back and confirmed first.
Voice asks.
The machine decides.
The bigger the action, the more ManuVox asks of you. And some things it will never do by voice — the hardware E-stop stays the only safety stop.
It only says what it saw
“One-seven is paused” is spoken only once the robot reports it. Older data is spoken with its age.
It never guesses
Two robots at dock four? It asks which one. Your PIN is always keyed, never spoken or recorded.
Respectful of people
No voiceprints. No productivity scoring of workers. It tracks the machines’ history, not the people’s.
When a robot is stuck, the right person’s phone rings.
Not a beep. A conversation. The person who answers can ask “what’s blocking it?”, acknowledge, or give a command — and if nobody answers, it moves up the chain on your rules.
One alert, not twelve
Three robots queued behind one blockage become one call: “three robots blocked behind one-seven.”
Closes itself
When the robot starts moving again, the alert resolves and whoever is on the call is told.
Quiet when you ask
Maintenance windows and rate limits stop alert fatigue before it starts.
Works on a bad day, too.
Loud floors, dropped internet, a fleet system that goes quiet. Each has a planned response, and pausing and alerts keep working through all of them.
{{ b.title }}
{{ b.body }}
Everyone on the floor. Each at their level.
Plugs into what already runs your site.
Adding a new robot vendor is a mapping file, not a custom project. Your robots, zones and task names are set up as configuration — nothing is hard-coded.
