Policyholder
Sees only their own claims.
- Pages
- Home, My claims, Documents, Payments, My policies, Emergency help
- Can start
- New claim, Send a document
An insurance claims portal is where policyholders file a claim with photos and follow it to settlement, and adjusters approve or decline each claim with the reason on the record.
Pattern: RequestsDescribe it to Pory
“We're a regional insurer. Policyholders should file claims with photos of the damage, adjusters approve or decline each one, and the claimant can see where their claim stands.”
My claims
In plain English
Pory gives every policyholder and adjuster a sign-in of their own. Each policyholder sees only their own claims. It covers file → adjust → pay. Claims, documents, visits and repairs, payments, letters, policies and claims team live in Pory's own database, so there's no spreadsheet to keep in sync.
What it does
Claims started with a phone call, a claim number read out twice and photos sent to an inbox nobody matched to the file. In Pory the policyholder uploads photos of the damage, picks the claim type, and gives the date and an estimated cost. The adjuster gets a complete claim on day one, not a callback list.
Decisions went out in letters that took a week to arrive and explained very little. The adjuster opens the claim, looks at the photos, the estimate and the reports linked to it, and approves or declines it; a decline carries a note the policyholder can read. Fewer complaints start with "nobody told me why".
The claims line spent most of its day answering "where's my claim at?" Each policyholder sees their own claims move from Submitted to Under assessment, Approved and Settled, with the inspector's visit and what's been paid alongside. The phone queue shortens, and the people still calling have a question worth an adjuster's time.
Every person signs in to their own view. This is what each role in the demo gets.
Sees only their own claims.
Sees every claim in the portal.
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How Pory builds a portal
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
“Where's my request?” answered as a progress bar on the submitter's own page.
Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. Pory sets this up from your description, and you can adjust it in the editor.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colors, your logo. Members see you.
Describe who signs in and what each person needs, and Pory builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited policyholders.