New Claim

Step 3 of 3 · The Client's code

This code has ended

A wrong code was entered too many times, or the code is more than 15 minutes old. Nothing was registered. After 5 wrong codes the policy is paused here for 15 minutes.

This lookup has expired

More than 15 minutes passed since you found the policy. Nothing was registered. Find the policy again; the incident you typed is kept in the draft.

Start again

Step 3 of 3. Send the code sends POST /claims/fnol/lookups/{id}/code {channel: "email"} (sendFnolCode), with its spinner on the button: six digits to the Policy's email, shown masked, valid 5 minutes, 5 attempts. There is no channel choice. The email names Asuransi Demo and Demo Motor Works and carries the consent text: the code is the Client's consent and confirms the Workshop.
500 CLAIM_CODE_NOT_SENT is an alert at the top and keeps the lookup. A lookup gone, past its 15 minutes, answers 404 NOT_FOUND and shows "This lookup has expired".
The code is asked on the same screen. "Send a new code" waits 60 s (resendFnolCode), at most 3 times, keeping the attempts; 429 CLAIM_RESEND_TOO_SOON answers one too soon.
Register the Claim sends POST /claims/fnol (registerFnolClaim) with the draft's Idempotency-Key, carrying the code and step 2's details, with its spinner on the button. 400 CLAIM_CODE_INVALID {attemptsLeft} is the field's error; 409 CLAIM_FNOL_ENDED, on the last attempt or a dead challenge, ends it, the last attempt pausing the Policy for FNOL for 15 minutes; 403 CLAIM_OVERLAP as on step 1.
A step-2 field the service refuses (a 400 such as CLAIM_INVALID_PHONE) is an alert at the top with a link back to step 2, at that field; nothing was registered.
Registered, the Claim is assigned to this Workshop with the Service advisor as its PIC, and the draft goes. The app opens the capture guide in Strict mode, compared with the Workshop's location, with the toast "Claim ACA-26-004881 registered"; "Later" leaves it as Capture due.
Back asks in a sheet to save or discard, as on step 2. Ended and expired go back to Claims, and Start again finds the policy again; an expired lookup keeps the incident in the draft.

Drafted: the refused alert "Nothing was registered" / "The Driver's phone isn't a valid phone number." with its link "Fix it in step 2".
Leave? on step 3 is step 2's sheet with its copy, and Back opens it, where the mockup's Back went to step 2: Back on both steps after the lookup asks before leaving FNOL. From step 3, step 2 is reached through the refused alert's link.
No Registered screen: registering opens the capture guide with the toast, as the Client's report does, where the mockup drew a capture stub on this screen.
Main's code-not-sent is a 500, where the mockup said 502.
The mockup's copy stays, with Asuransi Demo and Demo Motor Works for ACA and Autoprima Fatmawati: "We couldn't send the code", the consent line, "The code goes by email to", "Sent by email to … Ask the Client to read it to you.", "Not arrived?" with "Send a new code", "Wrong code. 4 attempts left." (main's text), and the ended and expired screens. Its SMS note goes.

ticket #697 → comment: Step 3 sends the code to the masked email only, with no channel choice, then asks for it on the same screen ("Ask the Client to read it to you.") with "Send a new code" after 60 s; ended and lookup expired each end in Start again.
ticket #697 → comment: A 400 on a step-2 field at registration is an alert at the top of step 3, "Nothing was registered" with the field's text, and a link back to step 2 at that field. Whether the challenge and its attempts survive that 400 is #476's to say.
ticket #697 → comment: Registering opens the capture guide with the toast "Claim ACA-26-004881 registered / You're its contact at the workshop."; there is no Registered screen.
ticket #698 → comment: Leaving step 3 asks in the same bottom sheet as step 2 (save or discard), and Back opens it.

The app is drawn in the phone frame; at phone width the frame drops. (12 Oct 2026)
Pushed screens (a Claim, FNOL) have a back button and the title only, and no tab bar. (12 Oct 2026)
Codes go by email only; no screen shows SMS or WhatsApp as a channel. (12 Oct 2026)
Every overlay is a bottom sheet; a confirmation takes role="alertdialog". (12 Oct 2026)
Leave? on FNOL step 3 (#698) and a step-2 field refused at registration (POST /claims/fnol 400) are drawn. (12 Oct 2026)
After FNOL registers, the app opens the capture guide in its staff Strict state with the toast, and there is no separate Registered screen. (12 Oct 2026)

From staff-app.html (FNOL · Code, #628); #476, #685, #697, #698; main's sendFnolCode, resendFnolCode, registerFnolClaim and their error codes