Feedback & Roadmap

What the package handles

What you can build with it

• An embedded customer form with owned submission history.
• Original request records, lexical grouping, manual merges and deduplicated authenticated votes.
• Reviewed public roadmap snapshots, private decisions and permitted follow-up.

Supported behavior

• Signed-in customer feedback form and own-submission history
• Original requests, title-word grouping and manual topic merges
• Authenticated voting and private decision history
• Separately reviewed read-only public roadmap
• Permitted Resend or HTTPS follow-up

Before you choose

Will it fit your project?

Who it is for

• Product teams receiving feedback through their app.
• Businesses publishing progress without exposing private customer submissions.

Runtime and connections

Current packages run on Node.js 22.13+ and PostgreSQL 17. You provide hosting and connect the package to your existing app. The included guide describes the supported integration; this is not a hosted service.

Depending on the features you enable, setup can require your own Resend accounts and credentials. Their usage, plans and transaction charges are separate from the source purchase. Check the supported behavior below before choosing a connection.

A useful handoff to your coding agent

How setup works

The source package includes local setup instructions, an integration guide, examples, help articles and verification resources. Your agent can use those files without signing in to a hosted reference page.

1. Check the requirements. Your agent inspects the application, runtime, database and supported connections before making changes.
2. Configure your installation. Answer the product-specific questions below, connect your own accounts where needed and retain the configuration privately.
3. Connect and verify. Use the included checks and a representative workflow, then verify any chosen external service separately before relying on it.

Questions to prepare

• Where should signed-in customers submit feedback, and who reviews it?
• Which categories and title-word rules suit the product?
• Which summaries may appear publicly, and who publishes roadmap changes?
• Is follow-up wanted, and how are verified contact details and permission recorded?

What your agent checks

• Submit as two customers and isolate their private histories.
• Keep original wording and private decisions out of the public roadmap.
• Publish, replace and withdraw a roadmap snapshot.
• Deduplicate votes and suppress follow-up after permission is withdrawn.

Scope of this edition

Important limits

The public roadmap is read-only; feedback and voting require app-authenticated customers. Grouping compares title words. Private topic changes do not silently replace published announcements, and the host must verify addresses used for email follow-up.

• Grouping is lexical, not semantic or AI prioritization.
• The existing app authenticates feedback submissions and verifies email ownership. The public roadmap is read-only; anonymous comments and votes are not supported.
• Public summaries are separate publication snapshots. Republish explicitly to change their title, explanation or status; withdraw before a private merge when needed.
• Topic summaries contain operator-selected titles; choose titles suitable for all authenticated readers.
• Grouping/operator lists inspect at most 1000 topics or requests. Each topic supports 1000 requests and 5000 voters.
• One request export at a time. In-flight messages cannot be recalled.