Claude Project: Your Personal Insurance CSR Assistant

What This Builds

You'll build a Claude Project that acts as a knowledgeable insurance CSR colleague — one who already knows your agency's procedures, common carrier rules, coverage details, and communication style. Instead of re-explaining your context every time you open Claude, your assistant is always ready. New CSRs can ask it basic questions without pulling a senior CSR away from calls; experienced CSRs can use it to draft letters, look up coverage rules, and handle edge cases faster.

Prerequisites

• Claude Pro account ({{tool:Claude.plan}} — {{tool:Claude.price}}) — Projects require a paid plan
• Your agency's procedures document or a list of common workflows (even rough notes work)
• 1-2 hours to set up and test

The Concept

A Claude Project is like a persistent AI coworker you've trained before they start. You give it documents, instructions, and context once — and every conversation within that Project automatically starts from that shared knowledge. Unlike a regular Claude chat (where you re-explain yourself each session), the Project remembers everything you've loaded. Think of it as hiring someone who already completed their onboarding before picking up the phone.

Build It Step by Step

Part 1: Create the Project

1. Log into Claude at {{tool:Claude.url}}
2. In the left sidebar, click Projects (below your recent conversations)
3. Click Create Project
4. Name it: "CSR Assistant — [Your Agency Name]"
5. You'll see an empty project workspace

What you should see: A Project space with a document upload area and a "Project Instructions" field on the left, and a conversation area on the right.

Part 2: Write your Project Instructions

The Project Instructions are the most important part — this is what tells Claude who it is and how to behave. In the Project Instructions field, paste and customize this:

You are a knowledgeable insurance customer service assistant for [Agency Name], an independent insurance agency specializing in [personal lines / commercial lines / both].

Your role is to help our CSR team:
- Draft professional emails, letters, and AMS activity logs
- Explain insurance coverage terms and policy language in plain English
- Answer common procedural questions about our workflows
- Help with renewal outreach, endorsement confirmations, and complaint responses

Communication style: Professional but warm. Use language a client without insurance knowledge can understand. Never use jargon without explaining it.

Important: You do not make final coverage decisions. When a CSR asks whether something is covered, provide the relevant policy language context and suggest they confirm with the carrier or a licensed agent. Never state definitively that something is or isn't covered without indicating this should be verified.

Our agency uses [Applied Epic / AMS360 / HawkSoft] as our agency management system.
Our main lines of business: [list your lines — auto, home, commercial, life, etc.]

Part 3: Upload reference documents

Click Add content (or the document upload button) and upload any of these that you have:

High value to upload:

• Your agency procedures manual (even a basic one)
• A list of carriers you work with and their key appetite rules
• Common coverage FAQ document if you have one
• ACORD form reference guides

Good to include:

• Sample emails the agency has approved for common situations
• A list of coverage terms and plain-language definitions your team uses
• State-specific requirements if applicable (e.g., state-mandated coverage disclosures)

Format tip: Even rough notes work. You can paste a list of bullet points directly into a document in Claude (click "Add text content" instead of uploading a file) — it doesn't need to be polished.

Part 4: Test and refine

Start a conversation within the Project (click New Conversation inside the Project). Test these scenarios:

1. "Draft a confirmation email: I added a 2024 F-150 pickup to John Miller's personal auto policy today. Premium went up $28/month. Effective today."
2. "A client is asking if their HO-3 covers damage from a slow roof leak they didn't notice for 6 months. What should I tell them?"
3. "What's the difference between actual cash value and replacement cost coverage? Explain it like I'm telling a confused 65-year-old client."

What good output looks like: For #1, a ready-to-send email. For #2, a balanced answer that explains the likely exclusion (gradual damage) while noting it should be confirmed against the actual policy. For #3, a plain-language analogy that's actually clear.

If the output isn't right: Go back to Project Instructions and add more specific guidance. If emails are too formal, add "Write in a friendly, approachable tone — not stuffy." If explanations are too long, add "Keep explanations to 2-3 sentences unless asked for more detail."

Real Example: New CSR Onboarding

Setup: Agency has 3 CSRs, recently hired a 4th who is new to insurance. Senior CSRs spend 2+ hours/day answering basic questions.

How they used it:

• Project Instructions include agency procedures, carrier list, and a "common questions" document
• New CSR bookmarks the Project URL and uses it for every question during their first 3 months
• Questions like "how do I process an address change in Epic?" and "what's the difference between HO-3 and HO-5?" get answered instantly

Input: "I need to process an address change for a homeowners client. What steps do I take in Applied Epic and do I need to notify the carrier?"

Output: Step-by-step guidance based on the procedures document, with a reminder that the carrier will receive a download confirmation.

Time saved: Senior CSRs reclaimed 60-90 min/day during the new hire's first 3 months.

What to Do When It Breaks

• Output is too generic → Go back to Project Instructions and add more specific context about your agency type, clients, and tone preferences
• Claude doesn't "remember" something you told it → The conversation memory only works within a single conversation — if you start a new chat in the Project, you start fresh (but Project Instructions always apply)
• File uploads aren't being referenced → Test by asking: "What does our procedures document say about [specific topic]?" If it can't find it, try uploading the document as a text paste instead of a file
• Coverage answers feel too cautious → Add to Project Instructions: "When explaining coverage concepts, give your best answer based on standard policy language while noting the CSR should confirm the specific policy"

Variations

• Simpler version: Skip the document uploads and just use the Project Instructions template — the context-setting alone significantly improves outputs
• Extended version: Add a "carrier appetite cheatsheet" document listing which carriers accept which types of risks — the assistant can help route new business submissions to the right carrier

What to Do Next

• This week: Build the project, add at least 2-3 reference documents, and use it for 10 real tasks
• This month: Share the project with your team — everyone on the CSR team can use the same Project, and it improves with more documents added
• Advanced: Add carrier-specific form guides so the assistant can help CSRs navigate complex endorsement requests without calling the carrier helpdesk

Advanced guide for insurance customer service representatives. Claude Projects require a paid Claude subscription. Review all AI-generated coverage explanations against actual policy language before communicating to clients.