Story-shaped Timeline
Open a claim, read the loss, the injuries, the parties, and the current posture in minutes — narrated chronologically with citations to the FNOL, police report, demand letter, and adjuster notes.
For Insurance
Lore reads the FNOL, the police report, the medical bills, the photos, the demand letter, and the email thread — and writes you the claim's story.
For carriers, MGAs, TPAs, and self-insured retentions running ServiceNow as the claims platform of record.
The pain points Lore™ targets in insurance.
Same product, your terms. These features show up the same way in every industry; what changes is the language and the workflow they fit into.
Open a claim, read the loss, the injuries, the parties, and the current posture in minutes — narrated chronologically with citations to the FNOL, police report, demand letter, and adjuster notes.
Ask 'what's the running medical total?' or 'who is the claimant's attorney?' Answer arrives in seconds with citations to the bills and emails it came from.
A 50-page bundle from defense counsel arrives as one PDF and lands in the case as twelve correctly named, correctly tagged documents.
Classify against your line-of-business taxonomy — FNOL, Coverage, Medical, Liability, Legal, Settlement — not a generic vendor schema.
Claim files stay in SharePoint where your IT already governs them. SN holds metadata, the audit trail, and the case spine — not the gigabytes.
Medical bills and treatment records can only be shared with parties that have an active BAA on file. The API blocks the share otherwise — no inbox-cc mistakes.
Removing the body shop from the claim expires every share they hold. No stale links sitting in their inbox a year later.
Today on customer-service cases. Tomorrow on a custom claim table, a subro file, a complaint case — the same workspace, retargeted with one config line.
sn_customerservice_case x_verge_claim A short form gets you into a working demo against a synthetic case.