Illustrative example, not a recorded Bot run. This sample was written to explain the task; your Bot's answer needs checking.
Your first request
Fictional records. R1: Alder desk lamp, $80, purchased September 1, 2026. W1: one-year warranty for manufacturing defects; proof of purchase required. N1: lamp stopped working October 10; cause unknown. No serial number or inspection is supplied.
Example result
The receipt records the purchase within W1's stated one-year period, but the cause is unknown, so coverage is not established. Draft: 'Please review this warranty request for my Alder desk lamp. It stopped working October 10. I can provide R1. Please confirm the claim steps and any serial number or inspection you need.' Not submitted.
Check the answer
Distinguish the warranty period from proof of coverage.
Request missing details without inventing a defect.
Do not submit a claim or arrange a return.
Choose where to try it
Already have an assistant? Copy the sample task into its chat. For a continuing role, review Receipt's instructions and limits first.
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
Operating guide
Know when to run it and who leads
Lead Bot
Receipt
Typical first run
15–30 minutes for a first manual run
When to run it
When a person supplies the approved brief and starts the workflow
Use this workflow when you need a claim draft with the purchase details, supporting records and missing information clearly marked.
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
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.
1
Receipt
Organize the purchase record and supplied warranty terms, identify missing claim details, and draft a factual warranty request. Do not promise eligibility or a refund
Produces: A claim draft with the purchase details, supporting records and missing information clearly marked.
Use the approved inputs I provide. Organize the purchase record and supplied warranty terms, identify missing claim details, and draft a factual warranty request. Do not promise eligibility or a refund. Return this result: A claim draft with the purchase details, supporting records and missing information clearly marked.. Ask me about missing information before you continue.
Overall request
Organize the purchase record and supplied warranty terms, identify missing claim details, and draft a factual warranty request. Do not promise eligibility or a refund 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
Distinguish the warranty period from proof of coverage. Request missing details without inventing a defect. Do not submit a claim or arrange a return.
Check the result
Check the result against your original material. You make the decisions listed below. Distinguish the warranty period from proof of coverage. Request missing details without inventing a defect. Do not submit a claim or arrange a return.
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.