Form page · /f/<id>
Motor claim: report damage
Report vehicle damage · 3-column grid · own header and theme · Its own page: share the link or open it on a tablet
Media & Evidence package
Motor claims with damage photos: AI damage assessment, decision-table triage and SLA, adjuster review, letters, and photos with faces and plates blurred for repairers.
Connects to Google Gemini
About this package
Insurance claim photo assessment starts from a claim form page where the claimant enters their policy, what happened and uploads photos of the damage (the camera opens on phones).
Analyze Image describes the damage and returns a structured assessment: severity, damaged parts, a rough cost range, whether the vehicle looks drivable and whether the photo matches the story. The Damage triage decision table turns that and the cover into a band (fast track, standard, specialist or coverage check), an estimate band, a decision SLA and whether an inspection is suggested. Every photo is also copied with faces and licence plates blurred, because repairers do not need them.
The adjuster reviews the claim with the AI assessment clearly marked as a hint, picks a repairer from the Approved repairers table and approves the repair, asks for an inspection or declines. Approval and decline letters are generated as PDFs and emailed, and the chosen repairer gets the job with the blurred photos only. The adjuster always decides.
Starts from a form page: share the Motor claim form (/f/<id>) in your app or website; each claim starts the workflow.
Someone fills in a form to start it: the workflow start form (Run dialog in the app, or your own portal posting to the API) or a standalone form page (/f/<id>) whose Form submitted trigger starts the workflow. People complete User Task forms along the way.
How forms workThe flow
Claim with photos
The claimant fills in the themed claim form and uploads damage photos.
AI damage assessment
Analyze Image returns a description, labels and a structured answer: severity, damaged parts, cost range, drivable, consistency.
Triage and SLA
The Damage triage decision table sets the band, estimate band, inspection suggestion and the decision SLA.
Blur for sharing
Each photo is copied with faces and licence plates blurred for repairers.
Adjuster review
The adjuster sees the assessment as a hint, picks a repairer and approves, requests an inspection or declines.
Letters and repairer job
Approval or decline letters are emailed as PDFs; the repairer gets the blurred photos only.
Forms
People start it from a form page (/f/<id>) with its own header, theme and buttons; submitting it starts the workflow. User Tasks show their fields and outcome buttons to the assignee.
Form page · /f/<id>
Report vehicle damage · 3-column grid · own header and theme · Its own page: share the link or open it on a tablet
User Task
{{band}}: {{claim_ref}} ({{form.claimant_name}}) · 2-column grid · own header and theme
From your code
Every workflow can be started over REST, MCP or the CLI, whatever its trigger, with the sample input below. Runs start straight away on the published version; replace <workflow id> with the id the install created.
REST
curl -X POST "$USERTASKS_URL/api/v1/workflows/start" \
-H "Authorization: Bearer $USERTASKS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"workflow_id":"<workflow id>","variables":{"policy_number":"POL-000123","claimant_name":"Riley Example","email":"riley.example@example.com","phone":"+1 555 0100","cover":"Comprehensive","incident_date":"2026-10-29","location":"Sample Street car park","description":"A trolley rolled into the driver door in the car park and dented it.","drivable":"Yes","declaration":true}}'CLI
usertasks workflows inputs <workflow id> # the start form: keys, types, required
usertasks workflows run <workflow id> --input policy_number=POL-000123 --input claimant_name="Riley Example" --input email=riley.example@example.com --input phone="+1 555 0100" … --waitWhat's included
| Type | Name | Details |
|---|---|---|
| Email template | Claim approved | Approval letter to the claimant (PDF attached). |
| Email template | Claim declined | Decline letter to the claimant (PDF attached). |
| Email template | Claim received | Sent to the claimant when the photos arrive. |
| Email template | Inspection needed | Sent when the adjuster asks for an inspection. |
| Email template | Repair job for repairer | Sent to the chosen repairer with the redacted photos (faces and plates blurred). |
| Data table | Approved repairers | Repairers the adjuster can assign; redacted photos are sent to them. |
| Data table | Motor claims | Claims reported with damage photos: AI assessment, triage band, adjuster decision and repairer. |
| Integration | Google Gemini (media AI) | Media AI provider for transcription, image and video analysis and finding what to redact. Paste your Gemini API key on install (aistudio.google.com). To use OpenAI, Azure AI or AWS instead, point the media steps at that integration. |
| Decision table | Damage triage | 6 rules — Triage band, estimate band, SLA and whether an inspection is needed, from the AI damage assessment and the policy. Tune the bands to your book; the AI estimate is a hint for the adjuster, never a settlement. |
| forms | Motor claim: report damage | Claimants report vehicle damage with photos; the claim is assessed, triaged and sent to an adjuster. |
| Workflow | Motor claim photo assessment | 28 steps — Damage photos from the claim form are analysed by AI, triaged by a decision table and reviewed by an adjuster, who approves the repair, asks for an inspection or declines; repairers only get copies with faces and plates blurred. |
Approved repairers · 3 sample rows
NameEmailRegionSpecialtyActive
Motor claims · 1 sample rows
ClaimPolicyClaimantEmailIncidentSeverity (AI)Damaged parts (AI)BandEstimate bandApprovedRepairerStatusDecided by
Requirements
Credentials never travel in a package. The install wizard asks for what your environment must provide, or installs it incomplete until you finish setup.
Integration “Google Gemini (media AI)”Required
Workflow “Motor claim photo assessment” assigneesRequired
Install
Works on UserTasks cloud and on any self-hosted instance. Installing creates the assets above; nothing runs until you complete setup and start it.
curl -fLO https://usertasks.com/gallery/insurance-claim-photo-assessment-1.0.0.utpkg
usertasks packages inspect insurance-claim-photo-assessment-1.0.0.utpkg # offline: checksum, hashes, signature
usertasks packages install insurance-claim-photo-assessment-1.0.0.utpkg --dry-run
usertasks packages install insurance-claim-photo-assessment-1.0.0.utpkg # prompts for each requirement
usertasks packages install insurance-claim-photo-assessment-1.0.0.utpkg --keep-incomplete --yes # in CI; finish with:
usertasks packages complete insurance-claim-photo-assessment -f values.yamlVerify the download
shasum -a 256 insurance-claim-photo-assessment-1.0.0.utpkg should print the file SHA-256. How gallery packages are signed.
Versions
Installing a newer version upgrades in place: local credentials and requirement values are kept, and changes you made are flagged first. How packages work
More packages
Media & Evidence Official
Public records requests from a form to release: statutory SLA, evidence gathering, AI-assisted redaction of video, photos, audio and documents, legal approval and an exemptions log.
Needs:Media AI providerREST APIAssigneesEmail
Media & Evidence Official
Customers upload an ID photo and a selfie: the document is read, checked by rules, the number blacked out for storage, and a person compares the photos and decides.
Needs:Media AI providerAssigneesEmail
Media & Evidence Official
Upload a meeting recording: transcript with speakers, AI-drafted minutes the organiser checks, a task for each action owner and the minutes emailed with an SRT.
Needs:Media AI providerAI modelEmail