Regulated Fees, Releases & Liens: A 2026 Towing Playbook

Towing is one of the most complaint-heavy corners of the vehicle business, and most of the friction lands in exactly the questions a website assistant invites: what does it cost to get my car back, is it even here, and was that tow legal. Those are not routine service questions. Release fees are regulated, vehicle location can be a safety matter, and the legality of a tow is frequently the thing in dispute. An assistant that answers them like a parts-counter question is wandering into regulated, contested territory.

This guide is the companion to the threat side of that story. The threat piece covers what goes wrong when an unguarded chatbot quotes a release fee or rules a tow legal. This one is the standard: what a compliant deployment looks like for a towing company in 2026, and the lines the system has to hold.

Release and Storage Fees Are Often Set by Law

Start with price, which here is not freeform. Nonconsensual towing is heavily regulated, and federal transportation law specifically preserves the states’ authority to regulate the price of nonconsensual tows. Many states and localities cap release fees and storage rates and set the notices that must be given. A figure improvised by a chatbot can exceed a legal cap or contradict your posted schedule, and an inflated quote in writing is what feeds predatory-towing complaints. Misleading charges also fall within the FTC’s authority over deceptive practices. The compliant position is that fees follow the regulated schedule, and the assistant routes the actual figure to your office.

Vehicle Location Follows Verification

Confirming a specific vehicle is in the lot looks harmless and sometimes is not. Telling whoever is in the chat where a car can be found can expose where a person can be found, which is a real hazard in domestic and stalking situations. A compliant assistant explains the retrieval process generally and leaves confirmation of a particular vehicle to a verified channel your team controls, rather than answering location first and verifying never.

Legality and Lien Rights Are Conclusions, Not Chat Answers

Whether a tow was authorized depends on signage, property authorization, notice, and state and local rules, and it is often exactly what a customer disputes. A chatbot that declares a tow "legal," or concedes it was not, hands the customer a statement to use. The same goes for advice about lien rights or reclaiming an abandoned vehicle, which run on state procedures that vary. A compliant assistant does not render legality conclusions or apply lien procedures to a specific car. It explains the general process and routes the dispute to management.

The 2026 Compliance Standard, Line by Line

A compliant towing assistant is defined by what it is built to refuse. Treat the list below as the floor.

• No improvised fees. Release and storage figures follow the regulated schedule, with the actual number routed to your office.
• No unverified location disclosure. Confirming a specific vehicle follows identity verification your team handles.
• No legality conclusions. The assistant never declares a tow legal or illegal.
• No lien or reclamation advice for a specific vehicle. State procedures route to management.
• Calm, factual tone for upset callers, without commitments it cannot keep.
• Every exchange is logged, so what a driver was told is reviewable.

The pattern is the one that runs through every regulated vertical. The assistant answers what carries no obligation, your services, hours, how the retrieval process works in general, what to bring, and routes fees, location confirmation, legality, and liens to people.

Why an Instruction Cannot Meet the Standard

The usual shortcut is to write these rules into the assistant’s prompt. Tell it never to quote a fee and never to rule on legality. Call the boundary set.

It is not, because of how the model handles a question worded differently than expected. You tell it never to quote release fees. A frantic driver asks, "roughly what am I looking at to get it back tonight?" The model hears a simple question and gives a number to help. The instruction was loaded the whole time. The phrasing just slipped past it.

That is the difference between an instruction and a standard. An instruction asks the model to behave; it does not stop it from speaking. A real boundary is built into the system and decides what the assistant may say before it answers, so a regulated fee or a legality conclusion never reaches a driver no matter how the question is framed. "Will not" is a suggestion. "Cannot" is an architecture.

What a Compliant Deployment Looks Like

Meeting the 2026 standard does not mean a static page. It means deploying an assistant that helps drivers understand your process and reach your team, without quoting regulated fees or ruling on a tow.

Fred is built that way. It answers from your own content, explains the general retrieval process, captures the inquiry, and routes fees, vehicle confirmation, legality, and lien questions to your team behind verification. It runs more than 50 industry guardrail packs, and the towing pack is built around regulated nonconsensual-tow pricing, verification before location disclosure, and the line between process and legality. Fred does not quote a release fee or call a tow legal. It cannot. It answers what it should and hands the rest to people.

That is the difference between hoping the assistant does not misquote a fee and being able to show why it cannot.

Frequently asked questions