A Reviewable Customer Portal Workflow

Try a fictional request, review and integration flow. See how incomplete information, approval and duplicate protection shape the first release.

Try the request and review boundary

Choose a fictional case and walk through the first release. Every action stays in this browser.

Customer request
Demo request R-014, update an account contact preference.
Account reference
Example account A-104
Workflow status
Destination records in this demonstration
0

A demonstration of the boundary

This is a fictional, local-only workflow. It creates no account, sends no record, connects to no client system and makes no payment or insurance decision. Reloading clears its state.

The customer request, reviewer decision and integration record are different states. Missing information should block approval. A retry should reuse the approved request reference instead of creating a second record.

What a production version also needs

The browser demonstration does not implement authentication, authorisation, server-side validation, durable queues or a real idempotency store. A production version needs those controls in the relevant backend and integration services. Client-side buttons cannot enforce a real access boundary.

The filled architecture decision explains the fictional first scope. The Insync project is a separate published example of connected insurance software delivery.