Your claims

Policy 01.203.2026.004512 · Asuransi Demo

Couldn't load your claimsCheck your connection and try again.

ACA-26-004871Estimate and approval

Collision · Toyota Avanza 1.3 G 2021 · B 1234 XYZ Next: estimate approved by 30 Sep 2026

ACA-26-002317Done

Glass · Toyota Avanza 1.3 G 2021 · B 1234 XYZ

No claims yet

Claims you report in the app, or that Asuransi Demo registers for you, show here.

Report an incident

Without the Client's cookie the proxy sends the Client to /claim. The page reads GET /api/client/claims: the Session's Claims, newest first, the newest 100. A 401 also goes to /claim.
A row holds the Claim number, the status as the Client reads it, the loss type, the Policy's vehicle and plate, and what comes next with its date. The vehicle and plate are the Policy's, from GET /api/auth/client/me: a Client Session holds one Policy.
A row opens its tracker, /claim/claims/{id}. A Claim that is Done, Rejected or Withdrawn has no next step, so its row has no "Next" line.
Loading shows two rows of skeletons. A failed read keeps the frame and shows a banner with Try again.
With no Claims the page says so and offers Report an incident, which opens the install card at /claim/report.

The title "Your claims" is main's page name (claim.page.claims), the header's.
Main's statuses: the chips read main's Client labels. Their tones are drafted: Done is success; Rejected is danger; Reported and Withdrawn are neutral; the others are info, as the mockup's Being checked.
Drafted: the row's layout and "Next: {what} by {date}"; "Couldn't load your claims" / "Check your connection and try again." (after the mockup's tracker); "No claims yet" / "Claims you report in the app, or that Asuransi Demo registers for you, show here."; the second sample Claim, ACA-26-002317 (Glass, Done).
Main's frame as on Your policy, at comfortable Density at every width (#429).

ticket #674 → comment: /claim/claims lists each Claim as drawn: number, status chip, loss type, the Policy's vehicle and plate, and "Next: … by …". Main's ClientClaimRow has no nextDue, so GET /client/claims gains it, as GET /client/claims/{id} has it.
ticket #674 → comment: the empty and failed states (drafted copy above), and Report an incident on the empty state opening /claim/report.
ticket #674 → comment: "Your claims" in the header and the sheet links to /claim/claims; main's CLIENT_PAGES lists it with no route.

Main's stepper (Reported, Being checked, Survey, Estimate and approval, In repair, Ready for pickup, Done) is the Client's status everywhere, so the chips read it. (12 Oct 2026)
Signed in on a phone, the switcher lives only in the burger menu and the header pill goes; signed-out steps keep the pill. (12 Oct 2026)

From client-capture.html#webclient (#180), client/policy.html's frame and main's ClientClaimRow, clientClaimStatus, ClientHeader; #429, #674