I Hear What Customers Say In the ProductSo Feedback Never Gets Lost

Improve Your Product

I Meet Customers Where They Use Your Product

Drop the Deck Collect widget into any page. Thumbs, a short note, or your own UI. Every response reaches Deck with who said it and where, and shows up in your inbox right away.

I Turn Written Feedback into Insights

Every weekday, I read the new written responses and turn them into insights, sorted into the themes you already track. Rating-only responses are kept just as they came in.

I Close the Loop on What You Ship

Link a widget to a Project and the feedback that arrives from then on lands on its Feedback tab. I turn it into insights that become Project evidence, and write up how it landed.

Install in Minutes. Or Let Your Agent Do It.

Create a widget, add a publishable key, and mount FeedbackDialog or ThumbsFeedback. Publishable keys only send feedback in, so they're safe in the browser. Or paste one prompt into your coding agent.

View @deck-io/feedback on npm

Add Deck's AI Skills to Make your Agents Savvy

Add skills to agent

Playbooks

Step-by-step workflows that use Deck Collect. Run each one in Deck or hand it to your AI agent.

Frequently Asked Questions

Deck Collect is in-product feedback for your app. A widget SDK, @deck-io/feedback, sends thumbs and written feedback from your product into Deck, where it lands in your inbox and is turned into insights. You may also hear it called the Deck widget.

Run pnpm add @deck-io/feedback, wrap your app in DeckProvider with a publishable key, and mount FeedbackDialog or ThumbsFeedback with your widget ID. You can also paste the install prompt from Deck into a coding agent, or ask your AI assistant to create the widget through Deck MCP. You create the publishable key yourself in Settings.

Yes. The headless useSubmitFeedback hook and submitFeedback function send feedback from any form or design system, and a server entry covers Node, Route Handlers, and Server Actions.

Yes. Publishable pk_ keys can only send widget feedback into Deck, and they are stored hashed. They are separate from secret dk_ API keys, which the SDK never uses.

New responses show up in your Deck Collect inbox right away. Written responses are turned into insights in a scheduled batch each weekday. Rating-only responses are stored as they are and never sent to AI.

Yes. Link a widget to a Project and new written responses land on its Feedback tab and become Project evidence. Relinking a widget only affects future responses.

The rating, the message, the user ID you pass in (plus an optional email and name), and any context you choose to add. In the browser, it also captures the page URL without query strings or hash fragments by default, and you can switch that off or widen it.