Your first request
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.
Back to workflows
One-Bot workflow
Turn customer feedback into useful bug reports
Draft issues that separate reported symptoms, reproduction evidence and feature requests.
Designed for: Small software teams sorting complaints and feature requests
Try a sample first
See what a useful result looks like
Illustrative example, not a recorded Bot run. This sample was written to explain the task; your Bot's answer needs checking.
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.
Choose where to try it
Already have an assistant? Copy the sample task into its chat. For a continuing role, review Coder's instructions and limits first.
These are setup guides, not automatic imports. Available tools and account access differ by app.Inspired by a use shared by @emanueledpt , found through Bot Usecases, curated by KP. The sample above is Bot Cabinet's own fictional example.
Community report; this adaptation has not been runtime-tested.
Full workflow and setup details
Before you begin
Gather the information the Bot needs
- 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
Run the first version one step at a time
Give one Bot the complete job
Use one Bot for the first run. Add a specialist only when the job becomes complicated enough to need a separate role, different access, or independent review.
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
Produces: Draft issues that separate reported symptoms, reproduction evidence and feature requests.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.
Use this as the complete first-run request.
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
Try the workflow with low-risk material
Keep a requested feature separate from a suspected bug. Do not call the failure reproduced. Do not post issues or change code.
Check the result
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.
Set it up in Hermes Desktop
Begin with one Bot and one manual run
- Open the linked starter page, download its .tar.gz profile, and import it from the Profiles screen in Hermes Desktop.
- Review the profile’s SOUL.md, Bot Passport, and requested access.
- Run the complete request in that Bot’s chat with low-risk material and review the result.
- Add a schedule, outside connection, or optional specialist only after the manual version works.