Give users a feedback button when an idea comes up. Bring the request into Ducalis, connect it to backlog work and tell the people who asked what happens next.
Set up your feedback widgetEmbed a feedback form in your website or web app. Identify signed-in customers and pass the context your team needs to understand their requests.
Review the idea, link it to work and use public statuses and approved release updates to close the loop.
Alex is setting up a team in Acme and needs Custom roles. They send a request through the in-app feedback widget. Your team reviews it in Ducalis and links it to Linear ENG-142.
Choose the Voting Board that receives requests before copying the widget code. Customers can describe feature requests, bugs or other product needs through the embedded form.
Use voter identification to pass a signed-in customer’s email and optional user ID, name or company. Add supported custom attributes such as a plan or market segment when they help your team understand the request.
Your team reviews the resulting idea, adds useful labels and checks matching requests before merging duplicates. Keep a clear customer-facing summary and the evidence needed for the product decision.
┌─ REQUEST IN DUCALIS ───────────┐ │ board Acme feedback │ │ idea Custom roles │ │ author Alex · Acme │ ├────────────────────────────────┤ │ Review request and context │ │ Label: access management │ │ Review matching ideas │ └────────────────────────────────┘
See how to organize feature requests from all your channels →
When Custom roles matches existing work, link it to that issue. If the work is new, use + New to create an issue in Ducalis or your connected task tracker.
The customer’s idea stays connected to the internal work. Compare impact, effort and customer context in Ducalis; your team decides what to build and what belongs on the roadmap.
With a connected tracker, you can link an idea to an existing issue even if that issue has not been imported into a Ducalis scoring board.
Prioritize the linked requests → · Connect your task tracker →
┌─ LINK TO PRODUCT WORK ─────────┐ │ idea Custom roles │ │ issue Linear ENG-142 │ ├────────────────────────────────┤ │ Link existing or create new │ │ Customer context → backlog │ │ Review impact and effort │ │ Team chooses the priority │ └────────────────────────────────┘
Configure idea statuses such as Planned, In progress and Done. Rules map the status of the linked issue to a customer-facing status.
Authors and voters can receive emails when their idea changes status. They control their notification preferences on the Voting Board.
Show progress in your public roadmap and choose the widget’s Public Roadmap configuration to place it alongside the feedback form. If tracker Done precedes the actual release, configure the release-webhook condition before marking the idea Done.
Build a roadmap from customer feedback → · Understand voter notifications →
Once Custom roles is available, prepare a customer-facing announcement. AI can draft it from the linked idea; your team checks availability, benefit, wording and links before approval.
Choose the widget’s Changelog configuration to display approved release updates alongside its feedback form. Explain what changed and where the customer can use it.
Subscribers can also receive release notes according to your configured delivery schedule or send trigger. Status-change emails and release-note delivery have separate settings.
Start on a test page, then check the request reaches the intended board before making the button available to customers.
Open Embed → Feedback/Roadmap/Changelog widget, copy your board’s script into the HTML head and use Verify to check the installation.
Install and verify the code →Keep the feedback form, or add a roadmap or changelog. Select what opens first and customize the button’s label, position, colors and language.
Configure identification and board access. Submit one test request, check its author and context in Ducalis, link it to an issue and verify status and release updates with a test subscriber.
Set up voter identification →
Collect feedback from an iOS app →
See what happens after a user sends a request, and how the same product surface can help them discover updates.
Install the feedback widget, collect one request and connect it to the work your team is planning.
Set up your feedback widgetFollow the widget setup guide → · See the full feedback-to-release workflow →