Use case · By industry
AI on claims, with a human yes.
AI drafts; a person approves; the record shows both.
Insurance and Pensions
AI can speed claims work but should not decide alone.
A claim note
The assistant drafts a note for the claims file.
Draft a note for this case.
A status change
Changing a claim status waits for the claims lead.
Update this record.
A member query
A pension balance question answered within role.
Summarise this account.
See it work
Watch it happen.
Step 1 of 4: Request
“Mark claim CL-7710 as approved for payment.”
Every request starts with a named person and a named agent.
Simplified example. Names and records are invented.
Text version
Peter K. (Claims Handler) asks Claims assistant: "Mark claim CL-7710 as approved for payment." The role check returns: Approval required. Human approval: Rejected. Every step is written to the audit log.
01 Request
Peter K. · Claims Handler · Claims assistant
Mark claim CL-7710 as approved for payment.
02 Role check
Approval required
- Role
- Claims staff (from your directory)
- Read
- Allowed
- Change
- Needs approval
Read-only first. Changes wait for a person.
03 Human approval
Rejected
- Approver
- Claims lead
- Action
- Change claim status, 1 claim
- Risk
- High
- Expires
- In 30 minutes
The claims lead rejects the status change. The draft note is kept; nothing is paid.
04 Audit log
- 09:14:02 · request · peter.k · claims-assistant · update_claim_status CL-7710
- 09:14:02 · policy · role=claims-staff · read=allow · change=approval_required
- 09:14:03 · approval · sent to claims-lead
- 09:21:47 · approval · rejected by peter.o
- 09:21:47 · closed · no change made
- 09:21:47 · logged · event 7f3a…e21 · on the record
See this in your own organisation.
Start with a free assessment. Two weeks. Read-only.
A one-page answer for your CEO and CISO. Assessments are offered at our discretion.