Towing in Lima: Build a CRM Around the Tow Job, Not the Sales Lead

A tow job creates a lot of paperwork, and almost none of it starts on paper. It starts as a phone call, then a text from the driver, a photo or two, a scribbled lot number and maybe a voicemail from an insurer. By the time someone asks what happened, the answer is spread across three phones and a clipboard.

That's the problem worth fixing first, and a custom CRM is the right tool for it.

The tow job is the record, not the customer

Off-the-shelf CRMs are built around a salesperson moving a lead through stages. Towing doesn't work that way. What you need to track is the vehicle and the job: who called it in (a motorist, a motor club, police, a property manager), where it was hooked, where it sits now, how many days it's been on the lot and who's allowed to pick it up.

When those details live in a driver's text thread, a notepad on the dash and the memory of whoever answered the phone at 2 a.m., you can't defend them when someone pushes back.

And Ohio expects you to be able to. Since January 1, 2026, the PUCO rule on tows from private property has capped the tow fee at $144 for vehicles under 10,001 pounds and storage at $22 per 24-hour period. Heavier weight classes have their own, higher caps. Commercial tows have their own rules too. The HB 403 changes, in effect since April 9, 2025, give the owner of a towed commercial vehicle a way to dispute the bill. The owner pays the undisputed portion and posts bond for the rest. You then have two business days to release the vehicle, the cargo and any personal property.

Every one of those rules depends on facts: tow type, weight rating, when the vehicle reached your lot, and when the payment and bond came in. If you can't pull those up in a minute, you're arguing from memory.

What a custom CRM for a tow company looks like

This is the job Paglow's Custom CRM service was built for. We don't give you a sales tool and tell you to make it fit. We map how your yard actually runs and build around that. Before anything gets built, you get three documents: a CRM spec, a data model and a build plan.

For a towing business, the data model usually comes down to four kinds of records:

• Tow job: call time, source, tow type (consent, private property, police-ordered, commercial recovery), pickup and drop locations, driver, truck
• Vehicle: VIN, plate, weight class, hook-up photos, lot location, days in storage
• Party: owner, insurer, motor club, property manager or agency, plus who is authorized to pick the vehicle up
• Money: the quote, the invoice, the cap that applies, payments, disputes and any bond received

The pipeline then follows the real life of a tow: called in, dispatched, on scene, hooked, on the lot, then released or disposed of. Each stage has required fields, so a job can't move to "on the lot" without photos and a lot spot.

Where the AI earns its keep

This is the part that fixes the scattered-texts problem. Drivers aren't going to fill out forms on the shoulder of I-75 at night, and nobody should ask them to. So the build plan lets them keep doing what they already do: text in a few photos and a one-line note. An AI step reads the message and photos, pulls out the plate, location and damage notes, and puts them into the right fields on the right job. The dispatcher checks it and approves with one tap instead of retyping it.

The automations are just as practical. If a private-property tow is priced over the cap for its weight class, it gets flagged before the invoice goes out. Storage days count themselves. When a commercial dispute is logged with payment and bond received, the two-business-day release clock starts and the right people can see it.

None of this needs a big platform switch. For most Allen County shops, the sensible start is one yard and one tow type. Private-property impounds are usually the right pick, because that's where the fee caps apply. Expand once your drivers trust it.

If your tow records live in three phones and a clipboard right now, start with something simple. Write down every detail you wish you'd had on hand during your last billing argument. That list is the first draft of your CRM spec, and it's the conversation we'd want to have with you.