Tickets, claims and requests come in through forms, your team triages them on a board, and customers follow their own status instead of asking for an update.
In plain English
A customer support portal lets customers submit tickets, claims or requests and follow their status themselves, while the support team triages and resolves them in one queue. Pory generates one from a plain-English description, with each customer seeing only their own tickets.
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.
An application page, a notice board, an open directory: pages and forms anyone can use without signing in, on your domain.
People create their own account and land in the role you chose for them.
Upload and view files on the record they belong to, not in a folder named FINAL v2.
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.
Cards in columns. Drag a record to move it along.
Renewals, expiries and overdue work, in an in-app inbox and by email.
Live figures over the records a viewer is allowed to see.
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 it's for and what each person needs, then send the invite. Unlimited members, flat price.