Its job
Keeps receipts, correspondence, deadlines, and next steps together while you resolve a refund, return, or warranty issue.
Back to The Cabinet
The Cabinet · Bot starter
The Cabinet · Bot starterPlanning and client work
Receipt
Returns and warranty case assistant
Keeps receipts, correspondence, deadlines, and next steps together while you resolve a refund, return, or warranty issue.
Best for: People tired of reconstructing a consumer issue every time they contact a company.
Hermes archive import checked; a full task run is still pending. Read the test status
Choose where to use it
Use Receipt on your platform
Choose your app for setup instructions and test results.
Hermes AgentArchive import passed
Import the profile, review its files, choose the access it needs, and run the first assignment. The archive imported successfully and its Skill was present in an isolated Hermes Agent 0.21.1 installation. Its task results have not been tested.
Keep track of your first Hermes run
Your Bot workbench
Pack 2.0.0Continue after the download
Task checks: 0 of 2. Setup: 0 of 3. Check only steps you completed. After running a task, review its result and tell us whether it helped. These are your confirmations, not independent Cabinet verification. Progress stays in this browser.
ChatGPT Workspace AgentSetup guide · test pending
Build the same job as a Workspace Agent, add its Agent Skill, then choose the files, apps, approvals and sharing rules it needs. This setup has not yet been installed or task-tested for Receipt.
ClaudeSetup guide · test pending
Use a Cowork plugin or Skill for a general work role. Use Claude Code only when the job involves code or a local project. This setup has not yet been installed or task-tested for Receipt.
Grok BotPrepared · test pending
Copy the job into a Grok Bot profile, try one task, and review the result before adding a Skill or Routine. This Bot has not been tested in Grok.
Download files for another app
Portable Bot Pack
Download the instructions, Bot Passport and setup notes as Markdown or JSON. The Agent Skill is a SKILL.md file. Check your app’s requirements and test it there; results can differ between apps.
Review the instructions and permissions, then run a test in your chosen app before relying on the result.
First task
Try one small job
Supply a fictional receipt for $80, an email promising a refund within ten business days, and no payment confirmation. Ask for a status summary and follow-up. It should distinguish promised from received, request the promise date if missing, draft a factual message, and leave the case open.
BringReceipts, order confirmation, and the applicable policy
Look forA case timeline with receipts and source references
Read the job, safety rules, files, and test record
Example
Keep the case together
Illustrative case note: An $80 refund was promised, but receipt is unconfirmed. The email does not show a date, so the ten-business-day deadline cannot yet be calculated. Next action: obtain the dated email and check the payment record before sending the drafted follow-up.
This fictional example shows the intended result; it is not a recorded Bot run.
Job and limits
What this Bot is responsible for
Outside its job
- Draft communications for review; ask before sending, filing a claim, canceling, or sharing personal information.
- Do not invent eligibility, policies, deadlines, purchases, or company promises.
- A promised refund is not a received refund. Confirm receipt before closing the case.
Information it relies on
- Receipts, order confirmation, and the applicable policy
- Correspondence, case numbers, and promised dates
- The outcome you want and any prior action taken
Ask you before
- Draft communications for review; ask before sending, filing a claim, canceling, or sharing personal information.
- Do not invent eligibility, policies, deadlines, purchases, or company promises.
- A promised refund is not a received refund. Confirm receipt before closing the case.
When it runs
Run when I provide new records or ask for a review. Agree a recurring schedule only after a successful first test.
What it produces
- A case timeline with receipts and source references
- A list of documented deadlines, promised actions, and missing information
- A ready-to-review follow-up message and a record of the outcome
Bot Pack 2.0
Put Receipt to work
Get the setup files, try the first task, and check the result. The pack also includes a reusable Skill and a plan for a Routine.
First assignment
Supply a fictional receipt for $80, an email promising a refund within ten business days, and no payment confirmation. Ask for a status summary and follow-up. It should distinguish promised from received, request the promise date if missing, draft a factual message, and leave the case open.
Check the result
Pause for a person to review these deliverables: A case timeline with receipts and source references; A list of documented deadlines, promised actions, and missing information; A ready-to-review follow-up message and a record of the outcome. Wait for approval before the Bot sends, publishes, schedules, purchases, deletes, deploys, or changes an outside account.
Prepared · test pending
Reusable Skill
Receipt core Skill
Run when I provide new records or ask for a review. Agree a recurring schedule only after a successful first test.
Produces- A case timeline with receipts and source references
- A list of documented deadlines, promised actions, and missing information
- A ready-to-review follow-up message and a record of the outcome
Manual test required
Planned Routine
Receipt primary Routine
Run when I provide new records or ask for a review. Agree a recurring schedule only after a successful first test.
Before schedulingStop, preserve the completed work, and report the failure before trying again or changing access.
The Skill and Routine have not been task-tested. Try them with sample material and approve the results before adding a schedule or outside access.
Try asking
- Organize these receipts and emails into a timeline for my missing refund.
- Compare the seller's return policy with my purchase record and tell me what information is missing.
- Draft a follow-up using the case number and commitments from our last conversation.
What it should produce
- A case timeline with receipts and source references
- A list of documented deadlines, promised actions, and missing information
- A ready-to-review follow-up message and a record of the outcome
What you provide
- Receipts, order confirmation, and the applicable policy
- Correspondence, case numbers, and promised dates
- The outcome you want and any prior action taken
Decisions you make
- Draft communications for review; ask before sending, filing a claim, canceling, or sharing personal information.
- Do not invent eligibility, policies, deadlines, purchases, or company promises.
- A promised refund is not a received refund. Confirm receipt before closing the case.
Bot Passport · version 2
Access and approval record
Review this record before setup. Update it whenever the Bot's job, tools, accounts, schedule, or authority changes.
- Receipts, order confirmation, and the applicable policy
- Correspondence, case numbers, and promised dates
- The outcome you want and any prior action taken
- A case timeline with receipts and source references
- A list of documented deadlines, promised actions, and missing information
- A ready-to-review follow-up message and a record of the outcome
- Analyze material supplied in its conversation
- Draft the listed deliverables for a person to review
- Identify missing information and ask questions
- Ask before sending, filing a claim, canceling, or sharing personal information
- Inventing eligibility, policies, deadlines, purchases, or company promises
Tools and access requested
Start with supplied files and conversation exports. Optional read-only access to specifically approved folders or services.
How to stop it
Disable its schedule, remove outside-service connections, and revoke or rotate any dedicated credentials.
What these rules can and cannot prevent
- Draft communications for review
- A promised refund is not a received refund. Confirm receipt before closing the case.
- Draft communications for review; ask before sending, filing a claim, canceling, or sharing personal information.
Set it up in Hermes Desktop
Import the profile and run one small test
The Hermes download contains its manifests, role instructions, Bot Passport, setup guide, license, and included Skills. The ZIP contains the same files for inspection.
- 1Download the Hermes profile.
Import the .tar.gz archive from the Profiles screen, or copy the terminal command above.
- 2Review the imported profile.
Read README.md and SOUL.md, then confirm the name, description, and standing instructions.
- 3Choose the access it needs.
Add only the skills, tools, and connections required for this job.
- 4Run the named first test.
Supply a fictional receipt for $80, an email promising a refund within ten business days, and no payment confirmation. Ask for a status summary and follow-up. It should distinguish promised from received, request the promise date if missing, draft a factual message, and leave the case open.
- 5Keep proof.
Save the exact input, the finished output, the Bot and Hermes versions, the date, and any correction you had to make.
- 6Test one failure.
Remove a required input or deny an optional connection. The Bot should stop or explain what is missing instead of inventing an answer or taking a different action.
- 7Repeat before automating.
Run the same job successfully again after any change to its instructions, tools, source material, or schedule.
Useful combinations
Pair Receipt with another role
Current review status: Automated package tests check that each ZIP and Hermes profile archive contains the same declared files. This archive imported successfully and its Skill was present in an isolated Hermes Agent 0.21.1 installation on September 9, 2026. Two published first-task runs passed the listed checks. A person has not yet completed the technical review. The Grok Bot build brief remains untested.