Voice-based service documentation
Two minutes of speech. A complete service job.
For field service teams in machinery and plant engineering: After the job, the technician records a voice memo. By the next morning, the report is ready for approval on your company letterhead.
Request a demoEvery case has many loose ends.
A call, an email, a scheduled maintenance visit: cases come in through many channels and then pass through many hands. Your people piece it all together in their heads.
Typical cases. Names, machines, and days are made up.
-
Monday
-
Hotline Monday
A customer reports a fault. The call isn’t logged anywhere afterward.
-
Email Monday
Fault report in the shared inbox, with a photo.
-
Maintenance Monday
Scheduled visit under the maintenance contract.
-
-
Tuesday
-
Technician Tuesday
“Fault fixed. I’ll write the report tonight at the hotel.”
-
Technician Tuesday
The machine’s history is scattered across old reports.
-
-
Thursday
-
Spare parts Thursday
The part is described, but the part number is missing. Another follow-up call.
-
Back office Thursday
Every report is structured differently, and required details are buried in free text. The technician is already at the next customer.
-
-
Afterward
No one starts from scratch, and no case gets dropped.
Two minutes of speech become a report, and every report becomes part of the machine’s history. Each job goes into the record for the machine and its customer, along with old reports from years back. No more writing reports at the hotel, no follow-up calls at the next customer, no digging through folders.
- 01 Intake
- 02 Dispatch
- 03 Close
-
01
Intake
Call, email, or scheduled visit: every case is logged, along with the machine’s history.
-
02
Dispatch
The technician heads out with everything already settled on the phone.
-
03
Close
Two minutes of talking. Out come the customer report and the internal log, every entry linked to the sentence it came from.
-
04
Follow up
Whatever comes up after the job is prepared and ready for approval.
Less work. Not another system.
What Firnora does differently, for everyone who works with it.
For the technician
-
Today
A phone call or an email, plus a briefing with the key points, but only the ones someone knows about.
Fully briefed before heading out.
Firnora adds the machine’s full history to your briefing: what happened before, what was ruled out, which parts to bring. Tailored to the way you work.
-
Today
“I’ll write the report tonight at the hotel.”
Told, not typed.
Two minutes of talking right after the job, like telling a coworker in the truck. If technicians end up typing more than before, Firnora is built wrong.
-
Today
Every new system raises the suspicion of being monitored.
Doesn’t rate people.
No time tracking, no rankings, no comparisons. Not switched off. Never built.
For the back office
-
Today
The report gets retyped and copied into the template, parts get looked up, and the quote is written separately.
No more retyping.
- Retype the report
- Copy into the template
- Look up parts and part numbers
- Write the quote
One recording produces the customer report and the internal log. Linked to your parts catalog, the quote is drafted and ready too.
-
Today
If a detail is missing, someone has to call back. And whether everything is right is a matter of trust.
Sourced, not made up.
Every field shows the sentence it came from. What wasn’t said stays visibly blank, and a suspicion stays a suspicion. Your back office reviews and approves instead of chasing people by phone.
-
Today
Three technicians, three ways to describe the same job.
Every report the same.
Findings, cause, action taken, and parts are always in the same place, no matter who’s talking.
For management
-
Today
The report sits for days, and so does the invoice.
Ready overnight.
The morning after the job, the report is ready for approval. Nobody has to chase it.
-
Today
The history is buried in old PDFs, and nobody notices when the same component fails for the third time.
The record is complete from day one.
Just import your old reports, scanned ones included. From then on, every job goes into the record, and recurring issues show up as numbers, split into confirmed and suspected.
-
Today
New software means integrations, training, and months.
No IT project.
Start without integration, in the browser and on a smartphone. Your existing systems stay as they are, and nobody has to enter anything.
“If you’re spending a lot of time in Firnora, something has gone wrong.”
Works without integration. Gets better with it.
Firnora reads from your systems and manages nothing. Schedules, work orders, and inventory stay in your systems.
Without integration
Import once, ready to go.
- Past reports
- Parts catalog
- Report template
With integration
Kept current from your systems.
- Master data
- Schedules
- Inventory
Your systems know a job took place. Firnora knows what came out of it.
No system at all? That works too. If you run on Excel, Outlook, and Word, you get the report, the record, and the quote all the same.
What does this cost you today?
Use your own numbers. We don’t assume anything.
We have technicians, each doing jobs a week. Every report takes our back office minutes, at € per hour. A service day costs us €. Each month we send someone out times when a phone call would have done, and times for a second visit because something was missing.
That costs you about – a year today.
- Back-office rework–
- Unnecessary trips–
- Second visits–
The calculator needs JavaScript.
We’ll go through your numbers with you to see how much of this Firnora takes over.
Go through the numbers togetherSample values. Please replace them with yours. Based on 46 working weeks. Trips and second visits count in full if your technicians are fully booked.
Founding Anchor Partnership
A small number of companies are building Firnora with us: on founding terms, with a direct line to the founding and development team, and a say in what comes next. You can cancel after three months.
Apply as a founding partnerA few practical questions.
Do my technicians now have to document everything twice?
No. The report is created from their memo. Whatever your systems already capture stays there.
What do technicians need?
A smartphone with a browser. They talk after the job, and that’s it.
What if something is missing or wrong?
Anything that wasn’t said stays visibly blank. Every entry shows the sentence it came from, and nothing goes out without approval.
What will the works council say?
Firnora doesn’t evaluate individual technicians. No time tracking, no rankings, no comparisons. That’s how it’s built. For long-term use, a works agreement is planned.
Where is the data processed?
In the EU by default. Recordings are not stored by the model provider, all subprocessors are disclosed in the contract, and data can be deleted at any time.
How much effort does it take to get started?
You import old reports and your report template, and you’re ready to go. No integration, no IT project.
Record a memo yourself.
In a short demo, you’ll see how it turns into a report and an internal log, every entry linked to its source.
Request a demo