Survey
Collect & act
Customer feedback & NPS portal
A customer feedback and NPS portal is where customers answer a 0–10 survey on a public page, the team sees promoter and detractor counts as responses arrive, and feedback worth acting on becomes a follow-up someone owns on a board.
Pattern: RequestsDescribe it to Pory
“We survey customers with the NPS question. Responses should come in through a public form, we want promoter and detractor counts on a home page, and a board to act on what people tell us.”
Viewing as
In plain English
What is a customer feedback & NPS portal?
A customer feedback and NPS portal is where customers answer a 0–10 survey on a public page, the team sees promoter and detractor counts as responses arrive, and feedback worth acting on becomes a follow-up someone owns on a board. 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 success lead and account manager) that shows only what that role should see, and flat pricing with unlimited customers.
What it does
Customers score you 0 to 10 on a public survey page
Survey answers used to pile up in a form tool's own spreadsheet, a long way from the accounts they were about. In Pory customers open a public survey page, give a score from 0 to 10, say why, and add their name and company — no account needed. Each answer arrives as a response the team can act on.
Public pages & formsDone by: Customer success lead
Promoter and detractor counts are live on the home page
Working out NPS meant pulling survey results into a spreadsheet and counting rows by hand. In Pory the team's home page counts responses, promoters and detractors as they come in, so the ingredients of the score are always current. Nobody has to run the numbers the night before the board meeting.
Counts, totals & averagesDone by: Customer success lead
Each detractor's complaint becomes a follow-up someone owns
Detractor comments were read, nodded at and forgotten, because nobody owned doing anything about them. In Pory each piece of feedback worth acting on becomes a follow-up with an owner and a due date, and the team drags it from To do through In progress to Done. The customer who scored you a 3 hears back before they cancel.
Board by statusDone by: Customer success lead
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 & triageWarranty claims portalSubmit → approve → replaceReturns & RMA portalRequest → authorize → refundFeature request board portalSubmit → triage → plannedBug reporting portalReport → triage → fix statusBeta program portalSignups, feedback, releasesProduct reviews portalSubmit → moderate → publish
Your customer feedback & NPS portal, live today.
Describe it in a sentence and send the invite. Unlimited customers, flat price.