VoteWant provides a feedback board that a product owner can put on a website, app, or game. A VoteWant property has a generated widget snippet. VoteWant presents one board for each product property. VoteWant's product page describes customer feature requests, bug reports, and votes as feedback inputs for an owner's product decisions. The board belongs to the product property named in VoteWant, while the widget supplies the feedback entry point on the product's own interface.

VoteWant is positioned as customer request tracking for product owners.

VoteWant calculates lexical duplicate suggestions before a public request is submitted, and its owner inbox can show duplicate clusters for review.

Define one intake path for product requests so customer observations do not split across inboxes, chat transcripts, and private notes. Record the source when a request enters the review queue.

Use a concise request title that names the customer problem rather than promising a solution. Preserve the contributor's original context separately from the owner's interpretation.

Review new intake on a predictable schedule.

Compare each new request with existing records before creating another roadmap item.

Treat votes as participation evidence, not an automatic priority score. Consider severity, recurrence, affected users, strategic fit, and the effort required to test a response.

Use a small status vocabulary that reflects decisions the team actually makes. Avoid labels that imply delivery commitments before work has been scheduled.

Add decision history when an owner investigates, defers, declines, or accepts a request. State which evidence changed the decision so later reviewers can understand the tradeoff.

Close obsolete records, update relevant context, and link shipped work to the problem it was intended to solve.

Separate customer demand from internal, synthetic, and agent-generated activity. Private, depublished, and otherwise non-public VoteWant boards return 404 from the public board API, which follows the same publication rules as rendered board pages.

When a browser loads the installed VoteWant script, it sends a minimal installation observation to VoteWant; the setup evidence check reads that server record and does not mark installation complete merely because a button was clicked. Keep owner credentials on a server, label each token by consumer, and revoke it when the integration ends.

Measure the path from intake to owner response rather than counting submissions alone. Look for missing context, slow review, and decisions that never reach contributors.

VoteWant public request pages include a Decision history section, and approved VoteWant-owned demo content can show provenance and visible owner decisions.

VoteWant renders public board visitors as anonymous until they authenticate, while public request submission and voting require a verified human identity; a verified human can vote once per request.

A developer may choose an existing interface element for the VoteWant launcher with the widget's data-target option.

VoteWant documents data-theme, data-shape, and data-color options for the widget launcher while retaining VoteWant attribution and the standard modal behavior.

The data-target option accepts a CSS selector for an existing page element; an invalid or absent target preserves placement immediately after the script tag.

GET /api/v1/boards/{board-slug} returns an activated board's public name, owner name, and public request summaries; the endpoint is CORS-enabled and requires no secret.

VoteWant instructs owners to keep scoped, revocable owner tokens in a server-side secret manager and not in a browser, app bundle, or game client; the current owner API creates private properties while setup progression and activation remain separately gated.

Start by naming the decision you need to make. Write a narrow request title, describe the observed problem, and separate the requested outcome from a proposed implementation. This keeps your review focused on customer need instead of locking your team into the first solution someone suggests.