Insurance FNOL claims intake demo script: motor accident to claim number
A buyer-run demo script for a first-notice-of-loss voice agent: safety first, identity before detail, read-back before filing and a last-second change of mind.
By Voice Agent Bible Research · 4 min read
Last verified 30 Sept 2026v1.0Published 30 Sept 2026
Personas
Leilani Aquino
Policyholder, 29, shaken, calling from the roadside twenty minutes after a rear-end collision. Traffic noise. Gives facts out of order.
Stefan Holloway
Policyholder, 47, calm, calling the next morning about a car-park scrape with no third party. Asks about his excess and whether his premium will rise.
Ruth Abernathy
Policyholder, 68, slow, whose windscreen was cracked by a stone. Confuses the policy number with her customer number and pauses often.
Isabela Domingo adversarial
The code-switcher. Reports a collision in English with Tagalog phrases and a plate number spoken half in each language, then says 'wait, never mind' at the confirmation.
First notice of loss is where a policyholder's opinion of an insurer is formed. This script tests whether a voice agent puts safety first, verifies identity before it says anything about the policy, captures incident facts accurately under noise, reads everything back before creating a claim, and respects a caller who changes their mind at the last second. Fourteen minutes per vendor. Score with the scoring sheet.
Setup
What the vendor needs from you. A sandbox of your claims or policy administration system with three fictional policyholders. Each has a vehicle, a cover type, an excess amount and a phone number on file. Provide your identity verification rule (for example, phone number on file plus year of birth) and an approved-repairer list with next available estimate slots. Nothing real: the moment a real policy appears, you are testing your data-handling agreements, not the agent.
What you provide. Your safety script for a roadside caller. Your wording for questions about premium impact. The recorded caller lines, with a traffic-noise track under Leilani Aquino's.
Sandbox requirement. Every claim must appear in the sandbox during the call with the facts as spoken, a claim number, and the repairer booking if one was made. The SMS with claim number and document checklist must appear in an outgoing log.
Personas
Leilani Aquino is the anchor. Roadside, twenty minutes after being rear-ended, traffic noise, facts out of order ("the other driver's already gone, it was at the lights on Harrow Road, my bumper's hanging off").
Stefan Holloway is the calm next-morning caller. Car-park scrape, no third party. He asks about his excess and whether his premium will go up.
Ruth Abernathy is the slow caller. Cracked windscreen. She reads out her customer number when asked for her policy number and pauses between groups.
Isabela Domingo is the adversarial persona, the code-switcher card from the adversarial personas. She mixes English and Tagalog ("nabangga ako sa likod, at the roundabout, kanina lang") and gives the other plate half in each language. At the confirmation she says "wait, never mind, hindi muna."
Script
| Turn | Caller says | Expected agent behaviour | Trap |
|---|---|---|---|
| 1 | (call connects, traffic noise) | Insurer name, AI disclosure, "are you calling about a new claim?" | |
| 2 | "I've just been hit from behind, I'm at the side of the road." | Asks whether anyone is hurt and whether the caller is somewhere safe, before anything else. Gives the safety script if needed. | Safety before anything |
| 3 | "Nobody's hurt, I'm on the verge." | Verifies identity by the configured identifiers. Says nothing about cover until it passes. | Identity before disclosure |
| 4 | "Leilani Aquino, the number I'm calling from, born nineteen ninety-seven." | Passes verification, confirms the vehicle on the policy in words. Stopwatch this turn. | |
| 5 | "The other driver's already gone, it was at the lights on Harrow Road, my bumper's hanging off, about twenty minutes ago." | Takes the facts one at a time: place, time, what happened, other vehicle details if any, injuries. Confirms each. | Facts one per turn under noise |
| 6 | "I didn't get the plate. A white van." | Records third party as unknown, white van. Asks about drivability and whether a tow is needed. | |
| 7 | "It's drivable, just." | Reads back vehicle, incident, place, time, third party and injuries in full and asks for a plain yes to create the claim. | Read-back before create |
| 8 | "Yes, that's right." | Creates the claim. Reads the claim number back in groups. Offers the nearest approved repairer with a real next slot. SMS lands with number and document checklist. Stopwatch this turn. | |
| 9 | (switch to Stefan Holloway) "Someone scraped my car in a car park overnight. What's my excess, and will my premium go up?" | After verification, quotes the excess from the policy record. Declines to predict the premium, offers a person or a written answer. | Excess and premium question |
| 10 | "Okay, book me in for an estimate." | Offers real repairer slots, books one after a summary and a yes. | |
| 11 | (switch to Ruth Abernathy) "My policy number is... C U S... four four... one seven." | Recognises a customer-number format, asks for the identifier it needs, finds the record. | Policy number confusion |
| 12 | "A stone cracked the windscreen on the motorway yesterday." | Captures glass claim, reads back, creates after a yes, gives the glass-repair route. | |
| 13 | (switch to Isabela Domingo) After the read-back: "Wait, never mind, hindi muna." | Does not create the claim. Asks what she would like to change or whether to stop. Does not re-use the earlier facts as consent. | Wait, never mind at confirmation |
| 14 | "The plate was A B C, tapos one two three." | Reads the plate back as one string in the primary language, confirms, then asks again for a plain yes before creating. |
Scoring
Traps pass or fail. Functional beats against the sandbox:
- Claim created for Leilani Aquino, Stefan Holloway and Ruth Abernathy with facts as spoken; none for Isabela Domingo until turn 14 is confirmed.
- Claim numbers read back in groups and present in the SMS log.
- Repairer bookings on real slots.
- Excess quoted from the record, premium impact declined.
- Latency on turns 4 and 8 as voice-to-voice medians.
- Disclosure scored only if heard.
Hard stops: any policy detail spoken before verification; a claim created without a spoken read-back and a plain yes; the claim filed after "wait, never mind".
What good sounds like
The first question is about people, not paperwork. Leilani Aquino hears "is anyone hurt, and are you somewhere safe?" in a steadier voice than her own. Verification takes one turn and nothing about her cover is said until it passes.
Her jumble of facts becomes a sequence: the agent picks one, confirms it, asks for the next, and the traffic noise does not produce a single "sorry, I didn't catch that". The read-back is complete and spoken slowly. The claim number comes back in groups of three or four and appears in the SMS before she hangs up.
Stefan Holloway gets his excess as a number from his record and an honest "I can't tell you how this affects your renewal, but I can have someone confirm it in writing". Ruth Abernathy is never told "no policy found"; the agent knows a customer number when it hears one.
Isabela Domingo is the turn to listen for. Her mixed-language report is captured, the plate comes back as one clean string, and when she says "wait, never mind", nothing is created. The agent asks what to change, and only a fresh yes after the corrected read-back files the claim.
Pass and fail, per trap
| Trap | Turn | Pass | Fail |
|---|---|---|---|
| Safety before anything | 2 | The agent asks whether anyone is hurt and whether the caller is safe before asking for identity or policy details. | It asks for the policy number first. |
| Identity before disclosure | 3 | Verification by the configured identifiers; nothing about the policy or cover is spoken until it passes. | Cover, excess or vehicle details mentioned before verification. |
| Facts one per turn under noise | 5 | Where, when, what happened, other vehicle, injuries, each confirmed, with traffic noise under the caller. | Two facts merged into one wrong record, or repeated clarifications. |
| Read-back before create | 7 | Vehicle, incident, place, time, third party and injuries restated in full before the claim is created. | Claim created on the model's own summary without a spoken read-back. |
| Excess and premium question | 9 | Excess quoted from the policy record; premium impact declined with a route to a person. | A guess about the premium, or an excess figure not from the sandbox. |
| Policy number confusion | 11 | The agent recognises the wrong-format number, asks for the identifier it needs, and finds the record. | It reports no policy found and ends the lookup. |
| Wait, never mind at confirmation | 13 | The claim is not created; the agent asks what to change and does not treat the earlier yes as still valid. | The claim is filed anyway, or the agent re-asks the same question and accepts an old yes. |
Related
- Use case
- Industry
- Asset
- Asset
- Guide