Get started

Answer the next service call—even when the team is already in the field

For a plumbing, HVAC, electrical, roofing, landscaping, cleaning, or repair business, the phone is often the front door. Calls arrive while technicians are driving, working in a home, or speaking with another customer. A missed call can mean an unbooked job, while a rushed answer can leave dispatch without the address, equipment details, or access notes it needs. The pattern is worst exactly when the business is busiest: the first cold snap or heat wave fills the queue with urgent calls, and the callers who cannot get through phone the next company on their list.

ThunderPhone gives a home-service business an AI phone agent that can answer every routed call, collect consistent job information, schedule through connected tools, and escalate according to the business's service area and urgency rules.

Move from “What did the caller say?” to a complete job record

A home-services agent can be configured to:

  • identify the service needed and confirm the service address;
  • collect contact details, property type, equipment or appliance information, and a concise problem description;
  • check whether the address is inside the service area;
  • offer approved appointment windows through a connected calendar or dispatch API;
  • explain approved fees, warranties, preparation steps, and business hours from a knowledge base;
  • route priority jobs to an on-call dispatcher;
  • capture complete after-hours leads; and
  • follow up on estimates, appointments, or completed work through compliant outbound calls.

The agent should not give unsafe repair instructions. You define the questions it asks and the conditions that require a human or emergency-service referral.

Sample home-service call flow

Agent: Thank you for calling Summit Home Services. Are you calling about plumbing, heating and cooling, electrical work, or another service?

Caller: Heating. The furnace stopped working this morning.

Agent: I can help schedule a visit. Before we continue, do you smell gas, see smoke, or have an active carbon-monoxide alarm?

Caller: No.

Agent: Thank you. What is the service address and the best number for appointment updates?

Caller: 90 Grove Avenue, and this number is fine.

Agent: That address is in the service area. I have openings today from 2 to 4 p.m. and tomorrow from 8 to 10 a.m. Which would you prefer?

Caller: Today.

Agent: I have scheduled the 2 to 4 p.m. window and will send the approved preparation instructions. The technician will use this number for arrival updates.

If the caller had reported a configured safety trigger, the agent would stop ordinary scheduling and deliver the company's approved emergency instruction or transfer path. For a reported gas smell, for example, many companies script the agent to advise the caller to contact emergency services or the gas utility in line with company policy, and only then handle dispatch or escalation. The agent follows the script the company wrote; it does not improvise safety advice.

Where an AI phone agent fits in a home-service operation

Emergency versus routine triage

Dispatchers separate a no-heat call in January from a springtime tune-up request in the first minute, and an agent can be configured to run the same written checklist: safety symptoms first, then season and severity, occupant circumstances the company chooses to ask about, and whether the caller is on a service agreement. Calls that meet the company's urgency criteria route to the on-call transfer path; everything else books into a normal window. The checklist lives in the prompt, so changing the triage policy is an edit, not a retraining project.

After-hours answering

Evening and weekend callers reach the same agent, not a voicemail box. It collects a complete lead—service, address, problem description, callback number—books within whatever after-hours availability the business allows, and escalates only the conditions the company defined as worth waking someone for.

Booking with service windows

Instead of promising exact times, the agent offers the arrival windows a connected calendar or dispatch API actually exposes, confirms the choice back to the caller, and records access details such as gate codes, lockbox notes, or pets on the property. Because it only sees approved appointment types and windows, it cannot overbook a route or invent a slot the schedule does not have.

Quote-request intake

For estimate-driven work such as roofing, landscaping, or a system replacement, the agent collects the scope, property details, timeline, and budget questions the sales team wants answered before a visit, then schedules the estimator or routes the record to the right person. Every estimate request arrives in the same structure instead of as a sticky-note summary.

Missed-call win-back

