Field notes

Field crews will send a voice note. They will not fill in your form

Field crews will send a voice note. They will not fill in your form

A refuelling driver, a waste collection crew, an infrastructure team. Today the report from the field is a phone call to dispatch or a note on paper. Weeks later somebody argues with a customer about what was actually done, and the argument is settled by whoever remembers more confidently. That is an expensive way to run a receivable.

The use case

The crew sends a voice note from the field, in the app they already have open. The agent extracts what was done and where, matches it to the work order, and opens an exception when something does not line up. The driver's job got easier, not harder, which is the only version of this that survives contact with a crew.

The detail that matters: a voice note works and a form does not. A form asks someone with dirty hands and three minutes to tap fourteen fields. A voice note asks them to talk for twenty seconds. Every field operation that has tried both knows which one gets used.

What it is worth to the business

You invoice for what was actually done. The dispute with the customer is settled against a record instead of a memory, and it is settled the same week rather than the next quarter. Dispatch stops being a transcription service and goes back to being a dispatch function.

Four decisions you have to make

  1. Is the field report the source of truth for billing, or an indication. This is a finance decision with a compliance tail, and it needs answering before anyone builds anything.
  2. Who approves an exception. Regional manager or dispatch. Exceptions are where the value is, so whoever owns them needs the time to actually handle them.
  3. Voice, text, or the crew's choice. Mandating one is simpler to build. Allowing both gets used more. Pick deliberately rather than by default.
  4. How long the record is kept and who can reach it. A recording of an employee doing their job is personal data. Retention and access are decisions you make once, at the start, in writing.

Where to start

One region, one service line. Compare what the agent extracted against what dispatch logged for the same fortnight, by hand. That comparison is your accuracy baseline and your business case in the same document.

Technical footnote

Hebrew transcription, field extraction, a write to the operational system. Accented and noisy Hebrew from a truck cab is the real engineering problem here, and it is worth testing on your own recordings before anyone promises a number. Test on the worst audio you have, not the best.

Field notes from the factory floor. Five use cases drawn from the same research pass: shift handover · frontline onboarding · field crew reporting · quote turnaround · batch records.

Invoicing off what dispatch remembers instead of what the crew reported?

Book a call
← Back to the blog