Customer
Sees only their own requests.
- Pages
- Home, My requests, Uploads, Roadmap, What's new
- Can start
- New request, Upload a file
My requests
Feature request board & public roadmap
A feature request board portal is where customers submit product ideas and follow what happens to each one, the product team triages requests through to planned, and a public roadmap page lets anyone see what's coming and suggest more.
Pattern: RequestsDescribe it to Pory
“Our customers send feature requests. We want them to submit ideas in one place and see what happened to theirs, with the product team triaging them onto a public roadmap.”
Viewing as
In plain English
How Pory sets it up
Pory gives every customer and product team a sign-in of their own. Each customer sees only their own requests. It covers submit → triage → planned. Requests, asked of you, releases and product team live in Pory's own database, so there's no spreadsheet to keep in sync.
What it does
Customers post an idea once, with the reason they need it
Feature requests were scattered across support tickets, sales call notes and a Slack channel called #ideas-maybe. In Pory a customer names the idea, picks the area of the product, explains what it would let them do and attaches a mock-up if they have one. The product team reads the request in the customer's own words, not a paraphrase from a call three weeks ago.
Forms to submit a recordDone by: Customer
The product team drags ideas from new to planned or declined
Triage used to be a spreadsheet session where half the rows were duplicates and nobody remembered who had asked. In Pory each request is a card in New, Under review, Planned, Shipped or Declined, and the product team moves it along as decisions get made. Each card keeps the requester's name and the team's latest update, so someone always knows who to tell.
Board by statusDone by: Product team
A public roadmap page anyone can open, no login required
The roadmap was a slide shown on sales calls and emailed to whoever asked, already out of date by the time it landed. In Pory the roadmap page is public: prospects and customers open it without an account and see every idea marked Planned or Shipped, straight from the same records the team triages. Sales stops attaching "latest roadmap" slides to follow-up emails.
Public pages & formsDone by: Product team
Customers check their own idea's status instead of asking sales
Customers who asked for a feature never heard back unless they chased their account manager, who then chased product. In Pory each customer sees their own requests with a progress bar from New through Under review to Planned and Shipped, and a line from the product team on each. When dark mode ships, the person who asked for it can see that it did.
Status tracker for the submitterDone by: Customer
Who sees what in a feature request board portal
Every person signs in to their own view. This is what each role in the demo gets.
Product team
Sees every request in the portal.
- Pages
- Home, Requests, Uploads, What's new, Triage guide
What’s in the feature request board portal template
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
Requests
- Idea (text)
- Area (choice: Boards, Mobile app, Integrations, Notifications, Permissions)
- Details (long text)
- What would it let you do? (long text)
- Mock-up or screenshot (file)
- Requested by (link)
- Submitted on (date)
- Customers asking (number)
- Latest from the product team (text)
- Status (choice: New, Under review, Planned, Shipped, Declined)
Asked of you
- What we'd like (text)
- Request (link)
- Needed by (date)
- File (file)
- Requested by (link)
- Status (choice: Requested, Uploaded, Checked)
Releases
- Release (text)
- Date (date)
- Area (choice: Boards, Mobile app, Integrations, Notifications, Permissions)
- Status (choice: Scheduled, Shipped)
- What changes (long text)
Product team
- Name (text)
- Role (text)
The parts behind this portal
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
Collect
2 partsForms
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.
Decide
2 partsStatus 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.
Control
3 partsWho sees which records
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.
Passwordless sign-in
A sign-in link by email, by default. Password sign-in if you'd rather.
Your brand
Your domain, your colors, your logo. Members see you.
Frequently asked questions
A customer signs in with a link sent to their email and lands on Home. They see Home, My requests, Uploads, Roadmap and What's new, and only the requests that are theirs. From there they can use “New request” and “Upload a file”.
The public pages: Roadmap and What's new. Anything about a particular person stays behind their sign-in.
More customer support portals
All customer support portalsSupport ticketing portalSubmit & triageWarranty claims portalSubmit → approve → replaceReturns & RMA portalRequest → authorize → refundBug reporting portalReport → triage → fix statusBeta program portalSignups, feedback, releasesCustomer feedback & NPS portalCollect & actProduct reviews portalSubmit → moderate → publish
Build your feature request board portal with Pory
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 customers.