Guide · United States

AI receptionist for home-services companies in the US

What the agent answers, what it always hands to a person, how calls land in ServiceTitan, Jobber or Housecall Pro, and the TCPA rules for callbacks and texts.

By Thoufic, founder of Flange ·

Why home-services companies miss the calls that matter

An HVAC company in July, a plumber after a hard freeze, a roofer the morning after a storm: the phones ring hardest when every technician is already on a job. The office manager is juggling the dispatch board, the owner is on a ladder, and the call goes to voicemail. A caller with water coming through the ceiling does not leave a message. They ring the next company on the list.

An AI receptionist is a voice agent that answers every inbound call, handles the routine ones from start to finish, and passes the rest to a person with a written summary. For HVAC, plumbing, electrical, roofing and pest control companies in the US, the hard part is not the voice. It is deciding exactly what the agent may say, what it must hand off, and how every call lands in the field service software you already run. This guide covers all three, plus the TCPA rules that apply the moment the system calls or texts anyone back.

What the agent should answer on its own

Start with the questions your office answers twenty times a day. These are safe to automate because the answers are fixed and the owner can sign them off once.

  • Hours and service area. Opening hours, after-hours rules, and whether you cover the caller's ZIP code. A ZIP code list is better than a radius, because nobody argues with a list.
  • What you do and don't do. "Do you service tankless water heaters?" "Do you do commercial roofs?" "Do you treat for termites or only general pests?"
  • Pricing ranges the owner approves. Your diagnostic or trip fee, your maintenance plan price, and a typical range for common jobs if you are comfortable sharing one. Never a firm quote for work nobody has seen.
  • Booking. Taking the caller's name, address, phone and a description of the problem, then offering real open slots for the job type, or creating a booking request your dispatcher confirms.
  • Emergency triage. A short set of questions that sorts "my AC is making a noise" from "I have no heat and there is a newborn in the house", so urgent calls jump the queue.
  • Existing customers. Confirming an appointment window, taking a reschedule request, or noting that a customer called about an open job.

Write this script with the owner, not for them. The pricing section in particular should contain only numbers they have approved in writing. If the agent is unsure, the correct answer is "I'll have someone confirm that for you", not a guess.

What it must hand off, every time

The handoff list matters more than the answer list. These calls go to a person straight away, by warm transfer to the on-call phone, or, if nobody picks up, by a text and a call to the on-call tech with the summary while the caller is told when to expect a callback.

  • Gas smells and carbon monoxide alarms. The agent reads the safety script you have agreed, based on your gas utility's guidance (typically: leave the building, don't touch switches, call from outside), and then alerts your on-call person. It does not troubleshoot.
  • Active leaks, flooding and sewage backups. Tell the caller where the main shut-off usually is if your script includes it, then hand off.
  • Electrical danger. Sparking, burning smells, a hot panel, or lines down after a storm.
  • Angry customers. Complaints, billing disputes, a callback about a repair that failed. A person handles these, and quickly.
  • Anything outside the script. Insurance claims, warranty arguments, commercial bids, legal threats, and anyone who simply asks for a person.

Test every one of these paths with real recorded calls before go-live. A handoff that works in a demo but rings a phone nobody carries at 2am is worse than no agent at all.

How calls get logged to ServiceTitan, Jobber or Housecall Pro

A receptionist that books jobs into a separate calendar creates more work, not less. The agent should write into the field service system your dispatchers already watch. In practice that means:

  1. Look up the caller by phone number and match them to an existing customer and service address.
  2. Create a new customer and location if there is no match, flagged for the office to check.
  3. Create the job or booking request with the job type, problem description and the slot offered.
  4. Attach the call summary, and the transcript or recording if you keep them.
  5. Record the lead source, so you can tell which ads and listings actually bring booked jobs.
  6. Put every unbooked call on a follow-up list with a reason: price shopper, out of area, call back later.

ServiceTitan, Jobber and Housecall Pro all offer API access, but what you can read and write depends on the product and your plan. We check this on the discovery call, before anyone commits to a design. Most companies start with booking requests that a dispatcher confirms, then switch on direct booking for two or three simple job types once the agent has proved itself. Connecting the phone line, the field service system and your CRM is the core of our integration work.

TCPA basics for callbacks and texts

