Use case · By industry
AI in banking, with control.
Role checks, human approval for changes, and a full record.
Banking
Staff and agents want AI on customer information.
A policy question
An officer asks the assistant to explain a product rule.
Explain this product rule.
A customer summary
The assistant summarises one account, within the officer's role.
Summarise this account.
A record change
A change to contact details waits for a supervisor.
Update this record.
See it work
Watch it happen.
Step 1 of 4: Request
“Update the phone number on customer record C-10428.”
Every request starts with a named person and a named agent.
Simplified example. Names and records are invented.
Text version
Amina K. (Relationship Officer) asks Staff assistant: "Update the phone number on customer record C-10428." The role check returns: Approval required. Human approval: Approved. Every step is written to the audit log.
01 Request
Amina K. · Relationship Officer · Staff assistant
Update the phone number on customer record C-10428.
02 Role check
Approval required
- Role
- Branch staff (from your directory)
- Read
- Allowed
- Change
- Needs approval
Read-only first. Changes wait for a person.
03 Human approval
Approved
- Approver
- Branch operations supervisor
- Action
- Change phone number, 1 record
- Risk
- Medium
- Expires
- In 30 minutes
The branch operations supervisor approves. Nobody approves their own request.
04 Audit log
- 09:14:02 · request · amina.k · staff-assistant · update_contact C-10428
- 09:14:02 · policy · role=branch-staff · read=allow · change=approval_required
- 09:14:03 · approval · sent to branch-ops-supervisor
- 09:21:47 · approval · approved by peter.o · maker-checker ok
- 09:21:47 · executed · update_contact · result=success
- 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.