Plumbing
Ask if water is active, what fixture or room is affected, whether a shutoff was attempted, whether photos are safe, and who should receive the callback. Do not diagnose or advise repairs.
View plumbing intakeContractor call script template
The script is where an AI receptionist either earns trust or loses it.
A good AI receptionist does more than sound natural. It asks the right contractor questions, refuses unsafe promises, captures missing job facts, and sends the owner a memo that makes the callback obvious.
Live call guardrails
OpenIdentify the business, collect caller and callback, then confirm the service need.
QualifyTown, issue type, urgency, active problem, access, safe photo, and customer status.
ProtectNo price, diagnosis, arrival, dispatch, safety, or insurance promise without approved rules.
HandoffSource, summary, missing facts, blocked promises, and the next owner action.
Copy the structure, not generic wording
A demo call sounds good. A real call script has to protect the business.
Competitor demos often prove that the agent can answer. Contractor owners need one more proof point: what the assistant asks, what it refuses to say, and what the team receives after the call.
Watch the handoff proofSample call: no-cool HVAC, 7:42 PM
Ask: town, system type, vulnerable resident, active issue, callback path
Say: I can collect details for the dispatcher to review
Do not say: we can be there tonight, price, diagnosis, or safety advice
Script map
Use this before a phone agent talks to live customers.
This is not a final legal or dispatch policy. It is the practical structure Cape Fear uses to turn contractor calls into owner-ready handoffs before deeper scheduling, CRM, or field-service writes.
| Script moment | Use this language pattern | Collect | Block |
|---|---|---|---|
| Greeting | Thanks for calling. I can collect details for the team so the right person can follow up. | Name, callback number, caller type, and source. | Pretending to be a licensed tech, owner, or dispatcher. |
| Service fit | What town is the job in, and what kind of service do you need? | Town, service address if appropriate, trade, issue type, and customer status. | Accepting work outside service area without review. |
| Urgency | Is this active right now, getting worse, or safe to review during business hours? | Active leak, no-cool risk, outage, blocked access, storm damage, or routine request. | Emergency advice, safety instructions, or dispatch claims. |
| Job facts | What happened, when did it start, and is there anything safe you can photograph? | Symptoms, timing, access, safe photos, equipment clue, affected room, or visible damage. | Diagnosis, repair instructions, or unsafe inspection prompts. |
| Scheduling | I can note your preferred window, but the office will confirm availability. | Preferred callback time, availability, constraints, and decision maker. | Arrival windows, technician assignment, or guaranteed booking unless approved. |
| Pricing | I can pass that question to the owner. I do not want to guess on price. | Budget concern, prior estimate, quote ID, or billing question. | Discounts, final quotes, diagnosis-based pricing, or insurance outcome. |
| Close | I have the details needed for review. The next step is a callback from the approved team contact. | Best callback path, missing facts, and permission to text or email when appropriate. | Final promise beyond the approved next step. |
Trade examples
Contractor scripts should change by trade and risk.
The same voice agent can sound polished in every demo and still fail the business if the script does not match the service call.
HVAC
Ask no-cool or no-heat status, system type if known, vulnerable-resident risk, thermostat clue, photo availability, and callback urgency. Do not promise same-night dispatch.
View HVAC intakeRoofing
Ask active drip, ceiling stain, storm timing, access, photo status, roof age if known, and safe callback priority. Do not give safety or insurance guidance.
View roof leak intakeRestoration
Ask source status, affected area, standing water, access, photos, rental or owner status, and urgent owner path. Do not promise mitigation or coverage outcomes.
View restoration intakeGarage door
Ask whether the door is stuck open or closed, car access, spring or opener clue, safe photo status, and callback window. Do not advise mechanical fixes.
View garage door intakeField-service software
Write the script before choosing the destination: owner memo, task, note, review queue, Jobber request, Housecall Pro job packet, or ServiceTitan dispatcher review.
View integration strategyOwner memo
The script is not done until the handoff is inspectable.
After the call, the owner should not receive a vague transcript. The useful output is a tight memo that separates facts, missing details, risk flags, blocked promises, and the next human action.
- source: Google Maps call, LSA, missed call, voicemail, form, or repeat customer
- caller: name, callback, town, customer status, and preferred follow-up path
- job: trade, issue, urgency, timing, access, safe photos, and missing facts
- guardrails: price, diagnosis, dispatch, safety, insurance, or arrival promises blocked
- next action: owner callback, office review, dispatcher queue, CRM note, or quote follow-up task
Prepare
Setup checklist
Turn the script into service-area, emergency, booking, transcript, and handoff decisions.
Use checklistTrust
Safe intake standard
Confirm data, photo, retention, integration, and promise boundaries before live launch.
Review trust rulesStart
Script review
Send one real missed-call path and get a contractor-safe AI receptionist script mapped.
Request script reviewFAQ
AI receptionist script questions.
What should a contractor AI receptionist script ask first?
Start with caller name, callback number, service address or town, job type, urgency, whether the issue is active, safe photo availability, and the best next human action.
Should the AI receptionist promise arrival times or prices?
Only when the contractor has approved exact rules and language. Otherwise the script should collect facts, avoid price, diagnosis, dispatch, safety, or arrival promises, and route the decision to the owner or dispatcher.
How does a call script become a useful handoff?
The script should end with a structured memo that includes source, caller, issue, urgency, missing facts, photos, blocked promises, and the next approved human action.
Script review output
QuestionsThe exact prompts the assistant should ask for the first workflow.
BoundariesThe phrases and decisions the assistant should route to a human.
HandoffThe owner memo, task, note, or queue format your team can inspect.