My tickets
Support ticketing portal
A support ticketing portal is where customers submit tickets and follow each one's status, and agents triage every ticket by priority on a board. Each ticket carries a reply-due date, so agents are reminded before a response slips.
Pattern: RequestsDescribe it to Pory
“Customers submit support tickets, our agents triage them by priority and work them through to resolved. Each ticket should have a reply-due date so nothing sits too long.”
Viewing as
In plain English
What is a support ticketing portal?
A support ticketing portal is where customers submit tickets and follow each one's status, and agents triage every ticket by priority on a board. Each ticket carries a reply-due date, so agents are reminded before a response slips. 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 agent) that shows only what that role should see, and flat pricing with unlimited customers.
What it does
Customers file a ticket with the screenshot, not a reply-all chain
Support requests came in through a shared inbox, a contact form and the founder's personal email, and the screenshot was always in a different message. In Pory a customer signs in, writes the subject, picks how urgent it is and the product area, describes the problem and attaches the screenshot. The ticket lands complete, so the first reply isn't "could you send a screenshot?"
Forms to submit a recordDone by: Customer
Urgent tickets stand out on the agents' board, not in an inbox
In a shared inbox an outage and a billing question look exactly the same, and both wait behind last night's out-of-office replies. Agents see each ticket as a card showing its priority, in New, In progress, Waiting on customer or Resolved, and drag it along as they work. The half-size-labels emergency gets picked up first.
Board by statusDone by: Agent
Customers see where their ticket stands without writing in to ask
Every "just checking in on this" email reopened a ticket and pushed it down the queue. In Pory each customer sees only their own tickets, with a progress bar from New through Waiting on customer to Resolved. When an agent needs something back, the ticket says so, and customers stop chasing.
Status tracker for the submitterDone by: Customer
Tickets carry a reply-due date, with a reminder before it passes
Response-time promises lived in a contract PDF, and nobody noticed a missed one until the customer did. In Pory the agent sets a reply-due date on each ticket to match its priority, and gets a reminder in the portal and by email as that date comes up. An urgent ticket can't quietly sit over the weekend.
Notifications & remindersDone by: Agent
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, in its detail view, 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.
Detail view with related items
Open a unit, a pet or a listing to see its details and everything tied to it — requests, visits, offers. Share it by link; edit, change the status or add a related item from there.
Notices & info pages
Check-in details, benefits, updates — a page for a role to read.
Counts, totals & averages
Live figures over the records a viewer is allowed to see.
Control
Who sees which records
Each person sees their own records, the ones assigned to them, their team's or the ones they manage. Fields can be hidden per role. Generated from your description, not set up 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.
Frequently asked questions
More customer support portals
All customer support portalsWarranty claims portalSubmit → approve → replaceReturns & 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 support ticketing portal, live today.
Describe it in a sentence and send the invite. Unlimited customers, flat price.