Set up a simple log to track customer feedback and bug reports
A ready-to-use spreadsheet structure, tagging scheme, and weekly review routine for teams without a ticketing system.
The prompt
Help me set up a log to track customer feedback, complaints, and bug reports that arrive by email or chat.
What we receive: [e.g. bug reports, feature requests, complaints, praise]
Channels: [support inbox, chat, social, sales calls]
Volume: [roughly per week]
Who logs and who reviews: [ROLES]
Tool: [e.g. Google Sheets, Excel, Airtable, Notion]
What we want to learn from it: [e.g. top product issues, churn reasons, release priorities]
Design:
1. Columns - with a short definition and allowed values for each: ID, date received, channel, customer or account (or anonymized ID), product/area, type, short summary, customer's own words (quote), severity, frequency/how many customers, status, owner, linked ticket or bug ID, date resolved, follow-up sent (Y/N).
2. Tagging scheme - a short, fixed list of types and product areas so entries can be counted; rules for when to add a new tag.
3. Severity guide - clear definitions with examples so different people rate the same way.
4. Logging rules - what counts as a duplicate, how to merge, and how quickly to log.
5. Weekly review routine - a 20-minute agenda, the summary to produce (top themes, new issues, trends), and how items reach the product or engineering team.
6. Closing the loop - when and how to tell customers their feedback led to a change.
7. Privacy - store only the customer data needed, restrict access, and set a retention period.
Return the column list as a table I can paste into my tool, plus example rows.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Customer Support prompts
What to fill in
- e.g. bug reports, feature requests, complaints, praise
- support inbox, chat, social, sales calls
- roughly per week
- ROLES
- e.g. Google Sheets, Excel, Airtable, Notion
- e.g. top product issues, churn reasons, release priorities
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Handle a warranty callback and decide what is coveredA fair way to assess a customer's warranty claim, decide responsibility, and reply clearly, whether the fix is covered or not.
- Explain a financial aid offer to a student and familyBreaks down a college aid offer into net cost, grants vs. loans, and next steps, with a clear reply to the family.
- Respond to a negative online review without breaching client confidentialityA short public reply to a bad Google or Avvo review that protects client confidences, plus guidance on whether to reply at all.
- Find out where my customer service chatbot fails and fix itAn analysis of your chatbot's conversations and metrics, with the gaps, root causes, and prioritized fixes to resolve more questions.