Customer Feedback Themes â€” Support Ops Template

One-shot Markdown template to convert a batch of feedback into top issues, sentiment, root causes, quantification, quick wins and roadmap items with owner suggestions.

What You'll Get

A single one-shot Markdown prompt template that outputs a stakeholder-ready report tailored to support managers and ops leads.

Standardized sections: Executive summary, Top 5 issues (with quotes, counts, severity, root causes, confidence), Sentiment distribution, Assumptions, and Mapping table.

Actionable deliverables: up to 3 quick wins (owner, effort, benefit) and up to 3 roadmap initiatives (owner, timeline, success metrics).

Compliance-safe rules: PII redaction instructions and guardrails for legal/regulatory claims.

A checklist of additional data to collect for accurate triage and metrics (versions, timestamps, segments, logs).

Clear rules: ask clarifying questions if required inputs are missing; sample-first-200 rule if >200 items are supplied.

How to Use

1Paste the feedback items as a bullet list into the {{feedback_items}} slot and supply Audience, Document type, Desired tone, Owner roles, and any constraints.

2If the assistant asks one concise clarifying question, answer it before expecting the final report.

3Limit input to 200 items or accept sampling: if you supply >200 items the template samples the first 200 and notes the sampling method.

4Use the generated Markdown directly in stakeholder channels; edit owners/timelines to match org capacity before execution.

Maximize accuracy by including metadata

Include ticket IDs, timestamps, product versions, user segment and any available logs/screenshots. Redact any PII before pasting. If you expect >200 items, pre-filter by severity or sample intentionally and note the method.

Works Best With

Best used when you have a compact batch of customer feedback and clear role owners

Provide 10-200 feedback items (short bullets or ticket snippets) â€” include ticket IDs, timestamps, versions when available.

Specify the primary audience, document type, desired tone, and a concise list of owner roles to map actions to.

Use for weekly feedback digests, sprint planning, KB triage, and churn-risk briefings to stakeholders.

Prompt Template


## Goal
- Produce a stakeholder-ready summary from a batch of customer feedback: **top 5 issues**, **sentiment distribution**, **root causes**, **quantified frequency**, **recommended quick wins**, and **long-term roadmap items with owner suggestions**.

## Inputs
- Required: 
  - Context and customer feedback batch as a bullet list.
  - Primary audience for the output (for framing and level of detail).
  - Desired document type and tone.
  - A list of roles available to assign owners.
  - Any constraints (timebox, metric definitions, severity rules).
- If any required input is missing the assistant must ask concise clarifying question(s) before producing the report.

## Prompt
You are an expert Customer Feedback Analyst preparing a concise, operational report for stakeholders. Use the inputs below exactly as provided. If any required input is missing, ask one short clarifying question and wait for the answer.

Feedback items (paste each feedback item or ticket as a separate bullet line, include any IDs or timestamps if available):
{{feedback_items}}

Audience:
{{audience}}

Document type (e.g., "internal report", "product roadmap brief", "support exec summary"):
{{document_type}}

Desired tone (choose one): {{desired_tone}}

When recommending owners, prefer these roles (provide as a bullet list):
{{owner_roles}}

Task: Analyze the provided feedback and produce a Markdown report with the sections and formatting specified in the Output Format. Follow these rules while analyzing and writing:
- Extract and normalize themes; group feedback into thematic clusters and assign each cluster a short label (1-3 words).
- Provide the **Top 5 issues** by frequency and impact. For each issue include: short description, representative quote(s) (copy exact text from input, truncate to 200 chars), count and percentage of total items, estimated severity (High/Medium/Low) with a one-line justification, and a concise root cause hypothesis (1-2 sentences).
- Calculate **Sentiment distribution** (Positive / Neutral / Negative) with raw counts and percentages. Use simple sentiment heuristics based on explicit language; when uncertain, mark item as "Ambiguous".
- Provide a **Confidence** score for each theme (High/Medium/Low) and list any assumptions made in calculating counts or sentiments.
- Produce **Recommended quick wins** (3 maximum) with: action, expected benefit metric, approximate effort class (Low/Medium/High), and suggested owner role from {{owner_roles}}.
- Produce **Long-term roadmap items** (3 maximum) with: initiative title, desired outcome, success metrics, rough estimate of timeline (quarters) and suggested owner role from {{owner_roles}}.
- Add a short **Impact vs Effort** one-line mapping for each recommended item.
- Include a one-paragraph **Executive Summary** (2-3 sentences) tailored to {{audience}} in the {{desired_tone}} tone and the named {{document_type}} format.
- Include a **"Collect these details"** checklist of additional data to collect if needed (user segments, product versions, timestamps, support ticket IDs, reproducible steps, screenshots/log extracts).
- Provide a simple **mapping table** (Markdown table) that maps each original feedback item (use its line number or provided ID) to the assigned theme label.
- Ensure output is concise, uses bullets and tables, and is suitable for direct distribution to stakeholders.

