Lesson 9 of 15 · 6 min

Insurance-claim questions: what the AI must hand to a human

Know which insurance-claim questions the AI must hand to a human.

Read the lesson

Goal: Set clear limits on what the roofing AI says about insurance, and route every claim question to a person.

You need: A live voice agent, Quick answers, and the client's own insurance wording in writing.

Why this matters

Insurance is the hardest part of storm roofing. Homeowners ask what their policy covers, who pays the deductible, and whether the roofer will meet the adjuster. These are fair questions. They are also questions the AI must not answer.

A wrong answer about coverage can cost the homeowner money. It can also put the roofer in legal trouble. Rules about claims and deductibles differ by state. Some promises a roofer might make are not allowed in some states. The client and its advisors decide what anyone at the company may say.

So the AI's job is narrow. It books the inspection. It says, in the client's words, that a person handles insurance questions. It makes sure a person calls back.

That is not a weak answer. The homeowner hears that the company has a real person who knows claims. That builds trust.

Size changes the setup:

  • Owner-operator. The owner handles every insurance callback. Keep the task list short and dated.
  • Fleet (Summit Roofing). A project manager or insurance specialist owns these tasks. Route to that person.
  • Multi-location. Each location may have its own specialist and its own state rules.

What the AI may do, and what it hands off

Draw the line in writing with the client.

The AI may book an inspection and take the name, address, damage and a time. It may read the client's insurance line, create a callback task and say a specialist will call. A person handles what a policy covers, deductibles, claims, claim numbers and the adjuster meeting. A person also handles contract terms and payment from insurance.

Fig 1

The AI's insurance line

The AI may
  • Book an inspection
  • Take name, address, damage and a time
  • Read the client's insurance line
  • Create a callback task
  • Say a specialist will call
A person handles
  • What a policy covers
  • Deductibles and who pays them
  • Claims and claim numbers
  • Meeting the adjuster
  • Contract terms and insurance payments
The AI books and hands off. People answer claim questions.

The client writes the insurance line. Each client writes its own, like emergency wording. SAU gives no standard wording. Use this template, and the client fills every bracket:

There is no price guard or topic guard setting. You enforce the line with the voice instructions and Quick answers. Then you prove it with tests.

Fig 2

An insurance question on a call

  1. Caller asks about coverage or a claim
  2. Agent reads the client's line word for word
  3. Does the caller want a person right now?YesBusiness hours: Transfer to your team. After hours: a clear callback timeNoOffer an inspection time
  4. Create a follow-up taskOwner: the insurance specialist
  5. The specialist calls back the same day
Every insurance question ends with a person and a callback time.

Build it in ServiceAgent

  1. Get the client's insurance topics and approved line in writing. File the copy.
  2. Open Voice Agents, then the agent, then Basics. Add a rule: "Never discuss coverage, deductibles, claims or adjusters."
  3. Paste the template, with the client's words, into the voice instructions.
  4. Open Knowledge → Quick answers → Add FAQ. Add the approved line as the answer to common insurance questions.
  5. Open Actions → Allowed actions. Turn on Create a follow-up task.
  6. Open Follow-up. Attach "When Call ended then Create CRM Task". Set the specialist as the task Owner.
  7. Open Test & publish → Practice conversation. Type ten insurance questions, including pushy ones.
  8. Read every answer. Any coverage claim is a fail. Fix the instructions and test again.
  9. Click Publish.

Check it works: In a browser test, ask whether insurance will pay for the whole roof. The agent must read the client's line, offer a time, and create the task.

Worked example: Summit Roofing

After a storm, Summit's AI takes 120 calls on the first day. These are example inputs.

  • 20% of callers ask an insurance question: 120 × 20% = 24 callers.
  • Each gets a callback task for the project manager.
  • Each callback takes about 6 minutes: 24 × 6 = 144 minutes.

That is 2 hours and 24 minutes of calls on day one. The project manager needs that time blocked before the storm week, or tasks pile up.

Fig 3Example numbers

Callback load on storm day one

Insurance callers: 120 × 20%24
×Minutes per callback6
Callback time144 minutes, about 2.4 hours
Block the specialist's time before the storm, not after.

