Where it clearly helped
Dispatch updates that stop the phone ringing. A two-line message — vehicle located, en route, ETA [window] — sent at pickup rather than when someone calls asking. Most of the call volume during a job is people wanting to know where you are. Replying to that proactively costs almost nothing and removes half the interruptions.
Release instructions. What the owner needs to bring, who is authorised to collect, what payment methods are accepted, and when. The same email, sent on intake, prevented most of the "nobody told me" conversations at the yard. Generating it from a fixed template meant the required documents list never varied.
Invoice wording. Line-by-line: hook-up, mileage, per-day storage starting when, after-hours surcharge, and what triggered each. In our thirty days, disputes were about unclear line items far more often than about the total.
Where it nearly went wrong
Anything about authority to release. Who may collect the vehicle, what proof is required, whether a lien applies. A draft will state these confidently and get the specifics wrong, and this is the one area where being wrong has consequences beyond an awkward conversation. Release conditions come from your own policy and applicable local requirements, quoted rather than paraphrased.
Hold periods and storage accrual dates. "Storage begins after 24 hours" written loosely, or a start date computed incorrectly. These determine money owed, so they get written with the actual dates and the actual rule, not rounded to something plausible.
Condition descriptions at pickup. A generated note describing the vehicle as "in good condition" when nobody photographed it. What you write at collection is what a later claim compares against — describe what was observed, list damage by location, and photograph before moving.
The ten minutes that decide disputes
Everything that later matters gets recorded at collection: photographs from several angles, existing damage listed by panel, mileage if relevant, contents noted, and where it was taken from and by whose request. Generated prose is very good at writing up a good record and useless when the record is thin — it will produce confident sentences about damage nobody documented.
Two conversions worth having
Work that arrives through motor clubs and insurance programmes pays differently from private calls, and each relationship comes with reporting requirements that are worth knowing before accepting it. The operators who did best over thirty days were not the fastest — they were the ones whose paperwork matched what each referring party needed the first time, so invoices were paid without correspondence. Worth asking any new account what fields they require on submission, because retrofitting those later means rewriting records you have already closed.
Editing time, from our 30-day benchmark
Our 30-day test measured roughly 22 minutes of editing per 1,000 words on the low-cost dedicated writer against about 8 minutes on the general assistant — near $7 per piece of your time at $30 per hour. In towing the return came from intake and invoice documents that were previously inconsistent, while the collection record stayed manual because it is evidence rather than copy.
A workflow that holds up
Send the intake message with required documents and release conditions quoted verbatim from your policy, not paraphrased. Photograph and write damage notes at collection, by location, before anything moves. Keep invoices itemised with each trigger stated, including when storage starts to accrue. Reply to "where are you" before being asked. Anything about authority, hold periods or liability is written by hand and checked against your own terms.
Standardise the paperwork, hand-write the authority
Dispatch messages scale; release conditions do not delegate.
Try Rytr →Frequently Asked Questions
Can AI write tow dispatch messages?
Yes — pickup confirmation, en route updates with an ETA window, and delivery notifications are well suited to templates and cut inbound calls noticeably.
Should it write release and payment terms?
No. Quote release conditions, authorisation requirements and hold periods verbatim from your own policy and applicable local requirements. Errors there have consequences.
What prevents disputes best?
Photographs and damage notes taken at collection, listed by location, before moving the vehicle — plus an itemised invoice stating what triggered each line.
Can it help with condition reports?
It can write up a record you already made. It cannot observe damage, and it will invent confident descriptions if the notes are thin — which is worse than leaving it blank.
What should a small operator set up first?
The intake message with documents and release terms quoted, and an itemised invoice template including when daily storage begins.