Full AI transformation for insurance.
AI agents for every insurance process. Claims, renewals and back office, run end to end across the systems your company already uses. Your people sign off on the calls that are theirs.
- Human sign-off on critical actions
- Role-based permissions
- Built for regulated data
Ready connectors for the tools insurers and agencies already work in
The decision takes a minute.Getting to it takes weeks.
A car claim waiting on the appraiser's report. A renewal where the premium jumped 18%. An endorsement stuck in a shared inbox. Each one waits while someone pulls the policy, chases the documents, finds who can approve it, and then keys the result into three systems by hand.
Most of that time goes into chasing, not deciding.
Every process, without replacing a single system.
Fruxon agents work inside the core system, the CRM and the inbox you already use, and keep every case moving.
Claims tracking
From first notice to payment. It opens the claim, checks coverage, collects documents, assigns the appraiser and tracks every deadline, then hands the file to whoever owns the next step.
Renewal tracking
Every policy coming up for renewal, across every insurer. It re-prices, flags the jumps, sends the notice on time and records the customer's consent the way the regulator requires.
Back-office automation
Endorsements, cancellations, address and beneficiary changes, power-of-attorney forms. It reads the request, prepares the change in the core system and files the paperwork.
Underwriting intake
Proposals arrive complete. It extracts the details, requests existing coverage from the industry data hubs, with the customer's consent and through authorized channels, and hands the underwriter a ready file.
Commissions & production
It matches every insurer's production report against the commission you expect, explains each gap and files the claim with the insurer before the month closes.
Service & complaints
Customer requests and complaints are routed, answered and tracked against response deadlines, with every reply on record and the hard ones escalated to a person.
Watch a flow run, end to end.
Every flow runs in your systems. The red steps wait for a person. Everything else just gets done.
Step 1 of 6
First notice
The insured reports a collision by email. Fruxon opens the claim in the core system and links the policy, the vehicle and the agent.
Your people make the call.Fruxon does the legwork.
When a call needs a person, it asks that person once, where they already work, then finishes the job in your systems.
It finds the gap.
It pulls the policy, the appraiser's report and the plumber's invoice, and checks them against the claims policy. The damage is over the sub-limit, and no rule covers it.
Its reasoning in the run, written before it asks anyone. The lookups in the core system and the claims policy took under two seconds.
It knows who owns the call.
Property claims go to Dana, underwriting exceptions to Ronen. Not to a shared inbox. It reaches each of them where they already work.
Dana owns property claims, and she's on Teams. That's where the question goes.
She answers in a line. It does the rest.
One message with everything she needs to decide. Her answer goes straight back into the run, with her name on it.
Dana answered 19 minutes later. The agent posted ₪14,400 after the deductible, scheduled the payment and sent the insured the plumber-network offer.
Dana answered once. She won't be asked again.
Her answer becomes a rule in the claims policy, reviewed before the agent uses it. The next claim like it settles on its own.
The first claim
Kfar Saba · water damage over the sub-limit · asked Dana
The next one, two days later
Ra'anana · same pattern · nobody asked
Every answer works that way. What's left for your people is the case nobody has seen yet.
Every claim comes with its paper trail.
What it checked, what it decided, who approved it and in what words, kept with the case itself. And what each one cost to handle.
Every decision has a name on it.
What Dana was asked, what she answered and when, kept on the claim's run.
The record can't be rewritten.
Nobody can edit or delete an approval once it's made, not even an admin. Ready for the regulator, the auditor and the ombudsman.
A limit stops the agent.
Set a daily, weekly or monthly limit per agent. When it's reached, the agent stops and you get an email.
Asked on Teams · 16:31
Damage ₪18,400, water sub-limit ₪15,000, no extension. Pay to the sub-limit, or approve an exception?Dana Levi answered · 16:50
Pay to the sub-limit. Offer our plumber network for the rest at the panel rate.| Case | Type | Status | Approved by | Cost |
|---|---|---|---|---|
| CL-24-118 | Home claim | Paid | Dana Levi | ₪3.40 |
| CL-24-311 | Motor claim | Closed | Yael Cohen | ₪4.10 |
| RN-58217 | Renewal | Consent signed | Ronen Azulay | ₪1.20 |
| EN-2290 | Endorsement | Applied | Ronen Azulay | ₪0.85 |
| CL-24-327 | Health claim | Waiting on hospital | — | ₪1.90 |
Built for an industry that answers to a regulator.
Medical records, financial data, ID numbers. Every agent sees only what its job needs, and every action is on the record.
Only what its job needs.
Each agent gets only the systems, lines of business and fields its job needs. You decide which data it may touch.
You name the sign-offs.
Payments above a threshold, coverage exceptions, cancellations, anything with medical data. Whatever you name waits for a person.
Your data stays yours.
Encrypted in transit and at rest, isolated per organization, and never used to train models.
Certifications, security policies, subprocessors and the DPA, kept current in one place.
Visit the Trust CenterWorks in the systems an insurer runs on.
Ready connectors for the tools your people already work in. The rest of your stack, from the core policy system to the industry data hubs, is connected during rollout.
Ready today
Connect and go- Microsoft Teams
- SAP
- Salesforce
- Outlook
- Priority
- SharePoint
- BAFI CRM
- Excel
- Gmail
- monday.com
- Slack
Connected for you
During rollout- Core policy and claims systems
- Agency platforms and CRMs
- Insurer production and commission reports
- Industry data hubs, with the customer's consent
- Customer messaging and e-signature
Wired in during rollout, through the access each system offers. Your system of record stays the system of record.
One line of business first.Then the next.
One flow, one team, and permission to ask about everything. The run history tells you when it's ready for more.
Week 1
It starts read-only.
Connected to one flow, say motor claims. It can see everything before it may change anything, and drafts every action for review.
Weeks 2–4
It acts, with sign-off.
It does the work, and waits for a person on every action you named. Nothing you named goes through without a sign-off.
Month 2 onward
You widen it, one action at a time.
Renewals, endorsements, commissions. Each new permission is a decision you make, with the run history to back it.
Questions we hear from insurers
Have more questions? Contact us
Start it narrow.Widen it when it earns it.
One channel, one job, and permission to ask about everything. Within a week you'll see whether it's ready for more.
Why we built Fruxon
