My claims
Warranty claims portal
A warranty claims portal is where customers claim a repair or replacement with their proof of purchase attached, the warranty team approves or rejects each claim with a reason, and customers follow their claim through to a replacement.
Pattern: RequestsDescribe it to Pory
“Customers with a faulty appliance should be able to file a warranty claim with their receipt. Our warranty team approves or rejects it, and approved claims get a replacement sent.”
Viewing as
In plain English
What is a warranty claims portal?
A warranty claims portal is where customers claim a repair or replacement with their proof of purchase attached, the warranty team approves or rejects each claim with a reason, and customers follow their claim through to a replacement. It follows the Requests pattern: someone submits, someone decides, it moves through statuses. Pory generates it from a plain-English description, with a login for each role (customer and warranty team) that shows only what that role should see, and flat pricing with unlimited customers.
What it does
Customers claim with the receipt and serial number attached up front
Warranty claims arrived by email with no receipt, then a second email with a photo of the wrong receipt, then a phone call. In Pory a customer says what's wrong, picks the product, enters the purchase date and serial number, and uploads their proof of purchase. The warranty team gets a complete claim the first time, and the back-and-forth ends.
Forms to submit a recordDone by: Customer
The warranty team rules on each claim with the reason written down
Deciding a claim meant digging the receipt out of an inbox and explaining a rejection in a fresh email, which the customer then disputed by phone. In Pory the team opens the claim with its serial number and proof of purchase, and approves it or rejects it with a decision note on the claim. The customer reads the reason where they filed it.
Approve / reject with a reasonDone by: Warranty team
Customers follow their claim from submitted to replacement sent
"Has my replacement shipped?" was a call the team took several times a day. In Pory each customer signs in to see only their own claims, with a progress bar through Submitted, Under review, Approved and Replacement sent. They know the new blender is on its way before they think to ring.
Status tracker for the submitterDone by: Customer
The parts every portal is built from
Pory generates a portal from these pieces and wires the permissions between them. The same parts run a grant round, a help desk, and a tenant portal — only the names on the pages change.
Collect
Forms
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
Public pages
An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.
Self sign-up
People create their own account and land in the role you chose for them.
File attachments
Upload and view files on the record they belong to — not in a folder named FINAL v2.
Decide
Approve / reject with a reason
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
Status tracker
“Where's my request?” answered as a progress bar on the submitter's own page.
Board by status
Cards in columns. Drag a record to move it along.
Checklists
Task lists ticked off per record, with progress — onboarding runs, inspections, opening duties.
Assign to a person
Name who a record is for and it lands on their list, and nobody else's.
Notes & scores
A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.
Reminders by date
Renewals, expiries and overdue work, in an in-app inbox and by email.
Share
Tables
Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.
People directory
Portraits, names, and roles from a table, shown only to the roles allowed to see them.
Calendar
Records on a month or week view, by date.
Gallery & image grid
Records as cards or photos.
Record pop-up & linked records
A shareable pop-up with a record's details and what's linked to it. Edit, change status, or add a linked record from there.
Notices & info pages
Check-in details, benefits, updates — a page for a role to read.
Counts, totals & averages
Live figures over the rows a viewer is allowed to read.
Control
Role & row access
Own, assigned, managed, and team rows; hidden fields per role. Generated from your description, not configured field by field.
No-Password Doors
A sign-in link by email, by default. Password sign-in if you'd rather.
Your brand
Your domain, your colours, your logo. Members see you.
On purpose
Four things Pory won’t do
A portal runs a program, a service, or a process. These jobs belong to tools built for them, and Pory keeps the records around them instead.
Take payments
Pory tracks who owes what and who has paid. It doesn't collect the money — keep your payment tool for that.
Book time slots
Availability, capacity, time zones, and reschedules are a whole product. Pory holds what happens after the booking.
Host the conversation
No feeds, threads, likes, or polls. A note on a record, yes; a forum, no. Where members talk is another tool's job.
Plan routes
Pory keeps the service record, not the map.
Frequently asked questions
More customer support portals
All customer support portalsSupport ticketing portalSubmit & triageReturns & RMA portalRequest → authorize → refundFeature request board portalSubmit → triage → plannedBug reporting portalReport → triage → fix statusBeta program portalSignups, feedback, releasesCustomer feedback & NPS portalCollect & actProduct reviews portalSubmit → moderate → publish
Your warranty claims portal, live today.
Describe it in a sentence and send the invite. Unlimited customers, flat price.