RefId User Identity
RefId identity lets teams collect feedback without forcing signups. Add a refId to the public board URL and Request Mark uses it as the user's voting and commenting identity, giving founders clearer demand signals without extra user friction.
When it helps
Why teams use this
Scattered feedback slows small teams down
startups, indie hackers, SaaS teams, and micro-SaaS builders often hear requests across email, support, calls, chat, and founder replies. Request Mark gives that signal a structured place to live.
Internal tools are not public feedback tools
Delivery tools are useful after a decision is made. A feedback board helps users submit, vote, and follow requests before work becomes an internal ticket.
Visible progress builds trust
Statuses and admin updates help users understand whether a request is new, planned, in progress, shipped, or closed.
What this helps you do
After setup
What improves after setup
A clearer intake path
Teams get one page to share when a customer asks for a feature, instead of manually copying notes into a spreadsheet or backlog.
Better prioritization signals
Votes, comments, requester identity, and status history create a more useful demand picture than memory or gut feel.
A faster path to delivery
When a request has enough signal, the team can move it into Linear, Trello, or the delivery system that owns implementation.
How it works
- 1Choose the user or account identifier you already trust.
- 2Append it to the board link as the refId parameter.
- 3Send the link through the channel where the customer asked for the feature.
- 4Review requests and comments with the user identity preserved.
FAQ
What does refId mean?+
RefId is the identifier Request Mark uses to recognize a public board visitor. It can be an email, account ID, customer ID, or another internal reference.
Can refId replace a login wall?+
For feedback collection, yes. It lets users vote and comment from a secure link without creating a Request Mark account.