Answering inbound calls is the low-risk part. The Telephone Consumer Protection Act (TCPA) is mostly about outbound calls and texts, and an AI receptionist often does both: calling back missed callers, texting appointment reminders, sending tune-up offers. This is general guidance, not legal advice. Take your own legal advice before you switch on any outbound calling or texting.

  • AI voices count as artificial voices. In February 2024 the FCC ruled that calls using AI-generated voices fall under the TCPA's rules for "artificial or prerecorded voice" calls. That means you need the person's prior express consent before the agent calls their mobile, and prior express written consent if the call is marketing.
  • Informational is not the same as marketing. "Your technician is on the way" and an appointment reminder are informational. "Book your spring AC tune-up for $X" is marketing and needs the stricter written consent. Keep the two in separate flows with separate consent records.
  • Quiet hours. Telephone solicitations are limited to 8am to 9pm in the called person's local time, and some states, Florida among them, set narrower windows. The simple rule is to apply quiet hours to all automated outbound contact, using the customer's time zone, not your office's.
  • Do Not Call. Check marketing calls against the National Do Not Call Registry and keep your own internal do-not-call list.
  • Opt-outs. Since April 2025, people can revoke consent by any reasonable means, such as replying "STOP" or saying "don't call me again" on a call, and you have up to 10 business days to honour it. Build one opt-out flag that the agent, your texting tool and your CRM all respect.
  • Call recording. Some states, California among them, require every party's consent to record. Say at the start of the call that it may be recorded.
  • Business texting registration. US carriers expect business texting from ordinary 10-digit numbers to be registered (A2P 10DLC). Your texting provider handles the paperwork, but it takes time, so start early.

The FCC's guide to unwanted robocalls and texts is a useful plain-English starting point.

Spanish-speaking callers

In much of Texas, Florida, California, Arizona and beyond, a share of your callers would rather speak Spanish. Our systems are built English-first, and there are two honest ways to handle this. The simpler one: the agent recognises a Spanish speaker, says in Spanish that it is connecting them, and routes the call to a bilingual person on your team or texts them a callback time. The fuller one: a Spanish script built and tested as its own flow, with a native speaker on your side reviewing real calls before it goes live. Raise it on the discovery call and we will tell you plainly what is achievable for your call mix. What we won't do is let the agent improvise in a language nobody at your company checks.

What to automate first

  1. After-hours and overflow calls. These are calls you are losing today, so any booked job is a gain and the risk is low.
  2. Booking for two or three simple job types. Maintenance visits, diagnostic calls, a pest inspection. Leave complex installs and commercial work to people.
  3. Confirmations and reminders, once your consent records are in order.
  4. Follow-up on unbooked calls and open estimates, with a person approving the message before anything goes out at first.

Agree the measure before the build: answer rate, booked jobs from after-hours calls, or time to callback. Every system we ship reports against the number we agreed.

Mistakes to avoid

  • Letting it quote. A range the owner approved is fine. A price for a job nobody has seen is a dispute waiting to happen.
  • Pretending to be human. Tell callers at the start that they are speaking with an AI assistant. Most people don't mind if it books them quickly. They do mind finding out later.
  • No tested emergency path. Test the gas, leak and electrical scripts with real calls, at night, before launch.
  • Writing straight onto the dispatch board on day one. Start with booking requests, then widen.
  • Treating outbound like inbound. The moment the agent calls or texts, TCPA rules apply. Get consent and quiet hours right first.

Where to go from here

Our home services page covers the wider picture, from lead pipelines to quote follow-up, and our AI automation for US businesses page explains how we work remotely with US teams across time zones. For budgeting, see how much AI automation costs.

FAQ

Common questions

  • Can an AI receptionist book jobs directly into ServiceTitan, Jobber or Housecall Pro?

    Usually, yes, through each product's API, though what can be written depends on the product and your plan. Most companies start with booking requests a dispatcher confirms, then allow direct booking for a few simple job types.

  • What should an AI receptionist never handle on its own?

    Gas smells, carbon monoxide alarms, active leaks, electrical danger, angry customers, billing disputes and anything outside its script. Those go straight to a person, with a written summary of the call.

  • Does the TCPA apply to an AI receptionist?

    Mostly to the outbound side. The FCC ruled in 2024 that AI-generated voices count as artificial voices, so AI callbacks to mobiles need prior express consent, and marketing calls need written consent. Quiet hours, Do Not Call and opt-out rules also apply. Take your own legal advice.

  • Can the AI receptionist speak Spanish?

    Our systems are built English-first. The usual options are routing Spanish speakers to a bilingual person, or building and testing a separate Spanish flow reviewed by a native speaker on your team. We tell you plainly what is achievable on the discovery call.

  • Should callers be told they are talking to an AI?

    Yes. Say it at the start of the call. Callers mostly care that they get booked quickly, and being upfront avoids complaints later.

Understand what is worth solving.Build what is needed to solve it.

Get started