What do insurance policyholders contact you about?
Most policyholder contacts ask for a fact that already lives in your policy, billing or claims system. Agent resolves those once it can read the record. Anything that turns on coverage, money or a dispute belongs with licensed staff or adjusters.
| Conversation type | Can Agent resolve it? | Hand off when | Data Agent needs |
|---|---|---|---|
| Proof of insurance and auto ID cards | Yes, after verifying the policyholder | The policy is lapsed or pending cancellation, or an SR-22 or other state filing is needed | Policy status, ID card file |
| Declarations page or policy copy | Yes, for the current term | A certified copy is requested, or an attorney or other third party is asking | Document store, term dates |
| Amount due, due date, payment link, autopay | Yes | A payment failed inside a pending-cancellation window, or the policyholder asks for a hardship arrangement | Billing balance, installments, cancel date |
| Certificate of insurance | Partly: standard certificates for holders on file | The contract asks for additional insured status, a waiver of subrogation or custom wording | Certificate template, holder list, endorsements |
| Endorsement: add a vehicle or driver, change address, add a mortgagee | Collects and routes; never binds | Always, once details are complete | VIN or driver details, effective date |
| Claim status | Yes: stage, adjuster, last update, missing documents | A valuation or denial is disputed, an attorney or injury is mentioned, or the file has gone quiet | Read access to the claims system |
| First notice of loss | Partly: captures the details and creates a dated record | Someone is injured, the home is unsafe, or the policyholder asks if it is covered | Your FNOL fields, claims API or webhook |
| "Am I covered if...?" | No | Always, to a licensed agent or the claims team | Policy summary only |
| Renewal date and premium | Partly: confirms what the renewal offer shows | The policyholder asks why the premium changed or wants a new quote | Renewal offer |
| Cancellation request | Collects and routes | Always; return premium comes from your policy system | Requested date and reason |
"Collects and routes" still saves work: the endorsement or cancellation request reaches your team with the policyholder verified and the VIN, dates or contract attached.
What does an AI procedure for claim status look like?
Claim status is the insurance version of "where is my order", except it runs for weeks. Homeowners in J.D. Power's 2026 property claims study waited 40.7 days on average for final payment, as reported by Insurance Journal, and quiet stretches in that window produce "what is happening with my claim?" messages. A claims team could write the procedure for Agent like this.
Example procedure: claim status
- Verify the person with the claim number plus the ZIP code and date of birth on file, or the logged-in portal account. After two failed attempts, hand off.
- If they are a third-party claimant, share only their own claim's status, never the insured's policy details.
- Read the claim: stage, adjuster, last activity date, outstanding documents, payments issued.
- Explain the stage and next step in plain words, and list missing documents with the upload link.
- Report any payment exactly as the claims system shows it. Never estimate a settlement or promise a date.
- If the last adjuster activity is more than 10 business days old, create a callback task through the claims webhook, due in one business day, and post the claim number to the claims Slack channel.
- Hand off at once on: attorney, department of insurance, bad faith, denial, injury, total loss valuation, or two negative messages in a row.
- Never say what is covered, never change claim data. Spend limit: $0.
Example conversation
Policyholder: It has been three weeks since the hailstorm. What is happening with my roof claim?
Agent: I can check. Please confirm your claim number and the ZIP code on the policy.
Policyholder: HO-2291-0457, 73112.
Agent: Thanks. Your claim is in estimate review with your adjuster, Dana, who received your contractor's estimate on September 22. Photos of the interior ceiling are still needed; you can upload them here. Because the file has had no update for 10 business days, I have asked Dana to call you by tomorrow afternoon.
Policyholder: Will they pay for the gutters too?
Agent: I can't tell you what your policy covers, but I have passed that question to Dana so she can answer it on her call.
Dana receives the conversation, the claim record Agent read and the task it created.
What guardrails does an insurance AI agent need?
Agent is configured to state what the policy and claims records show and route everything else, so it never interprets coverage or changes a policy, and your FNOL procedure can record each loss report with a date the day it arrives. The rest is configuration you write in plain language.
What Agent must never do
- Discuss coverage terms. The NAIC Producer Licensing Model Act treats conferring with or advising a buyer on a policy's benefits, terms or conditions as negotiating insurance when done by someone who sells or obtains insurance, which is licensed work. Agent states facts on record and routes the question.
- Quote, bind or recommend coverage. These go to a licensed producer.
- Give financial or legal advice, including whether to file a claim or accept a settlement.
- Move money. Return premium and claim payments come from your systems and staff.
What triggers a handoff
- Keywords such as attorney, sue, bad faith, complaint, fraud, injury or deceased.
- Customer tier, so flagged commercial accounts go straight to their account manager.
- Negative sentiment or distress after a serious loss.
- Coverage, cancellation, quotes, subrogation and anything Agent cannot verify.
Loss reports are on a clock
The NAIC property and casualty claims settlement model regulation gives insurers 15 days to acknowledge a notice of claim and treats notice to an insurer's agent as notice to the insurer. State rules differ, but a chat saying "a tree fell on my garage" is a claim notice even on an agency's website. Agent should record it with a date and route it the same day.
Data handling
Write procedures so Agent verifies identity before revealing policy or claim data and never asks for full card or Social Security numbers; Agent acts only through connector permissions you can revoke. The NAIC Insurance Data Security Model Law expects licensees to use due diligence when choosing third-party service providers, so put Aftersales through your vendor review: it offers a GDPR data processing agreement and hosts data in the US. Health plans, including Medicare supplement insurers, are HIPAA covered entities; Aftersales offers HIPAA support with a signed BAA on the Enterprise plan, and Scale adds SSO. The NAIC model bulletin on insurers’ use of AI also asks carriers to govern AI they buy from third parties, and your procedures, escalation rules and Monitors results document how Agent is controlled. Aftersales does not make you compliant. Share your procedures, escalation rules and Monitors reports with compliance during vendor review.
Which channels matter most for insurance customer service?
Phone and email carry the heaviest insurance conversations; chat and text absorb the routine ones.
- Phone. Serious losses still arrive by call. Growth and Scale include warm and cold transfers, recording consent and per-brand numbers, useful for an MGA running several programs.
- Email. Contractors, landlords and lenders send certificate requests with contracts attached.
- Portal chat. The natural home for after-hours ID cards, payment links and claim status.
- SMS. Good for claim updates, but outbound texts need consent under the TCPA (see the FCC's guide to robocalls and texts), so start with replies.
- WhatsApp. Expected in many markets outside the US. Agent replies in 31 languages.
- Slack Connect. MGAs can answer producing agencies in shared channels inside the same Inbox queue.
Which insurance systems should the AI agent connect to?
Connect policy administration, billing and claims first; read access to those covers most of the table above. Permissions are explicit per connector, so claims access can stay read-only while FNOL intake writes one new record.
| System | What Agent reads or does | How it connects |
|---|---|---|
| Policy administration system | Status, term dates, ID cards, declarations | Aftersales API or webhooks |
| Billing system | Balance, due dates, pending-cancellation dates, payment link | Aftersales API or webhooks |
| Claims system | Stage, adjuster, payments; creates the FNOL record | Aftersales API or webhooks |
| Agency management system | Client and policy records, activity notes | Aftersales API or webhooks |
| Salesforce, Zendesk or Freshdesk | Existing records; Agent can also run inside them | Named integrations |
| Slack | Side conversations with claims or underwriting | Named integration |
| Stripe | Only if you collect premium through it | Named integration |
Core suites and agency systems vary, so confirm specific connectors on a call. Put billing rules and claims FAQs in Knowledge so Agent, staff and the help center answer from one source.
What does AI customer service cost for an insurance team?
A mid-sized agency or MGA service team would pay about $2,368 a month at list prices, roughly $0.59 per conversation, on these assumptions:
- 8 service reps on Growth, billed annually, and 4,000 conversations a month.
- Agent resolves 40%, well below the 71% median Aftersales customers reach after 90 days, because coverage, cancellations, quotes and disputes go to people.
- Copilot for every rep; 6 licensed producers who only review and approve.
| Line item | Calculation | Monthly cost |
|---|---|---|
| 8 service seats on Growth | 8 × $69 | $552 |
| Agent resolutions | 1,600 × $0.99 | $1,584 |
| Copilot for 8 reps | 8 × $29 | $232 |
| 6 producers as Lite seats | Included on Growth | $0 |
| Total per month | $2,368 |
Conversations Agent cannot help with are free. Carriers needing SSO would pick Scale at $109 per seat ($872 for 8); a BAA requires the Enterprise plan. Teams staying in Salesforce Service Cloud, Zendesk or Freshdesk can use Agent on its own: $0.99 per resolution, a minimum monthly commitment and no seats. See pricing.
How do you roll out an insurance AI agent in 30 days?
Start read-only on one line of business, prove it, then widen.
- Week 1. Tag three months of conversations by intent and pick three types, usually ID cards, billing and claim status. Connect read access and agree the handoff list with licensed staff and compliance.
- Week 2. Write procedures or import macros. Replay past conversations and have a licensed reviewer flag any answer that drifts toward coverage. Draft FNOL intake, but hold it until claims leadership signs off.
- Week 3. Go live on portal chat and email, after hours first, for one line such as personal auto. Run Monitors on every conversation.
- Week 4. Add FNOL intake, certificates and SMS replies. Report resolution rate and handoff reasons to compliance, defined as in our resolution rate guide.