Quotes, Licensing & TCPA: A 2026 Playbook for Home-Service Sites

Home services feels like the low-risk end of the regulated world, and that is exactly what makes the AI exposure easy to miss. A plumber, an HVAC company, an electrician, a roofer: the work is hands-on and local, so an assistant on the website seems like a harmless way to book more jobs. The catch is that the two things customers most want from that assistant, a price and a promise about the work, are the two things that quietly create legal obligations the moment your site states them.

This guide is the companion to the threat side of that story. The threat piece covers what goes wrong when an unguarded chatbot quotes and promises. This one is the standard: what a compliant deployment looks like for a home services business in 2026, and the specific lines the system has to hold.

A Quote Is a Number You Can Be Held To

When your website states a price, the customer hears a commitment, and contract law often agrees with the customer. A figure presented as the cost of a job can become the basis of the bargain, and a description of what the work will accomplish can operate as an express warranty under the commercial code. "We’ll have that running like new" is a friendly sentence and a warranty claim at the same time.

So the dangerous answers are the ordinary ones. "How much to replace a water heater?" pulls a confident range the technician has not validated against the actual house. "Can you get rid of the mold for good?" gets a reassuring yes that becomes a promise you now have to honor. The assistant meant to be helpful. It bound the business.

Texting Leads Is Its Own Rulebook

Home services runs on fast follow-up, and follow-up usually means a text. That puts the Telephone Consumer Protection Act in the room. Automated calls and texts to a customer require the right consent, and an assistant that captures a phone number and fires off messages without it is generating TCPA exposure at the speed of automation. The fix is not subtle: capture proper consent, or route the outreach through a compliant path, and never let the tool improvise marketing texts.

Licensed Trades Have a License Line Too

Plumbing, electrical, and HVAC work is licensed in most jurisdictions, and giving specific technical or safety guidance can cross from "general info" into the territory the license protects. An assistant that walks a homeowner through a gas connection or an electrical repair is not saving them a service call; it is offering unlicensed technical advice with real safety stakes. The compliant move is to keep that guidance with a licensed tech.

The 2026 Compliance Standard, Line by Line

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

• No firm price quotes. A range or a number stated as the cost becomes a commitment, so pricing routes to a person who can see the actual job.
• It does not promise outcomes. "Guaranteed," "like new," "gone for good" are warranty language; the assistant describes services without warranting results.
• Technical and safety guidance stays with licensed techs. The assistant does not coach a homeowner through licensed trade work.
• Outreach respects consent. Phone numbers are captured with proper TCPA consent, and the tool never sends automated marketing texts on its own initiative.
• Scheduling commitments are confirmed by a human. "We’ll be there at nine" is a promise the dispatcher owns, not the chatbot.
• And every exchange is logged, so what was offered to a customer is reviewable rather than lost in a widget.

The pattern is the same one that runs through every vertical. The assistant answers what carries no obligation, services offered, service area, hours, how booking works, general "what does this service include" questions, and routes every price, promise, and piece of technical guidance to a person. That division is the whole standard.

Why an Instruction Cannot Meet the Standard

The usual shortcut is to write the rules into the assistant’s prompt. Tell it never to quote a price, never to promise a result, and call the boundary set.

It is not set, because of how the model reads a request. It follows an instruction when the question resembles the wording it was warned about, and slips the moment the phrasing changes. You tell it never to quote a price. The customer never says "give me a quote." They ask, "roughly what do most people pay for this?" The model hears a harmless question and produces a number. The instruction was loaded the whole time. It just did not recognize the sentence that crossed the line into a quote your business now wears.

That is the difference between an instruction and a standard. An instruction asks the model to behave; it does not stop the model from speaking. A real boundary is built into the system and decides what the assistant may say before it answers, so a price or an outcome promise never reaches the customer 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 brochure site with no assistant. It means deploying one built to book jobs without binding the business, and one that keeps a clean record of what customers were told.

Fred is built that way. It answers from your own service content, captures the lead with proper consent, and routes pricing, outcome promises, technical guidance, and scheduling commitments to a person on your team. It runs more than 50 industry guardrail packs, and the home services pack is built around quotes, warranty language, and consent-based outreach. Fred does not quote a water heater or promise the mold is gone for good. It cannot. It answers what it should, captures the job, and hands the commitments to the people who can stand behind them.

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

Frequently asked questions