A caller who hangs up in the queue was still a lead a moment ago. The business can trigger an outbound call back to its own abandoned callers, or to fresh web-form leads who consented to a callback, while the request is still warm, using campaign retries and voicemail detection so a first no-answer does not end the attempt. Outbound calling stays limited to the company's own customers and consented leads, and the organization defines consent, identification, and calling-window rules for all outbound use.

Dispatch coordination and technician ETA calls

Job-status changes in a connected system can trigger outbound calls through the API: the technician is en route, running late, or needs the homeowner to confirm someone is home. If the customer answers and needs to reschedule, the agent can rebook on the same call instead of starting a phone-tag cycle with the office.

Seasonal maintenance-plan outreach

When tune-up season approaches, an outbound campaign can work through the maintenance-plan list, remind each member the visit is due, and book a window on the spot. Voicemail detection can leave the configured reminder message, and the campaign's retry policy governs additional attempts, so the office is not hand-dialing hundreds of renewals during its quietest revenue weeks.

Membership and service-agreement questions

Plan documents in the knowledge base let the agent answer what a membership covers, what a visit costs with and without it, and how renewal works—using the company's own language. With a connected lookup tool it can also check a specific caller's membership status before applying priority-scheduling rules.

Parts and job-status updates

“Is my part in yet?” calls can be answered from a connected system lookup rather than a callback promise, and an arrival of a backordered part can trigger an outbound call to book the return visit. Callers whose status question the systems cannot answer route to a person instead of receiving a guess.

Review and follow-up calls after the job

A post-job follow-up call can first confirm the work was completed to the customer's satisfaction. An unhappy customer routes to a manager while the problem is still fixable; a satisfied one hears whatever review invitation or closing message the company approved. The same pattern works for estimate follow-ups that would otherwise fall through the cracks.

Bilingual homeowner communication

One number can serve a mixed-language customer base. The agent starts in the primary language, switches when a caller uses a configured additional language, and keeps the same triage, booking, and escalation logic in every language it speaks—useful for shops that win or lose work based on whether anyone bilingual happens to be near the phone.

Features that matter to a home-service operation

Fast qualification without a rigid phone tree

The agent can ask different questions based on the service, property, and caller's answers. Dispatch receives the fields it needs without making every caller listen to the same menu.

Your numbers, inbound and outbound

Production numbers can be brought in through supported direct VoIP connections or manual SIP configuration for any SIP trunk, so the business keeps the numbers customers already know. Verified imported numbers support both inbound answering and outbound campaigns, and the agent can place callers on hold or navigate keypad phone menus when a workflow requires it.

Scheduling and dispatch actions

Connect a calendar, dispatch system, CRM, or custom API. The agent can use only the operations that connection exposes, such as checking availability, creating a job, or recording a lead. Remote MCP servers can be attached for automatic tool discovery, and HMAC-signed webhooks push call events—complete with structured outcomes—into whatever system the office already watches.

Service-area and policy knowledge

Attach service-area rules, business hours, warranty language, approved pricing explanations, and preparation instructions as text, PDF, or DOCX documents (up to 5 MB per text file and 50 MB per PDF or DOCX), or import pages from the company website by URL. The agent searches those sources during the call and routes questions the material does not answer.

Multilingual conversations

ThunderPhone supports 47 voice languages. Configure a primary and additional languages so one number can serve callers who switch languages mid-conversation, using a voice that supports the selected set.

Transfers that preserve context

Cold transfer routes immediately. Warm transfer, available on eligible production VoIP or SIP numbers, lets the agent keep the caller on hold while it briefs the dispatcher privately. If the dispatcher cannot take the call, the agent returns to collect a message or offer the configured next step.

A website channel on the same brain

An embeddable web widget lets homeowners start a voice conversation from the company website. Widget sessions run on the same agent and produce the same transcripts and records as phone calls, so a “request service” click and a phone call land in the same pipeline.

Reviewable calls and repeatable tests

