Voice claims intake (FNOL)
The customer calls and describes it; policy found by plate, cover checked, claim opened and adjuster assigned.
Voice claims intake (FNOL)
- Call connected: "someone hit my car last night" · plate 34 ABC 123
- Live transcript with noise filtering; tone: calm, confidence 0.95
- Policy found by plate: comprehensive #KS-2291045, active, excess 2,000
- Plan: gather incident facts → coverage → open claim → assign adjuster
- Incident: hit while parked, 7 Sep 23:30, Kadıköy · no injuries · third party unknown
- Cover: collision within comprehensive · 0 claims in 12 months · no waiting period
- Claim #CL-2026-118342 opened, reserve set at 45,000
- Nearest partner adjuster (Kadıköy) assigned, appointment tomorrow 10:00
- Spoken summary read out, customer confirmed the claim number
- Claim number and photo upload link sent on WhatsApp
Simulation · derived from real agent definitions · every agent can be built by dialogue with the Autonomous Agent and validated with a test corpus
"Someone hit my car" call on the claims line
Claim opened, reserve set, adjuster appointment and photo link with the customer
Agents
Claims Supervisor
Decomposes the objective, delegates to agents, manages approval points, merges the result.
Speech Agent
Transcribes live audio and filters noise
transcribe_streamdetect_emotionIntake Agent
Gathers incident facts, asks follow-ups, gives a spoken summary
extract_claim_factsask_followupsynthesize_speechPolicy Agent
Finds the policy, checks cover and claim history
get_policy_by_platecheck_coverageget_claim_historyClaims Registration Agent
Opens the claim, sets the reserve, assigns the adjuster
create_claimset_reserveassign_adjustersend_whatsappSteps
| # | Kind | Agent | What happens | System | ms | tok |
|---|---|---|---|---|---|---|
| 01 | ingest | Claims Supervisor | Call connected: "someone hit my car last night" · plate 34 ABC 123 | — | 200 | — |
| 02 | reason | Speech Agent | Live transcript with noise filtering; tone: calm, confidence 0.95 | — | 480 | 170 |
| 03 | tool | Policy Agent | Policy found by plate: comprehensive #KS-2291045, active, excess 2,000 | Policy Admin System | 420 | — |
| 04 | plan | Claims Supervisor | Plan: gather incident facts → coverage → open claim → assign adjuster | — | 280 | 210 |
| 05 | reason | Intake Agent | Incident: hit while parked, 7 Sep 23:30, Kadıköy · no injuries · third party unknown | — | 1,100 | 1,240 |
| 06 | verify | Policy Agent | Cover: collision within comprehensive · 0 claims in 12 months · no waiting period | — | 560 | 480 |
| 07 | write | Claims Registration Agent | Claim #CL-2026-118342 opened, reserve set at 45,000 | Guidewire ClaimCenter | 620 | — |
| 08 | write | Claims Registration Agent | Nearest partner adjuster (Kadıköy) assigned, appointment tomorrow 10:00 | Guidewire ClaimCenter | 380 | — |
| 09 | notify | Intake Agent | Spoken summary read out, customer confirmed the claim number | Genesys SIP | 380 | 160 |
| 10 | notify | Claims Registration Agent | Claim number and photo upload link sent on WhatsApp | WhatsApp Business API | 240 | — |
Policy renewal offer
Policies re-priced, sharp increases go to approval; customer accepts with one tap and the policy is issued.
Underwriting document extraction
Medical reports and labs read and assessed against the manual; underwriters only see files above threshold.
Motor claim photo assessment
Damage detected from photos, estimate built from parts and labour, adjuster only approves; repair slot booked.
Time to move from experimenting with AI to transforming with it.
In a 30-minute discovery session we take your 2–3 priority business problems, show a live demo of a similar scenario, and draft a roadmap that starts with the Value layer.
- Your 2–3 priority problems
- Live demo of a similar scenario
- Roadmap starting with value analysis