An AI listens in on the service call and puts what they need in front of them — while they are still talking. Serial number, warranty status, the last job on that machine, and what the manual says about the symptom.
It never speaks to your customer and it decides nothing. It listens, it writes, and your engineer stays in charge of the call.
On screen, now
It connects to your exchange as a silent extension. Nothing changes for the engineer.
Machine history and warranty come from your system. Nothing is stored in its place.
No search of its own, no job sheet opened, no part ordered.
Your engineer knows hydraulics. What they do not know off the top of their head is what happened to that particular machine, on that site, eight months ago — and whether the warranty ran out.
That information is in the ERP, in a PDF manual, and in an old job sheet. Three windows, three searches, while somebody stands next to a stopped machine and waits.
So the call ends with “I’ll check and call you back.” That callback is where the day goes.
Not a summary emailed afterwards. A state on screen that keeps up with the conversation, so the answer arrives before the caller has finished describing the problem.
Your engineer presses nothing and swaps no headset. Your phone system signals an incoming call; the system starts listening on its own.
The caller and the engineer on separate channels, so it is always clear who said what — and so the call can be read back later.
Serial number, machine type, symptom, location. Not a summary afterwards: a state on screen that keeps up with the conversation.
And what that symptom usually points to — the question an experienced colleague would lean over and prompt.
Service manuals, fault codes, parts lists. Your engineer starts the search; the system does not act on its own.
From the serial number: machine history, warranty status, previous job sheets — while the caller is still talking.
For training, and for the calls that turn into arguments about what was promised. The recording and the transcript stay on your side.
The customer is still talking. On the left, every line is transcribed as it is said — in the middle, the machine model, its serial number and the fault code are already there, all pulled from the call itself. On the right, the question still to ask before the quote can be accurate.
This list matters as much as the one above. What we do not write down, you will assume — and that argument is expensive after the quote.
It is an assistant, not a record. No speech system transcribes a noisy line perfectly, and this one does not either. Your engineer sees what it writes and corrects it — that is why the screen is in front of them, and not behind them.
A service desk, several technicians, and more than a couple of calls a day. The value comes from the calls that would otherwise end in a callback — so it scales with how often that happens.
Your engineers know their job. What they do not know off the top of their head is the history of that particular machine and what the manual says — and that is exactly what they cannot look up while talking.
We are not replacing expertise. We are taking the search time out of it.
No procurement marathon. A demo first, so you can see whether it is worth the conversation at all.
We show it running on a real call, on our own system. You see the transcript and the state on screen as it happens.
15 minutesWhich ERP, which phone system, what it needs to know at your company. This is what the quote is based on.
one conversationAfter the survey. The price depends on how many systems have to be joined up, which is why there is no price list on this page.
no price listThere is no free tier and no trial period. Every minute the system listens costs us money, so a free tier would not be forgone profit but a real bill. The demo is how you try it — fifteen minutes, on a real call, with no preparation needed on your side.
What it does on a call, what it needs from your ERP, where it stops. It will not quote you a price it cannot stand behind — that needs a look at your systems first.
And we will show you the system running. Fifteen minutes, no preparation needed on your side.
Or write to pongracz.zoltan@weboptimai.com — a person reads it, and answers within one working day.