# Turn customer feedback into useful bug reports

Designed for: Small software teams sorting complaints and feature requests

Result: Draft issues that separate reported symptoms, reproduction evidence and feature requests.

## Try a sample first

Illustrative example, not a recorded Bot run. This adaptation has not been runtime-tested.

### Complete first request

Group the supplied customer feedback, preserve source references, and draft issues. Distinguish reports from reproduced failures and new features. Remove private details and ask before posting Use only the records I supply. Label missing or uncertain information. Do not connect accounts, browse, send, submit, publish, spend money or create a schedule. Return a draft for my review.

Fictional feedback. F1: 'Export fails after I choose CSV on my phone.' F2: 'Please add XLSX export.' F3: 'CSV download is blank on mobile.' No device, browser, logs or reproduction steps are supplied.

### Example result

Possible related bug reports: F1 and F3, mobile CSV export; relationship unconfirmed and not reproduced. Request browser, device and steps. Separate feature request: XLSX export (F2). Prepare two drafts; do not open issues or claim a fix.

### Check the answer

- Keep a requested feature separate from a suspected bug.
- Do not call the failure reproduced.
- Do not post issues or change code.

Inspired by a community use shared by @emanueledpt: https://x.com/emanueledpt/status/2108896139344838986
Found through Bot Usecases (https://botusecases.netlify.app/), curated by KP. This fictional sample was written by Bot Cabinet.

## Operating guide

- **When to use it:** Use this workflow when you need draft issues that separate reported symptoms, reproduction evidence and feature requests.
- **Lead Bot:** Coder
- **Cadence:** When a new request arrives and a person assigns it
- **Typical first run:** 15–30 minutes for a first manual run

### Access for the first run

- The approved inputs listed on this page
- Only the files, sources, and services required for this run
- No sending, publishing, spending, or live-system changes without approval

## Recommended starting Bot

1. Coder

Use Coder with the task below. This is a workflow for an existing role, not a separate installed Bot.

## Information to gather

- Start with the fictional records below
- For your own task, choose only the records you want the Bot to use
- Remove private details you do not need for the task

## Workflow

### 1. Coder

Group the supplied customer feedback, preserve source references, and draft issues. Distinguish reports from reproduced failures and new features. Remove private details and ask before posting

Output: Draft issues that separate reported symptoms, reproduction evidence and feature requests.

Message to send:

Use the approved inputs I provide. Group the supplied customer feedback, preserve source references, and draft issues. Distinguish reports from reproduced failures and new features. Remove private details and ask before posting. Return this result: Draft issues that separate reported symptoms, reproduction evidence and feature requests.. Ask me about missing information before you continue.

## Overall request

Group the supplied customer feedback, preserve source references, and draft issues. Distinguish reports from reproduced failures and new features. Remove private details and ask before posting Use only the records I supply. Label missing or uncertain information. Do not connect accounts, browse, send, submit, publish, spend money or create a schedule. Return a draft for my review.

## Decisions for a person

- Check the result against the supplied records
- Approve any account connection, schedule or outside action separately
- Review anything before it is sent, submitted, purchased or published

## First test

Keep a requested feature separate from a suspected bug. Do not call the failure reproduced. Do not post issues or change code.

## Success checkpoint

Check the result against your original material. You make the decisions listed below. Keep a requested feature separate from a suspected bug. Do not call the failure reproduced. Do not post issues or change code.

## If the workflow stalls

If the result is incomplete, mark the missing information and ask the same Bot to correct it. Add another Bot only when a genuinely separate role or independent check would help.

## Hermes Desktop setup

1. Open the linked Bot's page, download its .tar.gz profile, and import it from the Profiles screen in Hermes Desktop.
2. Review the profile's SOUL.md, Bot Passport, and requested access.
3. Run the complete request in that Bot's chat with low-risk material and review the result.
4. Add a schedule, outside connection, or optional specialist only after the manual version works.