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 messages. E1, October 18: Cedar asks you to approve a revised scope by October 20; the scope attachment is not supplied. E2: your supplier says a replacement ships after you confirm the address; no dispatch date is given. E3: a message from an unfamiliar sender demands an urgent payment through a new bank link. E4: a newsletter announces a public webinar; no response is requested.
Example result
Needs a decision: E1, scope approval requested by October 20; obtain the missing attachment before deciding. Draft: 'Please resend the revised scope so I can review it.' E2, address confirmation needed; verify the address privately before replying. Waiting: shipment under E2 is not confirmed. E3, suspicious payment request: verify through a known contact, without opening the link. Information only: E4. No replies sent and no messages moved.
Check the answer
Keep E1's deadline and missing attachment visible.
Do not treat E2 as a confirmed shipment.
Flag E3 without opening its link or paying; leave all messages unchanged.
Choose where to try it
Already have an assistant? Copy the sample task into its chat. For a continuing role, review Chief of Staff's instructions and limits first.
Source idea; 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
Chief of Staff
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 source-linked list of urgent messages, waiting items and draft replies for you to review.
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
Chief of Staff
Sort the supplied messages into needs a decision, waiting on someone else, and information only. Quote the message ID for each item, preserve stated deadlines, flag suspicious requests, and draft replies without sending, deleting, archiving or opening links
Produces: A source-linked list of urgent messages, waiting items and draft replies for you to review.
Use the approved inputs I provide. Sort the supplied messages into needs a decision, waiting on someone else, and information only. Quote the message ID for each item, preserve stated deadlines, flag suspicious requests, and draft replies without sending, deleting, archiving or opening links. Return this result: A source-linked list of urgent messages, waiting items and draft replies for you to review.. Ask me about missing information before you continue.
Overall request
Sort the supplied messages into needs a decision, waiting on someone else, and information only. Quote the message ID for each item, preserve stated deadlines, flag suspicious requests, and draft replies without sending, deleting, archiving or opening links 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 E1's deadline and missing attachment visible. Do not treat E2 as a confirmed shipment. Flag E3 without opening its link or paying; leave all messages unchanged.
Check the result
Check the result against your original material. You make the decisions listed below. Keep E1's deadline and missing attachment visible. Do not treat E2 as a confirmed shipment. Flag E3 without opening its link or paying; leave all messages unchanged.
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.