Sign in · Prototype

[Product name] Language

Report a claim

Enter the policy number and the plate on your policy. We'll send you a code to sign in.

No policy matches this number and plateCheck both against your policy document and try again.

We can't send you a codeYour policy has no email on file. Call the call centre to report your claim.

Sign-in paused for this policyToo many wrong codes. Try again in , or call 021-3199-9100.

Need help?021-3199-9100 · 24 hours

Need help?021-3199-9100

Need help?Contact Asuransi Demo's call centre

We only use your details to find your policy. Privacy

Use a different policy

We'll email you a code

Policy 01.203.2026.004512 · B 1234 XYZ, insured with Asuransi Demo.

We couldn't send your codeSomething went wrong on our side. Try again in a moment.

Sign-in paused for this policyToo many wrong codes. Try again in , or call 021-3199-9100.

The code works for 5 minutes.

Back

Check your email

We sent a 6-digit code to d************o@customer.test. It works for 5 minutes.

Didn't get it? That was the last resend. Start again for a new code.

This sign-in has ended

The code expired, or a wrong code was entered too many times. Start again for a new code.

Work for an insurer or a workshop? Staff sign-in

C1 is the Client's sign-in in the app: web's three steps, rules and copy (the Client's web sign-in), in the app frame. Signed out, the header holds the brand and the language pill, which changes the app in place.
The capture email's link opens the app when it is installed and fills in the Policy number and plate (#667). Opened without a link, both are empty.
POST /api/auth/client/policy {policyNumber, plate}; 404 IDENTITY_POLICY_NOT_FOUND marks both fields and its help box shows the platform's call centre; 409 IDENTITY_POLICY_NO_CONTACT shows the Insurer's own number, or "Contact Asuransi Demo's call centre" when it has none.
429 IDENTITY_POLICY_LOCKED shows "Sign-in paused for this policy" with its countdown from retryAfter and the Insurer's number, on step 1 and on Send code. Five wrong codes for one Policy within 15 minutes, across challenges, pause it for 15 minutes.
Other codes are form errors above the fields, from errorCode, falling back by kind; no answer shows "We couldn't connect…", and 429 RATE_LIMITED "Too many attempts…". Steps 2 and 3 show them in the same place.
POST /api/auth/client/sign-in {lookupId, channel: "email", client: "mobile", locale}: the code goes by email only, to the Policy's email, masked one star per hidden character. The app keeps its Session in body tokens.
POST /api/auth/client/sign-in/code {challengeId, code}: 6 digits, valid 5 minutes, 5 attempts; 401 IDENTITY_CHALLENGE_EXPIRED shows the ended card. Resend after the countdown, at most 3 per challenge; the third shows "That was the last resend…" with no form error.
A passed code opens consent, then Report an incident, when the Client is reporting a new Claim, or Your claims when they have no draft. From a staff-registered Claim's capture email it opens that Claim's consent.
"Staff sign-in" under C1 opens staff sign-in (#628: one app, two sign-ins). The app remembers which kind signed in last and opens on it; signing in as one kind signs the other out.
A Client's capture link opened while staff are signed in asks first, in a sheet: Stay signed in returns to the staff Claims tab; Sign out and open sends POST /api/auth/sign-out {refreshToken}, with its progress on the button, then opens C1 filled in from the link.

Web's sign-in, newer than the mockup: three steps ("Continue", "We'll email you a code", "Check your email"), web's copy and every state client/claim.html draws, for the mockup's one screen with "Send code" (decision 4; #668's "C1 in three steps as on web").
The capture link comes by email: the mockup's "Opened from your WhatsApp link: both are filled in." goes (v1 sends email only, #549).
The main action sits in the footer, as on every app screen; each step's alerts stay above its fields, and "Use a different policy" and "Back" stay web's text links.
"Staff sign-in" is a text line under Continue, with staff-app.html's copy "Work for an insurer or a workshop?" (#628). staff-app.html draws it as an outline button in a card.
The capture-link question is a bottom sheet over C1 filled in from the link, with staff-app.html's copy and Rina Santoso's name; the mockup drew a centred dialog.

ticket #668 → comment: C1 is web's three steps with web's copy and states, in the app frame: the brand and the language pill in the header, the step's button in the footer.
ticket #668 → comment: A passed code opens Report an incident when reporting, Your claims when there is no draft, or the Claim's consent from a staff-registered Claim's capture email.
ticket #667 → comment: The capture link arrives by email (v1 sends email only); the mockup's "WhatsApp link" wording goes.
ticket #688 → comment: "Staff sign-in" is a text line under C1's Continue: "Work for an insurer or a workshop? Staff sign-in".
ticket #688 → comment: a Client's capture link opened while staff are signed in asks "Sign out of your staff account?" in a bottom sheet, with "Stay signed in" and "Sign out and open", the progress on that button.

The app is drawn in a phone frame on a wide screen; at phone width the frame drops. (12 Oct 2026)
C1 sign-in is web's three steps with web's copy and states (client/claim.html). (12 Oct 2026)
Signed in, the language lives in the Account tab only; signed out, sign-in keeps the pill. (12 Oct 2026)
The staff link stays the text line under Continue, and opens staff sign-in. (12 Oct 2026)
Every overlay is a bottom sheet; a confirmation is an alert dialog. (12 Oct 2026)

From client/claim.html, client-capture.html (Sign-in, #180) and staff-app.html (C1 with the staff link and the capture-link question, #628); #667, #668, #688