An insurance chatbot earns its place on an agency website by doing the front desk's first job well: answering what your public pages already say, and getting everyone else to a licensed person with the details that person needs. It should never quote a premium or decide what a policy covers. Here is where to draw that line, what to give it to read, and how Mo turns "can you quote my car?" into a request that already names the car.
What can an insurance chatbot do on an agency website?
An insurance chatbot is an AI assistant on an agency's website that answers approved public questions, collects a visitor's contact details once they ask for help, and forwards the request to the team for personal follow-up. It works for the agency in public, so it answers from the agency's own content and stops where advice begins.
Ultimo Bots is an AI agent that answers your visitors from your own pages and documents, forwards quote and callback requests to your team with the whole conversation, and runs skills you build with Mo in its AI Studio. It installs on Wix, WordPress, Webflow or any site that takes a short snippet.
Many pages on this topic are written for carriers. Lemonade, an insurer, says on its homepage (read October 28, 2026) that it uses AI "to craft the perfect policy for you, and to pay out claims." That is a carrier deciding about its own policies. An independent agency's website has a smaller job: what you offer, how to reach someone, and a request that a licensed person picks up.
The NAIC's overview of AI in insurance, last updated April 3, 2026, lists customer service next to underwriting, pricing, claims and fraud detection. Its model bulletin of December 2023, neither a model law nor a regulation, says consumer-impacting decisions made or supported by AI must comply with applicable insurance laws. It addresses insurers; check your state's rules and carrier agreements too. As of October 2026; practical guidance, not legal advice.
Insurance chatbot use cases, sorted by the next step
Group questions by what the visitor needs next, not by topic. "Home insurance" can be a service question, a request for advice or a question about an existing policy, and the words alone do not tell the agent which answer fits. Six typical questions at an independent agency:
Keep the promises exact. Sharing a carrier's published claim number means the visitor can call it; it does not file a claim. Forwarding a request does not promise a callback time unless a behavior names one. For a chatbot for insurance agents, these distinctions are the product brief.
Which answers belong in the knowledge base?
Give the agent a source pack you would hand to any stranger at the front desk: services by line, office hours and addresses, the lines you do not write, the carriers' published claim numbers and how a quote request works. The agent reads your website, uploaded PDF, DOC and DOCX files and Q&A pairs in its knowledge base, and answers from that content, not from guesses about your business.
- Agent reads
- Services
- Office hours
- Carrier claim lines
- Stays out
- Policy numbers
- Health details
- Claim files
The crawl reads the text on your pages, images only by their alt text and embedded frames not at all, so a wall of carrier logos tells the agent little more than their alt text. List your carriers as text, and settle conflicts first: if two pages give different Saturday hours, the agent may quote either. Re-read the site after a change; on Boost it can do so monthly on its own, on Ultimo up to daily.
Name an owner for each source. When a carrier changes its claim number, that person updates the page and checks the new answer. Keep customer records, policy documents and internal case notes out of this pack entirely.
Insurance chatbot examples: an auto quote request
Take Harbor Pine Insurance, an example independent agency with two licensed agents and a Webflow site. On a Thursday at 11 am both agents are with clients and nobody is online in the portal. A visitor, Jordan, asks whether the agency can quote a used car she is about to buy.
The agent begins with "I'm Harbor Pine's AI assistant," because a behavior tells it to say so whenever its replies have not, then answers from the services page: yes, Harbor Pine quotes personal auto with several carriers. It does not guess a price. It offers once to pass the request to a licensed agent, and asks for her name and email only after Jordan says yes.
For insurance lead capture, the built-in Lead Generation skill does exactly that much. It asks only for the missing details, sums up the request in one sentence and forwards it, and the agent confirms in its own words, for example "Thanks, Jordan. The team has your request." The lead reaches you exactly as typed, with the transcript beside it in Leads. The new-lead alert goes out in the portal and by email by default.
What the team does not get is the car. "A used SUV" tells your agent little, so the first reply is a question about the vehicle, and Jordan may have insured elsewhere by the time she answers.
Auto quotes: ask for the VIN, not the car
Answers and lead forms are the floor. Open the AI Studio, tell Mo, the builder there, what the agent should do, and Mo builds the skill. For auto quotes the message could read:
When someone wants an auto quote, ask for the car's VIN. Look it up with NHTSA's public VIN decoder (docs: https://vpic.nhtsa.dot.gov/api/), say the year, make and model back and ask if that is the car. Then forward the request to us with the VIN, year, make, model, name and email.Mo reads NHTSA's API documentation itself and builds a skill from two steps: a call to the vPIC decode endpoint and a forward to your Leads. The National Highway Traffic Safety Administration runs that API, and it answered our test call without any key on October 28, 2026, so there is nothing to store. Had it needed one, Mo would ask for it in a secure field, stored encrypted and never sent to the AI.
Mo tests the lookup, then the skill in a test chat, which makes real calls to NHTSA but writes no leads; your own chats in the Test tab do write real leads. From then on, Jordan pastes her VIN, the agent replies "That decodes as a 2021 Toyota RAV4. Is that the car?", she says yes, and the request lands in Leads with the vehicle and the whole conversation. Your licensed agent opens the conversation with the right car instead of a question about it.
When this works: a public HTTPS API that answers within 20 seconds, open like NHTSA's or with an API key or access token. Mo connects your agency system the same way when it has a public API with an API key, to file quote requests there. A skill can also send the details by webhook to a Make or n8n scenario you connect to that system, which can answer within 20 seconds, or to Zapier, which carries them one way into your Zap.
Keep every skill on the public side: public lookups like the VIN decoder and requests forwarded to your team, while policies, premiums and claim status stay in the carrier's portal and with your licensed agents. New skills per plan: Free 1, Smart 3, Boost 10, Ultimo 30, and the standard Lead Generation skill does not count against them (AI Studio).
Disclosure, data and the rules that hold the line
On your website and chat link, Ultimo Bots shows "You are chatting with an AI assistant" above the first message on every plan, and you cannot switch it off. Visitors can close it, and it steps aside while a teammate is in the chat.
Then add three behaviors: short rules of up to 250 characters that apply on every channel and outrank the agent's defaults. In the AI Studio, open the Behaviors tab in the "Your agent" panel, click Add Behaviors, paste one rule and click Add. The first keeps the agent on the public side:
Answer general agency questions from our own content. For personal coverage advice, premiums, underwriting or claim decisions, offer to forward the request to a licensed agent. Never say a request changes a policy or files a claim.The second keeps sensitive data out of the chat:
Never ask for policy numbers, Social Security numbers, driver's license numbers, health details or payment details. If a visitor shares them, do not repeat them and offer to have our team contact them instead.For WhatsApp and Instagram, a third behavior tells the agent to say it is an AI assistant whenever none of its replies has said so yet.
A rule cannot stop a visitor from typing a policy number anyway, and every chat is kept as a transcript, so decide who reviews conversations and how long you keep them. Keep health information out of this setup: the agent works with public agency information and ordinary contact details. Ultimo Bots names its main sub-processors in the help center and confirms the current list on request. As of October 2026; practical guidance, not legal advice.
When does a licensed person take over?
At Harbor Pine, the handover follows one switch: the online status in the portal. While Marcus sits with a client he stays offline, so the website chat shows no "Talk to a human" button. The agent keeps answering and offers to forward anything it cannot answer reliably, and a visitor who wants a person leaves a request for the team.
Back at his desk, Marcus switches himself online and the button appears. When a visitor asks for a person, he joins from the portal, the chat tells the visitor he has joined, and the AI stays quiet until he leaves (live chat). On WhatsApp and Instagram he pauses the AI for that one conversation and replies from the portal inbox, and his replies cost no AI credits.
Choose the website placement with the same care: a floating widget on every page, or an inline chat on your contact page, which makes its purpose plain during a first rollout.
What does an AI agent for an insurance agency cost?
Ultimo Bots is priced per AI agent, with a monthly allowance of AI credits, and teammates cost nothing extra, so an agency with two licensed agents and a CSR pays what a solo agent pays. As of October 2026, Smart is $29 a month, or $19 a month billed yearly, with 500 AI credits; the other plans are on the pricing page.
A standard answer uses 1 AI credit, so Smart covers up to 500 standard answers a month; a conversation usually takes several. Mo and your own test chats use the same balance: a quick question to Mo uses a few credits, building a skill more. At zero the agent pauses until your monthly AI credits renew, you buy extra credits or you upgrade.
Budget the people too: someone approves sources, reads chats and answers requests. Better insurance customer service shows up in those conversations, so measure answered questions and usable quote requests, not a vendor's conversion percentage.
Test the line between public answers and advice
Before launch, ask in pairs that start public and cross into advice. A correct answer to the first half proves nothing about the second:
- Service or recommendation: "Do you offer life insurance?" then "Which policy should I buy for my family?"
- Process or action: "How do I report a claim?" then "So my claim is filed now?"
- Route or account: "Where is my carrier's customer portal?" then "What is my deductible?"
- Request or sensitive intake: "Can someone call me?" then a pasted policy number.
For each pair, note the reply and its source, and have the licensed person for that line judge it. Fix the source or the behavior, then ask again in other words. Run the handover once with a teammate online and once with nobody online, and clear your test leads before launch.
Give the pilot an owner and a weekly rhythm
Three recurring calendar entries keep the first version honest.
- Each morning: the inquiry owner assigns new requests in Leads to a licensed agent. Anything about an existing policy moves into your normal service process.
- Midweek: the content owner reads a sample of chats, including one the agent could not answer and one that needed a person, and fixes the source behind it.
- Friday: the agency lead decides whether the scope works, and adds a public topic only when someone owns its sources and its follow-up.
Start with information you can approve, a request you can answer and a person accountable for both.
Questions and answers
Is there an AI for insurance?
Yes, several kinds. Carriers use AI in underwriting, pricing, claims and fraud detection. On an independent agency's website, an AI agent such as Ultimo Bots answers approved public questions, forwards quote and callback requests to your team with the conversation, says it is an AI and runs skills you describe to Mo, its builder, such as a VIN lookup for auto quotes. Coverage advice, premiums and policy decisions stay with licensed people.
Which AI is best for insurance agents?
For the website: the one that answers your public questions correctly, stops at advice and gets requests to a licensed agent with the details they need. Test candidates with your own question pairs, from "Do you write flood insurance?" to "Is my basement covered?" Tools for rating, policy analysis or your agency management system are a separate decision.
Can an AI agent look up a policyholder's account?
Not on an agency website: keep the agent on the public side. With Ultimo Bots it runs public lookups that need no identity, such as decoding a VIN for a quote request, and forwards personal questions to your team. Policy, premium and claim details stay in the carrier's portal and with your licensed agents.
How is AI being used in the insurance industry?
The NAIC lists customer service, underwriting, pricing, claims and fraud detection (overview last updated April 3, 2026). Its December 2023 model bulletin says consumer-impacting decisions made or supported by AI must comply with applicable insurance laws. An agency's website assistant sits at the customer service end. As of October 2026; practical guidance, not legal advice.
Will AI take insurance agent jobs?
A website assistant takes the first exchange: hours, services, how to report a claim, a quote request with the right details. Assessing needs, recommending coverage and standing behind that advice stays with licensed agents. The NAIC's overview also says AI is more likely to support human workers than replace them entirely.
Are chatbots HIPAA compliant?
There is no category-wide answer; the actual use, data handling and agreements decide. The setup in this guide never asks for health records or claim files: the agent works with public agency information and ordinary contact details. As of October 2026; practical guidance, not legal advice.




