All use cases
Phones & Booking

A roofing owner says he'd let AI answer his phone for inspection bookings, but not for the leak call

His line: booking inspections, sure. The water-coming-through-the-ceiling call needs a person. Replies added the fix he liked: a short list of trigger words that skip the calendar and ring a human.

Real storyDone with AI phone answering (no specific product named)
TradesAll trades

What they did

Hunter Lapeyre, whose X bio says "I run a roofing company and generate leads," posted on November 4, 2026: "Would I let an AI answer my roofing phone? For booking inspections, sure. For this call, nah," with a meme of an emergency call. When a reply joked about a homeowner whose house was already flooded, he answered: "It'd cheerfully book them an inspection for next Tuesday." Replies suggested the same split in practical terms. One said: "let it take messages and book inspections, and give it a few trigger words ('leak', 'collapsed', 'water coming in') that ring your cell right away. Start with after-hours calls only and read the call log every Friday." Another: "Keep a short list of words that skip the calendar and go straight to a person: leak, water coming through, tree on the roof."

How it went

This is an owner's line in the sand, not a rollout report. He didn't say which product he would use or share call numbers. On the trigger-word idea he replied: "This is good workaround - can't wait until it's just good enough all the way around." Several replies came from accounts that sell AI phone tools, so read the setup advice as suggestions, not results.

Worth knowing

The risk he's pointing at is real: an AI receptionist that treats every caller the same will politely book a next-week inspection for someone with water pouring in. Before you turn one on, write down which calls must go to a person (active leaks, storm damage, anything structural, an angry customer) and test them with real phrasing, like "my ceiling is dripping" and "a tree came through the garage." Start with after-hours only and read every call summary for the first few weeks.

Try it yourself

You are setting up call rules for an AI phone receptionist at a small Wisconsin roofing company. Your job is to separate calls the AI may book from calls that must go to a person right away. You draft rules only; the owner approves them. TASK: Build an emergency trigger list, a booking script for routine inspections, and a test-call list. CONTEXT (fill in the [BRACKETS]): - [BUSINESS]: Example: Lake Country Roofing (fictional), Oconomowoc, WI - [SERVICES]: Example: residential re-roofs, repairs, storm inspections, gutters - [WHO GETS EMERGENCIES]: Example: owner's cell 6am-10pm, on-call foreman after 10pm - [INSPECTION SLOTS]: Example: weekdays 9am, 11am, 2pm; Saturdays 9am in storm season - [THINGS WE NEVER SAY ON THE PHONE]: Example: no prices, no insurance-coverage promises, no arrival guarantees - [SEASON NOTES]: Example: ice dams Jan-Mar, hail May-Aug STEPS: 1. List the trigger words and phrases that must skip booking and go to [WHO GETS EMERGENCIES] right away. Include plain homeowner phrasing (for example "my ceiling is dripping"), not just trade terms. Include [SEASON NOTES] items. 2. For each trigger, write the exact handoff line the AI says and what it texts to the on-call person (name, address, callback number, the caller's words). 3. Write the booking script for routine inspections using only [INSPECTION SLOTS]. Collect name, address, callback number, roof age if known, and what they noticed. 4. List what the AI must not say, using [THINGS WE NEVER SAY ON THE PHONE]. 5. Write 12 test calls: 6 that must hand off and 6 that should book. Include tricky ones, such as a calm caller describing an active leak. RULES: - When unsure whether a call is urgent, treat it as urgent and hand it off. - Never invent prices, insurance outcomes, warranties, or arrival times. - Mark anything you need from me as NEEDED. OUTPUT FORMAT: Part A: trigger list (table: phrase | why urgent | handoff line). Part B: booking script. Part C: do-not-say list. Part D: 12 test calls with expected result. FOLLOW-UPS TO TRY NEXT: - "Rewrite the handoff text so the foreman can read it in 5 seconds." - "Add storm-week rules for when inspection requests triple." - "Turn the 12 test calls into a Friday call-log review checklist."

Want help getting this working? Rise Systems in Oconomowoc sets these up.

Want this running in your business without the DIY? Rise Systems in Oconomowoc sets these up.

Free 15-minute AI check-up
Read the original

Source: X (Twitter) · November 4, 2026

Related