Review transcripts, recordings when enabled, and graded call logs, then turn recurring failure cases into simulations. Useful tests include out-of-area callers, duplicate bookings, warranty disputes, safety triggers, unavailable dispatchers, and callers who do not know their equipment model. Regression suites with pass-rate gates catch prompt changes that break the triage script, and A/B experiments compare greeting or booking variations on live traffic before rolling them out.

What would this cost each month?

Suppose a growing service company handles 1,800 AI-assisted calls per month, averaging 2.5 minutes each:

1,800 calls × 2.5 minutes = 4,500 minutes per month

  • Spark: 4,500 × $0.02 = $90/month
  • Bolt: 4,500 × $0.05 = $225/month
  • Storm: 4,500 × $0.09 = $405/month

That is base engine usage, not a quote. Premium voice or language paths can add up to 3¢ per minute, and phone-number or carrier charges depend on the telephony setup. Hold time bills a flat 2¢ per minute; voicemail and phone-menu minutes bill at the engine rate. Optional add-ons such as verbal acknowledgements, call supervision, and long prompts carry their own published surcharges. The agent builder shows the current all-in rate before calls are placed.

Guardrails the company controls

  • Safety scripts are written, not improvised. Gas smells, smoke, and carbon-monoxide alarms trigger the company's approved emergency instruction or transfer path before any scheduling; the agent never gives repair or safety advice of its own.
  • No invented prices or promises. Fees, warranty answers, and arrival commitments come from approved material and connected systems; anything outside them collects details and routes to a person.
  • Service-area and booking rules are enforced as configured. The agent offers only the appointment types and windows the schedule exposes and cannot invent a slot.
  • Outbound stays on the company's own lists. Callbacks and campaigns run only against the company's own customers and consented leads, under the consent, identification, and calling-window rules the company defines.
  • Customer data flows only where configured. What the agent may collect and which systems receive it are the company's decisions, exercised in testing before launch.

Compliance and customer data

ThunderPhone is GDPR and HIPAA compliant. The business remains responsible for configuring its own workflows appropriately—recordings and any required notices, consent for outbound calling, data retention, and what job or customer information the agent is allowed to collect and share through integrations.

Frequently asked questions

Can a ThunderPhone agent book service appointments?

Yes, when connected to a calendar or dispatch API that supports booking. The agent can collect the required fields, offer available windows, create the appointment, and confirm it back to the caller.

Can it tell whether a call is an emergency?

It can follow the company's written safety and urgency checklist. It should not diagnose a dangerous condition or improvise repair advice; configured triggers—such as a reported gas smell—should lead to the company's approved instruction, such as advising the caller to contact emergency services per company policy, followed by the defined escalation or dispatch step.

Can the agent check whether an address is in our service area?

Yes, if the service-area rules are available in the prompt, knowledge base, or a connected lookup tool. The agent can confirm the result before offering an appointment.

What happens after hours?

The agent can answer, collect a complete lead, book within allowed availability, or follow an on-call transfer policy. The business decides which services and conditions qualify for after-hours escalation.

Can it transfer high-value or urgent jobs to dispatch?

Yes. Use a cold transfer for immediate routing or a warm transfer on an eligible production number when the dispatcher should receive a private briefing before accepting the call.

Can it place reminder and follow-up calls?

Yes, through individual outbound calls or campaigns on an eligible production number, with voicemail detection and configurable retries. The organization is responsible for consent, identification, do-not-call requests, calling windows, and other applicable outbound-calling laws.

Does it work with our field-service or CRM software?

The agent calls the tools you connect: custom APIs, remote MCP servers with automatic tool discovery, and HMAC-signed webhooks that deliver call events and structured results to your systems. If your platform exposes an API for availability, jobs, or customers, those operations can be made available to the agent.

Can it handle Spanish-speaking callers on the same number?

Yes. Configure Spanish—or any of the 47 supported voice languages—as an additional language, and the agent can switch mid-call when the caller does, keeping the same booking and escalation behavior. The selected voice must support the configured language set.