Now the risk on the other side. Say the AI had guessed coverage on just 1 call in 24. That one call could create a dispute worth more than the whole job. The handoff costs 144 minutes. A dispute costs far more.

The AI time also stays low. Reading the line and offering a time adds well under a minute to a call. A long coverage discussion would add several minutes at 15 credits each.

Reviewing transcripts after go-live

The test calls prove the agent can follow the rule. Real callers prove whether it does. In the first two weeks, read every call where insurance came up.

Search the transcripts for words like "covered", "deductible", "claim" and "adjuster". For each call, ask three questions. Did the agent read the client's line? Did it avoid any guess? Did a task get created with the right owner?

If the agent slipped, find the caller's exact words. Add them as a new test in Practice conversation. Tighten the voice instructions, test again and publish.

Also check the callback side. Open the specialist's tasks and count how many are overdue. A perfect AI handoff fails if nobody calls back. If tasks pile up, the client needs more callback hours, not a different script.

Fig 4

Transcript check for insurance calls

  • Search for covered, deductible, claim and adjuster
  • Did the agent read the client's line?
  • Did it avoid any guess about coverage?
  • Was a task created with the right owner?
  • Are the specialist's callback tasks on time?
Do this for every insurance call in the first two weeks. A slip becomes a new test.

When a caller is upset

Storm callers are often stressed. Some get angry when the AI will not answer a coverage question. The client's line should say what happens next, and when. "Our insurance specialist will call you today" calms more people than "someone will be in touch".

If the caller asks for a person right now, the agent can use Transfer to your team during business hours. After hours, the task and a clear callback time do the job.

Fig 5

A stressed storm caller

  1. CallerWill insurance pay for my whole roof? I need to know.
  2. AI agent[CLIENT'S APPROVED INSURANCE LINE] Our insurance specialist will call you today.
  3. CallerFine. But I want a real answer.
  4. AI agentI understand. I can also book your inspection. Is Thursday at 10 am good?
  5. noteTask created for the specialist, due today
Say what happens next, and when. A clear callback time calms more people than a vague promise.

Common mistakes

  • Writing the insurance line yourself. Fix: the client writes it with its advisors. You paste it word for word.
  • A friendly guess. Fix: "Most policies cover hail" is still a coverage claim. Ban it in the instructions and test for it.
  • No owner for the callback. Fix: every insurance task names one person and a due date.
  • No time blocked for callbacks. Fix: plan the specialist's callback hours before storm season.
  • Testing with polite questions only. Fix: test pushy and emotional callers too.

Do this now

Send the client the insurance template with blank brackets. Ask for the topic list, the approved line and the callback owner. When it returns, build it in a draft and run ten typed tests in Practice conversation.

Practice the conversation

  1. Owner People always ask if insurance will pay. My guys know that stuff.
  2. Operator Good. Then your guys answer it, not the AI.
  3. Owner Will the AI just say "I don't know"?
  4. Operator No. It reads a line you write, books the inspection, and makes a callback task.
  5. Owner Who writes that line?
  6. Operator You do, with your advisors. Rules on claims differ by state, so it must be yours.
  7. Owner How many callbacks are we talking?
  8. Operator On a storm day, maybe 24. That is about two and a half hours for your project manager.
  9. Owner I can block that.
  10. Operator I will set them as the owner on every insurance task.

Quick check

  1. Who writes the line the AI reads when a caller asks about insurance?
    • The Operator, from an SAU template with fixed words
    • The client, with its advisors
    • The AI, based on the policy the caller describes
    • The insurance company
  2. A caller asks, "Will my deductible be covered?" What does the agent do?
    • Explain how deductibles usually work
    • Say the roofer often helps with deductibles
    • Read the client's line, offer a time and create a callback task
    • Transfer the call to the adjuster
  3. 150 storm callers reach the AI. 20% ask insurance questions. Callbacks take 6 minutes each. How long is the callback work?
    • 90 minutes
    • 150 minutes
    • 180 minutes
    • 300 minutes

ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.

Learn

Get certified

Community