Output only valid Markdown following the Output Format section below.

## Output Format
Support: Diagnosis questions â†’ Response draft â†’ Next steps

- Diagnosis questions
  - List any clarifying questions the analyst asked or would ask if inputs were incomplete.

- Response draft
  - Executive Summary (2-3 sentences)
  - Top 5 Issues (numbered). For each:
    - Issue label
    - Short description
    - Representative quote(s)
    - Count and % of total
    - Severity (High/Medium/Low) + 1-line justification
    - Root cause hypothesis (1-2 sentences)
    - Confidence (High/Medium/Low)
  - Sentiment distribution (counts + %)
  - Assumptions and data limitations (bulleted)
  - Mapping table: Original item ID/line â†’ Theme label

- Next steps
  - Recommended quick wins (bulleted, max 3) with owner role, effort, expected benefit
  - Long-term roadmap items (bulleted, max 3) with owner role, timeline, success metrics
  - Suggested follow-up actions for stakeholders (owners, timelines)
  - Collect these details checklist

Formatting requirements:
- Use bold for section headers and issue labels.
- Provide raw counts and percentages; do not invent absolute numbers beyond what's inferable from {{feedback_items}}. If you must estimate, mark estimates clearly.
- Keep the total report length under 800 words when possible; include expandable detail only in clearly labeled appendices if necessary.

## Guardrails
- Separate facts (pulled verbatim from input) vs assumptions (explicitly labeled). Do not present assumptions as facts.
- Do not invent ticket IDs, timestamps, or metrics. If input lacks data, state that and list required items to compute accurate frequencies.
- Do not expose PII. Redact or anonymize any personal data found in feedback; replace with [REDACTED].
- Provide sources: for every claim linking a theme to a count, point to the item line numbers or IDs.
- Avoid policy/legal claims without a cited source; flag those for stakeholder review.
- If sentiment is ambiguous, mark item "Ambiguous" rather than guessing.
- If more than 200 feedback items are pasted, summarize by sampling the first 200 and note the sampling method.

## Examples
- Mini decisions/actions excerpt

Decision: Prioritize "Checkout timeout" bug as highest near-term priority due to frequency and revenue impact.
Actions:
- Owner: Payments Lead (role from {{owner_roles}}) â€” Roll out fix in next sprint (Due: 2 weeks)
- Owner: Support Lead â€” Publish temporary retry guidance to users (Due: 3 business days)
Risks: Fix may require backend changes impacting other flows â€” list affected subsystems.
Open questions: Which product versions show the highest rate of errors? (collect via "Collect these details" checklist)

Variables

Usage Notes

Not for

â€¢ Making legal, clinical, or regulated-compliance decisions without review from appropriate counsel.

â€¢ Automated bulk analytics across very large datasets (>10k items) â€” use analytics tooling and then feed summarized results.

â€¢ Replacing human judgment for complex escalations; this template is for synthesis and recommended actions, not final approvals.

Do not include

â€¢ Raw PII (emails, full names, phone numbers) â€” redact or replace with [REDACTED].

â€¢ Proprietary credentials, API keys, or unredacted logs with secrets.

â€¢ Claims of precise revenue impact or SLA metrics if not supplied in inputs â€” the template will request those instead.

Customer Feedback Themes â€” Support Ops Template

Turn a pasted list of customer feedback items into a stakeholder-ready Markdown report: Top 5 issues, sentiment distribution, root cause hypotheses, counts, recommended quick wins, and 3 long-term roadmap items with suggested owners.

Turn this into a working asset in minutes.

Import into Workspace to auto-fill variables, adapt output style, and iterate with OctiAI's prompt editor.

Auto-fill & personalize from your inputs

AI-assisted edits: tone, structure, constraints

Attach context so outputs stay consistent

Iterate and save versions

What you'll get

Output format

Markdown

Best used when

When working on template or detailed.

Avoid when

Making legal, clinical, or regulated-compliance decisions without review from appropriate counsel.

Made for

What to fill in

Use the guidance below to complete each placeholder with the right level of detail.

Feedback Items