
Voice to ERP request: what it looks like in practice
There's one type of employee for whom every process digitisation of the past twenty years has almost-but-not-quite worked: the one who works outside. The technician, the service engineer, the driver, the inspector. Dirty hands, laptop in the van, no patience to fill in a whole form on a phone with a tiny keyboard.
What happens: the notification gets added in the evening, half remembered. Or not at all. And that's a more expensive problem than it seems, because exactly the data that's most valuable — what happened on location, what was repaired, what the customer said — lands worst in the systems.
Hold the button and speak.
New way of working:the technician opens the app on his phone, holds a button, and speaks:
"I've replaced the pump at customer De Vries, serial number ending in 847, new pumpinstalled, maintenance log updated, advised replacing the filter next time.
That's it. Here leases the button.
What the agent does next
In the few seconds after:
- The speech is transcribed
- Customer De Vries is matched to the right relation in your ERP
- The pump withserial number ending in 847 is looked up in the installed base
- A work order line is created, linked to this installation
- A maintenance action is recorded with date and technician
- The advice about the filter is converted into a follow-up appointment for the next cycle
The technician sees a confirmation on his screen. Done. No form filled in, no fields selected, no dates fiddled with on a small screen.
Use cases beyound the shop floor
This principle — speak, agent processes — works not only for technicians. Wherever people work on location or are on the move, the same friction exists:
- Accountmanagers. After a customer meeting, speak the summary in the car, land directly as a contact moment in the CRM part of your ERP. No hassle with loose notes that only get retyped a day later.
- Drivers. Confirm a delivery with a brief remark about location or recipient — important for the next route, usually lost.
- Inspectors. Dictate findings with a photo attachment, directly into the report. Usually inspectors sit typing out everything they saw during the day late into the evening.
- Directors. After a meeting, speak the action points, directly created as tasks in projects— instead of half-lost in a notepad.
Why this matters
The point isn't "faster." The point is: registration without friction.
The lower the barrier to record something, the more complete your data becomes. And complete data is what your AI agents will need to do better work. An agent that summarises service history is only as good as the history in it. An agent that uses customer conversations to prioritise prospects only works if those conversations are actually recorded.
Less typing. More data. Better processes
The paradoxical rule: to get smarter with AI, you need better data. To get better data, you have to lower the barrier to recording data. And you don't do that by making your forms prettier, but by removing them.
Speak and done. That's the simplicity the shop floor has been waiting for for twenty years.
