Insurance
The quote request and the claim, taken by phone.
An insurance broker gets three kinds of call over and over: somebody wants a quote, somebody has had an accident, and somebody has a policy about to expire. All three start with the same handful of fields, gathered by a person who could be doing something else.
The assistant takes quote requests with the fields underwriting needs, records first notice of loss and passes it to assessment, dials renewals before expiry, and hands any conversation about cover to an adviser. It issues no policies and approves no claims.
What rings at a broker
The three flows below have nothing in common except that each begins with a data-gathering step nobody wants to do on the phone.
A quote request
The type of cover, the details of the property or the person, the dates wanted, the contact details.
First notice of loss
What happened, when, where, the policy number. Recorded literally, with no assessment at all.
A renewal before expiry
An outbound call from a list you supply, confirming the intention to renew.
Document questions
What paperwork a file needs, where to send it, how long a response takes. From your documents.
A conversation about cover
Handed over. That is advice which binds the broker, and it is not automated.
The two main roads
A quote and a claim are opposite in register. The first is commercial and can run long. The second comes from somebody who has just had a bad day and has to be as short as possible.
- 01 Split quote from claim on the first line A first-notice call handled like a sales form is the worst thing that can happen on this line.
- 02 On the quote road, gather the fields Exactly the fields underwriting needs, as structured output with the same names every time.
- 03 On the claim road, record literally What happened, in the claimant own words, plus the policy number and contact details. No extra questions and no opinions.
- 04 Write it onward The lead into the CRM for a quote, a ticket for a claim, plus a message to the assessment team where appropriate.
- 05 Say what happens next and when An SMS or email with what was taken and the timeframe for a person to come back, because on a claim file the uncertainty is the hardest part.
What reaches underwriting and claims
The data arrives structured identically every time, whoever would have answered.
| The quote request | As structured output with the fields you define, plus the contact and deal in the CRM. |
|---|---|
| The claim file | A ticket in Zendesk or Freshdesk, with the literal description and the policy number. |
| The renewals | The outcome per contact in the campaign, with the renewal intention recorded. |
| On the call record | The transcript and the recording, which on a claim file become part of the documentation. |
What it does not do for a broker
Insurance is a regulated activity, and advice given wrongly binds the broker rather than the software vendor.
- It issues no policies and rates no premiums It does not quote, does not compare products and does not say what something would cost. It gathers the data a person quotes from.
- It approves and declines no claims It does not say whether an event is covered, does not estimate a settlement and does not comment on fault.
- It gives no cover advice It does not recommend one product over another and does not explain what happens in a particular case.
- No link to underwriting systems There is no connector for insurance platforms. The link to your system is your own HTTP tool or an MCP server.
- It collects no premiums Not the first instalment, not the subsequent ones, not on the phone and not through a link sent during the call.
What brokers ask us
Can it give an indicative price?
No, and that is a choice rather than a technical limit. A price said on the phone and contradicted at issue damages the relationship more than the call helps. What it can do is gather exactly the data a quote needs and say how soon somebody comes back with it.
Is it suitable for first notice of loss?
For taking the first details, yes, and precisely because it is available at night and at weekends, when most events happen. For anything else on the file, no. The assistant records and hands over, and that is all.
Can it call clients about renewals?
Yes, through an outbound campaign with the windows and suppressions configured. The list comes from you, and so does the basis on which you call. The product writes down, for every contact not dialled, why it was not.
How does it connect to our policy administration system?
Through an HTTP tool written over its API, with a JSON schema and versioning, or through an MCP server. We have no ready-made connector for any insurance system, and the integrations page shows exactly what exists.
Where to go next
Integrations
25 business connectors, 18 selectable providers, eight storage destinations.
Knowledge base
Upload, chunking, vectors in Postgres, and knowledge-only mode.
Security
Isolation, roles, audit, redaction, your own storage. And an honest list of the gaps.
Pricing
Components at their published price, the platform on top, and what we cannot price yet.
See it working on your own business
Five short steps. At the end, if you want one, an AI assistant rings you and handles a call the way it would handle yours.
- 01 Your business
- 02 What we found
- 03 What it should do
- 04 Connections
- 05 Your number
What you get, and what it costs
- A telephone number of your own, answered by an assistant built from what your website says. You can ring it the same day, from the phone in your pocket.
- Five steps, about four minutes. Reading your site takes half a minute, and after payment the number is usually live in under a minute.
- One payment: €3.00 for the first month of the number, plus the credit your calls are drawn from — the smallest bundle is €10.00. No subscription, no contract.
Calls cost €0.12 a minute, whoever rings and from wherever.
- €10.00 roughly 83 minutes of talking
- €20.00 roughly 166 minutes of talking
- €50.00 roughly 416 minutes of talking
From the second month the number costs €3.00 a month, taken from the same credit. If the credit will not cover it the number keeps answering for 14 days before it goes back to the pool.
What the assistant knows is built by reading your website, and an automated reading can get things wrong. That is why step two shows you everything we found, with a link to the page each fact came from, and you correct it before you pay — not after your first real call.
Nothing is built and nothing is charged until you pay. What you fill in is saved, and the link brings you back to it.
Notes
-
1
The tools named on this page are the ones in
App\Services\Integrations\ConnectorRegistrycarryingimplemented. Anything that is only in the catalogue, without that flag, is not named here as though it worked. - 2 Structured output is the mechanism that makes a quote request arrive with the same fields every time. It is described on the assistants page, together with schema versioning.