Customer Feedback Portal

What this is for

Turn scattered customer requests into a visible, evidence-backed conversation without losing workspace control.

When this helps

• Requests arrive by email and disappear into private threads.
• Customers cannot tell whether an idea was seen or already planned.
• Product teams collect votes but still lack the original context and follow-up path.
• Public feedback can expose private workspace data if the boundary is not explicit.

How it works

Enable a public roadmap for a workspace and share its slug. Visitors can submit an idea, vote with a browser identity, comment, and follow status changes by email. New submissions and comments are moderated before publication. The authenticated Feedback view lets the product team triage, publish, set status, set priority and quarter, merge duplicates, and notify subscribers. Public responses only expose approved requests and comments from the matching workspace.

Before you start

• A public roadmap slug enabled for the workspace.
• A customer idea with a clear title and problem description.
• Optional name and email when the customer wants status updates.
• A moderator who can approve, hide, merge, or update the request.

What you should see

• A persistent feature request linked to the workspace.
• Public votes, moderated comments, and subscriber status.
• A customer-visible status such as planned, in progress, done, or closed.
• A private product queue where evidence and duplicates can be managed safely.

Try it now

1. Open Settings → Roadmap and enable the public roadmap setting.
2. Share /r/<your-slug> with customers or add it to a support reply.
3. Review new submissions in Customer Feedback and approve only the ideas you want public.
4. Set the status, priority, target quarter, and owner context; merge duplicates instead of creating competing records.
5. Let customers follow an approved idea and unsubscribe from the visible email link at any time.

A real example

A customer submits “Let me export a filtered report” and includes the workflow that failed. The team approves it, merges two similar requests, marks the target quarter, and follows the status. The public board shows the shared problem and current status; the private workspace keeps the internal evidence and prioritization rationale.

Your next move

Connect the portal to Product Intelligence and Prioritization so public demand is considered with usage, revenue, support, and delivery evidence.