When should you use it?
- You suspect you pay for things you forgot
- Receipts land in your email
- A vendor's first answer was no
Not for: Charges you genuinely used; Sending disputes without reading them
What do you need, and what do you get?
You need
- Your inbox's purchase confirmations going back a year
- Approval for anything sent
You get
- List of recurring charges with last use
- Drafted refund request and follow-up
How does it work, step by step?
- Scan receiptsHave it list recurring charges over twelve months.
- Choose onePick the charge you can show you did not use.
- Review the draftRead the refund request before anything is sent.
- Answer the refusalIf the vendor says no, have it draft a polite, specific follow-up.
- Close it outCancel the unused service so it does not recur.
The prompt
Our own prompt, inspired by Sid Saladi and written to work in Custom agent, Grok Bot and Claude. Values in lime are placeholders.
Review a year of receipts in my inbox and show each repeating bill with vendor, amount, frequency and when I last appear to have used it. For the charge I choose, draft a refund request explaining the service was unused, with dates. Let me read it first; send nothing yet. If they decline, draft a follow-up and show me again.
Inspired by Sid Saladi: Meta Muse Use Cases: 50 Real Ways to Use Meta's Personal Agent (September 2026 Edition). The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- A refund is a request, not a guarantee; keep the tone factual.
- Cancel the underlying resource, or the charge returns next month.
Our take
Good starting errand for any assistant with mail access: limited in scope, undoable, and focused on recovering money. Persistence matters, since the refusal was answered with more evidence. Sid's example works because the scope is narrow: read a year of receipts, list recurring charges, and pick one you can show you never used. Read the refund request before anything is sent, and keep the tone factual; a refund is a request, not a guarantee. When the vendor said no, the useful move was a polite, specific follow-up with more evidence rather than giving up or getting angry. Close it out by canceling the unused service itself, or the charge comes back next month. Check the next bill to confirm it stopped. Give the assistant read access to receipts only, and keep sending under your control. Charges you did use are not candidates for a dispute, and shared team accounts need agreement from their owners first.
Where the time goes back: Tracing a mystery charge and arguing it is the job nobody gets around to; this does the legwork.
FAQ
Did the first request work?
Does it send on its own?
Source and credit
Inspired by Sid Saladi. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Meta Muse Use Cases: 50 Real Ways to Use Meta's Personal Agent (September 2026 Edition)
- Creator
- Sid Saladi
- Published on
- sidsaladi.substack.com (Substack)
- Original date
- Sep 21, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.