Ideas and votes
A public ideas page and a website widget where people post, vote and comment after an email code.
Build what customers ask for, and tell them when it ships
Collect product ideas from customers, let them vote, and show what is planned and what shipped.
Each domain has boards (feature requests, bugs, integrations) of numbered posts with a status (open, under review, planned, in progress, shipped, closed), visibility, priority, tags, an ETA month and internal notes. On feedback.<domain>/ideas people browse, search and sort ideas (trending, top, new), see similar ideas while they type, and vote, comment or post after a 6-digit email code: one vote per person per idea, with Gmail dots and +tags counted as one person. Each idea has its own page with a progress timeline; /roadmap groups ideas by status and /changelog lists releases with the ideas they answer. An /embed.js button opens the same ideas, roadmap and updates in a panel on any website. The team works from an inbox of new posts with "looks like" matches, merges duplicates (votes and voters move), changes a status with a note that emails the voters (the first 25 at once, the rest by a cron every 15 minutes, with an opt-out link) and publishes changelog entries that ship their linked posts. Insights by week, status, board and tag, CSV, POST /api/v1/posts for Support and other servers, webhooks, and Claude for duplicate suggestions, themes and changelog drafts.
What Feedback does for you.
A public ideas page and a website widget where people post, vote and comment after an email code.
An inbox of new posts with likely duplicates, one-click merges and status changes with a note.
Ideas grouped by status, and releases linked to the ideas they answer.
A suggested path for Feedback. What you can do depends on your access in the app.
Link to the ideas page or add the widget to the website.
Merge duplicates, set a status and reply.
Publish a changelog entry; voters get an email.
Live host, inventory, governance, health checks, verification, dependencies and history.
Each domain has boards (feature requests, bugs, integrations) of numbered posts with a status (open, under review, planned, in progress, shipped, closed), visibility, priority, tags, an ETA month and internal notes. On feedback.<domain>/ideas people browse, search and sort ideas (trending, top, new), see similar ideas while they type, and vote, comment or post after a 6-digit email code: one vote per person per idea, with Gmail dots and +tags counted as one person. Each idea has its own page with a progress timeline; /roadmap groups ideas by status and /changelog lists releases with the ideas they answer. An /embed.js button opens the same ideas, roadmap and updates in a panel on any website. The team works from an inbox of new posts with "looks like" matches, merges duplicates (votes and voters move), changes a status with a note that emails the voters (the first 25 at once, the rest by a cron every 15 minutes, with an opt-out link) and publishes changelog entries that ship their linked posts. Insights by week, status, board and tag, CSV, POST /api/v1/posts for Support and other servers, webhooks, and Claude for duplicate suggestions, themes and changelog drafts.
Support tickets belong to Support; testimonials and NPS belong to Reviews; polls belong to Engagement.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
feedbacks.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.