Used in
Widget, hosted help, tickets, and review
Feedback Review
Turn user feedback into support improvements.
Collect ratings, product-area feedback, feature requests, and suggestions, then group useful items by product area before they become private follow-up or draft answer improvements.
Ratings, product feedback, requests, and suggestions
Owner review with optional product-area sorting
Support Board and draft-answer handoff
Publish rule
Drafts stay review work until approved
Owner outcome
See what this feature changes in the support loop
Feedback Review
Feedback should improve support knowledge, not become a noisy public roadmap.
AnswerLattice keeps feedback private to the workspace, grouped by the right product area, and useful for support improvement only after owner review.
01 / Feedback Review
Collect multiple feedback types
End users can send general feedback, rate their experience, report product-area confusion, request a feature, or leave a suggestion from the Help Center.
Ratings, product feedback, requests, and suggestionsOwner review with optional product-area sortingSupport Board and draft-answer handoff
02
Review feedback in AnswerLattice
Owners and support staff can inspect feedback inside the AnswerLattice workspace without mixing it into another product or workspace.
03
Group by product area
Owners can assign, change, clear, and filter feedback by the product area it belongs to without asking users to classify it.
04
Use ratings as support pressure
Low ratings and repeated complaints become support signals, so owners can see where help content is failing users.
05
Move selected items to Support Board
Useful feedback can become a private Support Board card with source context, priority, tags, and follow-up notes.
06
Keep answer updates reviewed
Feedback can inform draft answers, but it does not auto-publish knowledge or rewrite customer-facing support.
07
Stay scoped and cost-aware
Feedback rows and signal events are written with AnswerLattice product, tenant, and workspace scope, while owner review uses bounded reads and indexed queries.
Workflow
From user feedback to reviewed support improvement.
Feedback Review gives SaaS owners a clean path from raw end-user input to support follow-up without adding public voting, roadmap management, or helpdesk workflow bloat.
01
User submits feedback
The Help Center captures the selected feedback type, rating, product area, request, or suggestion.
02
AnswerLattice logs the signal
The feedback row stays scoped to pId, tId, and sId, and a lightweight signal event is emitted when enabled.
03
Owner reviews the item
The dashboard shows recent feedback with type, rating, user context, submitted details, and optional product-area assignment.
04
Select useful follow-up
The owner can leave the row as feedback, move it to Support Board, or use it as evidence for draft-answer review.
05
Approve knowledge separately
Any reusable answer still goes through owner review before it becomes official support knowledge.
Connected support outputs
Feedback belongs inside the support knowledge loop.
Feedback Review is useful because end-user sentiment can become Support Board work, visible support gaps, product-area context, and reviewed answer improvements without becoming a separate feedback product.
Feature layer
01
Feedback Review
Feedback Review turns structured support knowledge, safe page context, and owner approval into usable support output.
02
Scattered knowledge
Docs, tickets, releases, screenshots, recordings, and notes become widget help, hosted help, fallback, and answer review from one workspace.
03
Page context
Ratings, product feedback, requests, and suggestions
Support outputs
01
Help Center
End users submit feedback from the same help center where they ask questions.
02
Product Areas
Owners keep feedback grouped by the part of the product where the confusion belongs.
03
Support-gap review
Feedback can join fallback, ticket, and conversation evidence for repeated-gap review.
04
Support Board
Owners can promote selected feedback into private follow-up cards.
05
Answer review
Draft answers stay human-reviewed before any support knowledge becomes official.
Support output layer
Feedback Review is one part of the full support layer.
A founder may start with feedback review, but the value comes from turning it into setup, in-app support, hosted help, fallback, and approved-answer review.
A familiar place for users to get help
Each feature is explained as something buyers already recognize: docs, FAQs, releases, tickets, feedback, notifications, or review work.
Feeds the support suite
The feature does not live alone. It helps turn scattered product knowledge, tickets, and signals into widget answers, hosted help, fallback, and owner review.
Owner control stays visible
Drafts, generated content, ticket gaps, and feedback remain reviewable before anything becomes official support.
Explore the support layer
Set up support
Create your workspace, add team access, turn starter sources into reviewed support drafts, and map the pages where users need help.
In-app help widget
Install one widget, pass safe page hints, accept explicit screenshot context, allow exact app origins, and answer users inside your app.
Help center and tickets
Turn scattered product knowledge into scannable docs, FAQs, owner answers, release notes, widget help, fallback tickets, feedback, and a focused read-only owner brief.
Review approved answers
See missing, stale, or release-affected support, review proposed changes, and approve what becomes official.
Worth checking
Before choosing feedback review, check the product fit.
Answer the evaluation questions before setup: how it launches, what stays safe, and how it differs from nearby support tools.
Setup path
Show how the feature fits into the widget, hosted help, fallback, and owner review before users depend on it.
View product mapSecurity boundary
Review safe page context, blocked private data, owner roles, fallback behavior, and approved-answer review.
Review securityCompare support options
See where AnswerLattice fits against chatbots, helpdesks, and static knowledge bases without treating them as the same product.
Compare optionsQuestions
What owners usually ask about feedback review.
Is this a public roadmap or voting board?
No. Feedback Review is private owner review. Feature requests are captured as support signals, not public votes or roadmap commitments.
Does feedback automatically change answers?
No. Feedback can create evidence for a support gap, but answers still require owner review before approval.
Can owners move feedback into Support Board?
Yes. Selected feedback can become a private Support Board card when it needs follow-up, notes, status tracking, or draft-answer handoff.
Why keep this inside AnswerLattice?
SaaS feedback often exposes missing support content. Keeping it in AnswerLattice lets owners turn user confusion into better help without building a separate feedback platform.
Launch feedback review as part of the full support loop.
AnswerLattice works best when feedback review feeds widget answers, hosted help, tickets, and answer review from the same reviewed support knowledge.