Deck Docs

Where feedback goes

How widget submissions move from your product into Deck insights and projects.

Where feedback goes

End-to-end flow

  1. User (or your backend) submits via @deck-io/feedback or @deck-io/feedback/server
  2. Deck stores a raw submission immediately under Manage → Widgets → [your widget]
  3. Deck snapshots the widget’s current Project link onto that submission (immutable for that row)
  4. When free-text is present, the submission stays pending until Deck’s weekday batch synthesizer claims it
    • Schedule: every 6 hours UTC, Monday–Friday
    • Uses organization synthesis credits
  5. Insights appear in Visualize (themes, categories, etc.)
  6. If the submission snapped to a Project, Deck may create Project Evidence and show the response under Build → Projects → [project] → Feedback
  7. Project Feedback → Synthesis can auto-generate a story when enough new widget-backed insights exist for that Project

Rating-only submissions

Submissions without a message stay raw (sentiment / thumbs only — no AI synthesis).

Empty or credit-exhausted batches never delete stored raw feedback.

Operator visibility

Manage → Widgets shows batch run status for operators:

  • latest run
  • counts
  • when a scope hit the 100-item cap and will continue in the next window

Project linking reminder

Link widgets to Projects for future free-text submissions only. Changing the link later does not rewrite past rows.

See also Projects.

Next

Security