01
Answer what you place
Trades, covers and whether you are whole-of-market or panel — answered from your own pages, in the enquirer's language, at whatever hour they are reading.
AI chatbot for insurance brokers that splits new quotes from live claims.
Two very different people use a broker's chat window: someone shopping for cover who has never spoken to you, and a client whose van has just been hit. Adoomi answers the published side for the first — the trades you place, the covers you arrange, whole-of-market or panel, what your quote process asks for — and gets the second to a claims handler with their own account of what happened. It gives no view on suitability, quotes no premium and confirms no cover, because it cannot see a policy.
Quotes and claims, sorted apartNo view on whether you're coveredYour pages, or a decline
Fig. 01.A · Insurance brokersClaims first
Split from quotes, sent straight on
24/7
Renewal shoppers answered after closing
No premium
Never an indication in chat
Fig. 02.A · pain quotesThe everyday problem
A claim and a quote look identical in an inbox
Both land as one long paragraph, and only one of them can wait. A prospect asking whether you place motor trade risks can be answered straight from your sectors page. A client reporting a smashed window at their unit cannot, and should not be sitting behind quote enquiries when somebody finally opens the inbox. Sorting the two is most of the job, and it has to happen before the office does.
Web07:42
“Do you cover construction, IT contractors, hospitality or fleet?”
WhatsApp21:15
“What types of cover do you arrange (PI, EL, PL, cyber, D&O, business interruption)?”
Web formSun
“Are you whole-of-market or panel?”
What you get
Two kinds of enquiry, two routes, one refusal.
02
Send the claim to the handler
A client reporting an incident is stopped, quoted back in their own words and routed to the claims handler you named — never assessed, never reassured about cover.
03
Never price, never rule
No premium indication, no suitability view, no confirmation that a policy responds. Those need somebody who can read the policy, and the assistant cannot see one.
Question coverage
What lands in a broker's chat window
Trades placed, covers arranged, whole-of-market or panel, what the quote process asks for, how a mid-term change is handled and where a claim goes — all answerable from your published pages, with pricing and suitability left to a broker.
Trades placedCovers arrangedWhole-of-market or panelQuote processMid-term changesReporting a claimRenewal timing
a
Adoomi
ChatVoice
A customer slipped on our forecourt this morning and an ambulance came. I don't know if we're covered for that.
I am stopping rather than guessing. I cannot see your policy and I will not tell you whether it responds. I am passing this to the claims handler now, in your words: customer slipped on the forecourt this morning, ambulance attended. What number should they ring?
I'll type my mobile. Should I be taking photos of the forecourt?
The handler will tell you what they need — I would only be guessing at that. I cannot take photographs in this window either; once they have picked this up on WhatsApp you can send them straight across there. Your message is already with them.
Sectors coveredTypes of coverQuote process
Type a question…● Voice
Buyer intent
The quote sheet filled in before a broker rings
A commercial enquiry that arrives as "can you insure us?" costs a broker a call. Adoomi asks what you need to approach a market: the trade, the turnover band, the covers wanted, the renewal date, whether cover is in place, whether there have been claims. It asks for bands and descriptions, not documents: the window takes no uploads. Schedules and claims histories reach the broker only after a WhatsApp handoff. What it holds is EU-hosted with GDPR export and deletion, never logged.
Vague enquiries, no context.
Your team chases the basics before they can reply.
a
Adoomi
TradeGroundworks contractor
Covers wantedPublic and employers' liability
RenewalEnd of next month
Contactcaptured@…
3 of 4 captured · 1 in progress
With AdoomiNew enquiry · readyEnq 5459
TradeGroundworks contractor
Covers wantedPublic and employers' liability
RenewalEnd of next month
Contactcaptured@…
One clean handoff.
Your team opens the enquiry and replies — no chasing.
STEP · 01
Split quote from claim
New cover, or something that has already happened
STEP · 02
Pin the trade
What the business actually does on site
STEP · 03
Take the quote sheet
Covers wanted, turnover band, renewal date, claims history
STEP · 04
Route it
New business to the class handler, claims to the claims handler
Fig. 06.A · after-hoursOut-of-hours
Renewal shopping happens after closing
A business owner opens the renewal invitation once the shutters are down, decides it looks steep, and starts searching. That is the hour your published pages have to do the talking: which trades you place, which covers you arrange, whether you are whole-of-market or on a panel, what you will need before anyone can approach an insurer. Adoomi answers those in the enquirer's own language, captures the rest as a quote sheet, and puts anything about a live policy in front of a person instead.
19:55
“"Do you place motor trade risks?"”
Straight off your sectors page
21:30
“"What do you need before you can quote?"”
Your published quote process
23:10
“"A window has been put through at the unit."”
Claims handler alerted, words attached
07:45
“Overnight queue”
Quote sheets first, the claim already sent
Time back
"Do you place this?" stops interrupting placements
The questions that repeat are the ones you have already published: the trades you place, whether you arrange employers' and public liability alongside professional indemnity, what a mid-term adjustment involves, how the quote process runs, what you charge for arranging cover. Adoomi answers them from your pages, re-read on a schedule and whenever you change one, so brokers spend the day on risks rather than on repetition.
Before Adoomi
- A claim reported overnight sits in the same inbox as the quote enquiries until someone sorts it.
- "Can you insure us?" costs a whole call before a broker knows what they are quoting on.
- Whole-of-market or panel gets asked on first contact and answered by a person every time.
- Renewal shoppers arrive in the evening and get a reply once the day's placements are done.
With Adoomi
- Trades placed and covers arranged answered from your own pages, in the enquirer's language.
- Quote sheets arrive with the trade, covers wanted, renewal date and claims history on them.
- A reported claim leaves the chat at once, in the client's own words, to the handler you named.
- Suitability and premium questions are refused in writing, with the enquiry captured for a broker.
Fig. 08.A · controlsTrust & safety
Where a claim goes, and what it never rules on
A claim is the moment this matters. Someone typing "a customer slipped in our yard" gets no assessment and no ruling on cover. The claims team hears it instead, in the client's own words, routed to the handler you named by email alert or a move onto WhatsApp. Photographs reach you only if the client sends them after that handover; the window takes no uploads. Suitability, premiums, terms and outcomes are refused every time. None of this makes your brokerage compliant with anything.
01
Published pages only
Trades, covers and process come from your own site. There is no insurance knowledge behind it to improvise from, so an unpublished trade gets a decline.
02
Claims go straight out
An incident report is never assessed. It leaves the chat as the client's own account, to the claims handler you named, with no view on whether it will be paid.
03
No prices, no suitability
Premiums, limits, terms and whether a policy responds are refused every time. They need a broker who can read the policy, and the assistant cannot see one.
04
Risk detail stays in the EU
Turnover bands and claims history are held in the EU with GDPR export and deletion, and no conversation content is ever written to logs.
How it works
How an AI chatbot for insurance brokers works.
01
Connect content
Point Adoomi at your sectors page, covers page and quote-process page. Those are the whole of what it may say; a trade you have not published gets a decline, not a guess.
02
Add the snippet
Name the destinations: new business to whoever handles that class, claims to the claims handler, complaints to the person you nominate. Then add one line to your website.
03
Test & go live
Check what it captured and where it stopped. Amend or block anything, and a changed policy-wording or fees page is picked up at the next re-read.
FAQ
FAQs about AI chatbots for insurance brokers.
Cover questions get no ruling, because the assistant cannot see a policy — nothing behind a login is visible to it. It says so, keeps what the client described, and routes it to the person you named. Reading the schedule and answering the question stays with a broker at your firm.
Claims stop the conversation. The assistant takes the client's own account of what happened, tells them a claims handler is being alerted, and routes it — an email alert to the handler you named, or the conversation moving onto WhatsApp with their words carried across. No view is offered on the outcome.
Premium indications sit outside what the assistant may say, rough ones included. It repeats whatever your pages publish about how you charge for arranging cover and what the quote process asks for, then captures the trade, the turnover band and the covers wanted so a broker can put the risk to an underwriter.
Details captured in the chat window are held in the EU, with GDPR export and deletion built in, and no conversation content is written to logs. The window sets no tracking cookies and accepts no file uploads, so schedules, proposal forms and photographs never pass through it.
Mid-term changes are captured, not made. The assistant cannot amend a policy, add a driver or issue a certificate, because it is connected to no insurer and no system. It explains what your page says the process involves, takes the detail of the change and sends it to whoever handles that account.
The Free plan is £0 a month for 50 message credits; Local is £8 for 200, Growth £20 for 500 and Scale £75 for 4,000. Setting up takes ~10 min — connect your website, read what the assistant proposes to say, add one line to your site — and no answer reaches a client unapproved.
Why this matters
What the design settles, and what it cannot
No conversion figures appear here because there are none worth showing you. What is settled by design: every answer comes from pages your brokerage approved, a reported claim never gets an assessment, a premium is never estimated, and cover is never confirmed — the assistant cannot read a policy, so it has nothing to confirm it from. Handovers carry the client's own sentences rather than somebody's summary of them.
The source it answers trades from
Whether you place a trade comes off your own sectors page — one you have not published is declined rather than guessed at.
Evening quote enquiries captured
Renewal shoppers reading your pages after closing get answers from them, and a quote sheet reaches you by morning.
Where a reported claim goes
Incidents leave the chat unassessed, in the client's own words, to the claims handler you named.
Start free
Type a claim into it and see where it lands
Give Adoomi your sectors page, your covers page and your quote-process page, then test it twice: ask whether you place a trade you do place, and report a claim that never happened. The first should come straight off the page. The second should stop, keep your words and name the handler it is going to. Change anything you dislike before it goes live. The Free plan is £0 a month with 50 message credits and setup takes ~10 min.
Claims go to a handlerNo premium guesses£0 to start, no card
Fig. 12.A · Insurance brokersExplore
More Professional Services chatbots
- AI chatbot for AccountantsSee how Adoomi handles enquiries for accountants.
- AI chatbot for Law firmsSee how Adoomi handles enquiries for law firms.
- AI chatbot for Mortgage brokersSee how Adoomi handles enquiries for mortgage brokers.