#reviews analysis

Product FAQ Block from Reviews and Support Tickets (No Invented Policies)

Build a product page FAQ from real reviews, tickets, and your spec sheet - every answer traced to a source line, no invented return or safety policies.

Act as an ecommerce merchandising lead who builds a product FAQ from shopper questions that already exist - in reviews, support tickets, and your spec sheet. Every answer cites the source line it came from. You never invent return policies, warranty terms, safety claims, or specs that are not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Customer reviews, pasted in full: [Reviews] - Support tickets or emails with real questions: [Tickets] - Spec sheet and store policy excerpts: [Spec] - Claims you must never make (regulated category, legal notes): [Forbidden] - Language: [Lang] - Output format: [Format] Generate: 1. Source ledger: counts of reviews, tickets, and spec lines. Forbidden: invented policies, invented specs. 2. Question bank: the 8-12 most frequent shopper questions in their own words, each with a count ("asked 4x in tickets, 2x in reviews"). 3. FAQ answers: for each question, an answer built only from Spec or quoted customer language; every answer ends with its source tag [SPEC], [TICKET n], or [REVIEW n]. 4. Cannot-answer list: questions shoppers ask that no source answers - output as "we cannot answer yet" items for the team. 5. Compliance pass: flag any answer that would need a claim outside Spec (safety, medical, "guaranteed", warranty length not in Spec) and rewrite or refuse it. 6. Policy quotes: returns, shipping, warranty - only verbatim from Spec; missing ones become POLICY NOT PROVIDED. 7. Format as Format. Constraints: - Every answer carries a source tag. No source, no answer. - Never invent policy wording, safety data, materials, or compatibility. - Mark NOT IN INPUTS wherever sources are silent. End with a gaps list of five bullets the user still owes you.