All use cases
Quotes & Estimates

Explain the insurance claim process to collision customers

A plain-English claim guide, an FAQ, and a 'what to bring' list.

Playbook
Works forBDAuto body

Who it's for

Body shops whose customers are confused and stressed after an accident.

What you'll have at the end

A plain-English claim guide, an FAQ, and a 'what to bring' list.

Time and cost

30 minutes. Free.

Before you start

  • Your process with insurers and the DRP relationships you have

Step-by-step

  1. Open chatgpt.com (or claude.ai) and sign in.

    What you'll see: home screen

The prompt

0 copies

Fill these in

FieldWhat it meansExample
[BUSINESS NAME]your shop's name as customers know itLakeside Auto Care
[CITY]where you're located; used for local detailsOconomowoc, WI
[TONE]how you talk to customersfriendly, straight-talking, no jargon
[CLAIM TYPE]common claimsdeer hit (comprehensive), rear-ended (other driver's insurance)
[YOUR PROCESS]how you handle claimswe photograph, write estimate, work with any insurer
[RENTAL]rental car helpEnterprise next door
You are a collision repair advisor who has walked thousands of Wisconsin drivers through insurance claims. ## Context (fill in the [BRACKETS]) - [BUSINESS NAME]: your shop's name as customers know it. Example: Lakeside Auto Care - [CITY]: where you're located; used for local details. Example: Oconomowoc, WI - [TONE]: how you talk to customers. Example: friendly, straight-talking, no jargon - [CLAIM TYPE]: common claims. Example: deer hit (comprehensive), rear-ended (other driver's insurance) - [YOUR PROCESS]: how you handle claims. Example: we photograph, write estimate, work with any insurer - [RENTAL]: rental car help. Example: Enterprise next door ## Task Write a customer guide to the claim process. ## Steps 1. Explain the steps from accident to pickup. 2. Explain the difference for [CLAIM TYPE]. 3. Explain that the customer can usually choose their repair shop (tell them to confirm in their policy). 4. List what to bring. 5. Write a short FAQ. ## Rules - Never promise a specific price, total, or completion time unless I gave it to you above; say "we'll confirm" instead. - Use only facts I gave you. If something is missing, write [CHECK: ...] instead of guessing. - Write at about an 8th-grade reading level: short sentences, no jargon, explain any technical term in plain words. - Where it fits, use Wisconsin details naturally (winter, road salt, seasons, local towns), but don't invent local facts. - Not legal or insurance advice; tell customers to check their policy. ## Output format Numbered steps · differences by claim type · what to bring · FAQ (5 Qs). Under 450 words. ## Follow-ups to try next - "Make a text version." - "What if the insurer's estimate is low? Write that section." - "Make a counter handout."

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

Follow-ups

Make a text version.
What if the insurer's estimate is low? Write that section.
Make a counter handout.

What good output looks like

A stressed customer can follow it step by step.

If it goes wrong

  • Too legalistic: 'plain words, short steps.'

Level up

Shop management software can send status updates by text through the repair. Cons: cost.

Worth knowing

Don't make coverage promises. Insurers and policies vary.

Wisconsin angle

Deer collisions are common in Wisconsin, especially in fall.

Source: Wisconsin Trades AI editorial

Related use cases
Keep browsing
All 43 Auto body use casesAll 20 Quotes & Estimates use cases