AI chatbots for insurance agencies.

A chatbot on your agency's website that collects quote details and policy changes for your agents, and leaves every cover decision to them.

Discuss your chatbot
A phone on a coral stand showing an example chat with an insurance agency's quote desk assistant: a food truck owner asks what cover they need and is passed to an agent.
An example conversation for insurance agencies.

What clients ask between renewals.

Can you quote my home and car together, how do I add a driver, can I get a certificate of insurance for a job tomorrow, when does my policy renew, how do I report a claim and am I covered if a tree falls on the shed. Most of these have a set answer or a set form. Whether a claim is covered is a question for an agent with the policy in front of them.

What the chatbot handles.

What it may say is written down before we build.

Quote requests

It asks what your agents ask first: what needs cover, the renewal date, the current insurer, past claims and the best time to call. Your agents get a summary they can quote from.

Policy changes

A new driver, a different car, a new address or a home extension: it collects the details and sends them to your service team, who make the change with the insurer.

Certificates and documents

Requests for a certificate of insurance, proof of cover or a copy of the policy reach your service team with the client and the deadline noted.

Claims

It gives the insurer's claims line and your agency's claims contact at once, and takes the first details for your claims handler. It never says whether a claim will be paid.

Where it stops.

It never advises on cover. It does not recommend a policy, compare insurers, say whether a loss is covered or confirm that cover is in place. Those questions go to a licensed agent with the client details already collected. It can show the licence details and disclosures your agency already uses.

After the conversation.

Quote requests go to your sales agents and policy changes to your service team.

Into your agency system

Where your agency management system has an API, requests are written straight into it. Without one, they arrive in your inbox as a summary your team can work from.

Follow-ups

A reminder to your team when a renewal is coming up, and a prompt to call back when a sent quote has gone quiet.

Questions we hear.

Can the chatbot tell people what cover they need?

No. It explains what your agency offers and collects details for a quote. Which cover someone needs, and how much of it, is a conversation with a licensed agent.

Can it tell a client whether a claim is covered?

No. It gives the claims line, takes the first details and passes them to your claims handler. Only the insurer decides a claim.

Can it issue certificates of insurance?

It collects the request, the certificate holder and the date needed, then sends it to your service team. Issuing the certificate stays with your team.

What client details does it ask for?

Only what a quote or change needs, and never card or bank details. Where conversations are kept, and for how long, is your decision, made before the build.

Does it work with our agency management system?

That depends on its API, and we check it before the build. Requests can always come to your inbox instead.

Show us your quote form.

Include the questions your agents ask before quoting and where requests land today. The consultation is free, over Google Meet, a voice call or text.

Book a free consultation