Sixteen forms
Incident report, site diary, compliance certificate, pre-start check, timesheet, vehicle fault report, quote, job notes, dictated email, skills check and more. Each one is the business's own version, with its own questions.
Paperwork by phone call
The report is filed before the technician leaves the site.
Your clients' field teams are good at the job and bad at the paperwork. A technician rings in, says what happened, and the record is filed before they leave.
What the agent does
Interviews the technician, then writes it up
The business defines the form. The agent asks the questions one at a time, renders the record as a branded PDF, and files it where the business wants it.
Talked, not typed
The technician talks. The agent asks what it still needs, in order, and skips what it already has. A dictated email or job note is taken the same way.
Knows who is filing
The caller is identified by their registered number, a PIN, or a code texted to them, so a report carries the right name and nobody files under somebody else.
Photos attach themselves
A photo the technician texts within the hour is attached to the record it belongs to. The damaged switchboard is on the incident report, not lost in a message thread.
Alerts with judgement
An incident report that says a site is unsafe texts the operations manager at once. A routine site check is filed quietly.
The agent rings them
Outbound rounds ring each technician at the end of the shift for the day's timesheet or site check. The same forms work over the texting agent, web chat and the API.
How it goes for the caller
An incident report from a managed site
- The technician rings inFrom their registered mobile, or with a PIN or texted code. They say which form, or just what happened.
- The agent asks the questionsWhich site, what happened, whether anyone was hurt, whether the area is safe. One at a time, nothing skipped.
- The record is builtThe answers are extracted into the form, rendered as a branded PDF, and the photo texted later is attached.
- It is filed and flaggedThe PDF is texted, emailed and filed into the job system. An unsafe site texts the operations manager at once.
What the business gets
A record in the right place, minutes after the job
Every record rendered as a branded PDF, texted and emailed, and kept in an inbox of records on the dashboard. For a business on Fergus, the record is filed as an attachment with notes on the named job. A quote taken by phone becomes a draft quote in Xero.
For a logistics firm with a fleet, the platform reads the vehicle lists from EROAD and MiX so the agent knows the vehicle and the driver. It reads those lists only and files nothing back.
The technician's identity is checked on every call, urgent findings reach the right manager immediately, and the call is on the record like any other, so there is an audit trail from the spoken words to the filed document.
Filing into Simpro, ServiceM8, Tradify, GoHighLevel, Freshservice and Autotask is planned and not yet built; a webhook is the route today. An emergency outside hours goes to escalation.
Sold through partners
A compliance product for clients with people in the field
Facilities management companies, national logistics firms, property management groups and any client with a field workforce buy this on the strength of one late report. You set the price, define the form library with the client and decide whether it is bundled with reception; Talkgate builds and runs the filing connectors. The partner programme explains the support model.
Next step
File an incident report by phone on a live account
A partner briefing walks through the form library, the identity check and the PDF landing on a job. See also call records and texting.